Good morning.
After updating from 24.7.9 to 24.7.10_2 (and pulling latest kernel) the LAN interface that had two vlans attached was unreachable.
At first, I thought something had failed with the interface itself, so swapped the LAN assignment to a different interface.
However, today, when the VLAN's were reassigned to the new parent interface, it too became unreachable.
Reverting to 24.7.9 (with 24.7.8 kernel, because 24.7.9 kernel was not available to download?) and restoring a backup has gotten us operational again.
Can this problem be duplicated elsewhere? Is this a kernel bug?
Gerald Martin
Similar Problem?
https://forum.opnsense.org/index.php?topic=44531.0
Sure looks like it. When the interface goes into a broken state, it won't respond to a ping, even from the opnsense shell
@franco can you confirm if this is a known bug - if so what the resolution plan is? Thank you.
Does anyone know if the underlying issue here has been identified and fixed in 24.7.11?
What are we looking at? An Intel driver regression from 24.7.8 to 24.7.10? Has anyone tried the older kernel?
# opnsense-update -kr 24.7.8
(reboot)
Cheers,
Franco
Hey Franco, thanks for taking interest in this.
Yes, as stated in my original post, we had to revert to the 24.7.8 kernel to get operational.
This user appeared to have the same issue:
https://forum.opnsense.org/index.php?topic=44531.0
Running a Supermicro server chassis with Intel gigabit hardware.
Gerald
@franco just curious if this issue has been identified and fixed in the latest kernel?
Can anyone tell me if this bug has been resolved? I'd be ready to update to current if it is....
Thanks to anyone who can help.
GM
There isn't a known "bug" . Like I wrote a couple of times on that thread i.e. https://forum.opnsense.org/index.php?msg=226441 , it is likely a configuration problem.
If you want to get assistance trying to pinpoint it, show your configuration please.
A reminder by way of quoting from that thread, it applies here relating to mixing tagged and untagged traffic:
TLD: mixed traffic works until it doesn't, due to as meyergru says a variety of reasons. Usually hardware and configuration & the combination. Hence it is not advised to be done. {snip}
Quote from: gerald_martin on April 10, 2025, 01:17:20 AMCan anyone tell me if this bug has been resolved? I'd be ready to update to current if it is....
Thanks to anyone who can help.
GM
Fastest way is to take a snapshot and upgrade to 25.1.5.
Follow up here. I took the advice to save a snapshot of a working config, then updated. The update from 24.7.9 to 24.7.12 broke the untagged traffic to the interface. The update from 24.7.12 to 25.1 resolved the problem. 25.1 > current = appears to be working fine.