Native Vlan with computer link

[boussora.yacine]

Hello, i wanna ask what is the utility of native vlan with computer, if a native vlan can untag just one VLAN, so why we make a native VLAN and not switchport access VLAN x.

[AllertGen]

Hi, boussora.yacine.

Usually you need to configure end devices ports (like servers, PCs, etc.) as swichport access ports. It is because end devices don't use vlan tags at they network works. But sometime end devices can support device tags (linux, intel network cards, phone devices, etc.) and for such devices you can configure ports as trank with native vlan.

But usually you don't need to do so. So you can configure port for PC in the trunk mode with native vlan only at the case when you want to use additional interfaces with vlan tag support in the future. In other cases it can hit your network securety.

Best Regards.

[boussora.yacine]

Thank You AlletGen, i am just wondering why sometimes we use trunk port with PC's and configure a native VLAN on this link if it ll understand just one VLAN, so why not access port, what is the utility here??

Best Regards

[thepopp]

There is a default VLAN that is configured for every switch. If a port is not tagged with a VLAN ID, it gets sent to the default VLAN. VLAN=subnet (mostly). This tells the switch which other ports may (and may not) receive traffic from this port. The default VLAN is, by default, VLAN 1 unless otherwise changed. It is good security practice to change the default VLAN to something other than one.

Additionally, trunking will not function if the native VLANs are not the same.