Best native VLAN explained I have watched ever. Thanks for your time.

Thanks a lot, I now understand how the native vlan works. God bless you wherever you are.

Haha, this is too funny! Well done mate. I have just tested this in GNS3 and blimey, it works! Of course, you have to disable STP for both VLANs 2 and 3 but across a single trunk link between two switches you are not going to get a layer 2 network loop anyway. Also, it is STP that blocks the ports with a native vlan mismatch, not CDP, though CDP will be complaining about it a lot lol. Interesting stuff, thanks mate!

The way u explain this is awesome 👏👏👏

Superb. Great explanations. Everyone can grasp this.

Thank you for the video. It really helps me understand how native VLAN works!

finally found the right video for native vlan. thank u

WOW!!!!!1 finally i got my answer thank you very much brother. keep going

Great video. Very helpful and easy explanation. Many Thanks.

Thank you so much I really apreciate your work, it helped me to get a clear consept about native vlan thanks a lot.

1st time i saw this type of simple explanation thanks 👍

Great video.. thanks! Hope you make more

Thank you, that was the best explanation ever *thumbs up*

Best explanation about native vlan, you are my hero

Great Explanation! Thank you!

This is called EXPLANATION!!!!! ......THE BEST

Very good explanation Marious!

Thank you so much. This helps a lot!

very good and helpful information.

great video ..thumbs up

excellent !!!!!!!

Finally found the right video

great explanation

Well done!

its good video to learn about native vlan but its practically not supported in cisco sytems coz the spanning tree protocol is enabled by default and you will get the blocking port on another switch.its possible only if you disable spanning tree protocol.thanks

Good Explanation!

great work

best explain thank u very much sir

Hello and thank you for the deep explanation. However, will be great to see the behavior without disabling STP and other default settings then compare. Also, if it's possible, will be great to check other switches like JUNOS or DELL and see the results. Again, Thank you and God bless!

THANK YOU SO MUCH!!!!!!

Great ! Many thanks bro

Great video :)

Awesome.

Thank you!!!!!

The fundamental question about this above lab is in the second scenario when the f0/1 port is part of VLAN 5, how one can create Native VLAN 5 ?. As a definition Native VLAN should not be assigned to any port. Since port f0/1 is already assigned VLAN 5, then where is the question of creating Native VLAN 5?

thanks a lot....

awesome

The rule should be: 1.) If the switch receives a frame on a trunk port with no VLAN information, it assumes this frame belongs to the NATIVE VLAN. My thinking is that access ports belong to VLAN 1 by default, so, the switch tags the frame with VLAN ID 1 hence, no frames that reaches the switch untagged. If a trunk port receives this frame with NATIVE VLAN 1 also, then it will strip off the tag from the frame, and the receiving end of the trunk port will have to tag this with VLAN 1 since NATIVE VLAN on the other end is 1. Or am I understanding this totally wrong?

I had to watch this video 2 times cuz my dumb fkin brain couldn't wrap around this impossible concept at all.thanks a lot dude i love you

nicely explained. Thanks a lot. However, I tried to simulate the same in packet tracer but it did not work for me. I could configure everything bypassing the errors but I am not able to reach the other pc from the first. I dont know where I am going wrong: VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default xyz ports 2 VLAN0002 active Fa0/1 Switch(config)#do sh int tr Port Mode Encapsulation Status Native vlan Gig0/1 on 802.1q trunking 2 VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default xyz ports 20 VLAN0020 active Fa0/1 Switch(config-if)#sw mo tr Switch(config-if)#do sh in tr Port Mode Encapsulation Status Native vlan Gig0/1 on 802.1q trunking 20

? your pinging the same network on both sides. If u make one of the PCs 192.168.2.1/24 it would not work.

What happen to native vlan 2? lmao

"If a switch receives a frame with no vlan tag, it assumes this frame belongs to the native vlan" Lets say native vlan on switch is 5 AND destination host is on vlan 5. The switch has received a frame with no vlan tag so it will assume it belongs to the native vlan [5] and forward the frame to the host as its on the same vlan. My question is, right before it forwards the frame, will it tag the frame with vlan 5

@subhramajumder8992

6 жыл бұрын

jagjit vlan tagging concept not applicable for end host because a host never understand vlan tagging so while handing over a packet to a host switch discard the tagging so in ur case it doesnt matter that ur host belong from vlan5 or not as long as it a host it will alaways recieve a vlan tagging free packet

Why your not tagging the vlan at SW1 with the native vlan id but you are doing so at the SW2 ? isnt it right SW2 just to forward it to the native vlan ports without tagging it ?

@ItexampracticeNet

7 жыл бұрын

The idea is to match the native VLAN to a host so a switch will NOT tag this frame. Thanks to this trick, I can ping PC1 and PC2 even though they are NOT in the same vlan. Does it make sense?

@danielsazonov345

7 жыл бұрын

i got the idea.But why SW1 don't tag the frame since its his native vlan id but SW2 does tag the frame ?this is where i got confused.you say on sw1: no no its my native vlan so i will remove the id and on sw2 you tag it (there is its native vlan aswell)?why

@ItexampracticeNet

7 жыл бұрын

12:40 - watch from this point. On SW1 I say - do NOT tag anything for VLAN2 On SW2 I say - do NOT tag anything from VLAN3 Thanks to that I can ping PC1 and PC2 even though they are not in the same VLAN. Does it make sense now?

@ItexampracticeNet

7 жыл бұрын

Oh I think I understand what you mean... let's analyze the path AFTER the native VLAn change. PC1 is pinging PC2 PC1 is in VLAN2 (SW1) PC2 is in VLAN3 (SW2) PC1---------->PC2 This frame arrives at SW1 and SW1 goes - ok, you are connected to F0/1 - this means VLAN2, however this is my Native vlan so I will not tag it. And sends it to SW2 over the trunk. This untagged frame arrives at SW2 and switch SW2 goes: oh, I just received a frame with NO vlan information, I will tag it using my native vlan which is VLAN3. Does it make sense now? :)