1 00:00:00,980 --> 00:00:05,100 At the moment rather one acting is PC one can ping wrote a five. 2 00:00:05,240 --> 00:00:06,740 Acting is PC. 3 00:00:07,510 --> 00:00:08,720 All 10 of these debugs 4 00:00:11,810 --> 00:00:15,000 Let's have a look at some show commands. 5 00:00:15,020 --> 00:00:23,690 So first command on Rodda to show interface tunnel Zira tunnel zero is up up. 6 00:00:23,970 --> 00:00:25,560 The hardware type is tunnel. 7 00:00:25,830 --> 00:00:35,090 The IP address on the interface is tendered 1 to 3 to 1 slash 30 the encapsulation type is tunnel the 8 00:00:35,090 --> 00:00:40,960 tunnel source is forward wondered wondered one tunnel destination is forward one to two to two. 9 00:00:41,210 --> 00:00:47,370 The protocol and transport is GRV over IP version 4. 10 00:00:47,390 --> 00:00:58,050 Notice the MT you has been reduced for this interface because of the headers used in GRB the MT you 11 00:00:58,410 --> 00:01:05,190 force serial to slash zero or maximum transmission unit for interface to slash is zero. 12 00:01:06,120 --> 00:01:14,570 Is 5300 bytes but the MTUC for the GOP tunnel is 15:14. 13 00:01:14,800 --> 00:01:24,850 So 1 4 5 0 minus 1 5 1 4 gives us 36 bytes because of the additional headers used in Jari. 14 00:01:25,060 --> 00:01:27,400 The empty view is reduced. 15 00:01:27,400 --> 00:01:32,500 In other words only small packets can be transmitted across the serial link because of the additional 16 00:01:32,500 --> 00:01:38,550 headers added by Jeery originally we only have a single IP header. 17 00:01:38,750 --> 00:01:46,040 But now we have an additional IP header called the delivery header as well as the GOP header and we 18 00:01:46,040 --> 00:01:48,200 can see that by doing a shock capture 19 00:01:53,030 --> 00:01:57,320 it's going to capture traffic on cereal to slice one on Rodda three 20 00:02:01,160 --> 00:02:07,390 will send a ping from Rotto one acting as PC one two out of five acting as PC to 21 00:02:13,460 --> 00:02:14,450 the ping. 22 00:02:14,730 --> 00:02:20,320 I remember originally we would only have a single IP version 4 header with the payload. 23 00:02:20,510 --> 00:02:26,730 But now we have both the GOP header as well as the out of header or delivery header. 24 00:02:27,110 --> 00:02:32,540 So the original packet over here as received by Rodda to 25 00:02:38,130 --> 00:02:41,430 doesn't include the GOP headers. 26 00:02:41,550 --> 00:02:43,140 So when we do that ping again 27 00:02:49,630 --> 00:02:55,480 this is the first Itam interface on brought it to. 28 00:02:55,700 --> 00:03:04,310 We can see the ping message with the standard IP version for header and Ethernet header but when that 29 00:03:04,310 --> 00:03:12,310 goes across the serial interface no to a Cisco deal see we see the original header and payload. 30 00:03:12,540 --> 00:03:18,700 So there's the ping but notice once again the additional header. 31 00:03:18,790 --> 00:03:23,870 So we've got the delivery had a as well as the GOP header. 32 00:03:25,080 --> 00:03:33,120 So additional headers have been added when compared to the original packet because of that the empty 33 00:03:33,190 --> 00:03:34,790 view is reduced. 34 00:03:34,790 --> 00:03:43,480 You can only send a maximum packet size of 15 14 bytes because of the additional headers. 35 00:03:43,490 --> 00:03:51,820 So once again on serial to slash zero the empty use 5400 bytes. 36 00:03:52,320 --> 00:04:00,440 But on the tunnel interface it's 15 14 bytes because of the additional headers. 37 00:04:00,480 --> 00:04:08,290 You can also see something for mation by using the command show IP interface tunnel's 0 scrolling up 38 00:04:09,750 --> 00:04:16,760 just the command tunnel interface 00 is up up IP addresses tendered one to three to one slushed the 39 00:04:17,370 --> 00:04:22,990 broadcast is this him to use 14 seventy six bytes once again. 40 00:04:23,990 --> 00:04:30,640 Multicast reserved groups joined includes 3:58 0 0 10 which if you remember is the multicast group for 41 00:04:30,670 --> 00:04:31,840 your job. 42 00:04:32,150 --> 00:04:38,510 Your job is able to form a neighbor relationship across the tunnel interface in a very similar way to 43 00:04:38,510 --> 00:04:41,180 how you would format across a serial interface. 44 00:04:41,270 --> 00:04:49,040 Because this is a point to point link logically directly from one router to the other so as an example 45 00:04:49,040 --> 00:04:54,940 show IP choppy neighbor wrote it to has a neighbor relationship with Rob. 46 00:04:54,950 --> 00:05:03,200 For on this IP address and not on this IP address because the neighbor relationship is formed across 47 00:05:03,200 --> 00:05:04,610 the tunnel. 48 00:05:04,610 --> 00:05:08,140 Show IP GOP typology. 49 00:05:08,420 --> 00:05:16,960 We have learnt a route 10 1 2 0 0 via 10 1 3 2 through tunnels 0. 50 00:05:17,240 --> 00:05:21,080 And once again no one is able to ping Route 5. 51 00:05:21,230 --> 00:05:26,840 Acting as a PC when we do a trace to 10 1 to 2. 52 00:05:26,900 --> 00:05:35,540 Notice the trace goes to Rodda to then to route a for through the tunnel and then to roll a 5 route 53 00:05:35,560 --> 00:05:43,040 3 is not seen at all in the trace because logically routed to is directly connected to a fault in the 54 00:05:43,040 --> 00:05:44,060 same way. 55 00:05:44,240 --> 00:05:47,230 Wrote a 5 when tracing to 10 one on one. 56 00:05:47,480 --> 00:05:54,990 Since the traffic to rot for then logically to rockety and then to run a one.