The diagram of trunking just clicked all of the info together. Thank you professor for putting valuable content into the world and helping me accelerate my career!
Ive done 3 CCNA classes through college, and you are the only person who has ever fully explained why VLANs are used and why trunking is used. I know how to configure it, I knew that it was needed, but i never knew why.
Still powering towards NW+ cert. Doing job apps for IT tech positions, hoping to get a foot in the door. Can't believe I got here in my spare time starting in January. This channel rocks.
@@gregoryhilbert4291 I finished my Net+ several months later. About 6 months after that I'm entering an MBA program. It's a bad bad bad bad bad bad bad time to be trying to get into the IT field, unfortunately.
In the last slide, I understand that 802.1Q standard is built into the phone which is how the voice traffic is separated upon arriving to the switch? Would a single port on the switch differentiate the destination of data destined for both VLANs?
When you use both Voice and Data in the same switch port, you configure the SAME port with two VLANs. If a switch port is configured with more than one VLAN, then we need to tell the switch which packet belongs to which VLAN. Tagged packets are headers comprised of VLAN information. On the other hand, untagged packets are just normal; for example, a packet coming from PC doesn’t contain VLAN information because the PC don’t support 802.1q trunking.
@@SalamaAltalla This make a lot more sense. I’m getting some managed switches here soon so I should be able to understand this technology more deeply. Thank you
Never fail to disappoint. Most definitely the best at explaining some very complicated things in ways that seem so simple. Great explanation for trunking.
Explained nicely and simple. One question. In the example of a phone and PC on different vlans on the same switch port. How does the phone and the PC tell the switch what vlan they belong too? vlan100 or vlan200?
If I am correct wouldn't trunking cause an extra hop, why not just put the networks on the same switch, and then if necessary only trunk one of the networks?
I'll say it a million times over.
this is the way professors should be teaching. Best I.T. professor ever.
This guy probably the best tech guy , on his explanations
He is 1337
@@FreeThink1984What's 1337?
@@lucasgrey9794 leet
@@lucasgrey9794 Leet, look it up on wikipedia
The diagram of trunking just clicked all of the info together. Thank you professor for putting valuable content into the world and helping me accelerate my career!
I'm doing my CCNA now and had troubles getting my head around trunking, this helped clarify. Thanks alot :D
Ive done 3 CCNA classes through college, and you are the only person who has ever fully explained why VLANs are used and why trunking is used. I know how to configure it, I knew that it was needed, but i never knew why.
Still powering towards NW+ cert. Doing job apps for IT tech positions, hoping to get a foot in the door. Can't believe I got here in my spare time starting in January. This channel rocks.
How are things going 1 year later? I'm taking my Network + Exam this month
@@gregoryhilbert4291 I finished my Net+ several months later. About 6 months after that I'm entering an MBA program. It's a bad bad bad bad bad bad bad time to be trying to get into the IT field, unfortunately.
Phenomenal video. Needed a quick refresher and this helped a bunch!
that was the best explanation I saw about this topic
thank you very much
Fantastic explaination! Liked the video
This explaination helped me a lot
Thanks for the video! I figured that this is how it all works, but the CCNA book is not the best at explaining things and made me question myself.
In the last slide, I understand that 802.1Q standard is built into the phone which is how the voice traffic is separated upon arriving to the switch? Would a single port on the switch differentiate the destination of data destined for both VLANs?
When you use both Voice and Data in the same switch port, you configure the SAME port with two VLANs.
If a switch port is configured with more than one VLAN, then we need to tell the switch which packet belongs to which VLAN. Tagged packets are headers comprised of VLAN information. On the other hand, untagged packets are just normal; for example, a packet coming from PC doesn’t contain VLAN information because the PC don’t support 802.1q trunking.
YOu may google "Voice VLAN and Data VLAN on the same port"
@@SalamaAltalla This make a lot more sense. I’m getting some managed switches here soon so I should be able to understand this technology more deeply. Thank you
@@SalamaAltalla This was my question as well and your answer fixed my confusion. Thank you.
Never fail to disappoint. Most definitely the best at explaining some very complicated things in ways that seem so simple. Great explanation for trunking.
Never fail to disappoint? Don't think this means what you think it means.
@@gargleblaster haha
Thank you professor!
Fantastic! Thank you
Explained nicely and simple. One question. In the example of a phone and PC on different vlans on the same switch port. How does the phone and the PC tell the switch what vlan they belong too? vlan100 or vlan200?
I'm just here to acknowledge the Stargate reference at 1:40. :D
Thanks Professor 👨🏫
If I am correct wouldn't trunking cause an extra hop, why not just put the networks on the same switch, and then if necessary only trunk one of the networks?
What happens when the switches are in different buildings?
@@professormesser Thank you for clearing this up!
Enjoyed that one
one addition, this work on layer 3 switches
spot on
Gracias señor!
Hi professor! I can send you some Money or become a patreon? I appreciate so much your free work! You are a saint
yes u can send him money. I am his manger
@@Sam-bv6od 😂
dont listen to sam, I am the real manager