If we only have 1 vlan's traffic going across a connection between 2 switches, and it's not the native vlan we need to create an access port (or trunk if desired) but if it is 1 vlan, and that is the native vlan on both devices, we can just not do anything and traffic will successful traverse the connection yes?
Thanks for Vid. How do computers on each VLAN get their IP addresses? Is each switch doing DHCP? Are they setup to get IPs from the router... and then the router is able to tell that the computer is on a separate switch VLAN?
In this scenario, they were static ip addresses. In the case of a router doing DHCP, whatever access port the router is connected to, the VLAN configured to that port will come into play. The router will give out ip addresses to the machines connected to the other ports that are also configured to the same VLAN as the Router's port.
Previously, Cisco utilized both ISL and dot1q as means to tag frames across a trunk. ISL (Inter-Switch Link) is a Cisco proprietary protocol that is no longer used but was the default on older switches. Dot1q is what other vendors use and is a preferred method to encapsulate a trunk, we just need to specify it on some older models of Cisco switches.
If you were only to do that in this instance spanning tree would block the port as inconsistent. If you were to, however, set the native vlan on the trunk port to match the access port it would technically work as the voice vlan = tagged and the access vlan = untagged so the switch would know what belongs to each vlan.
Quick question, how do I know if a managed vlan capable switch supports trunk ports??? Or is it a thing all vlan switches do?? Is there a $200 range switch that you would recommend that would support it. This is mainly for my own experimentation. Again thx.
I would imagine that most switches that support VLANs would support VLAN tagging in some way. If you want a cheap switch to play around with, look into used Cisco equipment such as a 3750 switch.
As long as you turn on "ip routing" and the SVI or interface VLANs are on the same switch you will be able to ping between VLANs (if from PC it must have correct default gateway set). If the SVIs were on different switches you would need to set up static or dynamic routing to ping between the VLANs.
As long as you turn on "ip routing", given the switch is layer 3 capable, and SVI or interface VLANs are on the same switch you will be able to ping between VLANs (if from PC it must have correct default gateway set). If the SVIs were on different switches you would need to set up static or dynamic routing to ping between the VLANs.
One of the easiest and straight forward videos on TH-cam for trunks/access configurations. This channel is severely underrated
for real, i had problems understanding trunks ,now im good
1:45 seconds into this video and it is already perfectly explained.
Thanks for this video, I'm brushing my networking skills up after not touching it for years and you've really helped!
You made this so easy to understand, much appreciated.
Dude needs to come back!
Fantastic video. Told us exactly what we needed to know without any extra. Thank you!!
This was the best video...sweet and short with clear explanation thank you...
Very clear and easy explanation. Thanks a lot :)
Cheers mate, very clear explanation. Thank you.
Thank you! Very clear and easy to understand.
great video help me learn about this before class! i hope to see more videos soon
Best possible explanation thx!
Niiiice ❤ I like how you get straight to the coding 😂
Whats the difference between switchport mode access and switchport access VLAN 10? Why do I need to choose one or the other?
thank you for your efforts
Awesome video! Thanks for sharing!
If we only have 1 vlan's traffic going across a connection between 2 switches, and it's not the native vlan we need to create an access port (or trunk if desired) but if it is 1 vlan, and that is the native vlan on both devices, we can just not do anything and traffic will successful traverse the connection yes?
Loved it, Thanks 👍
Nice and easy explanation, thank you much!!!
Awesome video, Thank you!
very well explained video. thanks !
thank you for the clear explanation
clean explanation!
great simple explanation
Great video, helped me a lot. Can you say how do you use the powershell like this, with multiple devices in one window?
I used the Windows Terminal, you should be able to search for it in the Windows store.
@@lezunetworking thanks :)
منننووروررر للنم يا زعيييم suiiiiiiiiiiiiiiiiiiii
Tnx bro
Thanks 👍
Got it, cheers 👍 😁
Thx!
Thanks for Vid.
How do computers on each VLAN get their IP addresses? Is each switch doing DHCP? Are they setup to get IPs from the router... and then the router is able to tell that the computer is on a separate switch VLAN?
In this scenario, they were static ip addresses. In the case of a router doing DHCP, whatever access port the router is connected to, the VLAN configured to that port will come into play. The router will give out ip addresses to the machines connected to the other ports that are also configured to the same VLAN as the Router's port.
man i was wondering why my frkn ovs vlans could not reach my router and then i noticed that the port type was set to intern
Thanks man!
Sir can i ask? What is the purpose of encapsolation that you put on configuration after switchport mode trunk
Previously, Cisco utilized both ISL and dot1q as means to tag frames across a trunk. ISL (Inter-Switch Link) is a Cisco proprietary protocol that is no longer used but was the default on older switches. Dot1q is what other vendors use and is a preferred method to encapsulate a trunk, we just need to specify it on some older models of Cisco switches.
Do you need to add switchport trunk allowed vlan 10, 20? If you dont add it, shouldnt it just allow all vlans between the 2 switches?
What happens if you keep gi0/3 an access port and have vlan 10 the access vlan and vlan 20 the voice vlan...would it work?
If you were only to do that in this instance spanning tree would block the port as inconsistent. If you were to, however, set the native vlan on the trunk port to match the access port it would technically work as the voice vlan = tagged and the access vlan = untagged so the switch would know what belongs to each vlan.
@@lezunetworking good call, both would try to be designated forwarding...turn off STP? Lol
Quick question, how do I know if a managed vlan capable switch supports trunk ports??? Or is it a thing all vlan switches do?? Is there a $200 range switch that you would recommend that would support it. This is mainly for my own experimentation. Again thx.
I would imagine that most switches that support VLANs would support VLAN tagging in some way. If you want a cheap switch to play around with, look into used Cisco equipment such as a 3750 switch.
@@lezunetworking thank you so much!!
can the computer from vlan 10 ping the computer from vlan 20?
As long as you turn on "ip routing" and the SVI or interface VLANs are on the same switch you will be able to ping between VLANs (if from PC it must have correct default gateway set). If the SVIs were on different switches you would need to set up static or dynamic routing to ping between the VLANs.
U dindnt show ping from vlan 10 pcs to vlan 20 pcs, doest it work ? Its different subnet!!!
u show ping from pcs that are connected in vlan 10 correct
As long as you turn on "ip routing", given the switch is layer 3 capable, and SVI or interface VLANs are on the same switch you will be able to ping between VLANs (if from PC it must have correct default gateway set). If the SVIs were on different switches you would need to set up static or dynamic routing to ping between the VLANs.
lol at that typing speed
Nice Video but music annoying af
Slowdown