1 00:00:00,620 --> 00:00:06,410 So what we'll do once again is remove the layer three information on switch one and make this the into 2 00:00:06,410 --> 00:00:07,730 VLAN routing device. 3 00:00:08,180 --> 00:00:11,180 Once again, this is not something you're going to want to do in the real world. 4 00:00:12,140 --> 00:00:15,680 It's just to show you what's happening in the background. 5 00:00:15,680 --> 00:00:24,110 So I'll remove the IP address from VLAN one, from VLAN two, and from VLAN 11. 6 00:00:28,930 --> 00:00:32,950 So show IP interface brief. 7 00:00:33,850 --> 00:00:43,990 No IP addresses are configured on switch one, so rather one won't be able to ping ten 1 to 4. 8 00:00:44,230 --> 00:00:44,500 Right. 9 00:00:44,560 --> 00:00:48,370 A one cannot ping rather for acting as a PC. 10 00:00:49,090 --> 00:00:52,030 So let's have a look at root of five and configure it. 11 00:00:52,830 --> 00:00:56,490 So in front of five interface f0/0 no shut. 12 00:00:58,930 --> 00:01:00,790 Well exit out of their interface. 13 00:01:00,790 --> 00:01:03,160 Fost Ethernet 001. 14 00:01:03,550 --> 00:01:05,349 This is creating a sub interface. 15 00:01:06,560 --> 00:01:13,550 If I try and configure an IP address directly on this interface, it's going to fail because it needs 16 00:01:13,550 --> 00:01:16,850 to know the 02.1 Q tagging. 17 00:01:17,420 --> 00:01:24,410 So encapsulation dot one key vlan one and this is the native VLAN. 18 00:01:25,100 --> 00:01:28,340 Now I'll be able to put an IP address on that interface. 19 00:01:28,460 --> 00:01:29,840 So do show run. 20 00:01:34,140 --> 00:01:39,600 No IP address is configured on the physical interface and IP address is configured on this sub interface. 21 00:01:40,050 --> 00:01:44,460 Sub interface one lets create one for two. 22 00:01:44,460 --> 00:01:47,220 So encapsulation 1q2. 23 00:01:48,120 --> 00:01:53,630 In other words vlan two IP address 10.12 2.254 24 00:01:55,590 --> 00:02:09,210 with the mask interface first Ethernet zero 0.11 Encapsulation dot one key VLAN number is 11 IP address. 25 00:02:09,210 --> 00:02:12,060 10.1 11 2.4. 26 00:02:15,430 --> 00:02:16,210 Show Run. 27 00:02:19,650 --> 00:02:23,040 So once again, no IP address configured on the physical interface. 28 00:02:23,550 --> 00:02:32,280 Sub interface one is in VLAN one, it's the native VLAN sub interface two is in VLAN two, it's using 29 00:02:32,280 --> 00:02:39,060 ED one Q sub interface 11 is in VLAN 11 using ADA 2 to 1. 30 00:02:39,060 --> 00:02:41,700 Q These numbers don't have to match up. 31 00:02:41,700 --> 00:02:45,420 It just makes more sense to do that, to keep things consistent. 32 00:02:45,630 --> 00:02:49,800 Now let's see if router one can ping right of for. 33 00:02:52,550 --> 00:02:55,970 Let's check if the traffic actually hits rather. 34 00:02:56,060 --> 00:02:59,660 Five debug ip icmp. 35 00:03:00,830 --> 00:03:02,750 Make sure it can ping its default gateway. 36 00:03:07,750 --> 00:03:08,950 Check some of your stuff. 37 00:03:08,950 --> 00:03:10,600 So show IP interface brief. 38 00:03:12,340 --> 00:03:14,470 Interfaces up, so that's good. 39 00:03:15,190 --> 00:03:18,030 Can the router ping itself? 40 00:03:18,040 --> 00:03:21,010 So ping tended 1.12254. 41 00:03:24,250 --> 00:03:26,350 Plan to camping itself. 42 00:03:27,880 --> 00:03:36,670 VLAN 11 camping itself can Ryder to ping the default gateway so first paying right of for camping road 43 00:03:36,670 --> 00:03:39,630 of four so traffic is going from here to here. 44 00:03:39,640 --> 00:03:42,070 Let's see if we can ping its default gateway. 45 00:03:46,580 --> 00:03:48,560 So let's do a Wireshark capture. 46 00:03:48,590 --> 00:03:49,730 See what's going on. 47 00:03:56,660 --> 00:04:00,890 So no traffic's arriving on this port, and that's probably an issue with this hub. 48 00:04:02,710 --> 00:04:06,370 So what I'll do now is save the configs on the devices. 49 00:04:08,910 --> 00:04:10,800 This looks like a genius three problem. 50 00:04:10,800 --> 00:04:14,850 And that's why sometimes you might want to use physical switches. 51 00:04:15,300 --> 00:04:20,670 So I'll save all the configs and then I will reboot. 52 00:04:21,690 --> 00:04:22,440 I'll stop. 53 00:04:22,440 --> 00:04:24,420 Genius three and started again. 54 00:04:26,410 --> 00:04:31,450 And then we can try again and see if it solves our problem. 55 00:04:32,290 --> 00:04:38,170 So I'm going to reboot everything and in the next video we'll continue to see if it solved the problem. 56 00:04:39,610 --> 00:04:46,660 Okay so after reboot writer one as an example is able to ping rather to. 57 00:04:46,750 --> 00:04:49,360 So that's this device pinging this device. 58 00:04:50,360 --> 00:04:54,860 If we do a capture on that link to write of five. 59 00:04:57,890 --> 00:04:59,450 And do the ping again. 60 00:05:02,130 --> 00:05:03,660 44 ICMP. 61 00:05:05,100 --> 00:05:12,300 What you'll notice is the pings received from router one on VLAN 11. 62 00:05:13,130 --> 00:05:16,970 And the reply goes back as VLAN two. 63 00:05:17,480 --> 00:05:23,570 So once again, here's VLAN 11 and the reply is going back as VLAN two. 64 00:05:24,750 --> 00:05:25,830 VLAN 11. 65 00:05:27,440 --> 00:05:34,700 Reply being VLAN two now I had some problems in junior three setting this up, so you may run into similar 66 00:05:34,700 --> 00:05:39,920 problems, but the moral of the story is that traffic from this PC is untagged here. 67 00:05:40,310 --> 00:05:43,430 It goes across as tagged hits this router. 68 00:05:43,430 --> 00:05:52,970 It does the entire VLAN routing and changes it to VLAN two goes tagged here back to the switch and untagged 69 00:05:52,970 --> 00:05:59,150 to PC to now typically once again you wouldn't want to do any of this. 70 00:05:59,180 --> 00:06:05,540 You would simply enable inter VLAN routing on switch one or switch two. 71 00:06:06,260 --> 00:06:12,740 In a separate video, I'm going to show you a more realistic real world topology and show you how to 72 00:06:12,740 --> 00:06:17,960 set up inter VLAN routing as well as HSP and spanning tree optimization.