Urgent problem with VLAN interfaces saying "no carrier" after upgrading to 18.7

[Tsuroerusu]

With it being stated that 18.7 has focused on stability, I decided to not wait for two or three point releases as I normally do before upgrading my company firewalls (A high availability setup of two firewalls).

However, the result was that none of my VLAN "interfaces" activate properly. On the main page, they are marked with red saying "Ethernet autoselect", and under System --> Interfaces --> Overview their status says "no carrier".

All of my physical interfaces activate without a problem, and I have WAN access (Which is through a physical interface), but none of my VLANs seem to work.

I have tried re-jiggering the interface assignments, so that the system would, I assume, re-write the VLAN configuration, but that did not fix things at all.

The VLANs are configured on an ix interface, and my switch reports that the ports going to the VLAN NICs are not active. Could this have something to do with the backported Intel NIC drivers of 18.7? Was the ix driver backported?

Does anybody have any suggestion as to what I can do to resolve this problem?

[JasMan]

Hey,
just an idea: what happens when you create a new VLAN interface? Will this work or has it the same problem as the existing VLAN interfaces?

"no carrier" sounds like he's missing the binding to the physical interface or something like that.

Jas

[mimugmail]

You can try to downgrade the kernel (please note to unplug power, reboot is not enough):

https://github.com/opnsense/core/issues/2591

[Tsuroerusu]

You can try to downgrade the kernel (please note to unplug power, reboot is not enough):

https://github.com/opnsense/core/issues/2591

Thanks a lot for pointing me to that page on Github, I tried just simply booting kernel.old via the bootloader menu, and that solved the problem. So I would say this is an issue with the backported drivers. Also, no power cycling was necessary, just kernel.old in my case, however since my ix device is in a PCI-E card, then rebooting might have a slightly different effect than if it was an onboard device.