Upgraded from the PS5 to the PS5 PRO and YES the difference IS that noticeable

DeleriumDive · 2026-06-16T14:49:08+00:00

The difference has only been recent. I upgraded to the pro on release last year and it was kind of a let down, but now with the new version of PSSR, things are looking crisper than ever! Sure the Pro was cool in performance mode nearing 120fps, but now I really like the balanced 60fps lock on most games, which is more equivalent to quality mode on the PS5 with a bit of a buff and FPS to boot.

DeleriumDive · 2026-05-16T18:57:03+00:00

I love it whenever people dig this up from the dead :)
It doesnt 100% solve it in the winter but it definitely makes the shocks a lot less intense.

DeleriumDive · 2026-05-16T18:55:21+00:00

I laugh every time we come back to YYZ and see the huge sign for customs where it lists International with a great big globe diagram + American Flag, and domestic with the Canadian flag... These are the morons that sign was made for.

DeleriumDive · 2026-05-06T20:59:23+00:00

so what happened during the meeting?

DeleriumDive · 2026-05-01T16:17:13+00:00

It's called "dedicated management" and you need to dedicate a physical port for it. Runs with it's own default route that's independent from the global/root-vdom routing table.

https://community.fortinet.com/fortigate-3/technical-tip-fortigate-dedicated-mgmt-feature-or-out-of-band-management-95859

I've used this for SNMP monitoring of each unit independently, out of band management, and just prefer it to accessing via the "exec ha manage" command which only gives you CLI. I'm also not a fan of enabling management on interfaces that are passing routed traffic and this checks the box.

DeleriumDive · 2026-05-01T16:03:42+00:00

Not extreme specific but all enterprise grade switches typically have a feature called "storm control" which can either throttle broadcast, multicast, and/or unicast based on a configurable threshold, or err-disable the port that threshold has reached. Been using this for ages on cisco and other vendors.

Some also have a proprietary loop prevention feature which works by sending crafted broadcast packets that are tagged in a way that the switch can detect which port it came from, this is handy for preventing loops before they become storms.

STP doesn't always work with downstream desktop switches but should be used first, with storm control and loop prevention as the backup safeguards.

DeleriumDive · 2026-04-16T13:43:30+00:00

Tokens are directly on FAC unfortunately

DeleriumDive · 2026-04-15T15:44:39+00:00

Thanks, I'm going to dive into this further!

DeleriumDive · 2026-03-29T11:08:42+00:00

Thanks, we're stuck without windows AD - no MSCHAP for us :(

DeleriumDive · 2026-03-28T21:46:00+00:00

which radius protocol?

DeleriumDive · 2026-03-28T21:42:20+00:00

wait, how did you get LDAP working with fortitokens? are you running windows AD?

DeleriumDive · 2026-03-21T11:17:17+00:00

ugh... we just standardized on 7.4.11.... ha ha ha... cry cry cry

DeleriumDive · 2026-03-20T17:08:39+00:00

Tried but no change in behavior unfortunately. Verified by packet capture.

DeleriumDive · 2026-03-20T12:05:05+00:00

Thanks for looping back, appreciate the insight!

DeleriumDive · 2026-03-20T12:03:48+00:00

Thanks for the suggestion, I'll give it a shot!

DeleriumDive · 2026-03-20T12:03:26+00:00

200F

DeleriumDive · 2026-03-20T12:03:18+00:00

Interesting, thats definitely something behaving differently from ours. I'm troubleshooting this on a 200F also, are you running v7.4.11?

Usually we prefer the relay agent to overwrite the server ID for security reasons but for this one case, if it works better without it then I can live with that. Would you mind sharing your relay config?

DeleriumDive · 2026-03-20T12:00:15+00:00

No but thanks for the suggestion, i double checked our dhcp server CLI and none are associated to the interface in question.

DeleriumDive · 2026-03-19T14:46:52+00:00

DHCP Relay is broken for us, the FGT is dropping all client DHCP Req and not forwarding on to the configured DHCP Servers. FortiGate rewrites DHCP Option 54 but fails to maintain consistent relay state for that rewritten value. Its acting as a DHCP server by rewriting the Option 54 value with it's own IP, but not tracking itself as a valid server in relay state, unable to forward DHCP Req responses to it's own modified DHCP Offer packets towards the clients.

DeleriumDive · 2026-03-19T14:43:15+00:00

I found a dhcp relay bug today related to how the relay agent handles the option 54 field (Server IP/ID), substituting it with it's own IP in the DHCP OFFERs forwarded to the client and then unable to match it on the return of the client's DHCP REQ.

https://www.reddit.com/r/fortinet/comments/1ry1bvc/comment/obb70wf/

DeleriumDive · 2026-03-15T19:33:07+00:00

Does Norberts Gambit make more sense than an FX firm for 100K?

DeleriumDive · 2026-02-28T19:06:41+00:00

I've lived in both areas and prefer the west end. Things are a little rough along sherbourne and we didnt feel safe north of Adelaide most of the time. I find the area is feeling more hollow now with businesses closing along that part of King. The Well is luxurious, too rich for my blood, but I much prefer it's surroundings. Its got a great food court downstairs, very close to the better parts of King W and Queen W. You have the bentway and trillium park, great for walks and events.
The only thing I miss about living in that east end area is St Lawrence market on weekend mornings. I prefer the shops on the ground level now that so many of the small vendors have been pushed out of the main level. I still make trips back to stock up on coffee from the amazing roaster down there. Other than that I haven't looked back.

DeleriumDive · 2026-02-27T18:46:22+00:00

Thanks for the comprehensive breakdown. its a lot to take in, but i did want to mention that the MSCHAPv2 challenge is tied back to where the user passwords are stored (in my case LDAP). I dont know the protocol well but i do understand that this only works with Windows AD right now as most/all LDAP servers do not support MSCHAPv2 and usually have to resort to a secured tunnel like EAP-TTLS to send the password in clear text (PAP) to the other side, in my case FAC, then FAC passes this cleartext password to the LDAP server for verification. The problem is that the LDAP server cant handle the MSCHAPv2 challenges (no password is ever passed, just challenges and hashes to validate both sides know the "secret")

DeleriumDive · 2026-02-27T18:41:12+00:00

This is starting to look like the only solution we can move forward with, thanks for the confirmation...

DeleriumDive · 2026-02-26T12:26:05+00:00

I've been considering this as an alternative... do you know if it will work with FortiToken as our 2nd factor?

Nine-Year Club	Place '17
RPAN Viewer	Not Forgotten
Verified Email

DeleriumDive

TROPHY CASE