Recent posts

#1

26.7 Series / Re: No link with Intel E810 on...

Last post by bugacha - Today at 08:09:08 AM

I filed bug with FreeBSD 15.3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296989

It will take a while until this is fixed tho

Looks like there is some movement on this bug and this can be mainlined into 15 version

[Components involved:]

#2

26.7 Series / Re: Intel E810 fails to link o...

Last post by bugacha - Today at 08:08:39 AM

Long time lurker, first time caller.

After upgrading from 26.1.x to 26.7, my WAN interface (ice0, Intel E810-XXV for SFP, 25GBase-LR to my ISP) stopped establishing a link entirely. It appears that link-negotiation fails when the ice driver loads its DDP package. On 26.7 there is no fallback when that negotiation fails, unlike on 26.1. Forcing "Safe Mode" (DDP package not loaded, 1 queue; ice_ddp_load="YES" forced via /boot/loader.conf.local) gives a reliable link on both branches. Updating to 26.7.3_8 gave me multiple retry/re-attach cycles instead of giving up after one but did not fully fix it. Without DDP, no 25Gbit fun :(

Components involved:

• NIC: Intel Ethernet Controller E810-XXV for SFP, genuine Intel reference card (not an OEM-customized part)
• Driver: iflib ice, driver_version 1.43.3-k (identical across all OPNsense versions tested)
• Firmware: fw 7.8.2, api 1.7, nvm 4.80 (identical across all tests)
• DDP: ICE OS Default Package version 1.3.41.0, track id 0xc0000001

I am wondering if...

• anyone else has seen E810 fail to negotiate link in full-DDP mode specifically after upgrading to 26.7, where Safe Mode links fine?
• the queue-reconfiguration-triggered link flap on the DDP-loaded attach is a known iflib/ice interaction, or worth its own upstream report?
• anyone has any recommendation on forcing requested_fec at boot to test the theory above?

Happy to pull more diagnostics.

read up here

https://forum.opnsense.org/index.php?topic=52405.0


FreeBSD driver's bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296989 is being fixed and hopefully can be mainlined into 15

#3

26.7 Series / Re: PPPoE over an unassigned V...

Last post by franco - Today at 07:45:54 AM

Not sure why it considers pppoe0 down/unable to come up, but it's probably hidden somewhere in your setup.

Can you share this from 26.7.5?

# pluginctl -Q


Thanks,
Franco

#4

26.7 Series / Re: pkg: 2.3.1_1 -> 2.8.4_1 Pa...

Last post by franco - Today at 07:38:09 AM

Change the mirror then.  Although I find it strange it knows about 2.8.4._1 and I didn't see the errors in the log before.


Cheers,
Franco

#5

Development and Code Review / Re: 26.7.5 git tag for src rep...

Last post by none - Today at 12:15:19 AM

the error:

/usr/src/sys/dev/pci/pci_host_generic_fdt.c:122:2: error: call to undeclared function 'ofw_bus_destroy_iinfo'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]
  122 |         ofw_bus_destroy_iinfo(&sc->pci_iinfo);
      |         ^
/usr/src/sys/dev/pci/pci_host_generic_fdt.c:122:2: note: did you mean 'ofw_bus_setup_iinfo'?
/usr/src/sys/dev/ofw/ofw_bus_subr.h:88:6: note: 'ofw_bus_setup_iinfo' declared here
   88 | void    ofw_bus_setup_iinfo(phandle_t, struct ofw_bus_iinfo *, int);
      |         ^
1 error generated.
--- pci_host_generic_fdt.o ---
*** [pci_host_generic_fdt.o] Error code 1

make[2]: stopped making "all" in /usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM

#6

Development and Code Review / 26.7.5 git tag for src repo

Last post by none - October 03, 2026, 10:37:09 PM

Hello,

I build arm images and the 26.7.5 build failed for src. I got to find out the reason was this:

ofw_bus_destroy_iinfo()

that was introduced in this commit:

https://github.com/opnsense/src/commit/ed5b1f4fb4d2f4c8c13004f7fc7560fb8e6b7864

So now there is no 26.7.5 tag and the build fails complaining about this function. I saw that src tagged 26.7.4 doesn't have this call, so I am trying to build 26.7.5 using src tagged 26.7.4. Will be a 26.7.5 tag or should I expect just 26.7.6?

Thanks

none

#7

26.7 Series / Re: pkg: 2.3.1_1 -> 2.8.4_1 Pa...

Last post by mirek.i - October 03, 2026, 10:17:30 PM

# pkg upgrade -y pkg; echo $?
Updating OPNsense repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository OPNsense has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository OPNsense
Error updating repositories!
3

#8

26.7 Series / Re: PPPoE over an unassigned V...

Last post by fanski - October 03, 2026, 09:29:11 PM

Hi,

I have a very similar problem and hope it's ok to reply to this topic, otherwise I can also open a new one.

So when on 26.7.1 my PPPoE config works fine and the connection comes up. I get an IP from the ISP etc and there is no problem as far as I can see.
But if I'm upgrading to 26.7.5 (I also tried to upgrade to 26.7.4 and 26.7.4_1 before multiple times) the PPPoE always fails. The interfaces are up and if I check the Interface Overview/assignments/etc. everything looks the same for me but I don't get a public IP and the status of the WAN interface on the Dashboard is active but "undefined".

I did some research with AI (in fact Claude, ChatGPT and Gemini) and after I tried all the suggested workarounds the AI always comes to the conclusion this must be a bug.
I'm not sure if this is really true because you know AI always sounds pretty sure about everything but isn't always right and after some research I also read a lot about most problems are more config errors than bugs so I guess this is maybe more my problem.

So from the log I can see that the PPPoE just doesn't work, but I'm not sure why. If I do a diff between 26.7.1 log and 26.7.5 log I can see the order of the log messages regarding the WAN interface and PPPoE is a little different but everything happens at the same second. For the AI this is the root cause as the order has to be different and this is a key problem for my config. But as I already mentioned I'm not really sure about this.

Another potential problem according to the AI is that I have 2 10G interfaces for internal traffic and the WAN interface is only a 1G interface. The AI tells me this is a big problem as the 10G interfaces are seen as priority interfaces and the OPNSense tries to connect via those interfaces instead of the 10G which then fails. But I can't see any hint of that in the log files.

I tried to follow the How To Guide about PPPoE over VLAN but it's already 5 years old and I'm not sure if this is still correct after all those years.

Maybe someone can help me, because I now spent so many hours on that problem that I don't know what options are left to solve this issue.

Many thanks in advance.

#9

General Discussion / Re: Strange WiFi issue

Last post by suur13 - October 03, 2026, 09:09:54 PM

Is Multicast DNS allowed on the WiFi Bridge ?!

Perhaps disable IGMP Snooping tuneable or something like that ?

Sorry, but I can not even find neither settings

#10

General Discussion / Re: Strange WiFi issue

Last post by nero355 - October 03, 2026, 08:36:21 PM

If I connect iPhone to Wifi via Opnsense box own WLAN interface I can not reach BubbleUPnP.

Is Multicast DNS allowed on the WiFi Bridge ?!

Perhaps disable IGMP Snooping tuneable or something like that ?


/Just some thoughts...