None of my VLAN interfaces are working after upgrade to 22.7

[XeroX]

What is i211-AT? I only see i211 on my system. So maybe I should not set it to "Leave default" after all.

I am currently travelling and won't be back for 2 months, so I will wait until I am home before updating to 22.7 and/or playing around with those settings...

i211-AT = Intel i211

But my described scenario only applies to configurations with IPS.

I mean, nobody knows your configuration, so I wouldn't risk it.

[tessus]

I know that i211 is Intel, since I also have that NIC, but what I am saying is that I don't see the suffix -AT on my system. Neither in the UI, nor on the commandline.

[XeroX]

I know that i211 is Intel, since I also have that NIC, but what I am saying is that I don't see the suffix -AT on my system. Neither in the UI, nor on the commandline.

Its the official name for that chipset. Not sure whats the decision behind the naming schemes on the driver.

However now you know.

https://www.intel.com/content/www/us/en/products/sku/64404/intel-ethernet-controller-i211at/specifications.html

[tessus]

Thanks for the info.

[a3w]

22.7 Broke VLAN!!!

Everything worked prior to upgrading from 22.X to 22.7 and had been for years.

I initially saw this post and a potential solution (i.e. changing the "Interfaces>>Settings>>VLAN Hardware Filter" to "Default" when it was previously set to "Disable VLAN Hardware Filter" which by the way should have no impact on my system running modern NICs that fully support VLAN and all those other features (CRC, TSO, LRO...)

I rebooted the system a few dozen times adjusting all those settings within the Interfaces>>Settings, only to be left with the same result...a broken system/setup (VLAN inoperable)

I originally transitioned from pfSense to OPNsense but now I plan to abandon OPNsense after this debacle as it appears quality control is nonexsistent or lazy - time spent on this issue more than justifies an alternate firewall.

My final attempt and what push my decision to start pursing an alternative was a brand new clean install of OPNsense. I built a new/fresh installation from scratch and amazingly it worked!!! I was content but then during a power failure and a reboot of the system the issue returned and VLANs broke again.fine

Anyone else dealing with this and frustrated... I would rollback to a version prior to 22.7, seek alternatives or bang your head and spend hours troubleshooting to no avail.

[Patrick M. Hausen]

Have you assigned and enabled  the parent interface of your VLANs?

[AdSchellevis]

I would start looking at your dmesg output and system logging, it's likely driver/firmware related, when it's about Intels ixgbe series the number of (upstream) changes between both versions seem to be limited.

https://github.com/opnsense/src/commits/stable/22.1/sys/dev/ixgbe
https://github.com/opnsense/src/commits/stable/22.7/sys/dev/ixgbe

As Intel stuffs quite a collection of cards in these drivers (same for em/igb, ixl), issues can be isolated to specific models as well.

[JasonJoel]

but now I plan to abandon OPNsense after this debacle as it appears quality control is nonexsistent or lazy

No worries. Good luck on whatever other system you choose.

I would rollback to a version prior to 22.7

I would give different advice, and I think it applies to all software in general: never install v1 of a new release chain on a production system - wait for the 1st point release... AKA if 22.7 didn't have something you needed immediately, it would be better to wait for 22.7.x release, or test offline 1st...

[franco]

The change looks to be in FreeBSD 13.1. I'm not sure what we could do differently here other than what we have done in 2017 when we changed the VLAN filtering default to the most compatible value.

Venting is fine but passing the administrative task of YOUR setup to the COMMUNITY seems like a fruitless strategy.


Cheers,
Franco

[Patrick M. Hausen]

Also actual `ifconfig`, `dmesg` and `tcpdump` output would be helpful instead of "does not work".

1. Problem description
2. What is expected behaviour
3. What happens instead
4. How to reproduce

Problem report 101 ...

[Taomyn]

I haven't yet plunged into the upgrade from 22.1 to 22.7 but this thread makes me nervous - I have some VLANs, one is the PPPoE for my WAN connection, another is a DMZ and the final one appears to be something for WireGuard.


I checked and all the HW settings mentioned are set to disabled, so I did some testing with 22.1 to see what happened when I set them to default, I tried all of them and then just one at a time, and at no point did I end up with a working setup. Either no VLAN networks working or working for a short time before stopping - even setting everything back to "disabled" made no difference, I was forced to restore back using the change history.


I did see the mention of creating the parent interface if it's not there but I don't know what that means nor what settings it should have.

[Patrick M. Hausen]

* Go to Interfaces > Assigmnents.
* Create a new interface assignment for the parent interface of your VLANs, I use "_TR" as the description for "trunk", that's an interface carrying VLANs in Cisco speak.
* Go to Interfaces > (e.g.) _TR.
* Check "Enable".
* Save and apply.

I have upgraded two systems without any problems. It's going to be six in a week or two.

The "assign the parent interface" requirement was introduced some time into the 21.7 or 22.1 release. I don't remember exactly. But anyone using VLANs and running 22.1.x should already have that!

HTH,
Patrick

[Taomyn]

The "assign the parent interface" requirement was introduced some time into the 21.7 or 22.1 release. I don't remember exactly. But anyone using VLANs and running 22.1.x should already have that!

Thanks for the advice, I will do this the moment I get home. As for the requirement, my installation goes back quite a few major releases, way before 22.1.x maybe even, and it was never requested to assign a parent interface and I can't believe I will be the only one.

[Patrick M. Hausen]

It was in the release notes of the update with which it was introduced. And some forum discussion here. It was explicitly stated that you need to do that even if you had not before.

[Vesalius]

Thanks for the advice, I will do this the moment I get home. As for the requirement, my installation goes back quite a few major releases, way before 22.1.x maybe even, and it was never requested to assign a parent interface and I can't believe I will be the only one.

Soon after 22.1 was introduced, someone made a YouTube walkthrough on this requirement, if that helps.

https://youtu.be/69cNH9UX_es