MAAS uses 0 for untagged vlan's vid
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
Bug Description
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. In fact, vlans in maas aren't 'tagged' or 'untagged' at all - that's a property of the link between an interface and a vlan.
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. This keeps from giving the impression that vlans in maas can be 'tagged' or 'untagged'.
Also, fixing bug 1766334 would really reduce the impact of this issue, because then we would have real vlan IDs for vlans maas discovers.
This is related to bug 1774017 but is a little different.
| Changed in maas: | |
| importance: | Undecided → Low |
| milestone: | none → 2.5.0 |
| status: | New → Triaged |
| summary: |
- MAAS conflates untagged vlans with vid 0 + [2.x] MAAS uses 0 for untagged vlans vid |
| Changed in maas: | |
| importance: | Low → Medium |
| summary: |
- [2.x] MAAS uses 0 for untagged vlans vid + [2.x] MAAS uses 0 for untagged vlan's vid |
| Jason Hobbs (jason-hobbs) wrote Re: [2.x] MAAS uses 0 for untagged vlan's vid | #1 |
| description: | updated |
| description: | updated |
| tags: | added: foundations-engine |
| description: | updated |
| tags: | added: networking |
| tags: | added: internal |
| Changed in maas: | |
| milestone: | 2.5.0 → 2.5.x |
| Adam Collard (adam-collard) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| status: | Invalid → New |
| summary: |
- [2.x] MAAS uses 0 for untagged vlan's vid + MAAS uses 0 for untagged vlan's vid |
| Changed in maas: | |
| milestone: | 2.5.x → none |
| tags: | removed: internal |
| Changed in maas: | |
| importance: | Medium → Low |
| status: | New → Triaged |
| Jerzy Husakowski (jhusakowski) wrote | #3 |
| Changed in maas: | |
| milestone: | none → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
The new name you gave this bug is confusing too :) There is no such thing as an 'untagged vlan' in the maas model - vlans can be both tagged or untagged, depending on how they're connected to interfaces.
MAAS may discover a vlan and it may be untagged on the interface it is discovered on, but that doesn't make the vlan untagged - that's a property of the vlan's connection to that interface, not the vlan itself.