1 00:00:01,080 --> 00:00:06,110 Now before we can figure out tunnel's we need to make sure that the tunnel endpoints points have connectivity 2 00:00:06,260 --> 00:00:07,340 to each other. 3 00:00:07,340 --> 00:00:09,390 So Ratatouille should be able to ping a. 4 00:00:09,620 --> 00:00:11,080 And vice versa. 5 00:00:11,420 --> 00:00:17,420 In this example I'm going to set up the tunnel from the serial interfaces so logically it looks like 6 00:00:17,420 --> 00:00:25,430 we have this separate tunnel interface but the tunnel is actually configured from serial 020 to serial 7 00:00:25,430 --> 00:00:26,860 020. 8 00:00:27,250 --> 00:00:36,410 So router 2 can be paying for that one two to two yes we can and on Radio 4 Kemy paying for that wonder 9 00:00:36,430 --> 00:00:37,230 one to one. 10 00:00:37,420 --> 00:00:42,080 Yes we can now ping uses a different protocol to Geo re. 11 00:00:42,280 --> 00:00:49,500 So you need to confirm that you have connectivity using GRV from this interface to this interface. 12 00:00:49,780 --> 00:00:56,110 But for the moment we've used ping as our initial test to ensure that we have basic connectivity so 13 00:00:56,110 --> 00:01:04,460 to configure a tunnel you go convert the interface tunnel and you specify a number I'm going to choose 14 00:01:04,460 --> 00:01:06,510 0 to keep it simple. 15 00:01:06,740 --> 00:01:11,990 But as you see there's a wide range of HTML numbers that you can choose from tunnel's 0 and this example 16 00:01:11,990 --> 00:01:19,250 has gone down the tunnel interface will only come up if we have IP connectivity to the tunnel destination 17 00:01:19,640 --> 00:01:21,980 which we still need to configure. 18 00:01:22,020 --> 00:01:29,280 But first let's configure an IP address on the tunnel and I'm going to configure this as a slash 30 19 00:01:29,520 --> 00:01:34,500 network and once again we're going to use a private IP address. 20 00:01:34,740 --> 00:01:40,440 So we're going to be sending traffic across the Internet using private IP addresses but it'll work because 21 00:01:40,440 --> 00:01:44,220 Rodda 3 is going to route traffic based on the hour ahead. 22 00:01:45,520 --> 00:01:53,560 Or as described in the OR if he is the delivery header so the GRC header and payload packet is not going 23 00:01:53,560 --> 00:01:57,030 to be read by the Internet routers. 24 00:01:57,050 --> 00:02:03,130 They are simply going to ratchet traffic based on the delivery header. 25 00:02:03,260 --> 00:02:04,960 We need to specify the tunnel mode 26 00:02:08,070 --> 00:02:15,430 notice multiple options are available but we're going to use Chiari and IP version 4 that is actually 27 00:02:15,430 --> 00:02:16,060 the default. 28 00:02:16,060 --> 00:02:22,600 So when we look at the tunnel interface you'll notice that command doesn't display because that is once 29 00:02:22,600 --> 00:02:24,840 again the default tunnel mode. 30 00:02:25,210 --> 00:02:31,880 You don't need to specify the tunnel source now just the tunnel command gives you multiple options. 31 00:02:31,940 --> 00:02:38,390 We've already chosen mode but now we will select the source of the tunnel. 32 00:02:38,490 --> 00:02:41,670 You can choose a physical interface or not address. 33 00:02:41,700 --> 00:02:46,510 In this example I'm simply going to choose IP address and hit enter. 34 00:02:46,780 --> 00:02:55,010 The tunnel is going to originate from this IP address and it's going to go to a destination for one 35 00:02:55,010 --> 00:02:56,990 or two to two. 36 00:02:57,050 --> 00:03:04,790 In other words Rodda for as you can see the tunnel has now come up and that's because we have IP connectivity 37 00:03:05,150 --> 00:03:08,990 from this router to the destination of the tunnel. 38 00:03:09,290 --> 00:03:13,440 The tunnel however is not going to work because we have to configure the other side. 39 00:03:13,670 --> 00:03:22,490 So comfy interface tunnels zero on route for IP address tend toward one or three to. 40 00:03:23,390 --> 00:03:26,170 Keep it in the same subnet. 41 00:03:26,280 --> 00:03:30,900 So the Saudis once again 10 to 1 2 3 to 1 42 00:03:34,020 --> 00:03:44,490 and the side is 10 to 1 2 3 to 2 sit back and write a for tunnel mode GRV might. 43 00:03:44,600 --> 00:03:50,140 You don't have to specify that come on because it's the default but I'll do it here for completeness 44 00:03:52,670 --> 00:04:00,770 tunnel sources for Wonder 1:58 tunnel destination is Forder wonder wondered one and hopefully what we 45 00:04:00,770 --> 00:04:10,820 should see is that that tunnel comes up and there it does show IP interface brief shows us that we now 46 00:04:10,820 --> 00:04:16,420 have a tunnel interface that's up up on the side and on Rodda to 47 00:04:19,350 --> 00:04:26,190 the tunnels up on router to send router to we should be able to ping wrought a forest tunneling to face 48 00:04:26,250 --> 00:04:27,590 which we can. 49 00:04:27,720 --> 00:04:31,480 So no just we pinging that one two three to two. 50 00:04:31,770 --> 00:04:39,150 But rodded 3 has no visibility of that route. 51 00:04:39,270 --> 00:04:44,190 And that shows quite nicely that rotisseries able to route traffic from this IP address to the IP address 52 00:04:44,640 --> 00:04:47,460 without actually reading those IP addresses. 53 00:04:47,630 --> 00:04:53,110 It's simply writing traffic based on the source to the destination. 54 00:04:53,180 --> 00:04:59,930 So let's prove that I'll start a capture here I'm going to start a capture using HDL C because the default 55 00:04:59,930 --> 00:05:14,030 encapsulation is HDL C on Siska serial links on interface serial to one on router three. 56 00:05:14,070 --> 00:05:21,540 So at the moment we see CTP we see some other the messages but what I'll do is do a ping from Rodek 57 00:05:21,540 --> 00:05:23,440 to Toronto for again. 58 00:05:25,400 --> 00:05:27,530 And there you go there's an ICMP messages 59 00:05:31,390 --> 00:05:39,430 so you can see it's an ICMP from 1 2 3 to 1 to 10 to 1 or 3 to 2 The lead to encapsulation is HDL see 60 00:05:39,690 --> 00:05:44,280 the protocol used at least 3 is IP version 4. 61 00:05:44,420 --> 00:05:49,580 And notice the source and destination IP addresses for that wondered wondered one destination is 4 1 62 00:05:49,580 --> 00:05:51,270 2 2 to 2. 63 00:05:51,290 --> 00:05:55,570 In other words this router is sending traffic to this router. 64 00:05:56,310 --> 00:06:04,170 Rotisseries going to route based on these IP addresses not on the IP addresses contained in the encapsulated 65 00:06:04,170 --> 00:06:07,670 packet at least for we can see Jari. 66 00:06:08,160 --> 00:06:17,400 So generic writing cancellation using IP version for and inside there we can see the source tendered 67 00:06:17,400 --> 00:06:21,860 one or three to one and destination of tendered one to three to two. 68 00:06:21,870 --> 00:06:31,490 In other words we've encapsulated an IP version for packet within an IP version 4 packet the original 69 00:06:31,760 --> 00:06:34,440 traffic was a pain. 70 00:06:34,790 --> 00:06:35,810 So there's the paying. 71 00:06:35,870 --> 00:06:42,320 And if we go to the next packet we can see the ping reply and kept isolated and not provision for with 72 00:06:42,320 --> 00:06:48,960 injury within our provision for within HDL see. 73 00:06:48,990 --> 00:06:56,230 So we've now successfully configured a tunnel from rodded to Toronto for I'll stop that capture in the 74 00:06:56,230 --> 00:06:57,450 next video. 75 00:06:57,790 --> 00:07:04,960 Will check whether one can ping wrote a five decimal Why shot captures and do some other tests.