Forum Discussion
lizhuh_55036
Nimbostratus
Nimbostratusport-based access vs tag-based access vlans
The document says
Port-based access to VLANs occurs when you add an interface to a VLAN
as an untagged interface. In this case, the VLAN is the only VLAN that you can associate with that interface.
How come the GUI allows user to put add an interface as a untagged member of one vlan and tagged member of other vlans? Is this a bug?
The document says by default, trunk's macaddress is the mac address of the lowest interface member. How come in reality, the GUI shows that trunk as a MAC address different from any mamber interface's mac?
Is there anyway I can change the behavior so that trunk uses a mac address of lowest numbered interface?
- You might want to post this one over on the Advanced Design and Config forum as you will likely get a better response over there.
-Joe - JRahm
Admin
Moved to the correct forum. It is not a bug for an interface to be tagged and untagged. Any interface can be configured to receive packets with multiple tags, and thus can be part of many vlans. However, it can be untagged for only interface. This is akin to cisco's "native" vlan.
