@viktor_g Thanks for your help.

Update: I noticed that many of the logs were not updating and there were 8 zombie processes shortly after a fresh reboot. Decided to nuke the logs and reboot: find /var/log -type f -exec rm -f {} ; && reboot Gateways came back up after the reboot, then went back down. WTH? Also still a very odd lag on UI when saving changes.

@stephenw10 Thank you. It was hardware. Replaced SSD resolved it.

@lecygne After all these years pfsense developers are still not convinced that "taking master role too early" is an issue in some cases!

@bingo600 said in Firewall logs - showing other: Re ISP - The Gateway monitor is prob pinging the isp def-gw. how can I confirm this ? please note I am still learning and my knowledge is very limited at the moment

https://forum.netgate.com/topic/137938/shaw-300-issue-with-arris-xb6-modem-severe-intermittent-wan-slowdowns/9?_=1614764271055 Sounds similar to issue I had couple years ago with Shaw cable. Not sure if it was modem or moca filter that resolved as both were done at same time.

@viktor_g A completely clean install on version 2.5.0-RELEASE

@zacaustin I have a Sony Bravia and a sg3100, it’s on my guest vlan It works perfectly hardwired.. I have a Ubnt nano mounted directly above it which also works fine.. It works on just the out of box dns resolver for me and also by setting it up with next dns google blocking... where it’s pushed dns servers by pfsense and it blocks google services

@gertjan I mis-typed. I running 2.5.0 on top of freebsd 12.2. https://docs.netgate.com/pfsense/en/latest/releases/2-5-0.html

@lucsuryo Could you create a bugreport https://docs.netgate.com/pfsense/en/latest/development/bug-reports.html

@jknott I already migrated the "source" machine to v2.5.0 and found a cert corruption issue + dns issue. I had to redo the whole config on the new machine. However, it offered me the opportunity to "clean up" the whole config ;-) I want to keep the old machine as a spare one eventually (even if not kept up to date) , so I'm looking for a 2.5.0 -> 2.5.0 transfer procedure.

Update... I upgraded pfSense and Suricata to: pfSense 2.5.0-RELEASE (amd64) FreeBSD 12.2-STABLE Suricata 6.0.0_9 Interestingly, I'm still receiving the entries in the system logs as my initial post, however, not to the degree that I was receiving them when I first posted the issue. I find that this is only occurring on my wireless LAN segment where a lot of streaming is occurring; Hulu, YouTube, etc. I had hoped that the pfSense and Suricata updates would have resolved the issue. Hmmm.