Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.2.3. Native VLAN

💡 First Principle: When 802.1Q trunk ports send frames, they insert a 4-byte tag identifying the VLAN. But one VLAN gets special treatment—the native VLAN sends frames WITHOUT a tag. This exists for backward compatibility with devices that don't understand VLAN tags. By default, the native VLAN is VLAN 1.

Why is this a security concern? The native VLAN creates an attack vector called VLAN hopping. An attacker sends double-tagged frames: the outer tag matches the native VLAN (and gets stripped by the first switch), revealing the inner tag pointing to a target VLAN. The second switch delivers the frame to the attacker's chosen VLAN—bypassing your segmentation entirely.

What happens when native VLANs mismatch? If Switch A has native VLAN 1 and Switch B has native VLAN 99 on the same trunk, untagged frames from A arrive at B and get placed in VLAN 99 instead of VLAN 1. Traffic ends up in the wrong VLAN, users lose connectivity, and CDP/STP may report errors.

Security Best Practices:
  • Change the native VLAN to an unused VLAN (e.g., VLAN 999)
  • Ensure native VLAN matches on both ends of every trunk
  • Never use the native VLAN for user traffic
  • Consider vlan dot1q tag native (global config) to tag even native VLAN frames
Switch(config-if)# switchport trunk native vlan 999
Verification:
Switch# show interfaces trunk

Port        Mode         Encapsulation  Status        Native vlan
Gi0/24      on           802.1q         trunking      99

Port        Vlans allowed on trunk
Gi0/24      10,20,30

Reading the full output: Vlans allowed on trunk is the configured list; allowed and active in management domain narrows it to allowed VLANs that actually exist on this switch (a VLAN never created does not appear, even if allowed); in spanning tree forwarding state and not pruned narrows again to those STP is forwarding and VTP has not pruned.

⚠️ Exam Trap: A native VLAN mismatch doesn't just cause traffic issues. PVST+ detects the PVID inconsistency and blocks the mismatched VLANs on that port, while the other allowed VLANs keep forwarding — so the trunk stays up and the fault is easy to miss. The security risk is that untagged frames are re-homed into a different VLAN at the far end, bridging two broadcast domains over a path no router ACL sees.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned