Comment 0 for bug 1773405
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote MAAS conflates untagged vlans with vid 0 | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
A vlan can never have vlan ID 0 - it is a reserved value; valid vlan IDs are from 1-4095. However, maas allows assigning vid 0 to vlans, and models new untagged vlans it disocvers as 'vid 0/untagged'.
This leads to confusion because it gives the impression that 'untagged' vlans must be vid 0 in maas, which isn't true.
vid 0 is not a valid vlan id - it is just a reserved value in an 802.1q header indicating no vlan tag is present. It makes sense in the context of a 802.1q header, but not in the context of a network model - all vlans have actual non 0 id's, unless you're using consumer grade equipment which doesn't support vlans at all.
It would be clearer and more accurate if MAAS said vlans it discovered have "unknown" vlan IDs.