Regression #13622
open
Retain previous VLAN tag type for existing interfaces on upgrade
Added by Steve Wheeler almost 3 years ago.
Updated 6 days ago.
Plus Target Version:
25.11
Affected Architecture:
All
Description
In 2.7/23.01 QinQ uses if_vlan instead of netgraph and set the outer tag ethertype as 802.1ad (0x88a8). That is the expected tags tag type for most QinQ links but is not what netgraph set in 2.6/22.05 and earlier. That used 802.1q (0x8100) for both tags. That could lead to existing QinQ links failing at upgrade.
This change needs to be documented. The new behaviour is probably correct for most new interfaces.
There should be an option to revert to the previous behaviour if required. ifconfig can set the vlanproto value directly in 23.01.
Existing QinQ interfaces could be automatically set to that at upgrade to maintain compatibility with connected devices.
See: https://redmine.pfsense.org/issues/13340
- Plus Target Version changed from 23.01 to 23.05
Moving ahead to 23.05, we can document the change for now.
- Plus Target Version changed from 23.05 to 23.09
- Target version changed from 2.7.0 to CE-Next
- Plus Target Version changed from 23.09 to 24.01
- Plus Target Version changed from 24.01 to 24.03
- Plus Target Version changed from 24.03 to 24.07
- Plus Target Version changed from 24.07 to 24.08
- Plus Target Version changed from 24.08 to 24.11
- Plus Target Version changed from 24.11 to 25.01
- Plus Target Version changed from 25.01 to 25.03
- Plus Target Version changed from 25.03 to 25.07
Is there any timeline to resolve this one? Double stacked 802.1q packets are far more common than 802.1ad in my experience. This is also a breaking change from anything pre 2.7.
- Plus Target Version changed from 25.07 to 25.11
- Status changed from New to In Progress
- Assignee set to Marcos M
- Target version changed from CE-Next to 2.9.0
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
- Subject changed from QinQ ethertype tags changed to Retain previous VLAN tag type for existing interfaces on upgrade
Also available in: Atom
PDF