WEBVTT 00:00.860 --> 00:02.210 Give VPN with OSPF. 00:03.290 --> 00:03.590 Okay. 00:04.790 --> 00:07.610 Let's configure the tunnel first before doing any routing. 00:08.000 --> 00:08.900 I'll go to R1. 00:09.950 --> 00:12.680 This is my hub, so let's do it from here. 00:12.980 --> 00:14.990 What are the configurations I need to do on the Hub now? 00:14.990 --> 00:17.630 You should be experts on this interface. 00:18.320 --> 00:23.750 Channel zero then IP address 192 168 .1.1. 00:25.870 --> 00:31.840 Another source is serial zero zero tunnel destination. 00:32.950 --> 00:34.450 No tunnel known. 00:34.450 --> 00:35.320 Yes. 00:35.410 --> 00:36.910 Nice tunnel mode. 00:39.310 --> 00:41.890 Multi point, right? 00:44.470 --> 00:45.910 That's the first one that we use. 00:46.570 --> 00:47.350 That's the normal one. 00:48.220 --> 00:48.460 IP. 00:49.210 --> 00:52.750 IP and IP network ID. 00:54.130 --> 00:59.650 So we need to map anything in the beginning. 00:59.650 --> 01:01.870 No, let's just let them come and register. 01:05.140 --> 01:05.800 That'll be one. 01:07.270 --> 01:10.150 I'll do the same on the other hub, but this becomes R2. 01:15.190 --> 01:20.290 Right becomes that too then spoke. 01:22.140 --> 01:32.370 Interface Channel zero IP Address 1921681.3 then down source remains the same. 01:34.940 --> 01:44.570 Dalmore MultiPoint IP and network ID is ten. 01:52.320 --> 01:56.090 Mapping one 51.69. 01:57.200 --> 01:58.250 For now, it's enough. 02:16.290 --> 02:16.460 And. 02:20.040 --> 02:20.460 Not good. 02:21.600 --> 02:22.140 Let's try that. 02:27.500 --> 02:29.420 Karen is the Hapac, so let's record that. 02:29.810 --> 02:31.400 Before that, I want to see R1. 02:31.400 --> 02:32.950 Has he received all the mappings or not? 02:32.960 --> 02:35.790 Have people come and registered for HP? 02:36.170 --> 02:38.440 Three, four and five all have come registered. 02:38.450 --> 02:38.660 No. 02:38.660 --> 02:42.200 Mapping is incomplete, so everything seems okay right now. 02:42.200 --> 02:43.220 I will not do anything. 02:43.220 --> 02:44.750 I'll just keep my wireshark on. 02:46.580 --> 02:48.310 I can start capturing on R3. 02:57.340 --> 02:57.530 Right. 02:58.330 --> 03:05.740 That's being from R2 to R2, R3 to R4, because my spokes are R3 and R4 92 168 .1.4. 03:06.850 --> 03:07.210 Bingo. 03:07.210 --> 03:07.900 Successful. 03:10.890 --> 03:11.100 He. 03:13.730 --> 03:14.660 Now there's only one. 03:17.130 --> 03:19.280 Three, two, one, one, two, four, one. 03:20.910 --> 03:24.120 Our first reply should also be our first resolution request should be here. 03:25.930 --> 03:27.830 Them from the other side. 03:27.830 --> 03:30.080 Yeah I'm capturing arteries part. 03:30.230 --> 03:30.830 Should have a reply. 03:30.860 --> 03:31.090 Right. 03:31.220 --> 03:31.940 R3 will show me. 03:32.420 --> 03:32.720 Yeah. 03:35.610 --> 03:38.820 It has a request, only a request. 03:39.720 --> 03:42.120 And then it gets a reply from Ford. 03:43.680 --> 03:44.880 Ford doesn't send a request, 03:49.890 --> 03:51.420 but it has it resolved. 03:51.600 --> 03:53.550 But it is not sending it all. 03:53.970 --> 03:55.410 Alpha did not send the request. 03:56.430 --> 04:01.320 Let's let's again try this with your what do you call it, phase three. 04:02.300 --> 04:03.270 So we see it here. 04:03.330 --> 04:05.130 We'll see phase three if it goes both ways. 04:06.010 --> 04:10.790 So the redirect message and then it will trigger the delay. 04:11.220 --> 04:14.960 We'll see that before doing that. 04:14.970 --> 04:15.690 This is fine. 04:15.690 --> 04:17.250 Right now I want to do what? 04:17.610 --> 04:19.580 Internal networks to talk to each other. 04:19.590 --> 04:28.350 So for that, from the hubs perspective, I need to go to interface Channel zero IP, NTP map multicast 04:28.380 --> 04:33.210 to all the dynamically learned pairs, also to the spokes. 04:34.060 --> 04:42.940 I'll go and say IP interface Channel zero IP NTP map multicast to 150 .1. 16 dot. 04:44.560 --> 04:46.960 Why was this a public address? 04:46.990 --> 04:47.470 Another one. 04:47.920 --> 04:49.450 When we try to server, it's a one. 04:50.980 --> 04:54.550 When we type on the server, the server address is the 192. 04:55.090 --> 05:01.720 Yes, but why is this When you map what you're saying is if you are going to the private address of 05:01.720 --> 05:09.020 this, the public header should be IP map 192 168 1.1. 05:09.040 --> 05:15.440 If you are going to 192 168 1.1 the outside header destination should be one 51.16 dot. 05:16.690 --> 05:17.470 It's like this. 05:23.060 --> 05:33.620 It's like on my pocket is going from 192.1 68 .1. 2 to 1 92.168.1.1. 05:36.640 --> 05:36.940 Right. 05:37.510 --> 05:42.340 I'm saying if when I say map, map 182 and 68, 1.1. 05:42.340 --> 05:47.400 If the inside address, the private address that he's trying to go is 182 168 1.1. 05:47.440 --> 05:53.620 The outside header should be 151 dot 16 dot one source is already specified. 05:55.930 --> 05:58.870 So based on this I say this is the public address here. 05:58.870 --> 06:00.670 You're saying if it is multicast. 06:03.470 --> 06:04.340 Then send it to. 06:08.240 --> 06:09.770 151 dot 16 dot one. 06:11.600 --> 06:13.250 Understand the difference between the two. 06:14.390 --> 06:15.290 Just give me a second. 06:17.840 --> 06:17.980 Yep. 06:19.970 --> 06:20.330 Good night. 06:21.410 --> 06:23.660 Now, that's what I'm doing on this, folks. 06:23.870 --> 06:26.120 I'm saying all the multicasts should be sent. 06:27.030 --> 06:38.850 Its IP address every map multicast 151 dot 16 dot I'll have to run OSPF now before I run OSPF, I need 06:38.850 --> 06:44.700 to make sure that what I need to make sure that the tunnels go down and up. 06:48.740 --> 06:50.030 Right now I'm not using dual hub. 06:50.750 --> 06:53.150 I'll tell you why is the reason for that. 06:54.080 --> 06:54.770 It's single hub. 06:56.090 --> 06:58.370 I do have not I have not given him as the NHS. 06:58.400 --> 06:59.850 I have not pointed anything to it. 06:59.890 --> 07:00.440 R2 is just. 07:03.410 --> 07:04.700 That's what I'm explaining. 07:05.300 --> 07:05.960 I'll explain. 07:05.990 --> 07:08.810 It does work with dual hub, but you'll have to change certain things. 07:09.440 --> 07:10.790 You'll see that first. 07:10.790 --> 07:11.510 I'll go here. 07:12.080 --> 07:21.470 Router OSPF one network is 182 168 1.0 Area zero Network ten 000. 07:24.190 --> 07:26.870 Also area code. 07:27.070 --> 07:27.280 Three 07:30.820 --> 07:31.300 daughters 07:34.660 --> 07:35.560 use the same command. 07:41.690 --> 07:42.460 Area zero. 07:42.800 --> 07:44.330 Network ten 000. 07:54.400 --> 07:56.380 Copy this and paste this everywhere else. 08:03.590 --> 08:04.520 My neighbor is up right 08:07.430 --> 08:07.730 here. 08:07.760 --> 08:11.240 The neighbor is up, so I be best neighbors. 08:11.570 --> 08:15.710 My neighbor is up full from this end. 08:19.890 --> 08:21.930 Nothing from here. 08:21.930 --> 08:22.680 Only one is up. 08:22.680 --> 08:23.160 Let's check. 08:23.160 --> 08:23.460 Why? 08:23.640 --> 08:27.950 Show IP, OSPF Interface Tunnel zero. 08:27.960 --> 08:29.040 What is the network type? 08:32.410 --> 08:34.490 The input type is point to point. 08:34.510 --> 08:39.160 By default, you're running on top of what is the network type. 08:40.760 --> 08:41.930 This is money. 08:42.830 --> 08:45.230 And it's supposed to be. 08:47.100 --> 08:47.790 Point to point. 08:47.790 --> 08:49.770 See what network type is. 08:49.800 --> 08:53.460 Network type depends upon what is your layer two technology that you are running on. 08:55.050 --> 09:00.440 Depending upon the layer two technology that you are running on, right. 09:00.660 --> 09:04.130 We will consider it to be you're running on serial links right now. 09:04.140 --> 09:11.400 If if this was a broadcast link, if this was an Ethernet link, if he is an Ethernet here, it will 09:11.580 --> 09:15.090 it will move to Nvme and not broadcast nvme. 09:15.690 --> 09:19.740 But since it's a serial link, consider it to be a point to point link. 09:21.150 --> 09:21.990 When this works. 09:21.990 --> 09:24.690 See the problem with point to point is. 09:25.200 --> 09:33.870 Point to point can only have one neighbor in OSPF, one media for there has to be no in point to point. 09:33.900 --> 09:39.540 There is no elections for point to point has no elections. 09:39.570 --> 09:41.430 That is only in broadcast networks. 09:41.960 --> 09:43.380 For point to point means. 09:43.410 --> 09:45.480 On this link, only one end is connected. 09:45.480 --> 09:46.900 Only one router is connected. 09:49.570 --> 09:50.680 One point doesn't matter. 09:52.150 --> 09:53.290 That's what you see right now. 09:53.290 --> 09:57.250 These are point to point, right when you do your OSPF neighbors. 09:59.150 --> 10:00.350 The state is now. 10:00.920 --> 10:02.660 That's why the neighbor came quickly. 10:03.680 --> 10:06.620 Why do they not require any elections? 10:06.620 --> 10:08.270 Because they know that it's a point to point. 10:08.270 --> 10:09.350 Point to point means what? 10:09.380 --> 10:11.450 One point to another point. 10:12.740 --> 10:14.570 Will this work in this scenario? 10:15.380 --> 10:18.620 If it's point to point means R1 can only have one neighbor. 10:20.450 --> 10:23.240 Right now, R3 and R4 right now R1 is with whom? 10:24.770 --> 10:25.970 R1 and R3. 10:26.150 --> 10:28.140 R1 with R4 and R1 with R5. 10:28.160 --> 10:32.020 Neighbor will not form because it's a point to point link here. 10:35.480 --> 10:35.990 Exactly. 10:36.210 --> 10:36.750 Exactly. 10:37.340 --> 10:42.320 So what I'll do is I'll go to the hub and change the network type to point to multipoint. 10:42.650 --> 10:45.020 So this point will be a multi point link. 10:45.380 --> 10:48.710 It can cause, but from the spokes I'll keep them as point to point. 10:50.480 --> 10:51.890 For them it's okay. 10:52.010 --> 10:55.910 R4 is pointing to R1, R5 is pointing to R1, R3 is pointing to R1. 10:55.910 --> 10:58.830 They're all pointing to one neighbor for their from their side. 10:58.830 --> 11:03.870 Point to point is fine, but from the hub side it should be a multi point thing for OSPF. 11:03.900 --> 11:10.380 I'm not talking about the network as it is not OSPF treats it as a different thing. 11:11.560 --> 11:18.900 So I'll go to the Hub and change the type to what we're why is why he came up first. 11:19.530 --> 11:21.120 Whoever comes up first becomes the next. 11:22.710 --> 11:28.350 Now to do this, I'll go to R1 Interface Channel zero, IP, OSPF network type. 11:28.590 --> 11:30.150 I can have all of these different types. 11:30.150 --> 11:37.830 I'll choose point to, point to multipoint, point to multipoint. 11:39.150 --> 11:39.800 Change the type. 11:39.810 --> 11:41.070 The neighbor doesn't come up. 11:42.510 --> 11:43.560 It got detached. 11:43.590 --> 11:44.310 Delete it. 11:45.300 --> 11:46.560 Can you guess why? 11:51.530 --> 11:51.770 See. 11:54.230 --> 11:54.800 Exactly. 11:55.100 --> 11:55.760 Check this out. 11:56.420 --> 11:59.450 So IP, OSPF Interface Tunnel zero. 12:00.680 --> 12:02.780 What is your hello timer 30? 12:02.780 --> 12:09.320 And the moment you change your network type to point to multipoint, your hello timer also changes. 12:11.300 --> 12:15.010 And in OSPF to form, neighbors should have the same. 12:15.020 --> 12:15.220 Hello. 12:15.230 --> 12:15.580 Thanks. 12:17.270 --> 12:19.810 This is exactly why they brought it into routing in Switzerland. 12:20.930 --> 12:22.520 So these small little things. 12:23.210 --> 12:26.060 Now you change the network type, right? 12:26.060 --> 12:27.380 So you think it should work. 12:27.380 --> 12:30.560 But since hello timer was changed the other side. 12:30.560 --> 12:33.020 Let's check the hello timer on R3 show. 12:33.050 --> 12:35.390 IP, OSPF interface tunnel zero. 12:37.220 --> 12:42.650 Either I can either change it on all the spokes, make them as 30 or on the hub. 12:42.650 --> 12:43.430 Just on the hub. 12:43.430 --> 12:44.630 I'll have to change it. 12:44.660 --> 12:46.730 Interface Tunnel zero IP OSPF. 12:46.730 --> 12:47.390 Hello. 12:48.080 --> 12:48.410 Ten. 12:51.110 --> 12:52.930 That is calculated by itself. 12:52.940 --> 12:53.270 Normal. 12:53.300 --> 12:53.640 Yeah. 12:53.990 --> 12:54.620 Three times. 12:54.620 --> 12:56.630 The Hello neighbor is up. 12:59.850 --> 13:01.320 What about the other neighbors? 13:07.350 --> 13:10.140 So run section interface. 13:13.580 --> 13:15.230 So run for the first time. 13:19.550 --> 13:20.150 Oh, it's. 13:25.370 --> 13:28.640 I need to change the network type back again to show you because I was shut down. 13:33.880 --> 13:34.320 It it up. 13:34.770 --> 13:38.270 See if it becomes network. 13:38.450 --> 13:40.530 The default was point to point, right? 13:41.160 --> 13:43.230 If I change it to point to point, my neighbors will go down. 13:46.330 --> 13:47.290 I'll have one. 13:47.320 --> 13:48.970 She'll keep on flapping one. 13:49.000 --> 13:49.900 Then we'll go down. 13:49.900 --> 13:51.790 Then another one will come up, Then we'll go down. 13:51.790 --> 13:53.080 Then another one will come up. 13:53.560 --> 13:57.010 Then three will come up, then not four will come up. 13:57.040 --> 13:58.000 It'll keep on flapping. 13:59.590 --> 13:59.860 Right. 13:59.860 --> 14:05.440 Because it's unstable by R1 is point to point and all of the others are also point to point. 14:06.220 --> 14:08.260 So R1 is not accepting is getting one. 14:08.260 --> 14:09.070 Hello from here. 14:09.070 --> 14:09.730 One from here. 14:09.730 --> 14:10.600 One from here. 14:10.640 --> 14:14.860 They keep on flapping for this for you to fix it. 14:14.980 --> 14:18.160 Interface channel zero IP OSPF network point to. 14:22.390 --> 14:25.570 Changed to MultiPoint interface Channel zero. 14:25.570 --> 14:27.370 Check the hello timer again. 14:27.940 --> 14:28.930 The low is 30. 14:28.960 --> 14:30.340 Go back again to IP. 14:30.340 --> 14:31.000 OSPF. 14:32.230 --> 14:33.580 Hello to ten. 14:34.300 --> 14:37.900 The moment you do this, it will stabilize and everything will come back. 14:45.420 --> 14:48.420 Loading done loading done loading. 14:50.220 --> 14:50.820 Loading is done. 14:52.020 --> 14:57.120 IP route has all the routes. 14:57.900 --> 14:59.370 Two is not in the picture anymore. 14:59.520 --> 15:01.170 Can I play this with 10.2? 15:02.310 --> 15:03.660 Can I have dual hub in here? 15:05.010 --> 15:06.780 In this topology can I have dual hub. 15:10.760 --> 15:12.390 I can only have one half. 15:13.560 --> 15:15.990 In this case, I can only have one half. 15:16.380 --> 15:16.950 Correct. 15:17.610 --> 15:18.840 Why only one half? 15:21.790 --> 15:26.830 Because all my spokes are point to point, they can only point to one of the hubs. 15:28.210 --> 15:29.980 I could make them point to multipoint. 15:32.130 --> 15:33.060 That's phase three. 15:36.000 --> 15:37.830 So all of them will be point to multipoint. 15:37.860 --> 15:39.870 That is the final solution of the problem. 15:40.650 --> 15:42.180 Make everybody point to multipoint. 15:42.450 --> 15:43.140 Why this one? 15:43.710 --> 15:45.390 Because you can only have one point. 15:45.450 --> 15:47.670 Because my spokes are point to point, right? 15:48.540 --> 15:49.620 My spokes are what? 15:50.370 --> 15:51.870 My job is point to multipoint. 15:51.900 --> 15:54.090 If they are point to point, they can only point to one guy. 15:54.910 --> 15:55.080 Okay. 15:55.680 --> 15:56.670 They can only have one thing. 15:57.390 --> 16:01.320 So you see, there is no here in this case. 16:01.320 --> 16:04.550 No, These are separate links. 16:04.560 --> 16:05.400 One at a time. 16:06.630 --> 16:06.930 Right. 16:06.930 --> 16:10.170 Since they are point to point, they will all be pointing one place. 16:10.380 --> 16:19.030 So only 1.10 hub to hub where everybody is pointing. 16:19.050 --> 16:21.900 What I want you to see is check the routing table here. 16:26.100 --> 16:26.790 Then Not one. 16:27.240 --> 16:28.080 Then not four. 16:28.530 --> 16:29.190 Then not five. 16:29.190 --> 16:30.000 All through what? 16:33.090 --> 16:33.630 Phase one. 16:34.800 --> 16:35.250 All through. 16:35.430 --> 16:35.850 Phase one. 16:35.850 --> 16:41.400 If I think Trace route ten .5.5.5 with the source of ten .3.3.3. 16:42.240 --> 16:42.990 Goes through the hub. 16:45.180 --> 16:45.840 How can I make it? 16:45.840 --> 16:46.170 Spoke to. 16:46.170 --> 16:46.680 Spoke. 16:49.530 --> 16:50.070 Redirect. 16:50.070 --> 16:50.580 Shortcut. 16:52.140 --> 16:52.590 Redirect. 16:53.130 --> 16:53.540 Shortcut. 16:53.550 --> 16:54.390 Let's do that. 16:54.460 --> 16:55.310 Interface Tunnel zero. 16:55.320 --> 16:56.410 My wireshark is running. 16:56.430 --> 17:01.440 IP, NTP redirect and on the spokes. 17:04.230 --> 17:06.260 I shot. 17:12.600 --> 17:12.840 The. 17:17.090 --> 17:19.580 And both tabless. 17:22.070 --> 17:27.410 Basically what you're doing is whatever redirect you're getting, you're using that to send to trigger 17:27.410 --> 17:29.110 your resolution request. 17:31.400 --> 17:31.980 How's that? 17:32.540 --> 17:32.780 Yeah. 17:34.490 --> 17:34.840 Yeah. 17:35.720 --> 17:38.360 If you don't do it, doesn't have that. 17:38.540 --> 17:39.610 It doesn't have the full route. 17:39.620 --> 17:40.460 Its route is pointing. 17:40.490 --> 17:40.970 Towards what? 17:42.050 --> 17:42.560 Towards the hub. 17:44.130 --> 17:44.380 Yes. 17:44.600 --> 17:45.290 Yes. 17:46.910 --> 17:50.850 So you have to go to that table, get that information from there, and then move forward. 17:53.120 --> 17:53.650 From this. 17:55.310 --> 17:57.380 That's why self should be enabled for this. 17:58.250 --> 18:00.860 Yes, it should be there. 18:00.860 --> 18:04.840 If it doesn't, then it won't be able to, obviously. 18:05.750 --> 18:06.680 For that, Yes. 18:09.380 --> 18:10.480 I'll stand on an. 18:10.940 --> 18:11.780 This is the hub. 18:12.210 --> 18:12.320 Right. 18:12.350 --> 18:12.870 So the hub. 18:12.910 --> 18:14.480 I'll keep checking it. 18:14.720 --> 18:18.170 Now, this is spoke with, spoke, R3, spoke. 18:19.190 --> 18:20.540 So I'll keep it as it is. 18:20.540 --> 18:23.330 Let OSPF be because then I'll know that this is the spoke. 18:24.470 --> 18:27.490 I will ping from R3. 18:27.990 --> 18:30.230 Now I want to go. 18:30.230 --> 18:34.760 Where Ping ten 444 with the source of ten. 18:34.760 --> 18:35.190 Three three. 18:38.290 --> 18:46.780 This second resolution, request and resolution, replies C to redirects to different corners. 18:47.320 --> 18:47.770 Right. 18:47.800 --> 18:51.220 Then a request from 3 to 4. 18:51.820 --> 18:57.370 When you're looking at this, look at this as a couple from 3 to 4, from 3 to 4. 18:58.480 --> 18:58.720 Right. 18:58.720 --> 18:59.890 From 3 to 4. 18:59.920 --> 19:00.160 Sorry. 19:00.160 --> 19:01.030 From four to. 19:03.470 --> 19:08.590 A request going from three, going into one, coming out from one going to four. 19:11.650 --> 19:15.940 Which one ID is exactly? 19:16.750 --> 19:18.640 ID one session, right? 19:18.670 --> 19:19.150 Correct. 19:19.360 --> 19:21.670 So six and six. 19:21.670 --> 19:22.030 Right. 19:22.060 --> 19:23.020 Going from 3 to 1. 19:23.020 --> 19:25.330 Coming out from one to going to four. 19:25.330 --> 19:26.710 So this is one request. 19:26.740 --> 19:27.760 That's another request. 19:27.760 --> 19:29.890 So four requests, right? 19:29.890 --> 19:32.200 And then the replies go straight. 19:32.200 --> 19:35.020 So if you check the other side, you should have two replies. 19:39.530 --> 19:41.120 The recent reply should be to. 19:43.220 --> 19:46.880 So why did the other one? 19:47.180 --> 19:51.800 This four replies I think is because of the redirect sent to both sides. 19:53.270 --> 19:55.460 Because the redirect is sent to both sides. 19:55.460 --> 20:01.520 The other one, the one which we did before the resolution request, is created on its own, right? 20:01.520 --> 20:08.210 So when it sends to the other side, I think in the resolution request, it stated, what is the address 20:08.210 --> 20:08.990 of the other side? 20:11.420 --> 20:12.680 In the resolution request. 20:13.670 --> 20:15.650 So it doesn't have to send it back up again. 20:15.650 --> 20:20.600 But sometimes it does, because yesterday I remember I think one of the times it does. 20:20.600 --> 20:21.110 It does. 20:21.110 --> 20:21.890 You'll see four. 20:21.890 --> 20:24.380 So sometimes it does if he doesn't receive it properly. 20:25.010 --> 20:26.090 Mostly it doesn't. 20:26.210 --> 20:27.110 We saw it today also. 20:27.110 --> 20:28.520 It doesn't Mostly it doesn't. 20:29.000 --> 20:31.580 So but again, the process is the same. 20:31.880 --> 20:32.570 Request. 20:32.570 --> 20:33.560 Request, reply. 20:33.980 --> 20:37.460 If he doesn't resolve it, request request, just like it's happening right now. 20:38.390 --> 20:40.820 So whoever receives it, they'll send a resolution request. 20:40.850 --> 20:42.740 Resolution request will go to the other side. 20:42.770 --> 20:44.210 Replies will come straight. 20:44.240 --> 20:45.290 That's what's happening. 20:46.130 --> 20:46.400 Yeah. 20:47.240 --> 20:48.230 Same concept. 20:48.410 --> 20:49.010 Spoke to spoke. 20:49.010 --> 20:49.910 Communication is done. 20:49.940 --> 20:50.660 Phase three is done. 20:50.660 --> 20:51.380 But the problem is. 20:51.380 --> 20:51.920 What? 20:56.090 --> 20:57.410 The problem is only one hub. 20:58.910 --> 21:00.740 In this case, Only one hub. 21:00.770 --> 21:02.300 How do I move to other hubs? 21:03.770 --> 21:09.980 I need to go to all the spokes, IP, OSPF, Network, Point to multipoint. 21:15.640 --> 21:17.320 IP OSPF network. 21:17.350 --> 21:20.500 Point to multipoint and r-5 also. 21:22.810 --> 21:27.740 IP network point to all the spokes are point to multipoint. 21:28.040 --> 21:30.500 I need to change the timer back up again here. 21:31.790 --> 21:34.040 Back to 31st we have. 21:34.040 --> 21:34.310 Hello. 21:34.310 --> 21:39.890 Interval is 30 so that now it's in synchronized hello timers with all the other spokes. 21:41.180 --> 21:41.580 Right. 21:42.050 --> 21:45.920 Also R2 needs to be configured for OSPF so I'll go here. 21:46.370 --> 21:55.250 Router OSPF one Network 192 168 .1.0 Area zero Network ten 000. 21:58.130 --> 22:01.910 Let's have a look at our two and tell me which commands are missing. 22:07.820 --> 22:08.820 But commands are missing here. 22:11.930 --> 22:17.560 Type and map multicast dynamic IP and. 22:18.890 --> 22:19.790 Nothing much. 22:20.330 --> 22:21.320 Network ID is up. 22:22.580 --> 22:23.480 That's all right. 22:23.720 --> 22:24.620 Anything else? 22:24.920 --> 22:27.670 IP, OSPF, Network. 22:27.680 --> 22:29.690 Point to MultiPoint. 22:31.190 --> 22:31.700 Another hop. 22:31.700 --> 22:32.060 Right. 22:32.940 --> 22:35.720 Should also have point to multipoint configurations. 22:37.630 --> 22:37.900 He's the 22:41.110 --> 22:42.790 first for the third degree. 22:44.560 --> 22:45.280 Let's go here. 22:45.280 --> 22:56.530 I need to point them towards NHS 192 168 1.2 Give them the mapping for NHS map 192 168 1.2 is 150 .1. 22:56.920 --> 22:59.800 20 6.2 multicast. 23:02.930 --> 23:04.040 150 dot. 23:06.150 --> 23:06.630 26. 23:07.830 --> 23:08.370 That's it. 23:13.120 --> 23:15.850 Probably the same thing and everywhere else. 23:22.540 --> 23:22.810 Right. 23:25.510 --> 23:26.200 What does it say? 23:26.230 --> 23:27.100 Number two is up. 23:31.750 --> 23:35.410 Neighbor two is up from here, also neighbor two will be. 23:37.910 --> 23:38.450 Wipe it out. 23:39.830 --> 23:43.610 Now I have to neighbors some I'm getting from some load balancing. 23:43.970 --> 23:47.810 I'm load balancing to go to these networks. 23:49.040 --> 23:50.900 Now, see, this is OSPF. 23:51.530 --> 23:56.980 It gives you the full information about the network based on this LSA database. 23:56.990 --> 23:58.400 It tells you everything. 23:58.670 --> 24:03.500 182 168 1.21.41.31.01.1. 24:03.500 --> 24:05.090 Everything is in the routing table. 24:06.290 --> 24:07.670 You can summarize. 24:08.540 --> 24:11.080 You can summarize and get you the same information. 24:11.450 --> 24:13.190 Will keep it make it easier for you. 24:13.880 --> 24:17.150 So if you see R2 right now, try it out. 24:23.080 --> 24:25.140 I do has all the information. 24:25.140 --> 24:27.840 Ten, one, ten, two, ten, three, ten, four and ten. 24:27.840 --> 24:28.410 Five. 24:28.770 --> 24:32.520 Now let's go ahead and try to do what? 24:36.080 --> 24:36.680 From R3. 24:37.310 --> 24:38.720 Let's try to go to traceroute. 24:38.750 --> 24:40.190 Ten .5.5.5. 24:40.670 --> 24:44.600 Source of ten .3.3.3 first. 24:44.630 --> 24:45.860 Second is string. 24:46.760 --> 24:47.900 Go to 10.4. 24:51.270 --> 24:52.550 Is going directly anyways. 24:53.520 --> 24:55.320 So and is the same. 24:59.160 --> 25:00.120 Same as yesterday. 25:00.330 --> 25:01.590 There is no difference. 25:04.240 --> 25:04.520 Right. 25:04.570 --> 25:05.370 No difference at all. 25:05.380 --> 25:11.140 So the only thing that you have to be careful about is to make sure you have the network types are okay. 25:12.280 --> 25:14.980 Also, another thing is R1 and R2. 25:15.010 --> 25:20.920 See, there's a problem on R1 and R2 show IP route if you do it on R1 is getting the information about 25:20.920 --> 25:25.210 10.2, but from where? 25:27.600 --> 25:28.680 From the spokes. 25:29.190 --> 25:30.810 Should that be the case? 25:33.060 --> 25:36.630 That's because R1 and R2 are not neighbors among themselves. 25:38.030 --> 25:41.090 And since it's always split horizon problem is not here. 25:42.050 --> 25:45.260 So R3 learns 10.2 and tells it to whom? 25:46.220 --> 25:47.840 R1 r1. 25:47.840 --> 25:51.290 R2 learns ten not sorry r4 learns ten R2 tells it to. 25:51.500 --> 25:58.880 R1 To fix that, I'll create a neighbor relationship between R1 and R2 directly so they can communicate 25:58.880 --> 26:01.400 and R2 and R1 will be the Loopbacks will be shared. 26:03.290 --> 26:03.890 Yeah. 26:04.460 --> 26:06.140 Point to multipoint is anyways. 26:06.950 --> 26:08.990 Anyways, it's multi point, so no problem with that. 26:08.990 --> 26:09.320 Right. 26:09.350 --> 26:11.090 So let's go here on R1. 26:11.570 --> 26:12.530 How do you do that? 26:15.020 --> 26:17.540 Because it won't be dynamically registered to me. 26:17.750 --> 26:18.740 I'll have to map it. 26:18.770 --> 26:28.820 102 168 1.2 is 150 dot 150 .1. 26 dot. 26:30.970 --> 26:33.970 Also I need to say map my multicast. 26:33.970 --> 26:35.650 I'm sending it to the dynamic pairs. 26:35.650 --> 26:37.690 I also need to send it to this guy, which is. 26:39.660 --> 26:42.150 150 .1.26.. 26:44.830 --> 26:46.370 I from R1 from R2. 26:46.400 --> 26:53.150 Same IP map 192 168 .1.1. 26:55.860 --> 27:02.490 Hype and IP Man hundred 92.162 Sorry multicast. 27:04.750 --> 27:05.200 16. 27:05.210 --> 27:05.470 Dark 27:08.260 --> 27:11.770 neighbor is up high, one's neighbor is up. 27:12.370 --> 27:15.180 R2, R1, R1, R2, ship it out now. 27:15.220 --> 27:17.110 10.2 will be stable. 27:21.110 --> 27:22.310 Everything goes to normal. 27:25.240 --> 27:27.220 They even from our trees perspective. 27:27.230 --> 27:27.740 Check. 27:30.610 --> 27:34.270 It's all good for Archie to go to 10.4. 27:34.300 --> 27:38.080 There's two ways for him to go to 10.5. 27:38.110 --> 27:39.220 There's two directions. 27:43.260 --> 27:43.500 Right. 27:43.500 --> 27:45.630 So it doesn't matter which one does it choose. 27:45.720 --> 27:47.790 As long as he's getting the reply, it's fine. 27:52.510 --> 27:52.990 Okay. 27:55.120 --> 27:55.660 Good enough. 27:57.400 --> 27:58.120 Everybody okay? 28:01.980 --> 28:04.650 What I'll do is I'll shut the tunnels on the hubs. 28:04.890 --> 28:05.940 On the spokes. 28:07.360 --> 28:07.690 Three. 28:12.270 --> 28:13.140 You have to summarize it. 28:13.740 --> 28:19.170 You have to summarize the routes to the routing table. 28:19.440 --> 28:20.670 I think it's area summary. 28:21.210 --> 28:22.290 I think it's summary. 28:22.320 --> 28:23.190 Summary address. 28:25.740 --> 28:27.280 Okay, we can summarize. 28:29.590 --> 28:30.820 Somebody's address, I think. 28:34.790 --> 28:41.510 Somebody address that for the somebody address works on but still try. 28:50.470 --> 28:52.780 I shut my spokes again. 28:54.610 --> 28:58.120 I want to show you when the hub dies, what happens with. 28:58.150 --> 28:59.140 What do you call it? 29:00.250 --> 29:00.580 Spoke to. 29:00.580 --> 29:00.820 Spoke. 29:00.820 --> 29:01.390 Communication. 29:02.650 --> 29:02.980 Loading. 29:02.980 --> 29:03.250 Done. 29:10.740 --> 29:15.000 No router OSPF one. 29:15.780 --> 29:18.600 Summary Address ten 000. 29:32.470 --> 29:39.850 Somebody that works for as and area zero somebody works on between entire areas within the area. 29:41.380 --> 29:43.240 No, because it will not work for a reason. 29:43.240 --> 29:44.990 Because it's lsas. 29:45.010 --> 29:45.460 Right. 29:45.700 --> 29:47.440 And lsas are shared everywhere. 29:47.920 --> 29:49.450 So lsa, he's, he's. 29:49.810 --> 29:50.350 He's lsa. 29:50.350 --> 29:53.440 He's lsa and lsa one will come to everywhere. 29:53.440 --> 29:58.150 If he knows the LSA one, he sends him his LSA one sends him his LSA, one sends them LSA one. 29:59.920 --> 30:01.480 In this case, not like that. 30:01.480 --> 30:02.630 That will be broadcast. 30:02.650 --> 30:03.730 These are the hubs. 30:03.880 --> 30:06.160 So I'll send all my lsas to the hub. 30:06.550 --> 30:08.110 I'll send all my lsas to the hub. 30:08.480 --> 30:09.760 Send all my LSA to the hub. 30:10.040 --> 30:13.510 Yeah, go to any of them. 30:14.350 --> 30:14.770 Okay. 30:18.710 --> 30:19.720 Beat out. 30:24.790 --> 30:29.380 This information is still see this information is here to is because of the LSA. 30:31.150 --> 30:35.230 LSA is what advertise all the directly connected links to me. 30:36.130 --> 30:36.490 Right. 30:36.490 --> 30:40.570 So when our three tells R1R3 is telling r one. 30:40.570 --> 30:44.920 Listen, I have 180 268 1.3 and ten .3.3.0. 30:45.220 --> 30:45.600 Okay. 30:45.970 --> 30:48.580 Can you can you put the loopbacks in a different area? 30:49.210 --> 30:52.270 In a different area on the Loopbacks? 30:53.620 --> 30:54.940 That's a good that's a good thing. 30:56.200 --> 30:59.170 IP, OSPF, one area, let's say one. 31:03.560 --> 31:05.810 This is done interface loopback zero. 31:18.960 --> 31:20.220 Oh, between the. 31:20.510 --> 31:20.700 Yes. 31:20.930 --> 31:21.150 Yes. 31:21.200 --> 31:21.390 Yes. 31:22.770 --> 31:23.030 Five. 31:23.100 --> 31:24.180 Let's keep this at five. 31:25.680 --> 31:27.390 Let's keep this as four. 31:28.740 --> 31:30.210 Let's keep this as three. 31:30.960 --> 31:31.190 Right. 31:31.350 --> 31:35.490 So 3 or 4, depending upon how you're getting it. 31:35.520 --> 31:39.710 So right now should get it as interior. 31:43.490 --> 31:44.590 Now you can summarize. 31:46.260 --> 31:46.910 I will remind you. 31:47.750 --> 31:49.940 Now you can manage summarizing right one. 31:51.770 --> 31:54.080 So now I'm getting 10.4 as interior out. 31:54.470 --> 31:56.960 10.5 is inter area 10.3. 31:57.080 --> 32:02.570 So if I check my show, IP, OSPF database, I have area zero coming in. 32:02.570 --> 32:10.190 I have these guys which are coming in as threes 10.3, 10.4 and 10.5 is coming in as LSA three. 32:12.720 --> 32:12.950 Right. 32:13.110 --> 32:14.280 So I can. 32:20.380 --> 32:20.660 This. 32:22.560 --> 32:23.100 There is. 32:26.350 --> 32:27.740 Are zero range. 32:31.040 --> 32:31.580 I'm sorry. 32:32.690 --> 32:33.590 I thought it was me. 32:35.240 --> 32:36.020 It's this one. 32:36.200 --> 32:36.590 Summary. 32:36.780 --> 32:37.220 The summary. 32:37.220 --> 32:38.330 I want to try this first. 32:38.330 --> 32:39.450 I want to see if this works. 32:39.610 --> 32:43.490 Why do I use it in area zero or area one? 32:43.880 --> 32:45.500 Because he has only area zero. 32:45.740 --> 32:48.560 I could use it on the spokes, but that will not give me what I want. 32:53.070 --> 32:53.610 On the hub. 32:56.340 --> 32:58.500 But I have to connect all of them to area zero. 32:58.500 --> 32:58.980 Right? 33:01.810 --> 33:02.090 Because. 33:05.760 --> 33:06.510 But. 33:07.320 --> 33:07.830 Okay. 33:08.000 --> 33:08.480 Okay. 33:09.180 --> 33:13.110 What you're saying is the hub will remain. 33:13.110 --> 33:14.910 This part will remain in area. 33:15.930 --> 33:19.110 It has to be in areas in the spokes. 33:19.110 --> 33:28.680 Right now what I did was I made this area one area three area four, an area four, an area five, because 33:28.680 --> 33:30.780 all of them have to connect to the same area, right? 33:31.800 --> 33:34.110 My area right now, I can do summarization here. 33:34.110 --> 33:35.160 I cannot do it on one. 33:37.580 --> 33:39.210 Summarization can be done here right now. 33:39.230 --> 33:39.410 Why? 33:39.440 --> 33:41.270 Because AVR is here. 33:41.660 --> 33:42.830 R3 is the AVR. 33:43.040 --> 33:44.240 R5 is the AVR. 33:44.270 --> 33:45.380 R4 is the AVR. 33:45.800 --> 33:48.920 Doesn't serve the purpose of what I want to do. 33:49.910 --> 33:54.650 Why not put R2 and R1 and R2? 33:56.150 --> 33:57.170 You mean like this? 33:57.770 --> 33:59.450 But which interface? 33:59.480 --> 34:01.310 My connected interface is this guy. 34:02.420 --> 34:06.500 I need to connect from the same interface to all of them in the same area. 34:09.090 --> 34:09.440 Right. 34:09.720 --> 34:14.160 This is 192 168 1.0 slash 24. 34:14.190 --> 34:18.810 This is .1.2.3.4.5. 34:18.990 --> 34:22.620 We're here for the ten Network. 34:22.630 --> 34:25.110 For this ten network, you mean. 34:26.460 --> 34:28.290 Then I can only summarize ten dot one. 34:28.290 --> 34:29.940 I cannot summarize these guys. 34:31.440 --> 34:35.580 I'll be able to summarize ten .1.1.0, but that will not serve me the purpose. 34:36.510 --> 34:41.010 I will not be able to summarize these parts from one to another. 34:41.460 --> 34:45.510 Summarization is done when these roots are moving from this area to another area. 34:46.920 --> 34:48.120 One area summarization. 34:48.120 --> 34:50.190 So from here, how do I do it? 34:50.760 --> 34:56.430 I have all the roots coming in here, but I'm running Area zero. 34:58.730 --> 34:59.000 Right. 35:00.260 --> 35:01.820 So this way is not possible. 35:01.910 --> 35:03.020 You need to find another way. 35:03.530 --> 35:08.990 But again, that's exactly why OSPF is not used because of all these complications. 35:10.880 --> 35:11.690 All of this. 35:11.720 --> 35:13.460 It has too much information in there. 35:13.490 --> 35:15.500 It calculates the whole map of the network. 35:15.740 --> 35:19.280 You saw how it also knows every router now knows the endpoint. 35:23.450 --> 35:24.410 Full map of the necklace. 35:26.600 --> 35:26.830 Right. 35:31.060 --> 35:32.110 Summarization. 35:32.110 --> 35:33.790 I don't think it's possible here. 35:33.910 --> 35:38.220 Maybe it is, but it might be. 35:38.230 --> 35:43.630 I mean, it's too complicated for the whole network to design it like that. 35:44.870 --> 35:45.050 Right. 35:45.070 --> 35:46.400 So phase three will have issues. 35:46.420 --> 35:47.380 It won't be as the same. 35:47.410 --> 35:50.710 It won't be the same as what you do. 35:50.750 --> 35:53.380 No, just summary Disabled. 35:53.450 --> 35:54.430 No auto summary. 35:55.240 --> 35:56.140 Bring back the summary. 35:56.140 --> 35:59.100 Its default is default. 35:59.110 --> 36:00.190 It summarizes by default. 36:01.360 --> 36:01.780 Right. 36:04.370 --> 36:06.020 Yeah, that's what it is. 36:07.740 --> 36:09.650 Yeah, that's how it works. 36:10.430 --> 36:11.840 OSPF is complicated. 36:11.840 --> 36:22.310 Plus, the complication here is also these networks can see the Loopbacks as Loopbacks as slash 32 networks. 36:23.150 --> 36:23.740 How do you change it? 36:23.750 --> 36:27.080 Go to the Loopbacks, change the network type to slash 24. 36:27.110 --> 36:29.990 So they'll come as slash 24. 36:30.200 --> 36:32.350 So too many different things with OSPF. 36:32.360 --> 36:35.270 But again, let's move on to phase two. 36:35.300 --> 36:36.640 We did phase one and phase three. 36:36.650 --> 36:37.760 We didn't do phase two. 36:37.790 --> 36:39.050 What was phase two? 36:41.090 --> 36:46.850 Phase two was spoke the spoke without an redirects, without an IP. 36:47.090 --> 36:50.030 Now this is something which is not used a lot. 36:50.270 --> 36:53.630 Before I go there, I didn't check the most important part. 36:55.070 --> 36:55.640 Let's talk. 36:56.090 --> 36:56.840 I'll explain. 36:57.150 --> 37:00.620 I stopped R1, the hub is down. 37:00.620 --> 37:03.260 I need to make sure that my communication does not go down. 37:03.270 --> 37:08.790 Before doing that very carefully, I shut down my internal interfaces, so I made sure that my NPS are 37:08.790 --> 37:09.420 not resolved. 37:11.970 --> 37:13.770 I made sure that the NPCs are not resolved. 37:13.770 --> 37:20.130 So when I trace it out to ten .4.4.4, I need to make sure nothing goes. 37:26.750 --> 37:27.350 The first time. 37:27.350 --> 37:28.490 Obviously, it takes time. 37:30.080 --> 37:31.590 Second time it doesn't. 37:31.610 --> 37:32.780 It still takes time. 37:32.820 --> 37:43.880 So we have all the mappings as complete as I do show IP, show, IP direct command. 37:43.880 --> 37:44.600 Do I have that? 37:49.800 --> 37:53.060 I do have the redirect on the spokes. 38:00.300 --> 38:07.590 Everything is going from right now again because the hello timer, dead timer is what, 30 and that 38:07.590 --> 38:16.890 timer is 120 So it still thinks what one is alive until one 20s it will think one is alive. 38:16.890 --> 38:20.070 So you'll see that this latency will be there for the first packet. 38:20.070 --> 38:22.050 Latency will be there for that amount of time. 38:22.140 --> 38:23.250 10.4 has been resolved. 38:23.280 --> 38:24.780 Ten .5.5.5. 38:24.900 --> 38:27.810 The first latency will be there because he's looking for both the hubs. 38:31.320 --> 38:33.020 So traceroute will take a little time. 38:33.050 --> 38:34.610 Your traffic will not be stopped. 38:34.640 --> 38:35.780 It's still going through the hub. 38:37.610 --> 38:38.690 The traffic will not be stopped. 38:38.690 --> 38:41.690 But he's trying to see it's expired. 38:41.900 --> 38:43.160 But my spoke to spoke. 38:43.160 --> 38:47.150 Communication is still going on both sides. 38:49.460 --> 38:50.690 No, no, this is not through the hub. 38:50.720 --> 38:52.700 This is direct one hop. 38:53.030 --> 38:53.840 It's already resolved. 38:54.230 --> 38:59.150 The first packet resolution packet will take a little while because it will try to go to both of them. 38:59.150 --> 39:02.000 The other guy will not be there and then he'll try to go to the other one. 39:03.560 --> 39:05.060 This wouldn't be a problem. 39:05.060 --> 39:05.240 Why? 39:05.270 --> 39:07.850 Because you have two hours to do this. 39:08.720 --> 39:10.400 You have two full hours to do this. 39:11.510 --> 39:12.260 Here I remove. 39:12.290 --> 39:13.850 I shut down the tunnel to show you. 39:13.880 --> 39:16.760 Even if you don't have the mappings, it will still work. 39:17.800 --> 39:20.810 So here it works exactly like that. 39:21.020 --> 39:24.670 It's just that in the routing table you have to be careful of how it works. 39:24.680 --> 39:26.540 You have to know how OSPF works. 39:26.540 --> 39:30.380 For that, you have to understand OSPF properly. 39:30.380 --> 39:36.830 OSPF has been broken into and just to teach the concepts of OSPF how it actually works with different 39:36.830 --> 39:37.520 networks. 39:39.830 --> 39:41.630 We saw point to point. 39:41.720 --> 39:42.860 That was a single hub. 39:44.000 --> 39:48.140 We saw point to multipoint on everybody that was with dual hub. 39:48.170 --> 39:50.060 We saw phase one as phase three. 39:50.990 --> 39:53.000 What is the difference between phase two and phase three? 39:53.030 --> 39:56.480 Phase two does the same, spoke to spoke, but based on which table? 39:57.920 --> 39:59.120 The routing table. 40:01.040 --> 40:03.230 The information in phase two is not in self. 40:03.950 --> 40:07.760 It's in the routing table first, then it goes further. 40:09.140 --> 40:10.490 That is the difference between the two. 40:10.730 --> 40:14.000 If you don't understand step, if you have not done it before, it's all right. 40:14.030 --> 40:19.310 You just have to understand that routing table information should not be there. 40:19.340 --> 40:20.300 See, in phase. 40:20.330 --> 40:24.020 In the phase which I have right now, my next hops for all of them are what? 40:27.080 --> 40:29.300 What is my next hop for all these networks? 40:30.170 --> 40:30.860 That too. 40:31.880 --> 40:37.220 So in the routing table is not resolved in my routing table. 40:37.220 --> 40:38.400 It's not resolved. 40:38.910 --> 40:41.100 Again, if you want I just figured it out. 40:41.100 --> 40:47.940 If you want to solve the problem, if you want to solve the problem of this of the routing. 40:48.870 --> 40:49.200 Right. 40:49.290 --> 40:59.340 What you can do is you can actually go to all the spokes, not advertise, advertise it only to whom? 40:59.790 --> 41:00.430 To the hub. 41:00.450 --> 41:01.260 Let me think. 41:01.410 --> 41:03.270 The hub should not advertise anything back. 41:03.270 --> 41:10.320 So what I'll do in the hub is I'll apply a distribute list passive interface, but it will still receive. 41:10.350 --> 41:10.760 Right? 41:10.770 --> 41:12.500 I don't want him to send anything out. 41:12.510 --> 41:13.320 It will stop hellos. 41:13.320 --> 41:17.670 Also, what I'll do is I'll apply a distribute list. 41:19.650 --> 41:21.540 What I'm trying to do this is R1, right? 41:22.440 --> 41:23.250 Check this out. 41:24.750 --> 41:25.710 I'll go to R1. 41:26.760 --> 41:31.380 I'll create an access list ten which denies ten 000. 41:33.720 --> 41:36.080 I am trying to reduce the routing table on this post. 41:38.000 --> 41:38.330 Right. 41:38.460 --> 41:40.670 I'll create this access list and I'll say permit any 41:44.210 --> 41:44.520 done. 41:44.960 --> 41:47.330 Then I'll go to the interface channel zero. 41:48.080 --> 41:50.990 I'll say distribute list. 41:55.380 --> 41:56.400 First place. 41:56.550 --> 41:56.710 Yes. 41:56.910 --> 41:57.090 No. 41:57.090 --> 41:57.240 No. 41:58.500 --> 41:58.920 Yeah. 41:58.920 --> 42:00.120 No, it's all on the interface. 42:00.120 --> 42:02.490 Also IP, OSPF filter list. 42:02.490 --> 42:05.220 I think you can apply it on the interface. 42:10.530 --> 42:10.710 No. 42:14.370 --> 42:14.850 It is. 42:14.850 --> 42:15.630 Yes. 42:15.840 --> 42:17.100 Under the process it is. 42:17.100 --> 42:21.450 But you can apply it on the interface of I remember right now, I don't remember how it is here. 42:21.450 --> 42:26.730 You can distribute list and where do I want to apply it then? 42:26.760 --> 42:27.780 Which direction? 42:28.050 --> 42:29.040 Outgoing direction. 42:30.360 --> 42:31.110 Outgoing direction? 42:31.110 --> 42:31.350 Yes. 42:35.950 --> 42:37.380 It is not allowed without. 42:39.180 --> 42:39.630 Okay. 42:40.050 --> 42:42.420 So it wouldn't send any routes outside. 42:43.560 --> 42:47.880 Also on R2, I'll say router create the same access list. 42:47.910 --> 42:48.420 Why? 42:48.420 --> 42:49.080 I'll tell you why. 42:49.560 --> 42:57.300 If you are the one who is designing the VPN and you have to use OSPF or what I'll say is ten 000 just 42:57.300 --> 42:58.380 trying this stuff out. 42:59.520 --> 43:02.880 Access list and permit any router. 43:02.890 --> 43:08.820 OSPF one I'll say again distribute list ten in the outgoing direction. 43:09.420 --> 43:19.470 So if you see your show IP route, your routing table, it does not distribute. 43:23.750 --> 43:24.020 Player. 43:24.350 --> 43:25.280 OSPF. 43:39.250 --> 43:40.150 His back up again. 43:50.000 --> 43:51.380 There is still receiving the house. 43:51.950 --> 43:52.670 Oh, it's. 43:52.700 --> 43:53.030 Is it. 43:54.230 --> 43:54.710 It's not. 43:56.300 --> 44:03.500 It's only receiving from 1.1, which is good right now it's receiving from everybody. 44:05.910 --> 44:06.660 One, two, three, four. 44:06.700 --> 44:09.990 This is not gonna just look, listen to. 44:09.990 --> 44:13.290 You know, he's receiving it from everybody. 44:16.650 --> 44:17.250 I could do it. 44:17.250 --> 44:17.970 Incoming. 44:17.970 --> 44:19.530 But that wouldn't be a problem. 44:20.940 --> 44:23.550 But I want the hubs to have full information. 44:23.730 --> 44:25.560 The hubs should have the information. 44:25.770 --> 44:27.120 That's how they'll send the redirect. 44:28.680 --> 44:31.040 I want the hubs to have the information, but not send it out. 44:31.050 --> 44:33.870 The problem is, I'm learning everything from the same interface. 44:38.050 --> 44:39.370 Then they will directly communicate 44:42.040 --> 44:43.540 to the spokes. 44:43.930 --> 44:44.500 I know that. 44:44.500 --> 44:48.550 But what my objective is I want the routing table should not be here. 44:53.380 --> 44:53.830 Yeah. 44:57.690 --> 44:58.590 I can. 44:58.590 --> 45:01.770 But the problem is, then the hub will not have the information about the networks. 45:02.250 --> 45:08.590 The hub should have full information because then he knows that I need to send the redirect message. 45:08.610 --> 45:13.350 What I can do now, this is again more complicated, but I just want it to work. 45:13.560 --> 45:19.350 I'll create another ACL here on the spokes and I'll stop the incoming updates. 45:19.890 --> 45:20.640 You can do that, right? 45:20.730 --> 45:28.620 So I'll say deny ten 000 access list n permit any. 45:30.030 --> 45:37.580 Then I'll go to router OSPF one distribute list ten in the incoming links. 45:40.590 --> 45:42.480 You might ask the question, Why would I do that? 45:43.620 --> 45:44.730 Why would I do that? 45:44.730 --> 45:47.130 Because what I can do is I can have a static route. 45:49.690 --> 45:50.770 By myself. 45:50.770 --> 45:54.400 And I can say the next half of this static route is 1.1. 45:54.400 --> 45:58.810 And sorry, this is this is a mask. 46:03.360 --> 46:04.770 1.1 and one dot. 46:06.660 --> 46:08.130 I can manually tell him what? 46:10.110 --> 46:13.800 If you want to go to ten dot zero network, your next stop is 1.2 and one dot. 46:16.460 --> 46:18.860 Reducing the routing table on the spokes. 46:21.240 --> 46:22.160 On all the sports. 46:22.930 --> 46:28.470 I have to use the same command on all the scopes distribute list that this is what this is Disaster 46:28.470 --> 46:29.040 management. 46:30.330 --> 46:34.530 If you have 1000 spokes and too many routes are coming in, you could use that. 46:36.960 --> 46:37.560 It will not. 46:37.560 --> 46:38.700 I have the redirect there. 46:39.450 --> 46:40.680 That's the best part. 46:43.200 --> 46:44.820 Right here, right now. 46:44.820 --> 46:48.810 I need to first make sure that I don't have an incomplete mapping. 46:49.680 --> 46:51.180 Everybody is registered. 46:56.310 --> 46:57.570 Let's layer it everywhere. 47:00.840 --> 47:05.460 But when I do that, I need to shut a no shut from here. 47:18.420 --> 47:19.700 They come up and register again. 47:22.350 --> 47:24.160 Go register yourself to both of them. 47:24.180 --> 47:25.340 It has neighbors. 47:25.350 --> 47:28.230 Are you register yourself? 47:31.840 --> 47:32.590 And. 47:35.550 --> 47:36.500 Want to just turn yourself. 47:40.810 --> 47:40.990 Right. 47:42.460 --> 47:43.210 Ship it out. 47:44.590 --> 47:45.910 I do have all the routes. 47:46.480 --> 47:48.520 So I'll go do is R3. 47:48.670 --> 47:53.980 Let's check R3 show IP route has that I applied the distribute list to around R5. 47:54.880 --> 47:56.410 I want to make sure that it works. 47:57.160 --> 47:58.900 I have the distribute list already applied. 47:58.930 --> 48:01.930 Ten .0.0.0 so I can ping. 48:03.610 --> 48:07.750 I want to see if I can trace route to ten .4.4.4 with the source of ten dot. 48:11.510 --> 48:12.290 It's working fine. 48:12.770 --> 48:16.100 It's working the same as it was before. 48:18.230 --> 48:22.100 The only one reason why this should work is the hub should have full information. 48:23.450 --> 48:25.310 The hub should have because the hub will root. 48:25.340 --> 48:27.710 Then the hub will know that both are directly connected. 48:27.740 --> 48:29.480 Then it will send the redirect message. 48:29.710 --> 48:30.900 But why does it matter whether. 48:33.680 --> 48:38.470 If you have 1000 spokes, as I explained yesterday, 1000 spokes means 1000 routes in the routing. 48:41.770 --> 48:42.970 I'll be dropping in. 48:44.170 --> 48:46.360 Yeah, but you'll be consulting the routing table, right? 48:46.600 --> 48:49.030 What about the other outings that you're doing from the inside? 48:49.060 --> 48:50.260 What about those routings? 48:50.950 --> 48:52.900 You have a lot of memory for routing cables. 48:57.300 --> 49:00.780 You'll have to go to all the spokes and add the access, which is not feasible. 49:02.250 --> 49:03.210 It will work. 49:03.480 --> 49:10.800 Yes, you will not use it normally, but if you have 1000 spokes, it's better to use it to reduce the 49:10.800 --> 49:11.550 routing table. 49:12.780 --> 49:14.100 If you're using an example. 49:14.640 --> 49:17.490 But again, the best solution for this is what? 49:21.640 --> 49:21.790 Why? 49:24.410 --> 49:27.080 20 years accesses to different areas. 49:27.080 --> 49:32.960 Only you can summarize on the right one is not an its area zero. 49:33.110 --> 49:35.000 It's getting routes from area zero. 49:36.620 --> 49:40.130 Then it can stop from that loopback from that area. 49:40.160 --> 49:44.750 Coming into this area, you want routes to be stopped into area zero, right? 49:44.930 --> 49:48.710 The problem is area zero has many different gateways where the routes are coming in from. 49:48.710 --> 49:52.190 One is coming from here, one is coming from here, one is coming from here. 49:52.640 --> 49:56.420 Three is leaking in one, route four is leaking, one Route five is leaking one route. 49:56.450 --> 49:59.210 Once it comes into area zero, it's it's gone. 49:59.450 --> 50:00.530 You cannot stop it. 50:01.820 --> 50:03.380 So it comes into area zero. 50:03.380 --> 50:06.260 Then when it's come to it comes to R1, it's already in area zero. 50:09.670 --> 50:10.330 Right there. 50:10.330 --> 50:11.140 Timer expired. 50:12.480 --> 50:17.380 So already it we can stop the spokes. 50:17.380 --> 50:19.840 But the problem with that is the hub will not have the information. 50:19.840 --> 50:21.730 I want the hub to have full information. 50:22.280 --> 50:23.140 You cannot do it that way. 50:24.640 --> 50:25.350 The hub. 50:25.360 --> 50:29.560 So I can stop it when the hub is saying it out, telling others about it. 50:29.680 --> 50:34.180 I can go to the spokes and stop it on the spokes from receiving those 1000 rounds. 50:37.230 --> 50:38.370 The last is. 50:38.610 --> 50:39.420 Which one? 50:40.480 --> 50:41.740 Phase two. 50:42.130 --> 50:45.490 For phase two, first of all, what is phase two? 50:46.450 --> 50:48.850 What is the difference between phase two and phase three? 50:49.630 --> 50:50.200 Do you remember? 50:51.940 --> 50:53.440 Everything is in the routing table. 50:54.250 --> 50:55.880 All the information is in the routing table. 50:55.900 --> 51:01.030 The first thing that you will remove from your hub is the redirect command interface, Channel zero, 51:01.030 --> 51:03.430 No IP and redirect. 51:07.010 --> 51:17.210 No IB and AP in OSPF, Phase two is implemented using the network type broadcast. 51:19.910 --> 51:26.870 When you have a network type broadcast, you will have a BTR and everybody else will be there. 51:26.900 --> 51:32.060 They'll exchange their OSPF databases since they know that everybody is on the same network. 51:32.250 --> 51:34.160 They'll exchange every information. 51:34.340 --> 51:39.440 Then every router will find the closest path by himself using the SPF. 51:39.710 --> 51:45.110 It doesn't need the information from anybody else, Not the not the BTR, no split horizon problem. 51:45.140 --> 51:48.380 Every router will find its own way to the destination. 51:48.530 --> 51:50.960 It will find the next hop to the destination by itself. 51:50.990 --> 51:52.640 It will map the whole thing. 51:54.380 --> 52:01.400 But what do you have to make sure before you start this, you need to make sure that R3, R4 and R5 52:01.430 --> 52:04.460 do not become either DDR or the DDR. 52:06.460 --> 52:12.980 Focusing on the priority will be zero on all three of them before you start anything else. 52:13.000 --> 52:20.170 You can increase it here, but since I want them to never become the DRB, I'll keep it as zero. 52:21.430 --> 52:23.530 So automatically one of them will become the DRM. 52:24.250 --> 52:30.760 The first thing before you start this is you could go to your spokes interface tunnel zero IP, OSPF 52:30.760 --> 52:32.470 network type, not network. 52:32.470 --> 52:32.950 Sorry. 52:32.980 --> 52:39.700 Priority zero on all of them are for also IP. 52:39.700 --> 52:42.820 OSPF priority is high five. 52:48.690 --> 52:51.180 First priority is done. 52:52.230 --> 52:58.770 Then change the network type to or all of them. 53:14.390 --> 53:17.990 Done interface detached. 53:18.460 --> 53:20.390 Will take a little while to form a neighbor. 53:20.390 --> 53:20.780 Why? 53:25.620 --> 53:26.910 It'll take time to form neighbors. 53:26.910 --> 53:28.830 Why elections? 53:30.860 --> 53:35.330 Elections will take place for everything. 53:35.360 --> 53:36.380 Elections will take place. 53:36.390 --> 53:37.700 Elections do take time. 53:39.080 --> 53:44.720 Around one full hello dead interval elections will take place and then R1 and R2 will be deciding on 53:44.750 --> 53:47.980 who's going to be the doctor and who's going to be the fighter. 53:50.180 --> 53:50.790 It is. 53:54.230 --> 53:54.400 No. 53:55.880 --> 53:56.470 It was. 53:56.480 --> 53:57.320 Now it is. 53:58.340 --> 54:01.370 It takes a little while to converge because of the elections. 54:03.720 --> 54:04.000 Right. 54:04.020 --> 54:04.680 Who's the doctor? 54:07.510 --> 54:08.280 R2 is the doctor. 54:09.660 --> 54:11.400 R1 is the DDR. 54:11.430 --> 54:12.360 The others are. 54:12.870 --> 54:13.980 Check the routing table. 54:14.880 --> 54:15.900 You'll be surprised. 54:23.160 --> 54:24.210 Next up, resolved. 54:24.690 --> 54:25.510 Just like in. 54:25.980 --> 54:26.490 You said no. 54:26.490 --> 54:28.200 Next hop self in OSPF. 54:28.230 --> 54:30.150 You don't need to do that in broadcast networks. 54:31.290 --> 54:33.210 They will automatically resolve it themselves. 54:33.210 --> 54:36.900 They will find the closest path to wherever they're trying to go. 54:37.800 --> 54:43.140 They'll find the closest path, resolve the next hop and move forward. 54:43.140 --> 54:52.080 So now if you want to go to 192.168.1.4, you don't have to go through the event to the hub only to 54:52.080 --> 54:53.610 resolve the address of that phone. 54:53.850 --> 54:55.710 The information is in your routing table. 54:56.640 --> 55:01.920 Dot C is me, so I don't really need to go there. 55:02.310 --> 55:04.300 Five dot. 55:06.880 --> 55:11.230 I will have full information about you. 55:14.580 --> 55:19.860 In the routing table again here for this network type, you need to make sure that your full routing 55:19.860 --> 55:24.380 table is resolved where on all the spokes because the next hops are hidden. 55:24.390 --> 55:32.940 Where in this course in phase three, the next hops are where in the output table here it's in the routing 55:32.940 --> 55:33.150 table. 55:35.190 --> 55:37.110 That is the big difference between the two. 55:40.420 --> 55:41.290 Any questions? 55:43.220 --> 55:44.000 Any questions? 55:44.540 --> 55:45.170 Broadcast. 55:47.830 --> 55:48.130 Right. 55:49.210 --> 55:49.890 We don't need to. 55:49.900 --> 55:53.350 Multicast is already allowed is broadcast. 55:53.350 --> 55:53.530 Right? 55:53.560 --> 55:54.730 Network type is broadcast. 55:57.040 --> 56:05.380 I didn't use it in also I said multicast multicast to this address actually, you know I mean not right. 56:06.040 --> 56:06.370 That's true. 56:06.670 --> 56:08.800 Here is dot five and dot six. 56:09.580 --> 56:11.080 I'm mapping the full multicast, right? 56:12.100 --> 56:12.300 Yeah. 56:13.330 --> 56:21.070 It is supposed to broadcast the command for your broadcast remains the same IP map multicast to R1 to 56:21.070 --> 56:21.450 R2. 56:21.460 --> 56:25.170 R2 is sending it to the dynamic phase, is sending it among themselves. 56:25.180 --> 56:27.130 So that part remains the same. 56:27.130 --> 56:32.350 Make sure, though, when you're doing this, make sure you don't make the mistake of R1 and R2 not 56:32.350 --> 56:33.040 being neighbors. 56:34.960 --> 56:39.190 R1 and R2 should have static mappings between them because if they don't, they will not be able to 56:39.190 --> 56:40.420 do any elections. 56:42.070 --> 56:43.390 R1 and R2 have to be part. 56:43.420 --> 56:47.950 Then if you don't have that, you'll have a conflict. 56:47.950 --> 56:49.750 Yes, you'll have something like this. 56:49.750 --> 56:56.320 There'll be a separate election here, a separate election, which will be conflicting. 56:56.560 --> 57:00.010 So one side will come up, the other side will go down, one side will come up, the other side will 57:00.010 --> 57:00.580 go down. 57:00.580 --> 57:01.480 He'll become the doctor. 57:01.510 --> 57:02.830 Then he'll become the doctor. 57:02.980 --> 57:08.110 He'll keep on conflicting because they're not communicating to each other so they cannot elect among 57:08.110 --> 57:08.920 themselves. 57:09.250 --> 57:12.610 You need to make sure that this relationship is there. 57:13.690 --> 57:18.640 Then only they can participate fully in the complete election among them. 57:18.670 --> 57:21.220 These three are not participating. 57:21.310 --> 57:24.070 The elections are only between R1 and R2. 57:24.730 --> 57:27.430 One is the Doctor VR. 57:33.240 --> 57:33.690 Okay. 57:34.500 --> 57:37.790 From production point of view, not as important as ERP. 57:38.310 --> 57:44.220 So if you have to give your priorities, ERP phase three first priority, phase two, second priority, 57:44.970 --> 57:45.870 then come here. 57:46.530 --> 57:47.010 OSPF. 57:47.880 --> 57:50.910 OSPF point to MultiPoint is the first priority. 57:51.090 --> 57:52.590 Broadcast should be your least priority. 57:54.190 --> 57:55.980 Will never ever use this. 57:56.400 --> 57:58.080 It limits you to only two hubs. 58:01.900 --> 58:06.790 You can have a third one, but that will be useless for a long time unless one of them goes down. 58:06.910 --> 58:08.450 Then it will become the VR. 58:08.470 --> 58:14.410 Then it will do a synchronization and so many different things because the AR and VR, right. 58:14.650 --> 58:19.060 The third guy will not have any information about the network at one time. 58:19.060 --> 58:20.210 Only one, right? 58:20.590 --> 58:21.340 One is up. 58:21.340 --> 58:23.620 But he can go for his to both of them. 58:25.270 --> 58:25.960 You can't call him 58:29.560 --> 58:31.210 only when it has the full. 58:31.210 --> 58:33.070 But does it have full information? 58:33.940 --> 58:35.560 Yes, it has full information. 58:35.560 --> 58:39.100 So if it gets an IP resolution request, will it be able to send a redirect? 58:39.310 --> 58:40.210 It will. 58:41.590 --> 58:42.100 It will. 58:42.130 --> 58:45.190 The only thing is it will not update anybody on the network. 58:45.670 --> 58:46.210 Update. 58:46.210 --> 58:50.530 The job of updating about networks is R1, but if he gets a request, he will reply. 58:51.910 --> 58:55.840 But that is a separate process and OSPF is separate. 58:56.170 --> 58:58.660 The AR and VR both receive everything. 58:59.290 --> 59:03.500 It's just that when it's supposed to update the other neighbors about the other networks, only the 59:03.500 --> 59:04.250 DA doesn't. 59:04.880 --> 59:07.700 The DDR stays quiet, but it has full information. 59:08.360 --> 59:09.950 Why does it have full information? 59:09.950 --> 59:13.910 Because if the DA dies, VR will start updating everybody else. 59:13.940 --> 59:17.570 The problem with third hub would be the third hub will have no information at all. 59:18.620 --> 59:24.350 So if I have configured as the third hub also when he receives the resolution request, it will have 59:24.350 --> 59:27.350 no information about the network, so it will not be able to resolve that. 59:30.780 --> 59:36.110 Right so not not really use it is mostly used is one end. 59:38.090 --> 59:40.090 The first and the other ones in order. 59:41.320 --> 59:41.540 Clear. 59:43.100 --> 59:44.030 Any questions? 59:45.530 --> 59:45.950 No. 59:46.340 --> 59:49.220 That finishes your MVP and your first advanced VPN.