When and Why Native VLANs Are Used

switchswitchportvlan

This is probably a simple one, but I am very new to VLANs.

I'd like to avoid using VLAN 1 as well as gain a better understanding of when native VLANs come into play when setting up a switch.

On an 8-port switch, if ports 1-4 are set as access ports (untagged) on VLAN 10, and ports 5-7 are set as access ports (untagged) on VLAN 20, if port 8 is set to trunk mode (tagged, to connect to another switch) with native VLAN still on VLAN 1, that native VLAN 1 would never actually be used, right, since all traffic is set to VLAN 10 and 20? If this is correct, what would the setup look like for traffic to use the native VLAN?

Best Answer

If you have an 8-port switch with ports 1-4 on VLAN 10, and 5-7 on VLAN 20, port 8 as trunk and default VLAN 1 ...

It's correct, VLAN 1 shouldn't be used

Watch for

  • Untagged frames arriving on the trunk port 8
  • Tagged-as-VLAN-1 frames arriving on the access ports or the trunk port

What happens with these depends on your manufacturer, model, and potentially other configuration. The normal goal would be to

  • Drop any untagged frames arriving on a trunk
  • Drop any unknown-VLAN tagged frames arriving anywhere

How you configure this depends on the particular switch.

Of course, if everything is configured correctly, you'll never get these untagged or tagged with unknown VLAN frames. But what's at the other end of all your wires? If there is any chance of malicious frames, or the ever-present certainty of configuration errors, this is just for protection. As a security matter, one of the first things the malcious systems do is mess with VLANs and MAC addresses.