What are VLANS, TRUNKS & Q-in-Q?
HTML-код
- Опубликовано: 2 июн 2021
- What is a VLAN and why do you need them?
Adrian also talks a bit about trunk connections and covers the advanced version of VLANS, called Q-inQ. This is part of the technical fundamentals section in the relevant AWS courses.
▶ Check out Adrian's full range of content at learn.cantrill.io
▶ Join the best online technical study community techstudyslack.com
FOLLOW ME 😺
▶ Twitter: / adriancantrill
▶ RUclips: / learncantrill
OTHER VIDEOS AND PLAYLISTS 🎞
▶ Network Fundamentals • Networking Fundamentals
▶ Technical Fundamentals • Technical Fundamentals
▶ AWS Fundamentals • AWS Fundamentals
▶ Course Intros • learn.cantrill.io - Co...
▶ Exam Question Practice • AWS Exam Question Walk...
▶ MINI PROJECT - Hybrid DNS • Mini Project - Hybrid ...
▶ MINI PROJECT - Advanced VPN • Mini-project - Advance...
▶ MINI PROJECT - Pet Cuddle O Tron • Mini-project - Pet-Cud...
▶ MINI PROJECT - Web Identity Federation • Mini-project - Simple ...
▶ MINI PROJECT - Architecture Evolution • Mini-project - Applica...
▶ MINI PROJECT - Cat Pipeline • Mini Project - CatPipe...
▶ Best Videos • Best Videos
All rights reserved © 2022 Adrian Cantrill 
Наука
![Sean Rii, Karyon, Sharzkii - Taungule [My Love] (Official Music Video)](http://i.ytimg.com/vi/eJoMuypbSzQ/mqdefault.jpg)
Thank you for this explanative video. Great refresher from ccna studies.
Amazing! well explained. Thank you very much
Glad it was helpful!
I love the way you teach sir!
thanks !! :)
Hey adrian.. The way you teach any networking topics is amazing.. Do you have any plan to launch a full networking course.. will be a great help to students like me and also who want to change their domain to cloud 🙏🙏
The advanced networking specialty is close to completion :) learn.cantrill.io/p/aws-certified-advanced-networking-specialty !!
@@LearnCantrill In your opinion, how much networking knowledge one should have to go into cloud architecture? Would you say CCNA level is sufficient or maybe a person should be at CCNP level, or one would manage with Netywork+ ?
Thanks.
by the way, super cool videos and teaching style. Love the UK northern accent :-) miss it here, down under :-D
oh boi... this is mind boggling ... I am not good with networking but this seems pretty advanced. I wonder if this is relavant for SAA course... i am planning to come back to this one again...watched multiple times but i guess my brain firewall is not accepting inbound connections ;)
Keep at it.
Shouldn't the EtherType be after the VLAN tag in the tagged frame, as per the standard?
Will you come out with a aws security specialty course anytime soon?
at some point yeah - in my view its the least difficult and least valuable of the specialty certs - so I'm looking at it towards the end of the specs.
almost finished.
Hey , is there a video which is supposed to go prior to this in the playlist? It seems to reference previous material.
can you be specific ? videos reference other videos for sure but without knowing what you refer to, it's hard to answer.
The segment on physical segmentation. It says it has been covered in the previous lessons on technical fundermentals and it didn't make much sense to me.
I think the problem was that I've started in the wrong place. I'm coming into this totally new so I'm starting with the network fundermentals instead and will move on to technical fundermentals when I understand those.
i cover that in the networking fundamentals ruclips.net/p/PLTk5ZYSbd9Mi_ya5tVFD8NFfU1YZOyml1
07:42 , Shouldn't that be called 802.1AD instead of 802.1Q?
nope ... 802.1AD uses nested vlan tags, i.e nested 802.1Q vlan tags.
10:54 this is incorrect. Access ports do not tag vlans. When the frame "exits the access port" no tagging occurs, the vlan ID membership is simply retained. Vlan tagging only occurs at trunk links where the dot1q header is added an/or removed. Access ports simply associate the data with vlan ID membership.
keep in mind i'm trying to explain this in a way which makes sense for beginners. The way i've always been taught (and i think it helps) is that frames as they leave an access port are tagged with that port membership. That tag is removed, if they enter an access port of the same membership again. So while i appreciate your comment, i don't agree. The video is talking about 'exiting' an access port.
@@adriancantrill913 You can disagree with me all you want but at the end of the day that's just how 802.1Q tagging works. It's documented all over the RFC whitepapers. You'll find many other novice lessons like this on the internet commonly mistaking VLAN ID membership with VLAN tagging. I think it's especially important to get the terminology correct, especially for beginners, in order to avoid this very confusion in the future. In fact, this is the very reason they go so long thinking that because an access port is configured for vlan 10, that' its tagging vlan 10 when it is not. I understand that you say that youve always been taught that as frames leave an access port, that theyre tagged with that port membership. But again, this is incorrect. Just because a frame is exiting an access port it doesn't mean it's being tagged at all. If that frame that was exiting an access port was simply destined to another access port in that same broadcast domain on that same switch, there wouldnt be any tagging that would occur here. And no; no tag would be removed once it enters another access port on the same switch because an 802.1Q header was never added in the first place. Tagging does not occur between access ports whether it's leaving or exiting an access port (unless you specifically have a host connected to an access port that is sending 802.1Q frames which would be a very rare and unique use case). We need to be very clear about that. By it's very definition, "tagging" is adding a 4 byte 802.1q header to a frame and this only happens on trunk links. You're confusing the VLAN ID membership with the VLAN tag. The VLAN tag contains the VLAN ID. And this 802.1Q tag is added and removed ONLY on trunk links before it makes it to the destined access port. Therefore, no tagging of any kind occurs AT the access port. The switch simply uses the VLAN ID to create a VLAN tag to send the traffic accross it's trunk link if the traffic is not local to the switch. If the traffic is local to the switch, there's no tagging that needs to take place.
Here is the perfect example I found online with someone with the same confusion as you...the entire cisco community told him the same thing I am telling you.
community.cisco.com/t5/switching/confused-about-frame-tagging/td-p/951219
@@steelsteez6118 you seem to think i'm disagreeing with you on the technical details, i'm not. I've told you why i'm teaching this way, because i'm trying to help students understand things in steps. This is not an advanced lesson and in those advanced lessons im much more specific about when and where things are added. I know 100% how it works inside a switch, but sometimes for beginners you have to pain a picture in a certain way, even if slightly untrue to help the understanding of concepts. You see it in AWS all the time where things are presented one way at beginner level and then a correct overview is added at the advanced level. I appreciate your feedback, but im going to leave this as is.
coffee stain studios network o.o