You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing native VLAN results in correct data structure (two bridged VLANs, one routed VLAN on a VLAN-tagged subinterface). It looks like the vlan.mode from pxeboot VLAN is copied to the main interface (too soon?). Bad idea...
The text was updated successfully, but these errors were encountered:
fixesipspace#421)
* VLAN trunk is created before changing any link attributes based on access/native VLAN
* On routed access/native VLANs, set vlan.mode on all interfaces, not just on link
(because it won't be copied into interface attributes)
* Check whether routed native VLAN is supported by the platform
(implements feature flag discussed in ipspace#415)
* Cisco IOSv is the only device so far known to support routed native VLANs.
FRR/Cumulus should be able to do that as well, but that needs to be verified.
* Add 'routed native VLAN' test case
The following topology creates three routed segments on the R1-R2 link (native, red, and blue):
Removing native VLAN results in correct data structure (two bridged VLANs, one routed VLAN on a VLAN-tagged subinterface). It looks like the vlan.mode from pxeboot VLAN is copied to the main interface (too soon?). Bad idea...
The text was updated successfully, but these errors were encountered: