Options

Native Vlan

GngoghGngogh Member Posts: 165 ■■■□□□□□□□
in CCNA & CCENT
Hi,

Native vlan are a bit confusing.. i am trying to understand Native Vlans and untagged traffic.
I have been searching and im unable to find what exactly is a native vlan, all i find is that native vlan is used for untagged traffic and that you should not use Native vlan 1, because it leaves your network vulnerable to certain types of attacks (EX: Double tagging).

if all access ports are configured to access vlan x why do i need Native Vlan?
if trunk ports need a Native Vlan, than this means that all allowed Vlans in the trunk go through Native Vlan .

This is what is confusing me, and i dont understand why the need of Native Vlan if for example we dont have untagged traffic in a given network and we not use ip phones.
· Share on FacebookShare on Twitter

Comments

  • Options
    Dieg0MDieg0M Member Posts: 861
    The concept of native VLAN only applies if the port operational state is set to be a trunk. In the case of access ports, the traffic will always be untagged. As for voice VLAN's, they will use a similar concept to trunk ports and the Data VLAN will be considered as native.
    Follow my CCDE journey at www.routingnull0.com
    · Share on FacebookShare on Twitter
  • Options
    GngoghGngogh Member Posts: 165 ■■■□□□□□□□
    Dieg0M wrote: »
    In the case of access ports, the traffic will always be untagged.

    By default they are untagged because they belong to vlan 1 which is the native. but if they are in any other vlan that is not the native they are tagged with the vlan id, so the traffic will be tagged.

    Now you are confusing me...
    · Share on FacebookShare on Twitter
  • Options
    Dieg0MDieg0M Member Posts: 861
    No. An access port will only participate in the VLAN to which it has been assigned to and data will not be tagged. In the case of trunk ports they will use an 802.1q or ISL encapsulation to tag the packets between devices.
    Follow my CCDE journey at www.routingnull0.com
    · Share on FacebookShare on Twitter
  • Options
    davenulldavenull Member Posts: 173 ■■■□□□□□□□
    it looks like the 802.1q concept of native vlans was introduced to provide backward compatibility with devices that may not support vlan tagging
    · Share on FacebookShare on Twitter
  • Options
    OfWolfAndManOfWolfAndMan Member Posts: 923 ■■■■□□□□□□
    davenull wrote: »
    it looks like the 802.1q concept of native vlans was introduced to provide backward compatibility with devices that may not support vlan tagging

    Boom goes the dynamite.
    :study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []
    · Share on FacebookShare on Twitter
  • Options
    GngoghGngogh Member Posts: 165 ■■■□□□□□□□
    Dieg0M wrote: »
    No. An access port will only participate in the VLAN to which it has been assigned to and data will not be tagged. In the case of trunk ports they will use an 802.1q or ISL encapsulation to tag the packets between devices.

    ok.. i understand now how tagging works. thanks for your help.
    · Share on FacebookShare on Twitter
  • Options
    mikeybinecmikeybinec Member Posts: 484 ■■■□□□□□□□
    Another example of untagged traffic is CDP
    Cisco NetAcad Cuyamaca College
    A.S. LAN Management 2010 Grossmont College
    B.S. I.T. Management 2013 National University
    · Share on FacebookShare on Twitter
Sign In or Register to comment.