Messages

you can check with

Code Select Expand

pciconf -lcv whether ASPM is even enabled for NICs. i found that in a few aliexpress type machines i have, ASPM is just straight up disabled and there is no option to enable it.

linux i226 driver works fine with ASPM. tested OpenWRT on Odroid H4 ultra and no speed issues. load OPNsense on and immediate speed issues. disabled ASPM in BIOS, thankfully Odroid is a good brand with regular BIOS updates and support, and it immediately fixed all my speed test issues i was seeing.

Thanks!

Yeah seems like ASPM is off on my NICs too:

Code Select Expand

link x1(x1) speed 5.0(5.0) ASPM disabled(L1)

Yeah shuttle is kind of such a brand too, however they seem quite okay, they are somewhat based in germany, though sell taiwan made stuff.

Honestly, it's like always, I never get a problem where it just does work/or not work I always have such weird sometimes occuring problems, everywhere in my homelab lol

Reportedly, those adapters do not really work nicely with ASPM. If you can disable it in your BIOS, try that.

I don't actually have that option in my BIOS.

Thanks!

dmesg doesn't really show that much.
```
XXXXXXX@OPNsense:~ $  dmesg | grep -i i226
igc0: <Intel(R) Ethernet Controller I226-LM> mem 0x80c00000-0x80cfffff,0x80d00000-0x80d03fff at device 0.0 on pci1
igc1: <Intel(R) Ethernet Controller I226-LM> mem 0x80900000-0x809fffff,0x80a00000-0x80a03fff at device 0.0 on pci2
```

The problem is, that I'm not really sure which update, it must've happened between september 2024 and january 2025 which there were quite some updates, and as far as I remember downgrading is not really possible, nor something I'd really want to do on my single only prod firewall/router.

All available energy options are set to unrestricted/off, which are, though the mentioned ones are not even available in that bare minimum BIOS.
How would I even rollback a kernel manually?

Sorry for the assumption, but your answer sounds quite ai-generated.

Hi,
I own a Shuttle DL30N with those intel i-226-x ethernet controllers, as we know, they kind of have a reputation of quite a lot of problems, however fortunately they were fixed by intel upstream.

Luckily in August Shuttle uploaded a new BIOS with the upstream fix from intel, which solved all my issues, but since around, guessed 1 month I experience the same behaviour again, without really modifying anything except doing opnsense updates. Sadly I cannot really recall since which exactl update the problems re-appeared.

These problems include (Interfaces going in a weird on/off stale status)

Is anyone experiencing the same?
Has anyone found a fix yet?

Has this ever been solved?

I weirdly enough seem to experience the same.

I own a Shuttle DL30N with those intel i-226-x ethernet controllers.
Luckily in August Shuttle uploaded a new BIOS with the upstream fix from intel, which solved all my issues, but since around, guessed 1 month I experience the same behaviour again, without really modifying anything except doing opnsense updates.

Small Update on this thread, seems like intel did an upstream fix of the issue related to i-226-x ethernet controllers, watch out for new BIOS versions, my oem (Shuttle) released one in July which resolved ALL issues with stability (NIC's going down etc.).

Little Update here,

@imk82
I don't know how much to thank you, but the BIOS update for the faulty i226 ethernet ports actually solved my issues, I did actually search for a bios update, but before the new version was released . :D

Thanks!

It's called Uptime - Kuma, https://github.com/louislam/uptime-kuma

Thanks for the idea with the LAN Ports, due to the BSD issue, I came on the path with the BIOS, and there is actually a new Bios update online, since around a Month, with you call it, "Improved LAN stability"

https://global.shuttle.com/products/productsDownload?pn=DL30N%20SERIES

At least I got lucky, when choosing the vendor.
I'll first test the bios, then later check on the power options.

Thanks imk82

That is fitting my exact scenario very well, for me it also occured after switching to a Intel N100 based Mini-PC, with Intel NIC's, also for me it surprisingly often occurs when there is high load on the LAN interface. Also funnily enough I also have Intel-i226-LM NIC's.

I'll update as soon as I could look at the bios.

Hi Gauss23
Thanks for the suggestion with SPanning-Tree-Protocol, I don't have anything particularly set up in this direction.
As I don't have a console cable, I can only guess here, but mostly the opnsense seems online, just really sluggish, and sometimes not on all interfaces.

Thanks!

Seems I have the exact same problem!

Issue definitely keep occurring, I now have to physically reboot my opnsense around every 5 hours.

Most likely it's always the opnsense that becomes offline first, then my other Proxmox Nodes all become really sluggish, reachable/the other second not, login through proxmox webgui is then mostly not possible etc.

This seems really odd to me, where could I start to debug this?

Is that some package/ip conflict?
Hardware fault? (Opnsense has Intel NIC's and manufacturer labeled as opnsense good)
Config Error?
Problems with other Networking gear?
Problem with VLANs?

I can't seem to find any real trace here, not even any of the debug logs on opnsense tell me anything.
Also weirdly enough, all my web-applications, that are proxied through my reverseproxy are always online and fully accessible (except opnsense).

has anyone some idea where I could start?

So I've just further looked into this and even physically replaced the suspected broken switch.

After replacing the switch, the issue kep occuring, so I can now definitely say that opnsense is the problem.

Anyone got ideas on how to further troubleshoot here?

Hi

Yeah you are right!

Sorry about that, the images embed di not work correctly due to me not using the correct RAW iamge url, just fixed it. :)

Edit: altough the uptime-kuma board shows they are partually online, they are inaccessible for a normal browser, during that time.

For the reverse proxy, it's run inside a LXC inside Proxmox with an IP inside VLAN 20, it's nginxreverseproxy.

Feel free to let me know what else I shall provide.

Well what else could it be then?

Can't really imagine of the hosts themselves bening the problem here.

I imagined the switch, but could not get a single idea, even with the help of cisco support/forum.