Quote from: derek@stayawake.io on Today at 07:28:53 PMIf the cat could manage it, I'd be shocked, not having opposable thumbs an all."Cat Admin" is a real thing... Wouldn't be the first time... LOL! ^_^
Quote from: trippmcnealy on Today at 10:13:41 PMAfter updating to 26.7 I am unable to edit any rule that already exists. While a column does exist to show if the rule enabled or disabled, nothing exists in the column. If I create a new rule then there is information in the column, and I can enable/disable.
Quote from: tuto2 on Today at 11:50:59 AMA kernel patch related to your issue has been developed, assuming you're on 26.1.11_6, you can install it with:Sure, I'll install that now. What's the change(s) in this one?
# opnsense-update -zkr 26.1.11-igc
Quote from: nero355 on Today at 01:54:15 PMMay I suggest not involving this game into these issues ?Yeah, I know the game is buggy as hell. If it was the only issue I was having I wouldn't be here. But it's a useful canary; as I usually check into the game fairly early, it's often my first indication that something's going wrong. And the fact that bouncing the LAN interface on the firewall makes it immediately start working again (and the fact that I never had these issues before switching to the new firewall) leads me to believe this particular issue isn't the game's fault.
Quote from: BrandyWine on Today at 07:43:41 PMNo indicators if your issue is WAN or LAN side.I haven't dug too much into the WAN side because only bouncing the LAN interface has any effect. I've tried bouncing WAN first on a few occasions and it never changes anything.
QuoteDHCP stops working, so just for the LAN side?Yes, the firewall's DHCP client works just fine, it's the LAN-side clients on one or more VLANs that stop working.
QuoteVLANs? How do you mean? Two i226's and VLAN's on LAN side, so you run .1q or your VLAN's are L3 ?Yes, 802.1q VLANs on the LAN side only.
QuoteCan you SSH into the FW using a non i226 iface? I suggest you do that and start monitoring stuff. Run a ping to the FW LAN IP address, then wait for the no-traffic issue to arise, what does the ping show?The firewall has just the two i226-Vs. I could set it up to run in the background like the previous one, though. FreeBSD's dmesg doesn't appear to have a follow option, but neither dmesg nor the syslog have never shown any indication that they see anything wrong anyway.
Start a 2nd ssh session, then
dmesg -w | grep -E 'igc'
see if any kernel messages arrive when your issue happens.
Quote from: zz00mm on Today at 10:08:43 PMroot@fw254:~ # /usr/local/etc/rc.syshook.d/early/40-cpu-microcode
/usr/local/etc/rc.syshook.d/early/40-cpu-microcode: /usr/local/etc/rc.d/microcode_update: not found
pkg install cpu-microcode-rc