So what we'll do once again is remove the layer three information on switch one and make this the into
VLAN routing device.
Once again, this is not something you're going to want to do in the real world.
It's just to show you what's happening in the background.
So I'll remove the IP address from VLAN one, from VLAN two, and from VLAN 11.
So show IP interface brief.
No IP addresses are configured on switch one, so rather one won't be able to ping ten 1 to 4.
Right.
A one cannot ping rather for acting as a PC.
So let's have a look at root of five and configure it.
So in front of five interface f0/0 no shut.
Well exit out of their interface.
Fost Ethernet 001.
This is creating a sub interface.
If I try and configure an IP address directly on this interface, it's going to fail because it needs
to know the 02.1 Q tagging.
So encapsulation dot one key vlan one and this is the native VLAN.
Now I'll be able to put an IP address on that interface.
So do show run.
No IP address is configured on the physical interface and IP address is configured on this sub interface.
Sub interface one lets create one for two.
So encapsulation 1q2.
In other words vlan two IP address 10.12 2.254
with the mask interface first Ethernet zero 0.11 Encapsulation dot one key VLAN number is 11 IP address.
10.1 11 2.4.
Show Run.
So once again, no IP address configured on the physical interface.
Sub interface one is in VLAN one, it's the native VLAN sub interface two is in VLAN two, it's using
ED one Q sub interface 11 is in VLAN 11 using ADA 2 to 1.
Q These numbers don't have to match up.
It just makes more sense to do that, to keep things consistent.
Now let's see if router one can ping right of for.
Let's check if the traffic actually hits rather.
Five debug ip icmp.
Make sure it can ping its default gateway.
Check some of your stuff.
So show IP interface brief.
Interfaces up, so that's good.
Can the router ping itself?
So ping tended 1.12254.
Plan to camping itself.
VLAN 11 camping itself can Ryder to ping the default gateway so first paying right of for camping road
of four so traffic is going from here to here.
Let's see if we can ping its default gateway.
So let's do a Wireshark capture.
See what's going on.
So no traffic's arriving on this port, and that's probably an issue with this hub.
So what I'll do now is save the configs on the devices.
This looks like a genius three problem.
And that's why sometimes you might want to use physical switches.
So I'll save all the configs and then I will reboot.
I'll stop.
Genius three and started again.
And then we can try again and see if it solves our problem.
So I'm going to reboot everything and in the next video we'll continue to see if it solved the problem.
Okay so after reboot writer one as an example is able to ping rather to.
So that's this device pinging this device.
If we do a capture on that link to write of five.
And do the ping again.
44 ICMP.
What you'll notice is the pings received from router one on VLAN 11.
And the reply goes back as VLAN two.
So once again, here's VLAN 11 and the reply is going back as VLAN two.
VLAN 11.
Reply being VLAN two now I had some problems in junior three setting this up, so you may run into similar
problems, but the moral of the story is that traffic from this PC is untagged here.
It goes across as tagged hits this router.
It does the entire VLAN routing and changes it to VLAN two goes tagged here back to the switch and untagged
to PC to now typically once again you wouldn't want to do any of this.
You would simply enable inter VLAN routing on switch one or switch two.
In a separate video, I'm going to show you a more realistic real world topology and show you how to
set up inter VLAN routing as well as HSP and spanning tree optimization.