Give VPN with OSPF.
Okay.
Let's configure the tunnel first before doing any routing.
I'll go to R1.
This is my hub, so let's do it from here.
What are the configurations I need to do on the Hub now?
You should be experts on this interface.
Channel zero then IP address 192 168 .1.1.
Another source is serial zero zero tunnel destination.
No tunnel known.
Yes.
Nice tunnel mode.
Multi point, right?
That's the first one that we use.
That's the normal one.
IP.
IP and IP network ID.
So we need to map anything in the beginning.
No, let's just let them come and register.
That'll be one.
I'll do the same on the other hub, but this becomes R2.
Right becomes that too then spoke.
Interface Channel zero IP Address 1921681.3 then down source remains the same.
Dalmore MultiPoint IP and network ID is ten.
Mapping one 51.69.
For now, it's enough.
And.
Not good.
Let's try that.
Karen is the Hapac, so let's record that.
Before that, I want to see R1.
Has he received all the mappings or not?
Have people come and registered for HP?
Three, four and five all have come registered.
No.
Mapping is incomplete, so everything seems okay right now.
I will not do anything.
I'll just keep my wireshark on.
I can start capturing on R3.
Right.
That's being from R2 to R2, R3 to R4, because my spokes are R3 and R4 92 168 .1.4.
Bingo.
Successful.
He.
Now there's only one.
Three, two, one, one, two, four, one.
Our first reply should also be our first resolution request should be here.
Them from the other side.
Yeah I'm capturing arteries part.
Should have a reply.
Right.
R3 will show me.
Yeah.
It has a request, only a request.
And then it gets a reply from Ford.
Ford doesn't send a request,
but it has it resolved.
But it is not sending it all.
Alpha did not send the request.
Let's let's again try this with your what do you call it, phase three.
So we see it here.
We'll see phase three if it goes both ways.
So the redirect message and then it will trigger the delay.
We'll see that before doing that.
This is fine.
Right now I want to do what?
Internal networks to talk to each other.
So for that, from the hubs perspective, I need to go to interface Channel zero IP, NTP map multicast
to all the dynamically learned pairs, also to the spokes.
I'll go and say IP interface Channel zero IP NTP map multicast to 150 .1. 16 dot.
Why was this a public address?
Another one.
When we try to server, it's a one.
When we type on the server, the server address is the 192.
Yes, but why is this When you map what you're saying is if you are going to the private address of
this, the public header should be IP map 192 168 1.1.
If you are going to 192 168 1.1 the outside header destination should be one 51.16 dot.
It's like this.
It's like on my pocket is going from 192.1 68 .1. 2 to 1 92.168.1.1.
Right.
I'm saying if when I say map, map 182 and 68, 1.1.
If the inside address, the private address that he's trying to go is 182 168 1.1.
The outside header should be 151 dot 16 dot one source is already specified.
So based on this I say this is the public address here.
You're saying if it is multicast.
Then send it to.
151 dot 16 dot one.
Understand the difference between the two.
Just give me a second.
Yep.
Good night.
Now, that's what I'm doing on this, folks.
I'm saying all the multicasts should be sent.
Its IP address every map multicast 151 dot 16 dot I'll have to run OSPF now before I run OSPF, I need
to make sure that what I need to make sure that the tunnels go down and up.
Right now I'm not using dual hub.
I'll tell you why is the reason for that.
It's single hub.
I do have not I have not given him as the NHS.
I have not pointed anything to it.
R2 is just.
That's what I'm explaining.
I'll explain.
It does work with dual hub, but you'll have to change certain things.
You'll see that first.
I'll go here.
Router OSPF one network is 182 168 1.0 Area zero Network ten 000.
Also area code.
Three
daughters
use the same command.
Area zero.
Network ten 000.
Copy this and paste this everywhere else.
My neighbor is up right
here.
The neighbor is up, so I be best neighbors.
My neighbor is up full from this end.
Nothing from here.
Only one is up.
Let's check.
Why?
Show IP, OSPF Interface Tunnel zero.
What is the network type?
The input type is point to point.
By default, you're running on top of what is the network type.
This is money.
And it's supposed to be.
Point to point.
See what network type is.
Network type depends upon what is your layer two technology that you are running on.
Depending upon the layer two technology that you are running on, right.
We will consider it to be you're running on serial links right now.
If if this was a broadcast link, if this was an Ethernet link, if he is an Ethernet here, it will
it will move to Nvme and not broadcast nvme.
But since it's a serial link, consider it to be a point to point link.
When this works.
See the problem with point to point is.
Point to point can only have one neighbor in OSPF, one media for there has to be no in point to point.
There is no elections for point to point has no elections.
That is only in broadcast networks.
For point to point means.
On this link, only one end is connected.
Only one router is connected.
One point doesn't matter.
That's what you see right now.
These are point to point, right when you do your OSPF neighbors.
The state is now.
That's why the neighbor came quickly.
Why do they not require any elections?
Because they know that it's a point to point.
Point to point means what?
One point to another point.
Will this work in this scenario?
If it's point to point means R1 can only have one neighbor.
Right now, R3 and R4 right now R1 is with whom?
R1 and R3.
R1 with R4 and R1 with R5.
Neighbor will not form because it's a point to point link here.
Exactly.
So what I'll do is I'll go to the hub and change the network type to point to multipoint.
So this point will be a multi point link.
It can cause, but from the spokes I'll keep them as point to point.
For them it's okay.
R4 is pointing to R1, R5 is pointing to R1, R3 is pointing to R1.
They're all pointing to one neighbor for their from their side.
Point to point is fine, but from the hub side it should be a multi point thing for OSPF.
I'm not talking about the network as it is not OSPF treats it as a different thing.
So I'll go to the Hub and change the type to what we're why is why he came up first.
Whoever comes up first becomes the next.
Now to do this, I'll go to R1 Interface Channel zero, IP, OSPF network type.
I can have all of these different types.
I'll choose point to, point to multipoint, point to multipoint.
Change the type.
The neighbor doesn't come up.
It got detached.
Delete it.
Can you guess why?
See.
Exactly.
Check this out.
So IP, OSPF Interface Tunnel zero.
What is your hello timer 30?
And the moment you change your network type to point to multipoint, your hello timer also changes.
And in OSPF to form, neighbors should have the same.
Hello.
Thanks.
This is exactly why they brought it into routing in Switzerland.
So these small little things.
Now you change the network type, right?
So you think it should work.
But since hello timer was changed the other side.
Let's check the hello timer on R3 show.
IP, OSPF interface tunnel zero.
Either I can either change it on all the spokes, make them as 30 or on the hub.
Just on the hub.
I'll have to change it.
Interface Tunnel zero IP OSPF.
Hello.
Ten.
That is calculated by itself.
Normal.
Yeah.
Three times.
The Hello neighbor is up.
What about the other neighbors?
So run section interface.
So run for the first time.
Oh, it's.
I need to change the network type back again to show you because I was shut down.
It it up.
See if it becomes network.
The default was point to point, right?
If I change it to point to point, my neighbors will go down.
I'll have one.
She'll keep on flapping one.
Then we'll go down.
Then another one will come up, Then we'll go down.
Then another one will come up.
Then three will come up, then not four will come up.
It'll keep on flapping.
Right.
Because it's unstable by R1 is point to point and all of the others are also point to point.
So R1 is not accepting is getting one.
Hello from here.
One from here.
They keep on flapping for this for you to fix it.
Interface channel zero IP OSPF network point to.
Changed to MultiPoint interface Channel zero.
Check the hello timer again.
The low is 30.
Go back again to IP.
OSPF.
Hello to ten.
The moment you do this, it will stabilize and everything will come back.
Loading done loading done loading.
Loading is done.
IP route has all the routes.
Two is not in the picture anymore.
Can I play this with 10.2?
Can I have dual hub in here?
In this topology can I have dual hub.
I can only have one half.
In this case, I can only have one half.
Correct.
Why only one half?
Because all my spokes are point to point, they can only point to one of the hubs.
I could make them point to multipoint.
That's phase three.
So all of them will be point to multipoint.
That is the final solution of the problem.
Make everybody point to multipoint.
Why this one?
Because you can only have one point.
Because my spokes are point to point, right?
My spokes are what?
My job is point to multipoint.
If they are point to point, they can only point to one guy.
Okay.
They can only have one thing.
So you see, there is no here in this case.
No, These are separate links.
One at a time.
Right.
Since they are point to point, they will all be pointing one place.
So only 1.10 hub to hub where everybody is pointing.
What I want you to see is check the routing table here.
Then Not one.
Then not four.
Then not five.
All through what?
Phase one.
All through.
Phase one.
If I think Trace route ten .5.5.5 with the source of ten .3.3.3.
Goes through the hub.
How can I make it?
Spoke to.
Spoke.
Redirect.
Shortcut.
Redirect.
Shortcut.
Let's do that.
Interface Tunnel zero.
My wireshark is running.
IP, NTP redirect and on the spokes.
I shot.
The.
And both tabless.
Basically what you're doing is whatever redirect you're getting, you're using that to send to trigger
your resolution request.
How's that?
Yeah.
If you don't do it, doesn't have that.
It doesn't have the full route.
Its route is pointing.
Towards what?
Towards the hub.
Yes.
So you have to go to that table, get that information from there, and then move forward.
From this.
That's why self should be enabled for this.
Yes, it should be there.
If it doesn't, then it won't be able to, obviously.
For that, Yes.
I'll stand on an.
This is the hub.
Right.
So the hub.
I'll keep checking it.
Now, this is spoke with, spoke, R3, spoke.
So I'll keep it as it is.
Let OSPF be because then I'll know that this is the spoke.
I will ping from R3.
Now I want to go.
Where Ping ten 444 with the source of ten.
Three three.
This second resolution, request and resolution, replies C to redirects to different corners.
Right.
Then a request from 3 to 4.
When you're looking at this, look at this as a couple from 3 to 4, from 3 to 4.
Right.
From 3 to 4.
Sorry.
From four to.
A request going from three, going into one, coming out from one going to four.
Which one ID is exactly?
ID one session, right?
Correct.
So six and six.
Right.
Going from 3 to 1.
Coming out from one to going to four.
So this is one request.
That's another request.
So four requests, right?
And then the replies go straight.
So if you check the other side, you should have two replies.
The recent reply should be to.
So why did the other one?
This four replies I think is because of the redirect sent to both sides.
Because the redirect is sent to both sides.
The other one, the one which we did before the resolution request, is created on its own, right?
So when it sends to the other side, I think in the resolution request, it stated, what is the address
of the other side?
In the resolution request.
So it doesn't have to send it back up again.
But sometimes it does, because yesterday I remember I think one of the times it does.
It does.
You'll see four.
So sometimes it does if he doesn't receive it properly.
Mostly it doesn't.
We saw it today also.
It doesn't Mostly it doesn't.
So but again, the process is the same.
Request.
Request, reply.
If he doesn't resolve it, request request, just like it's happening right now.
So whoever receives it, they'll send a resolution request.
Resolution request will go to the other side.
Replies will come straight.
That's what's happening.
Yeah.
Same concept.
Spoke to spoke.
Communication is done.
Phase three is done.
But the problem is.
What?
The problem is only one hub.
In this case, Only one hub.
How do I move to other hubs?
I need to go to all the spokes, IP, OSPF, Network, Point to multipoint.
IP OSPF network.
Point to multipoint and r-5 also.
IP network point to all the spokes are point to multipoint.
I need to change the timer back up again here.
Back to 31st we have.
Hello.
Interval is 30 so that now it's in synchronized hello timers with all the other spokes.
Right.
Also R2 needs to be configured for OSPF so I'll go here.
Router OSPF one Network 192 168 .1.0 Area zero Network ten 000.
Let's have a look at our two and tell me which commands are missing.
But commands are missing here.
Type and map multicast dynamic IP and.
Nothing much.
Network ID is up.
That's all right.
Anything else?
IP, OSPF, Network.
Point to MultiPoint.
Another hop.
Right.
Should also have point to multipoint configurations.
He's the
first for the third degree.
Let's go here.
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.
20 6.2 multicast.
150 dot.
26.
That's it.
Probably the same thing and everywhere else.
Right.
What does it say?
Number two is up.
Neighbor two is up from here, also neighbor two will be.
Wipe it out.
Now I have to neighbors some I'm getting from some load balancing.
I'm load balancing to go to these networks.
Now, see, this is OSPF.
It gives you the full information about the network based on this LSA database.
It tells you everything.
182 168 1.21.41.31.01.1.
Everything is in the routing table.
You can summarize.
You can summarize and get you the same information.
Will keep it make it easier for you.
So if you see R2 right now, try it out.
I do has all the information.
Ten, one, ten, two, ten, three, ten, four and ten.
Five.
Now let's go ahead and try to do what?
From R3.
Let's try to go to traceroute.
Ten .5.5.5.
Source of ten .3.3.3 first.
Second is string.
Go to 10.4.
Is going directly anyways.
So and is the same.
Same as yesterday.
There is no difference.
Right.
No difference at all.
So the only thing that you have to be careful about is to make sure you have the network types are okay.
Also, another thing is R1 and R2.
See, there's a problem on R1 and R2 show IP route if you do it on R1 is getting the information about
10.2, but from where?
From the spokes.
Should that be the case?
That's because R1 and R2 are not neighbors among themselves.
And since it's always split horizon problem is not here.
So R3 learns 10.2 and tells it to whom?
R1 r1.
R2 learns ten not sorry r4 learns ten R2 tells it to.
R1 To fix that, I'll create a neighbor relationship between R1 and R2 directly so they can communicate
and R2 and R1 will be the Loopbacks will be shared.
Yeah.
Point to multipoint is anyways.
Anyways, it's multi point, so no problem with that.
Right.
So let's go here on R1.
How do you do that?
Because it won't be dynamically registered to me.
I'll have to map it.
102 168 1.2 is 150 dot 150 .1. 26 dot.
Also I need to say map my multicast.
I'm sending it to the dynamic pairs.
I also need to send it to this guy, which is.
150 .1.26..
I from R1 from R2.
Same IP map 192 168 .1.1.
Hype and IP Man hundred 92.162 Sorry multicast.
16.
Dark
neighbor is up high, one's neighbor is up.
R2, R1, R1, R2, ship it out now.
10.2 will be stable.
Everything goes to normal.
They even from our trees perspective.
Check.
It's all good for Archie to go to 10.4.
There's two ways for him to go to 10.5.
There's two directions.
Right.
So it doesn't matter which one does it choose.
As long as he's getting the reply, it's fine.
Okay.
Good enough.
Everybody okay?
What I'll do is I'll shut the tunnels on the hubs.
On the spokes.
Three.
You have to summarize it.
You have to summarize the routes to the routing table.
I think it's area summary.
I think it's summary.
Summary address.
Okay, we can summarize.
Somebody's address, I think.
Somebody address that for the somebody address works on but still try.
I shut my spokes again.
I want to show you when the hub dies, what happens with.
What do you call it?
Spoke to.
Spoke.
Communication.
Loading.
Done.
No router OSPF one.
Summary Address ten 000.
Somebody that works for as and area zero somebody works on between entire areas within the area.
No, because it will not work for a reason.
Because it's lsas.
Right.
And lsas are shared everywhere.
So lsa, he's, he's.
He's lsa.
He's lsa and lsa one will come to everywhere.
If he knows the LSA one, he sends him his LSA one sends him his LSA, one sends them LSA one.
In this case, not like that.
That will be broadcast.
These are the hubs.
So I'll send all my lsas to the hub.
I'll send all my lsas to the hub.
Send all my LSA to the hub.
Yeah, go to any of them.
Okay.
Beat out.
This information is still see this information is here to is because of the LSA.
LSA is what advertise all the directly connected links to me.
Right.
So when our three tells R1R3 is telling r one.
Listen, I have 180 268 1.3 and ten .3.3.0.
Okay.
Can you can you put the loopbacks in a different area?
In a different area on the Loopbacks?
That's a good that's a good thing.
IP, OSPF, one area, let's say one.
This is done interface loopback zero.
Oh, between the.
Yes.
Five.
Let's keep this at five.
Let's keep this as four.
Let's keep this as three.
Right.
So 3 or 4, depending upon how you're getting it.
So right now should get it as interior.
Now you can summarize.
I will remind you.
Now you can manage summarizing right one.
So now I'm getting 10.4 as interior out.
10.5 is inter area 10.3.
So if I check my show, IP, OSPF database, I have area zero coming in.
I have these guys which are coming in as threes 10.3, 10.4 and 10.5 is coming in as LSA three.
Right.
So I can.
This.
There is.
Are zero range.
I'm sorry.
I thought it was me.
It's this one.
Summary.
The summary.
I want to try this first.
I want to see if this works.
Why do I use it in area zero or area one?
Because he has only area zero.
I could use it on the spokes, but that will not give me what I want.
On the hub.
But I have to connect all of them to area zero.
Right?
Because.
But.
Okay.
What you're saying is the hub will remain.
This part will remain in area.
It has to be in areas in the spokes.
Right now what I did was I made this area one area three area four, an area four, an area five, because
all of them have to connect to the same area, right?
My area right now, I can do summarization here.
I cannot do it on one.
Summarization can be done here right now.
Why?
Because AVR is here.
R3 is the AVR.
R5 is the AVR.
R4 is the AVR.
Doesn't serve the purpose of what I want to do.
Why not put R2 and R1 and R2?
You mean like this?
But which interface?
My connected interface is this guy.
I need to connect from the same interface to all of them in the same area.
Right.
This is 192 168 1.0 slash 24.
This is .1.2.3.4.5.
We're here for the ten Network.
For this ten network, you mean.
Then I can only summarize ten dot one.
I cannot summarize these guys.
I'll be able to summarize ten .1.1.0, but that will not serve me the purpose.
I will not be able to summarize these parts from one to another.
Summarization is done when these roots are moving from this area to another area.
One area summarization.
So from here, how do I do it?
I have all the roots coming in here, but I'm running Area zero.
Right.
So this way is not possible.
You need to find another way.
But again, that's exactly why OSPF is not used because of all these complications.
All of this.
It has too much information in there.
It calculates the whole map of the network.
You saw how it also knows every router now knows the endpoint.
Full map of the necklace.
Right.
Summarization.
I don't think it's possible here.
Maybe it is, but it might be.
I mean, it's too complicated for the whole network to design it like that.
Right.
So phase three will have issues.
It won't be as the same.
It won't be the same as what you do.
No, just summary Disabled.
No auto summary.
Bring back the summary.
Its default is default.
It summarizes by default.
Right.
Yeah, that's what it is.
Yeah, that's how it works.
OSPF is complicated.
Plus, the complication here is also these networks can see the Loopbacks as Loopbacks as slash 32 networks.
How do you change it?
Go to the Loopbacks, change the network type to slash 24.
So they'll come as slash 24.
So too many different things with OSPF.
But again, let's move on to phase two.
We did phase one and phase three.
We didn't do phase two.
What was phase two?
Phase two was spoke the spoke without an redirects, without an IP.
Now this is something which is not used a lot.
Before I go there, I didn't check the most important part.
Let's talk.
I'll explain.
I stopped R1, the hub is down.
I need to make sure that my communication does not go down.
Before doing that very carefully, I shut down my internal interfaces, so I made sure that my NPS are
not resolved.
I made sure that the NPCs are not resolved.
So when I trace it out to ten .4.4.4, I need to make sure nothing goes.
The first time.
Obviously, it takes time.
Second time it doesn't.
It still takes time.
So we have all the mappings as complete as I do show IP, show, IP direct command.
Do I have that?
I do have the redirect on the spokes.
Everything is going from right now again because the hello timer, dead timer is what, 30 and that
timer is 120 So it still thinks what one is alive until one 20s it will think one is alive.
So you'll see that this latency will be there for the first packet.
Latency will be there for that amount of time.
10.4 has been resolved.
Ten .5.5.5.
The first latency will be there because he's looking for both the hubs.
So traceroute will take a little time.
Your traffic will not be stopped.
It's still going through the hub.
The traffic will not be stopped.
But he's trying to see it's expired.
But my spoke to spoke.
Communication is still going on both sides.
No, no, this is not through the hub.
This is direct one hop.
It's already resolved.
The first packet resolution packet will take a little while because it will try to go to both of them.
The other guy will not be there and then he'll try to go to the other one.
This wouldn't be a problem.
Why?
Because you have two hours to do this.
You have two full hours to do this.
Here I remove.
I shut down the tunnel to show you.
Even if you don't have the mappings, it will still work.
So here it works exactly like that.
It's just that in the routing table you have to be careful of how it works.
You have to know how OSPF works.
For that, you have to understand OSPF properly.
OSPF has been broken into and just to teach the concepts of OSPF how it actually works with different
networks.
We saw point to point.
That was a single hub.
We saw point to multipoint on everybody that was with dual hub.
We saw phase one as phase three.
What is the difference between phase two and phase three?
Phase two does the same, spoke to spoke, but based on which table?
The routing table.
The information in phase two is not in self.
It's in the routing table first, then it goes further.
That is the difference between the two.
If you don't understand step, if you have not done it before, it's all right.
You just have to understand that routing table information should not be there.
See, in phase.
In the phase which I have right now, my next hops for all of them are what?
What is my next hop for all these networks?
That too.
So in the routing table is not resolved in my routing table.
It's not resolved.
Again, if you want I just figured it out.
If you want to solve the problem, if you want to solve the problem of this of the routing.
Right.
What you can do is you can actually go to all the spokes, not advertise, advertise it only to whom?
To the hub.
Let me think.
The hub should not advertise anything back.
So what I'll do in the hub is I'll apply a distribute list passive interface, but it will still receive.
Right?
I don't want him to send anything out.
It will stop hellos.
Also, what I'll do is I'll apply a distribute list.
What I'm trying to do this is R1, right?
Check this out.
I'll go to R1.
I'll create an access list ten which denies ten 000.
I am trying to reduce the routing table on this post.
Right.
I'll create this access list and I'll say permit any
done.
Then I'll go to the interface channel zero.
I'll say distribute list.
First place.
Yes.
No.
Yeah.
No, it's all on the interface.
Also IP, OSPF filter list.
I think you can apply it on the interface.
No.
It is.
Yes.
Under the process it is.
But you can apply it on the interface of I remember right now, I don't remember how it is here.
You can distribute list and where do I want to apply it then?
Which direction?
Outgoing direction.
Outgoing direction?
Yes.
It is not allowed without.
Okay.
So it wouldn't send any routes outside.
Also on R2, I'll say router create the same access list.
Why?
I'll tell you why.
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
trying this stuff out.
Access list and permit any router.
OSPF one I'll say again distribute list ten in the outgoing direction.
So if you see your show IP route, your routing table, it does not distribute.
Player.
OSPF.
His back up again.
There is still receiving the house.
Oh, it's.
Is it.
It's not.
It's only receiving from 1.1, which is good right now it's receiving from everybody.
One, two, three, four.
This is not gonna just look, listen to.
You know, he's receiving it from everybody.
I could do it.
Incoming.
But that wouldn't be a problem.
But I want the hubs to have full information.
The hubs should have the information.
That's how they'll send the redirect.
I want the hubs to have the information, but not send it out.
The problem is, I'm learning everything from the same interface.
Then they will directly communicate
to the spokes.
I know that.
But what my objective is I want the routing table should not be here.
Yeah.
I can.
But the problem is, then the hub will not have the information about the networks.
The hub should have full information because then he knows that I need to send the redirect message.
What I can do now, this is again more complicated, but I just want it to work.
I'll create another ACL here on the spokes and I'll stop the incoming updates.
You can do that, right?
So I'll say deny ten 000 access list n permit any.
Then I'll go to router OSPF one distribute list ten in the incoming links.
You might ask the question, Why would I do that?
Why would I do that?
Because what I can do is I can have a static route.
By myself.
And I can say the next half of this static route is 1.1.
And sorry, this is this is a mask.
1.1 and one dot.
I can manually tell him what?
If you want to go to ten dot zero network, your next stop is 1.2 and one dot.
Reducing the routing table on the spokes.
On all the sports.
I have to use the same command on all the scopes distribute list that this is what this is Disaster
management.
If you have 1000 spokes and too many routes are coming in, you could use that.
It will not.
I have the redirect there.
That's the best part.
Right here, right now.
I need to first make sure that I don't have an incomplete mapping.
Everybody is registered.
Let's layer it everywhere.
But when I do that, I need to shut a no shut from here.
They come up and register again.
Go register yourself to both of them.
It has neighbors.
Are you register yourself?
And.
Want to just turn yourself.
Right.
Ship it out.
I do have all the routes.
So I'll go do is R3.
Let's check R3 show IP route has that I applied the distribute list to around R5.
I want to make sure that it works.
I have the distribute list already applied.
Ten .0.0.0 so I can ping.
I want to see if I can trace route to ten .4.4.4 with the source of ten dot.
It's working fine.
It's working the same as it was before.
The only one reason why this should work is the hub should have full information.
The hub should have because the hub will root.
Then the hub will know that both are directly connected.
Then it will send the redirect message.
But why does it matter whether.
If you have 1000 spokes, as I explained yesterday, 1000 spokes means 1000 routes in the routing.
I'll be dropping in.
Yeah, but you'll be consulting the routing table, right?
What about the other outings that you're doing from the inside?
What about those routings?
You have a lot of memory for routing cables.
You'll have to go to all the spokes and add the access, which is not feasible.
It will work.
Yes, you will not use it normally, but if you have 1000 spokes, it's better to use it to reduce the
routing table.
If you're using an example.
But again, the best solution for this is what?
Why?
20 years accesses to different areas.
Only you can summarize on the right one is not an its area zero.
It's getting routes from area zero.
Then it can stop from that loopback from that area.
Coming into this area, you want routes to be stopped into area zero, right?
The problem is area zero has many different gateways where the routes are coming in from.
One is coming from here, one is coming from here, one is coming from here.
Three is leaking in one, route four is leaking, one Route five is leaking one route.
Once it comes into area zero, it's it's gone.
You cannot stop it.
So it comes into area zero.
Then when it's come to it comes to R1, it's already in area zero.
Right there.
Timer expired.
So already it we can stop the spokes.
But the problem with that is the hub will not have the information.
I want the hub to have full information.
You cannot do it that way.
The hub.
So I can stop it when the hub is saying it out, telling others about it.
I can go to the spokes and stop it on the spokes from receiving those 1000 rounds.
The last is.
Which one?
Phase two.
For phase two, first of all, what is phase two?
What is the difference between phase two and phase three?
Do you remember?
Everything is in the routing table.
All the information is in the routing table.
The first thing that you will remove from your hub is the redirect command interface, Channel zero,
No IP and redirect.
No IB and AP in OSPF, Phase two is implemented using the network type broadcast.
When you have a network type broadcast, you will have a BTR and everybody else will be there.
They'll exchange their OSPF databases since they know that everybody is on the same network.
They'll exchange every information.
Then every router will find the closest path by himself using the SPF.
It doesn't need the information from anybody else, Not the not the BTR, no split horizon problem.
Every router will find its own way to the destination.
It will find the next hop to the destination by itself.
It will map the whole thing.
But what do you have to make sure before you start this, you need to make sure that R3, R4 and R5
do not become either DDR or the DDR.
Focusing on the priority will be zero on all three of them before you start anything else.
You can increase it here, but since I want them to never become the DRB, I'll keep it as zero.
So automatically one of them will become the DRM.
The first thing before you start this is you could go to your spokes interface tunnel zero IP, OSPF
network type, not network.
Sorry.
Priority zero on all of them are for also IP.
OSPF priority is high five.
First priority is done.
Then change the network type to or all of them.
Done interface detached.
Will take a little while to form a neighbor.
Why?
It'll take time to form neighbors.
Why elections?
Elections will take place for everything.
Elections will take place.
Elections do take time.
Around one full hello dead interval elections will take place and then R1 and R2 will be deciding on
who's going to be the doctor and who's going to be the fighter.
It is.
No.
It was.
Now it is.
It takes a little while to converge because of the elections.
Right.
Who's the doctor?
R2 is the doctor.
R1 is the DDR.
The others are.
Check the routing table.
You'll be surprised.
Next up, resolved.
Just like in.
You said no.
Next hop self in OSPF.
You don't need to do that in broadcast networks.
They will automatically resolve it themselves.
They will find the closest path to wherever they're trying to go.
They'll find the closest path, resolve the next hop and move forward.
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
resolve the address of that phone.
The information is in your routing table.
Dot C is me, so I don't really need to go there.
Five dot.
I will have full information about you.
In the routing table again here for this network type, you need to make sure that your full routing
table is resolved where on all the spokes because the next hops are hidden.
Where in this course in phase three, the next hops are where in the output table here it's in the routing
table.
That is the big difference between the two.
Any questions?
Broadcast.
Right.
We don't need to.
Multicast is already allowed is broadcast.
Right?
Network type is broadcast.
I didn't use it in also I said multicast multicast to this address actually, you know I mean not right.
That's true.
Here is dot five and dot six.
I'm mapping the full multicast, right?
Yeah.
It is supposed to broadcast the command for your broadcast remains the same IP map multicast to R1 to
R2.
R2 is sending it to the dynamic phase, is sending it among themselves.
So that part remains the same.
Make sure, though, when you're doing this, make sure you don't make the mistake of R1 and R2 not
being neighbors.
R1 and R2 should have static mappings between them because if they don't, they will not be able to
do any elections.
R1 and R2 have to be part.
Then if you don't have that, you'll have a conflict.
Yes, you'll have something like this.
There'll be a separate election here, a separate election, which will be conflicting.
So one side will come up, the other side will go down, one side will come up, the other side will
go down.
He'll become the doctor.
Then he'll become the doctor.
He'll keep on conflicting because they're not communicating to each other so they cannot elect among
themselves.
You need to make sure that this relationship is there.
Then only they can participate fully in the complete election among them.
These three are not participating.
The elections are only between R1 and R2.
One is the Doctor VR.
Okay.
From production point of view, not as important as ERP.
So if you have to give your priorities, ERP phase three first priority, phase two, second priority,
then come here.
OSPF.
OSPF point to MultiPoint is the first priority.
Broadcast should be your least priority.
Will never ever use this.
It limits you to only two hubs.
You can have a third one, but that will be useless for a long time unless one of them goes down.
Then it will become the VR.
Then it will do a synchronization and so many different things because the AR and VR, right.
The third guy will not have any information about the network at one time.
Only one, right?
One is up.
But he can go for his to both of them.
You can't call him
only when it has the full.
But does it have full information?
Yes, it has full information.
So if it gets an IP resolution request, will it be able to send a redirect?
It will.
The only thing is it will not update anybody on the network.
Update.
The job of updating about networks is R1, but if he gets a request, he will reply.
But that is a separate process and OSPF is separate.
The AR and VR both receive everything.
It's just that when it's supposed to update the other neighbors about the other networks, only the
DA doesn't.
The DDR stays quiet, but it has full information.
Why does it have full information?
Because if the DA dies, VR will start updating everybody else.
The problem with third hub would be the third hub will have no information at all.
So if I have configured as the third hub also when he receives the resolution request, it will have
no information about the network, so it will not be able to resolve that.
Right so not not really use it is mostly used is one end.
The first and the other ones in order.
Clear.
Any questions?
No.
That finishes your MVP and your first advanced VPN.