OPNsense 25.7.10 Ethernet detach problem

Started by burns1230, January 23, 2026, 07:58:49 AM

Previous topic - Next topic
Hi everyone!
I recently upgraded from 25.1 to 25.7.
The current version is 25.7.10.

However, after upgrading, the LAN keeps repeating detach and attach, and ultimately cannot connect to the system.
The system can only be used again after reboot.

System: Log Files: General

2026-01-23T07:32:15 Notice kernel     <6>[82529] bge8: link state changed to UP
2026-01-23T07:32:15 Notice opnsense   /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt6(bge8)
2026-01-23T07:32:13 Notice kernel     <6>[82527] bge8: link state changed to DOWN
2026-01-23T07:32:13 Notice opnsense   /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for opt6(bge8)
2026-01-23T07:32:07 Notice kernel     <6>[82522] bge8: link state changed to UP
2026-01-23T07:32:07 Notice opnsense   /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt6(bge8)
2026-01-23T07:32:02 Notice opnsense   /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for opt6(bge8)
2026-01-23T07:32:02 Notice kernel     <6>[82516] bge8: link state changed to DOWN

What should I do?
Should I downgrade to 25.1?


January 23, 2026, 10:07:25 AM #1 Last Edit: January 23, 2026, 10:11:28 AM by iMx
I cannot comment on changes between 25.1 and 25.7 specifically, nor first hand experience with bge interfaces ....

... BUT if you have ASPM enabled in the BIOS, I'd try turning that off (everywhere). 

Also set a tuneable, then reboot after setting:

hw.pci.enable_aspm=0
.. has fixed all sorts of interface randomness over the years for me, although primarily on Intel.  Then if you want to narrow it down after - i.e it resolves the issue - selectively re-enable.

You can check ASPM state with:

pciconf -lcv |grep -i aspm

ASPM state is as follows:

link x0(x2) speed 0.0(8.0) ASPM disabled(L0s/L1)
link x1(x2) speed 5.0(5.0) ASPM disabled(L0s/L1) ClockPM disabled
link x8(x8) speed 8.0(8.0) ASPM disabled(L1)

It doesn't seem to be an ASPM problem.

This phenomenon never happened before, but since upgrading the system to 25.7.10, it has been happening every day.

Could this be a compatibility issue between FreeBSD and Broadcom network cards?

> Could this be a compatibility issue between FreeBSD and Broadcom network cards?

Always a possibility - did you search for the underlying FreeBSD version and your interface model(s)?

Is it just 1 interface? Or multiple of the same model?

If you have a ZFS snapshot, rolling back and testing again should be easy enough.

Quote from: burns1230 on January 24, 2026, 08:39:33 AMCould this be a compatibility issue between FreeBSD and Broadcom network cards?
Which model exactly ?

You can always have a look around in the KERNEL make conf file like this one : https://cgit.freebsd.org/src/tree/sys/amd64/conf/GENERIC
It's the file where you enable/disable drivers used when compiling the FreeBSD Kernel from source like we use to do in the old days when pkg wasn't so fancy yet ;)
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)