"Recent posts
#1
26.7 Series / Re: No link with Intel E810 on...
Last post by paoba - Today at 11:56:20 AMthanks for the heads up! here some more details about my interfaces and my switch. I was supprised my switch thinks the opnsense LAN is connected by Medium-type "Fiber", which is incorrect.
I don't know what FEC settings my internet provider has on their switch, but if required I can open up a ticket to find out.
I will try the tunable for both ports and see what happens after a reboot and also try to upgrade again.
testing tunables:
Switch opnsense LAN Port details:
LAN Interface (ice0):
WAN Interface (ice1):
I don't know what FEC settings my internet provider has on their switch, but if required I can open up a ticket to find out.
I will try the tunable for both ports and see what happens after a reboot and also try to upgrade again.
testing tunables:
Code Select
dev.ice.0.requested_fec="RS-FEC"
dev.ice.1.requested_fec="RS-FEC"Switch opnsense LAN Port details:
Code Select
Medium-type is Fiber
Admin duplex mode is AUTO, oper duplex is Full
Admin speed is 25G, oper speed is 25G
Flow control admin status is OFF, flow control oper status is OFF
Admin negotiation mode is OFF, oper negotiation state is OFF
Admin FEC mode is auto, oper FEC mode is rsLAN Interface (ice0):
Code Select
dev.ice.0.requested_fec: RS-FEC
dev.ice.0.negotiated_fec: RS-FEC
dev.ice.0.current_speed: 25 Gbps
media: Ethernet autoselect (25G-AUI <full-duplex>)
plugged: SFP/SFP+/SFP28 25GBASE-CR CA-25G-S (Copper pigtail)WAN Interface (ice1):
Code Select
dev.ice.1.requested_fec: RS-FEC
dev.ice.1.negotiated_fec: RS-FEC
dev.ice.1.current_speed: 25 Gbps
media: Ethernet autoselect (25GBase-LR <full-duplex>)
plugged: SFP/SFP+/SFP28 100GBASE-LR4 or 25GBASE-LR (LC) #2
26.7 Series / Re: No link with Intel E810 on...
Last post by franco - Today at 11:16:27 AM@paoba yeah this seems like a slightly different issue from the pressing DDP load failed and driver doesn't work at all.
Cheers,
Franco
Cheers,
Franco
#3
26.7 Series / Re: No link with Intel E810 on...
Last post by bugacha - Today at 10:19:39 AMQuote from: paoba on October 13, 2026, 08:12:10 PMHey Franco
sorry I couldn't find time earlier for testing...
I just tried the update command and still have no link with the new kernel after reboot.
BUT! I was able to udpate anyway by disabling the DDP Package before the update...
I'm really sorry for the confusion and the false statement from my side! I guess I shouldn't do updates too late in the night...
Bad news... After I was on 26.7.7 I enabled the DDP Package again and had no link after the reboot.
Here are some logs. let me know if you need anything else.
On Version 26.7.7 with DDP enabled:Code Select[1] ice0: <Intel(R) Ethernet Connection E823-L for SFP - 1.43.3-k> mem 0xf0000000-0xf7ffffff,0xfa010000-0xfa01ffff at device 0.0 numa-domain 0 on pci10
[1] ice0: Loading the iflib ice driver
[1] ice0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.41.0, track id 0xc0000001.
[1] ice0: fw 7.2.14 api 1.7 nvm 3.42 etid 8001ff0f netlist 0.1.7000-1.25.0.f083a9d5 oem 1.3755.0
[1] ice0: Using 10 Tx and Rx queues
[1] ice0: Reserving 10 MSI-X interrupts for iRDMA
[1] ice0: Using MSI-X interrupts with 21 vectors
[1] ice0: Using 1024 TX descriptors and 1024 RX descriptors
[1] ice0: Ethernet address: ██:██:██:██:██:██
[1] ice0: ice_add_rss_cfg on VSI 0 could not configure every requested hash type
[1] ice0: Firmware LLDP agent disabled
[1] ice0: link state changed to DOWN
[1] ice0: netmap queues/slots: TX 10/1024, RX 10/1024
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[9] ice0: All configured link modes were attempted but failed to establish link.
[9] ice0: The device will restart the process to establish link.
[9] ice0: Possible Solution: Check link partner connection and configuration.
[47] ice0: Failed to add VLAN filters:
[47] ice0: - vlan 100, status -14
[47] ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
[56] ice0: All configured link modes were attempted but failed to establish link.
[56] ice0: The device will restart the process to establish link.
[56] ice0: Possible Solution: Check link partner connection and configuration.
What FEC settings do you have on the switch for this port ?
Try to play with RS or FC modes to see if link comes up.
From your log, driver and DDP are loaded fine, the issue is physical link which on this card is usually FEC related.
You can also try explicit tunnable in Opensense
Code Select
dev.ice.0.requested_fec="RS-FEC"
#4
26.7 Series / Re: 26.7.3 boot loop on Hyper-...
Last post by Monviech (Cedrik) - Today at 08:49:36 AMQuote from: iorx on Today at 08:32:53 AMHi again!
26.7.7 and I got a stable guest on Hyper-V again! KUDOS!
26.7.6 the bootloops was fixed but lots of other crashes... 😁
Brgs,
Great :)
Works like a charm also on my Hyper-V now, good that we tracked this one and also get a fix in the end. :)
#5
26.7 Series / Re: 26.7.3 boot loop on Hyper-...
Last post by (MARLOO) - Today at 08:41:48 AMThe 26.7.6 -> 26.7.7 update completed successfully via the GUI and the system ran normally afterwards.
Later, a scheduled reboot was triggered:
/usr/local/sbin/configctl -d -- system reboot
The shutdown started normally, but the firewall never completed the reboot.
Later, a scheduled reboot was triggered:
/usr/local/sbin/configctl -d -- system reboot
The shutdown started normally, but the firewall never completed the reboot.
#6
26.7 Series / Re: 26.7.3 boot loop on Hyper-...
Last post by (MARLOO) - Today at 08:41:28 AMNot Hyper-V here, but I had a similar symptom on a physical OPNsense box with Intel I226-V NICs.
A scheduled `configctl system reboot` started normally, but the system hung during the reboot with CPU at about 99% (seen in Grafana). I had to power-cycle it manually.
After the manual power cycle, OPNsense booted normally. A later manual reboot from the GUI also completed successfully.
No kernel panic, crash dump or watchdog message was found. CPU temperature was normal, and there was plenty of free RAM and no swap usage.
I have disabled the scheduled reboot for now. Has anyone else on physical I226-V hardware seen a scheduled reboot leave the system hung with high CPU usage?
A scheduled `configctl system reboot` started normally, but the system hung during the reboot with CPU at about 99% (seen in Grafana). I had to power-cycle it manually.
After the manual power cycle, OPNsense booted normally. A later manual reboot from the GUI also completed successfully.
No kernel panic, crash dump or watchdog message was found. CPU temperature was normal, and there was plenty of free RAM and no swap usage.
I have disabled the scheduled reboot for now. Has anyone else on physical I226-V hardware seen a scheduled reboot leave the system hung with high CPU usage?
#7
26.7 Series / [SOLVED] Re: 26.7.3 boot loop ...
Last post by iorx - Today at 08:32:53 AMHi again!
26.7.7 and I got a stable guest on Hyper-V again! KUDOS!
26.7.6 the bootloops was fixed but lots of other crashes... 😁
Brgs,
26.7.7 and I got a stable guest on Hyper-V again! KUDOS!
26.7.6 the bootloops was fixed but lots of other crashes... 😁
Brgs,
#8
26.7 Series / Re: Router Dead After Latest U...
Last post by (MARLOO) - Today at 08:30:20 AMUpdate to my previous positive report.
The 26.7.6 -> 26.7.7 update completed successfully and the system ran normally afterwards.
Later, while the firewall was running normally, the LAN interface briefly went down and came back up after a few seconds. This caused a temporary loss of connectivity.
After that, a scheduled reboot was triggered. The shutdown started normally, but the firewall never completed the reboot.
From Grafana I could see that CPU usage went to about 99%, but the firewall remained hung and unreachable. I had to power-cycle it manually.
After the manual power cycle, OPNsense booted normally.
I then tested a manual reboot from the GUI. It completed successfully and the system came back online.
No kernel panic, crash dump or watchdog message was found. CPU temperature was normal, and there was plenty of free RAM and no swap usage.
I have disabled the scheduled reboot for now. Has anyone else seen a brief LAN link loss followed by a scheduled reboot leaving OPNsense hung with high CPU usage?
The 26.7.6 -> 26.7.7 update completed successfully and the system ran normally afterwards.
Later, while the firewall was running normally, the LAN interface briefly went down and came back up after a few seconds. This caused a temporary loss of connectivity.
After that, a scheduled reboot was triggered. The shutdown started normally, but the firewall never completed the reboot.
From Grafana I could see that CPU usage went to about 99%, but the firewall remained hung and unreachable. I had to power-cycle it manually.
After the manual power cycle, OPNsense booted normally.
I then tested a manual reboot from the GUI. It completed successfully and the system came back online.
No kernel panic, crash dump or watchdog message was found. CPU temperature was normal, and there was plenty of free RAM and no swap usage.
I have disabled the scheduled reboot for now. Has anyone else seen a brief LAN link loss followed by a scheduled reboot leaving OPNsense hung with high CPU usage?
#9
General Discussion / Re: Best firewall solution for...
Last post by yourfriendarmando - Today at 06:50:54 AMA lot of the stock Block lists that can be loaded on OPNsense, should do a normal amount of blocking.
Loading too many Advertisement related block lists will begin to break your experience on the internet.
I choose all the general lists except for AdGuard, specifically because it will break some streaming, and perhaps, in your case, gaming.
Anything higher than Hagezi's PRO list will break stuff, as mentioned on their website https://github.com/hagezi/dns-blocklists
I have the OISD big block list for myself, which has some Ad blocking, but for clients, I just choose the NSFW list.
For the Hagezi targeted lists, all except for: Safesearch (though this could be good for kids), Badware Hoster.
I load a ton more via custom URL lists, but don't want to be overwhelming to begin with.
Sadly, too much Ad blocking also breaks a lot of those sponsored websites on the top of [your favorite search engine] your search results.
It gets angry people since most people are used to clicking on the first result, past the unrequited AI sputter.
Hope that helps, I'm happy with using Unbound, but the system is flexible to offload to a separate PI project.
Loading too many Advertisement related block lists will begin to break your experience on the internet.
I choose all the general lists except for AdGuard, specifically because it will break some streaming, and perhaps, in your case, gaming.
Anything higher than Hagezi's PRO list will break stuff, as mentioned on their website https://github.com/hagezi/dns-blocklists
I have the OISD big block list for myself, which has some Ad blocking, but for clients, I just choose the NSFW list.
For the Hagezi targeted lists, all except for: Safesearch (though this could be good for kids), Badware Hoster.
I load a ton more via custom URL lists, but don't want to be overwhelming to begin with.
Sadly, too much Ad blocking also breaks a lot of those sponsored websites on the top of [your favorite search engine] your search results.
It gets angry people since most people are used to clicking on the first result, past the unrequited AI sputter.
Hope that helps, I'm happy with using Unbound, but the system is flexible to offload to a separate PI project.
#10
General Discussion / Re: DNS over tls when running...
Last post by yourfriendarmando - Today at 06:33:26 AMIt's possible your client was using its own DNS services. Browsers tend to try using their own DNS these days out of the box.
