Router on a Stick, Inter-VLAN Routing - Part 3
Вставка
- Опубліковано 2 січ 2025
- A quick tutorial on inter-vlan routing and router on a stick for the Cisco CCNA. The demonstration is done using Packet Tracer. In part 3 I configure the router's subinterfaces with IP addresses and the 802.1Q trunking protocol for each VLAN including the native VLAN.
Click here for part 2: • Router on a Stick, Int...
Click here for part 1: • Router on a Stick, Int...
Subscribe and visit me at danscourses.com
This is just fantastic. Thanks for all the tutorials. Your narration style is excellent and makes complex subjects simpler to understand. Thanks again.
Thank you for taking the time to make these vids, they are really straightforward and helpful
Dear Dan, thank you so much for all your tutorials help, I passed my ccna exam today. You've been so helpful, I really appreciated all your hard work on your A-Z CCNA prep videos.
This is the most complete series I could find on this topic. Nicely done!!
Thanks for the awesome vids!
For anybody curious, another way to check what the Native VLAN is for a trunked interface--if we assume fa0/1 as the trunk--is to issue the command:
S1# show interface fa0/1 switchport
=======================================
Name: Fa0/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: down
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 55 (Native)
The switch only needs an ip address and gateway address if you want to be able to remotely connect into it (to manage it) and once your in it you want to be able to connect outside of the subnet.
The native vlan is a vlan designed to be backwards compatible with older devices that do not support VLAN tagging
VLANs are to seperate traffic into different broadcast domains. The only way they CAN communicate is with a Layer 3 device (a router or Layer 3 switch). Even then you have to do similar configurations on that router or L3 Switch as what Dan did here for them to see each other. They don't HAVE to talk to each other. If they should or shouldn't depends on your network design.
Sir you are a legend..
Thanks for making all these videos and making it easy for us to understand..
Thank you for taking the time to make this videos. It's a great resource and it's greatly appreciated.
Thank you so much. U saved me. Tomorrow is my demo to show this all and It is just 7 hrs away from me.
Thank you.
it was great that you made that little mistake with the native vlan(77), because allow us to know how to troubleshoot that and fix it, without freak out in the exam or a job interview...Thanks for the videos they are very helpful.
Nice video. For the noobs like me who may have run into this: You also need to configure each of the 3 computers with the ip addresses indicated and their corresponding gateways. Took me a while to catch that.
Musembi Nzioki man I was pulling my hair until I found your comment. I keep forgetting I’m working with layer 2 switches that don’t allow intervlan routing
Me too 😂
I love your videos. Very real world and clearly explained. Great job!!!
Well explained Thanks! I've been preparing for my CCNA with Boson Netsim but found it's a little buggy and limited on commands due to Boson's IOS. Switched to running Boson's Labs by setting up the labs in Packet Tracer. Used these videos as a guide to completing my interVlan lab.
dear sir you explained very well. Now i understood the concept.
Dear Dan amazing video, but could you please explain the need for configuring default-gateway on the switch and encapsulation dot1Q 55 "native" command ???
5:45 what if your vlan number is higher than 255? that doesn't fit in an ip address?
Watching this tutorial in 2020😍Love it
Hi Dan,
Thank u for the time u give us.
Can we trunk native vlan without adding vlan 55 to the allowed trunk?
It seemed like we trunk the native Vlan 55 twice.
Thank you
That was very helpful. Thank you for making it easy to understand
Thank you for sheading light on a difficult subject
thank u great , please upload more videos, you concept is very good and very clear
it won't ping any other pc bcz each vlan have own network it only ping to router.. but it can also ping to other pc/vlan u need some further configuration and connection with router.
Hey Dan...all your videos are great...Just one question here...Should we not be able to telnet into the switch through the laptop???bcoz hen i am trying to its saying connection closed by foreign host??
Awesome videos. Very clear and concise.
This was a great video... my question is.. what brands of routers will work? Does it have to be a Cisco?
Nice. But on this scenario, is it possible to config the DHCP on the router. To provide dynamic IP Addresses to the PCs?
that's really amazing!!!!!!!!!!love love love love!!!!!!
Never get confused again!!!!!!!!
I did full tutorial, Am i supposed to be able to ping the Native VLAN from the other networks? (.10... .77)
why do we need to configure the allowed specific vlans in the trunk link between switch &router?? if we left it without configuration will it affect the link traffic?
Did you configure your vty ports on the switch to allow access?
Hi thank you, I'd appreciate if you could answer this, does the default gateway of each PC need to be set to the address of tge sub interface?
Thank you for an explanation on this interesting topic.
It was very informative and i appreciate your help.
thank you so much for uer answer .. because i confused when i did the same thing in video and i found the vlans ping each other .. So previously i thought that vlans shouldn't communicate with each other ..
Thank you for the explanation, it helped me understand the routing part
the ip addresses for subinterfaces on the router - are they some new addresses that dont matter much or are they somehow connected to addresses of each VLAN? I mean do I just come up with some random address or does it have to be somehwo specific.
pls explain about passive interface and active interface on routers
Very descriptive. The best for beginners :-)
Why do you allowed vlan 1??
If you allowed in trunk native vlan 55, the native vlan 1 is only in the switch in the trunk vlan 1 is vlan 55.
How can you make static routes across more than one router WITH vlans spreading through out the routers on the other end?
I noticed that routing is working fine even If I didn't put that last configuration 'native' when configuring encapsulation for the sub-interface 0/0.55 of the router! Any explanation?
From my experience native vlan mismatch does not necessarily stop routing from working, ... but it does create annoying console messages.
Wow! Thanks for the quick response Mr. Dan. Your videos are great.
Thanks, much appreciated.
hey man, thanks for this video helped me a lot :)
What version of packet tracer are you using?
why not use interface range fa0/1-5 to do the configs instead of manually configuring mode access yade yade ya on each port??/
because configuration is not same for all interfaces
looks the same to me for what i saw
unless i missed a part thats diff
Millers Tutorials each port have different vlan assigned to it.
Millers Tutorials i could have used in below sense
Switch(config)#interface range fastethernet0/1 - 20
Switch(config-if-range)#speed 100
Switch(config-if-range)#duplex full
true
your videos are amazing!
i have a question sir.. is it the VLANs shouldn't contact each other ? or they have to ?
absolutely!
I had check all configuration of router and switch. It is also right. But i cannot ping the different VLANs
I think it's because dot1q encapsulation isnt enabled on the switch trunk?
192.168.10.1 brofist for you! This helped me a lot thanks!!!
I actually love you, thanks!
Will this work for all vlans on different floors and switches? Also would using VTP effect the configuration?
What was the point for the VLAN 55 if it hasn't been physically connected?
Awesome tut, thanks very much :D saved my bacon for my uni assignment! ^_^
You are the best bro
why to set a default gateway for a switch??without we generally ping between two different networks
with router gateway being enabled on end devices.so can we skip the gateway setting on switch or is it mandatory
I think he said that up so that the Management PC i.e., the one on the VLAN 77 can telnet or ssh into the switch for Management purposes. However, he hasn't configured telnet on it.
Am i need to set up the default gateway in each VALs?
can you show a configuration with a router on a stick with one switch and multiple vlans on the switch, ip addresses ceated with vlsm subnetting. My subinterfaces keeps showing conflict with the first subinterface.
Example
Router(config-subif)#ip address 172.16.0.1 255.255.0.0
Router(config-subif)#int gig 6/0.20
Router(config-subif)#ip address 172.16.1.1 255.255.0.0
% 172.16.0.0 overlaps with GigabitEthernet6/0.10
Router(config-subif)#
Do you have any tutorials for GNS3?
Hi,
Thanks for all the video's, they are very helpful.
At the start of this example there where 3 switches
running into one router on a stick.
Could you point me to a video of this please.
Or explain how to add extra switches to this example.
Thanks
Ever find any info on this?
Great tutorial, thank you very much!
According to this diagram, can i get ping response 77.2 (Switch IP) from Cisco Router???
Many many thanks for your great help!
Great series with really good instructions.
Do have 1 questions though.
If you wanted to assign a management IP address to the router (192.168.77.3 for example). How would you go about doing this?
I've tried:
interface fa0/0
Ip address 192.168.77.3 255.255.255.0
but get an error of "IP overlaps with FA0/0.100.
I also tried simply SSHing to 192.168.77.1 but that times out.
it is a wonderful lesson, i like it all!!
Is there any tutorial about Layer 3 switch?
Excelente leccion! Muchas gracias, gran ayuda!
can anyone pls tel me what is the use of creating the vlan interface 77 ???
i didnt got the point of creating it ?
Really helpful to understand thank you very much
Great videos. Thanks
you can't have another network on the same interface regardless if tis sub inf or not (your gigabit6/0, physical interface already configured with the same network address and your trying the same network address on a sub-interface of the interface 6/0 ND therefore ultimately you will get this overlapped error message. leave the physical interface blank and configure the sub interface instead.
So how come none of the vlans on the router do not have ip addresses? I did everything here and it shows the vlans on my router as administratively down/with no ip
I can only ping the gw
Everything works, just wondering why if it is replicating why it doesn't show the ip for vlans on router
thanks
Now how we can have access from one of the PC to cloud? I have configure router fa0/1 with DHCP which would be uplink to my cable modem. but I am not able to go online from any VLAN. I am talking about my lab.. I configured one real router 2431 and switch 3650 and create same vlan like ur video class.
+Munir Chowdhury I think that packet tracer doesnt support going to the world wide web...
I did this in packet tracer and i cannot ping the router from my switch and vice versa
thanks how do i tellnet into the mangement vlan
I configured the router and switch like you. But I can't ping different vlan
it won't ping any other pc bcz each vlan have own network it only ping to router.. but it can also ping to other pc/vlan u need some further configuration and connection with router.
Very well done
How u doing son u been doing ok love u
How, and what are the steps?
you forgot Telnet or ssh at the mgt vlan??
WHY the PC in MGMT VLAN 77 is able to ping ALL other PCs in VLAN 10-30? They are in different VLANs, cmon? WHY THIS IS HAPPENING?
becouse encapsulation on router port ... :)
very useful.....thank you very much~~~
million thanks, its really help !! ^_^
Please give us the date of sale
you are amazing !
that native vlan 55 won`t work. if you had configured a client without any vlan`s and try to ping that 55 native - you would not succeed. the native vlan between the switch and the router MUST stay at default #1. the only time you can change the native vlan is when going from switch to another switch, then you can do whatever native vlan you want. between a switch and a router it must stay 1
+willow klan it works for me
+Atzeni a I`ll try to explain that a little better:
if you are a native vlan 55 and you come untagged to the router, the router will first search the physical interface and if there is no match over there - it will search for the "native" statement in one of his sub-interfaces. try to configure this 55 sub-interface on a physical interface and you`ll see it works just fine
but if you are at native vlan 1 and you come to the router untagged - the router WILL NOT search the physical interface at all. it will only search in his sub-interfaces
for example, you are at 192.168.99.100 and your native vlan on the switch is 1. because you don`t belong to any specific vlan you are by default vlan 1. so leaving the switch (which it`s native vlan is 1 as mentioned) you supposedly do not have to configure a sub-interface, you are untagged, so you should be able to address the physical interface (as you did when you were 55) - but you`ll see you won`t be able to. you will have to create a sub-interface with the native statement ALTHOUGH you are travelling untagged.
that is why there can be no possible way you were vlan 1 and successfuly pinged a vlan 55 native - the frame would come with the "vlan 1" tag to the switch and there it will see that the native is 55, so it will send the frame tagged as usual. the frame would enter the router as vlan 1 and there would be no sub-interface to welcome him aboard. thus, the frame would be dropped.
try it and see it`s true.
Thank you!
man can't believe how many Student out there this means hard to find a job
compitation
Thank you thank you
Thnx man!
work job
thanks!
dzieki wielkie POZDRAWIAM (PL)
thanks bud
I enjoy your videos but please use a mic filter
do sh whatevr less ctrl c's
Thank you!