1 00:00:01,020 --> 00:00:07,060 So rotted protocols include IP version for an IP version 6. 2 00:00:07,080 --> 00:00:14,820 These protocols are independent of each other and to illustrate that let's look at a simple topology. 3 00:00:14,970 --> 00:00:16,560 So he has a question for you. 4 00:00:16,920 --> 00:00:21,270 Are these routers able to ping each other. 5 00:00:21,320 --> 00:00:29,780 And the answer is yes and no there's a problem in the IP version 4 addressing structure in this topology. 6 00:00:29,810 --> 00:00:39,230 If these two interfaces have IP addresses of 10.0 wanted 2.1 slushed 24 and 10 dot 1.40 slash 24 they 7 00:00:39,230 --> 00:00:47,270 are in different subnets but have been configured on the same link so Rotto one and router two will 8 00:00:47,270 --> 00:00:51,440 not be able to ping each other using IP version 4. 9 00:00:51,680 --> 00:00:55,640 However IP version 6 has been correctly configured. 10 00:00:55,790 --> 00:01:02,900 So these two addresses are in the same subnet and Rotto one and Rodek two will be able to ping each 11 00:01:02,900 --> 00:01:05,660 other using IP version 6. 12 00:01:05,660 --> 00:01:15,050 The point is what one rotted protocol does is totally independent and separate from a nother rafted 13 00:01:15,200 --> 00:01:24,920 protocol raftered protocols such as IP version for an IP version 6 act and work independently of each 14 00:01:24,920 --> 00:01:31,010 other and use a different routing protocols in the networking world. 15 00:01:31,010 --> 00:01:33,970 This is often called ships in the night. 16 00:01:34,190 --> 00:01:40,190 In other words what one ship in the night is doing is different to what another ship in the night is 17 00:01:40,190 --> 00:01:40,940 doing. 18 00:01:41,150 --> 00:01:48,710 Granted protocols are independent of each other and do not rely on one another raptor the protocols 19 00:01:48,810 --> 00:01:53,200 use a different routing protocols as an example. 20 00:01:53,330 --> 00:02:02,900 OSPF a vision too is a routing protocol used in IP version for OSPF version 3 is a writing protocol 21 00:02:02,900 --> 00:02:11,570 used in IP version 6 different router protocols use different routing protocols and they act independently 22 00:02:11,570 --> 00:02:20,300 of each other even if one ranted protocol is broken other rafted protocols may still function they are 23 00:02:20,330 --> 00:02:25,140 two main ways that rats get added to the writing tables of rotas. 24 00:02:25,370 --> 00:02:32,180 The first ways to use study Grotz where an administrator manually adds a raft to the writing table and 25 00:02:32,180 --> 00:02:36,370 the second way is to use dynamic writing protocols. 26 00:02:36,440 --> 00:02:42,890 So with static routes you as the administrator are adding the roots to the writing table. 27 00:02:43,010 --> 00:02:47,690 The advantage of this method is that there is no overhead on the network. 28 00:02:47,720 --> 00:02:55,550 In fact there are no keeper lives or constant writing updates saved between routers up or running information 29 00:02:55,550 --> 00:03:03,720 protocol which is an older routing protocol sends its entire writing table every 30 seconds. 30 00:03:03,800 --> 00:03:10,520 So when using static routes rather than wrap that overhead is removed more modern routing protocols 31 00:03:10,520 --> 00:03:18,350 such as E.I. GOP and OSPF remove this constant updating that took place in Rupp every 30 seconds. 32 00:03:18,620 --> 00:03:25,580 But they still send haloes and keep lowlives on the network which consume bandwidth with static routes 33 00:03:25,700 --> 00:03:27,310 that is removed. 34 00:03:27,380 --> 00:03:34,820 But the major disadvantage of steady gruts is that you as the administrator have to update the writing 35 00:03:34,820 --> 00:03:42,110 table which could be a lot of work if you have a large network steady Grotz do not automatically take 36 00:03:42,110 --> 00:03:45,310 into account changes in the network use. 37 00:03:45,440 --> 00:03:54,020 The administrator would have to manually update the writing table on a router or multiple routers if 38 00:03:54,050 --> 00:03:55,730 a link went down. 39 00:03:55,730 --> 00:03:59,140 So the overhead is not on the network. 40 00:03:59,270 --> 00:04:04,590 The overhead is on you as the administrator to keep everything updated. 41 00:04:04,610 --> 00:04:12,560 Static Grotz do not scale when networks become large the amount of work involved in keeping routing 42 00:04:12,560 --> 00:04:20,300 tables updated manually is just too great especially when there are lots of topology changes. 43 00:04:20,300 --> 00:04:25,460 Static routes do not up date routing tables when it topology changes. 44 00:04:25,460 --> 00:04:26,920 In most cases. 45 00:04:27,080 --> 00:04:35,290 Now that being said it is possible these days to monitor IP addresses and for example to remove a rock 46 00:04:35,410 --> 00:04:36,810 from the writing table. 47 00:04:37,040 --> 00:04:42,830 If an IP address is no longer available so it's possible to implement some dynamic options with static 48 00:04:42,830 --> 00:04:49,810 routes but the overhead is still large and static routes are cumbersome in large networks. 49 00:04:49,970 --> 00:04:54,110 Now static Grotz are still used in a lot of networks today. 50 00:04:54,140 --> 00:04:58,240 The most common example is a default static route. 51 00:04:58,400 --> 00:05:08,690 Your home DSL or cable or fiber Rodda will typically have a default route to your service provider So 52 00:05:08,690 --> 00:05:13,100 your home router doesn't know about the rats on the Internet. 53 00:05:13,100 --> 00:05:17,550 It simply forwards the traffic to your ISP. 54 00:05:17,600 --> 00:05:25,190 A default rot in a road is writing table basically tells the Rodda when you don't have a specific network 55 00:05:25,310 --> 00:05:28,690 for traffic that you receive in your writing table. 56 00:05:28,910 --> 00:05:37,700 Simply send the packets to the router that's configured as your default gateway or gateway of last resort. 57 00:05:37,700 --> 00:05:44,270 So when you configure a default route on a router you are pointing it to another router which means 58 00:05:44,270 --> 00:05:51,140 that that router will simply send the traffic to that default gateway when it doesn't have a more specific 59 00:05:51,170 --> 00:05:53,530 route in the writing table.