We are aware.
What does this term mean?
We are.
Virtual routing forwarding.
Okay.
What you're basically doing.
You're dividing your outer, which is, let's say, for example, in this case, our five, you're dividing
our five into instances.
Do you remember contexts in failover?
Security context.
What did you use to do?
We had one box.
But once you convert it into mode multiple, this one box is not one box anymore.
It becomes virtual boxes inside a big box.
So when you're dealing with it, you deal with context one and context two.
And then you assign interfaces to it.
The thing was, whatever interfaces you assign to context to has nothing to do with what interfaces
you assign to context one.
There was no co relationship between the two, so completely separate.
The traffic from here from C1 did not affect the traffic from C2.
The same concept can be applied to routers also on routers.
What you can do This is R5, for example.
I could divide R5.
Into two contacts.
How do you differentiate between the context in one context, only one interface can be put.
One interface.
Or if you want to have a look at it this way, one interface cannot be put in more than one context.
Or we will refer to them as we are from.
Now I say you can use shared interfaces here.
You cannot.
Here.
One should have a dedicated interface.
That's what I'm going to do here is I'm going to divide our five into two.
I'm going to divide our six into two.
And this is done locally, by the way.
We are local.
All right.
So what I'll do is I have one connection.
I have two connections here.
Right?
So I basically have a connection like this.
Basically something like that.
I the interface pointing to R1, I'll put it in one vf.
I have two interfaces here.
One of them I'll give it to this VF so I have a connection full setup on the other side.
I'll do the same.
Let's I do this for all the zero zero links.
Right now.
You can call this anything.
This site can be called anything.
You call it site A, and this site can be called.
So I'd be just a name.
Why would you require first of all, the question is why would you require the RF?
Right.
Usually what happens is.
This would be somewhat of a service provider.
Our five.
Our six will not be directly connected to each other.
This will be somewhat of a service provider.
So R5 and R6 is connected right now.
These are company assets.
Company.
I just wanted to talk to each other.
Usually you have something like this.
Or one wants to communicate.
To whom?
These are two parts of the same company.
Right Tomorrow what could happen is another company would come in to you, get a connection from you
so that they can communicate to each other.
Across the Mpls cloud.
Now you only have one router.
How do you make sure their traffic never interacts with each other?
And there can be a possibility where both of them are using the same subnet on the inside?
They can be a possibility that these guys address is also 1011 11.0 slash 20.
How will I manage that traffic?
It will be using.
No, this is a private networks.
Private to private communications.
It's actually an Mpls town.
Actually, it starts with Mpls.
That's what you do.
You do it in Mpls.
That's the biggest place.
I mean, biggest implementation of Vrfs are Mpls.
That's why.
That's why they were built.
But the question is.
All right.
You're doing this.
What if you wanted protection to the furthest traffic?
What have you wanted to protect this traffic going from here to here?
It is still going through the cloud, but it's open, right?
Clear text.
What problem are problems solved for you was now you have to write.
If you're connecting this interface to an instance of ERF and this interface, I'm connecting to this
instance of ERF.
It doesn't matter if both of them are in the same subnet.
IP This can be ten, 11, 11, this can be ten, 11.
11.
There is no correlation between the two.
Similarly, these two interfaces could have the same IP.
Who cares?
These are not connected to the same router.
Physically they are, but logically they are not.
Logically, they are connected to two different instances.
If we had lots of.
Subinterface.
And then put the subinterfaces in.
For each of those companies.
You just have to make sure one logical interface per vref at least.
Right.
Look, I'll do the same on the other side.
Let's see how this works.
Let's configure the edges first.
Simple one.
So.
You don't have to worry about the labels and everything that will be done for you.
Mpls Cloud will do it.
Your job is how to apply VPN to the RF aware router.
How do you use it?
Will come with labels come at two point.
Not where if it's just a router.
Labels will be.
As such.
They will be here.
They won't be changed.
See labels will not be used by you.
No Labels will be used by the cloud.
The cloud after we arrive, after we arrive takes place first routing and everything will be checked.
Right?
After the routing Mpls don't worry about.
Similar, but better.
Shut.
And they beat out.
When it starts.
R2 is done.
Then.
So r1, R2, r3, r4 set.
I need to fix what?
R5 is the one where I need to do my.
Okay.
First of all, the question is you need to define the VFS.
Very simple.
IPV, RF name it, I'll call it site A.
College site.
There are many options here.
You don't need to learn all of those.
These are used for export import.
These are all used in Mpls.
The one which we are doing here is the most simplest form.
It's called light.
You don't need to worry about these features.
All you need to worry about is.
A the RF is not up unless and until you give it a route distinguisher.
Route distinguisher is nothing but a number.
It has many different ways of applying and why we use it, where we use it that you see in Mpls in case
you move to Mpls right here.
In this case, all you need to do is to bring it up.
To bring it up.
All you need is a number here.
That's it.
Any number.
It's used with a colon and an address.
Number and a column number, colon number.
Why is it used for as.
It has its own boundary numbers.
It uses that later if you're using it for.
Because they use this for communication across across different edges.
Across different.
What do you call it?
Sites across the cloud.
They will use this number to communicate to each other.
Right now for us, we just need to point it out that this is a RF and this is the D for this VR, I'll
create another one.
IPV, RF, I'll call it site B.
Again, this is locally significant.
One, two.
You just have to make sure it's not the same.
You could use any other number.
Right.
The command is show.
It shows you the state right now.
I have site.
A site B is important.
You have to specify one does not matter what as long as they are separate.
It's okay as long as they don't clash.
Right now, you have, what, 1.1 and one colon two.
Do I have I assigned any interfaces right now?
No, Let's do that.
Zero zero.
Uh, this is zero zero.
This is zero zero.
The ones facing up are zero zero.
The one's facing down are zero.
One's.
Right.
So let's do that.
Interface is zero.
Zero is the one pointing towards R1.
And we specify an IP address.
Ten, 11.
11.5.
Shut.
Interface zero zero IP address is 15.1.1 50 6.5.
Check.
Right now, If you want a pink, I should be able to pink.
Ten, 11.
11.1.
But I'm using what normal routing right now.
I have not divided myself into different groups.
The way you do it is the moment you put.
Anything into IP forwarding site A this becomes part of.
It becomes part of what that we are.
So it's removed from the global routing table.
It will not be in your global routing table anymore.
I'll do the same thing for what?
Zero zero IPV RF forwarding.
Site.
Okay.
So serial zero zero and phase zero zero are part of side show IP interface brief.
Everything has been removed.
Now we configure it again.
IP Address 1011.
11.5.
Shirt interface Serial zero zero.
IP is one 51.50.
I configure two interfaces, right?
If I check my routing table right now.
I should see something.
I don't see anything.
Because now you're not in the global routing table anymore.
Now you're working with what VFS.
Every VRF will have its own routing table, its own routing information.
Right interfaces, which it has.
Separately, it will not interact with the other router.
How do you check that routing table?
Show IP route VRF site.
Okay.
Show me the routing table for site.
Right now, only one because cereal is down for cereal to be up.
The other side should also be up.
So IF00000.
For one, are you can have more as many as you want.
Right now I'm doing it this way.
R1 connected to.
Now when Vref is called.
What?
So R1 is connected here and C00.
FA00.
I'll create another one side B which I'll connect to zero one and serial zero one.
Unchained.
No, no, you cannot share.
That's the thing.
Subinterface you can with Subinterface you can, but you cannot share why I showed you this is because
I want to show you that I'll have the same IP address on both these interfaces.
And you'll see that it will not affect earlier it was not allowed.
But since these are two different instances of the VPN, it should be allowed.
So I'll go to Interface Serial zero one Interfaces of the same.
Okay.
IP are forwarding.
I'll call this side PC01 and phase zero one.
Our society.
Did you check your forwarding?
Type it out.
Site B.
Nothing.
Right now I have to specify an IP.
Interface for zero one IP addresses.
Ten dot 3330 3.5.
No shirt interface.
Zero zero.
I'll give it the same address.
151 .56.5.
Check this out.
Same IP addresses on two different interfaces.
I have same IP address.
Correct or not?
How is it possible?
Only because it's VR.
If it was not aware because the routing tables are different, they don't care about each other.
Side A doesn't care about side B.
What would you do to make it?
I put them into different verbs.
No, they they're not linked.
Right.
These are two different characters.
You see them here.
But you have to understand that these are two different routers.
It faces Christ interfaces.
Site has these two site has.
They are not linked.
They will not talk to each other.
These are two separate.
Okay.
I'll do the same thing on.
I six.
Same concept.
IPv4.
Now local the name can change, but just to avoid the confusion, I'll keep it as I think.
Right.
One, one.
Locally significant site B.
Hardy will be, let's say one, two.
Interface Serial zero zero IP vrf Forwarding site A serial zero zero NFA zero zero.
Zero one will be site.
Tripwire.
Correct.
Configured 0000 is inside a.
F01 is inside.
Let's configure them for zero zero is IP address one 5010.
22.
22.6.
Interface zero zero IP address is 153.1.156.6.
Shut.
That's the good thing is 001 is also the same.
The IP is the same.
Zero one is a little different.
Ten .1234 4440 4.6.
Skype VR interfaces.
Check this out.
000 is 56.601 is 56.6.
Also the same.
F00 1022 22.6 and 1044 44.6.
Correct.
Let's just verify on our four.
1044 44.4 Weather outwards six.
And also are to.
1022 six So our six is okay.
Clear.
Now, the good thing that you have to understand is when you ping again, you have to ping.
Using what?
Because you won't be using the same routing table.
You have to tell him which is the ping coming out from.
Pink F and then you specify side A, then you specify the destination.
This pink is coming out of the RF A and the destination is 10.11 point.
11.1.
Houston Live 11 one R1.
Bringing one from where?
Side A.
Now the connection looks like this.
This is how you look like this is not here anymore.
You have this.
151 .56.01 50 dot 150 6.0.
It doesn't make a difference and these addresses are the same.
Okay.
Kidnapping from here to here.
Should be able to ping from here to here.
I should be able to ping from here to here.
Let's ping from R6 is a to R2.
How pink.
Side since I'm bringing from side A.
Saturday, 1022 22.2 to be able to go.
Can.
From side B, I should be able to bring home 1044 44.4.
Not able to swipe interface f0 one.
Showed an interface for zero one.
Is part of side B, So pink.
Side B.
1044 44.
Dancex is me.
Not four is at the same.
What side?
A and side B?
Thank.
There were two different doubters.
Right?
Check out check this out this way.
This is your actual diagram.
They have nothing to do in the in between.
Okay.
So whatever you have here, it has nothing to do with here.
There's a borderline in the middle.
They will not communicate.
Even if I had.
Yeah.
I did it here.
Right.
How did it work here?
Same concept will work here.
That's why I read it here.
How is it different?
Address, right?
It's an interface with an address.
This is an interface with an address.
Same address on the interface.
You're coming from 56.5.
Going to 50 6.6.
Coming from Lebanon.
Lebanon?
Going to Lebanon.
You want me?
You mean this side should be 11?
No, no, that cannot be possible.
Cannot be.
I i by.
You have.
These are two.
Two different company sites, Right.
You cannot have two sites with the same IP.
Why would you do that?
I mean Site 11.11 and site 11.11.
Why would you do that?
Side B, side A and side B will not talk to each other.
This is a right.
This is for a customer completely dedicated to a customer side.
A side B is a different case for a different customer.
And these are two separate things.
If I didn't want it like that, why did I separate them?
I separated them for a reason.
Right?
Because I didn't want them to communicate to each other End to end, you have to make sure the IP's
are correct.
So where was I?
The pink was not happening.
That's because on our four.
To configure not F0 zero, but F0 one.
Let's try again.
Successful.
So our six can communicate to both R two and R four using different VFS.
I'll check it from r five also.
Our five should be able to bring site B ten dot one.
3330 3.3.
Greg also dot one is also.
Good enough.
What about routing?
I want routing to be in place.
I'll just show you one.
The other ones are simpler.
I'll show you OSPF.
Let's run OSPF on the whole thing.
Just.
Just for the fun of it.
What not.
What is not?
Why is it?
Context is supported there.
No routing is not supported.
When we divided.
Because usually when you divide it into context, Right.
You would usually have a default route doing the rest of the job for you.
Everyone will be pointing towards the firewall and you'll have a default route pointing towards here.
It's supported here.
It's supported.
This is different than that.
That provides you failover in so many different features.
This doesn't do anything like that.
One can be used for failover, right?
One goes down, the other comes up here.
You don't have anything like that.
It's very simple here.
Here as everything but everything as the router is getting divided.
Right.
The routing table is different.
Right now.
You can.
Yes, you can.
But whatever you have created, it will act as an individual router.
Say we say no is is is is entirely different.
Contexts are entirely different than that.
When you do it there, it's mostly used for failovers.
Can you divide the.
Here automatically gets done.
You can do it as per the.
You have to understand this is not done for security context or for payload or anything like that.
This is only done for Mpls so that different sites can communicate to each other.
To solve that problem of ten, 11, 11 and ten, 11, 11 two guys having the same address.
To solve that problem.
That's why it's there.
Now, if I can communicate, how do I run routing?
First of all, let's run it on the edge Devices Router OSPF one.
I'll go to the interface zero zero.
I say IP, OSPF one, Area zero.
Okay.
Good enough.
I'll go to LA to do the same thing.
Interface F00.
IP OSPF one area.
R3.
Hypersphere one area zero r4 is F01.
If I remember correctly.
Okay.
Interface levels.
So I enabled OSPF here on all the interfaces.
Correct.
Now I'll go over to our five.
You have to also make sure of one thing when you're doing it in VFS right side.
If you use the process ID one here inside B, you cannot use one.
You have to change the process ID because you don't want the two OSPF processes to communicate.
That's what a process ID does, right?
Make sure that two OSPF processes don't communicate to each other.
If you're doing that, you need to make sure that the other process ID is also different.
That's it.
Everything else is the same.
So what I'll do is since since this side is also area zero and this side is also area zero, does it
make a difference to me if I use that or this?
So I'll go to R5.
I'll say interface for zero zero IP.
First of all, I have to do my router.
OSPF one I have to tell him router OSPF one is in which VRF.
Side.
A.
Router.
OSPF two is in which the RF side.
Then I go to the interfaces interface fast Ethernet zero zero IP, OSPF one Area zero.
Interface Serial zero zero IP OSPF one Area for zero one IP OSPF two Area zero.
Positive zero one IP OSPF to area.
Today, the same thing will be repeated where again from the beginning router OSPF one is in VRF site
A.
Router.
OSPF two is in VRF site.
Interface serial zero zero is IP OSPF one area zero interface zero zero Same.
Zero one is you just change what the process.
Correct.
So now if you check show, IP, OSPF, Neighbors, you have four neighbors.
For neighbors.
One, two, three, four.
Three and four are side by side on the other side.
If you check the address, will be the same for this neighbor.
56.5 50 6.5.
Good.
Show IP route will be still empty.
Show IP route.
VRF site A.
Venture out for sight.
You have learned a new route.
What is that?
11, six, 11, ten, 11 from the other side.
Similarly, R5 will have learned about.
Today.
Ten 2222.
How is it together?
Us shows you what neighbors because process is right.
They are separated by process IDs.
Boys we have separates them on its own self by process.
One process it belongs to one or the other process.
It belongs to Every different protocol that you see now will have their own implementation of VRM,
but they won't.
Just let me.
It.
Yes.
Also, Vref is a local thing.
Yadav is local on route.
It does not affect the other routes.
It's completely local, so R1 has no idea what R5 is doing.
From our perspective, it's just connected to R5 and R5 addresses.
Ten, 11, 11.5.
Similarly for R3, it's connected to R5.
The address is 1033 33.5.
It doesn't know that R5 is actually two routers.
They're using different instances.
He doesn't know that.
The endpoints don't know that they're connected directly to him.
Then R5's job is to connect and create two instances and then move those instances across, basically
move packets based on those instances.
Right local.
It has nothing to do with the neighbor.
If he's using RF If hes not using RF is not worry about that.
Clear, right.
Let's set a pink from R1 to R, 3 or 3.
I want to add two.
I can bring from R1 to R2.
This is the other interface.
So let me ping from R3 for.
It's a normal thing.
There's no difference.
No difference at all.
Nothing changes.
Yeah, it has nothing to do with anything else.
Doesn't change the packet.
Doesn't do anything to the packet.
It just.
Yeah, it just separates the two routing instances.
If he gets a packet from one routing instance, he will only forward it from that instance.
He will not move to the other instance.
That's what he does.
Basically what you're doing is you're linking interfaces together.
So F00 and F00 are linked.
If a packet is coming from F00, it will not leak out from F01 or F01.
It will always go out from f zero.
You so.
Single autonomous system for.
Without us.
It is possible in BGP, BGP call it.
Yes.
There we use it.
Right.
We have something called address family.
We can divide it there also.
Otherwise, yes, you'll have to send out R and D from both sides to do that.
Correct.
My job was not to do this.
My job was to.
Create the tunnel protection is there.
Traffic is going through now.
I want to do what protect it from.
R5 to R6.
I'll create the tunnel directly connected, but who cares?
I'll create the tunnel between the two.
Between R5 and R6.
The map is the only thing that works.
Who doesn't support routing protocols.
I just ran routing protocols.
I'm not running crypto maps for routing protocols.
I'm not going to do that.
I'm going to do a normal one.
Traffic coming from ten, 11, 11 to 1022 will be encapsulated just like before.
Just like before.
That has nothing to do with the routing protocol.
Then it will be like which interesting traffic is going through.
Routing doesn't go through the tunnel.
That's a different story.
This is routing on public.
He knows the public addresses through the routing.
Right now.
Let's try on our five.
The difference.
Let's see the differences.
Right.
First of all, do you remember the IPS here?
151 dot 50 6.5.
This is 151 dot 50 6.5.
Also, just to avoid any confusion, let me see if I can ping.
I should be able to, obviously, because I'm able to communicate side to side, but still, just to
show you that.
This can be to address dot six and this would be dot six.
Two different sites, although that one is going from 0 to 0.
This is going from zero one.
Okay, Because now I'm going to be using my set command.
I don't want you to confuse yourself there.
This one we already know.
I will not specify my key right now.
Access list.
101.
Permit traffic coming from 1011.
11.0.
Excuse me, I'm going to ten 2220 2.0.
Crypto map.
I call it I map one.
IPCC.
As you can see here.
Who's my other peer?
Devin started.
Onefifty .1.56.6.
Correct set.
Transform set to set.
Match address.
This is what I used to do.
The only thing missing here is.
What?
We have to do that.
That's that's what I'm saying, Right?
We are missing something now.
Right now.
See, this part will not cause a problem because I'll be applying the crypto map to the interface.
Whichever interface the VRF belongs to, it will only be applied to that urf.
Correct.
That wouldn't be a problem because interfaces are already in VFS.
The only problem would be when you're sending the key.
Remember the key.
Where is the key taken from?
From the local router.
Right.
At that time, he doesn't know which key to use if you use your normal here.
Address Crypto ice cap key.
Cisco address.
150 1.5 56.6.
It wouldn't be able to take this because this belongs to the global table.
They said if you do it this way, you will have to find out a way to put the key in the VRF.
Which is done using the command crypto.
Keating.
And you specify the name of the keyring, I'll call it CR one.
Remember Ik v2 we had v2 keyring, right?
Isaac Camp also has a keyring, but until now we never used it.
Now we will use it.
KeyRing R1 Which VR app does this belong to?
Let's say site A.
Pre-shared key.
Address will be.
151 .56.6 and the key will be what?
To specify the key.
Okay, So what you're saying is.
Crypto ice cap.
No, not crypto.
Ice Crypto keyring.
Here.
One is in which we are.
Site here Sipri.
She said.
He addressed basically the next half.
150 .1.56.6 and the key is Cisco.
Okay.
Copy it.
Applied to.
If you have only one.
If you have only one, it's okay.
But if you have more than one sites say you have site B Also, you have to be careful.
Because then how will you tell him which belongs to which instance?
Not IPsec profile will now also make another if you have one is okay it will work.
Without that.
If you have more than one, it's better.
It might still work without it, but it's better if you create a crypto cam profile.
I'll call it Ik.
Prof.
One.
Then we do that and check out the first statement it gives me.
So I'll help you configure it.
It says it is deemed incomplete unless you specify the identity address.
Match identity address.
What is the identity address on the other side?
56.6.
You also here have to specify the VRF.
Then what is the key thing that I'm going to be using for this ICC profile?
CR one And what does this belong to?
It's like.
Where do you think I'll call this profile?
So you have the map.
I map 110.
IPsec Isakmp.
Here.
I set.
Set.
Transform, set and everything.
Right.
I will also say set Isakmp profile.
I named it something.
I brought one.
Did you understand what I did?
Is everything.
So I didn't paste it.
I just did it here.
So done.
Section three.
Always the same at five, right?
Ten, 11.
11, zero.
This is what I did.
56.6 is the other guy which I want to create my tunnel with.
So my key should be sent to 56.6.
If it's only one, it's okay.
If you have more than one.
You also need to create a profile in the profile.
You say this profile is for site A, The key ring is CR one, where you key is obviously the Cisco,
and then your match identity address is the address on the other side plus his.
You bind it.
Where?
In imap Suicide.
I profile I.
That's all you have to do.
Then go to interface zero zero crypto map iMap one.
Again here.
Crypto icecap profile.
I.
Like Prof.
One.
I said match identity.
Address is one 51.50 6.6 Vref is.
It.
Then I also say kidding.
Is.
And the IRS is.
Bind it.
Where?
In the map.
Believes a set transform that you also say set, I say can profile.
Big problem.
Today.
This is from one side.
Where do I bind it?
Interface Serial.
Interface.
000.
Crypto Map.
Where do I buying this?
I have one on serial zero zero.
I will also need to do the same thing on the other side on R6.
Right.
Let's copy and see.
What.
What do I need to change here?
Policy is the same.
Address will change to five.
ACL will reverse.
I guess.
The best.
That's it.
Even the application is on serial zero zero.
Yeah.
I'm sorry, I said that is in the second.
This is in a separate line.
Verify.
Here it is.
Okay.
The address of the peer is okay.
I have the same policies.
Site a CR one address.
Okay.
Seems fine.
Also applied to the interface.
I have.
My.
I don't know which place is this standing on?
This is zero one, so I'll have to monitor the other one also.
000.
Let's send interesting traffic from R2 to R1.
Goes through.
Check here.
Online packets.
GSP also has gone through like no difference at all.
If you check your crypto IPsec, that remains the same show.
Crypto IPsec will show you exactly which vrf you are protecting.
This is for VRF A and then packets have gone in and gone out.
And the same stuff.
I don't see any difference in this one.
It's not really anything difficult.
It's the same thing that you have done until now.
Exact same thing.
You just have to make sure that the keyring and profile are applied.
You can do that.
That's it.
It's nothing different.
Everything will be done for you.
Routing will be done for you.
Will be done for you.
Your routes will always already be there.
All you have to do is apply the VPN.
How?
Just use the keyring and the profile.
Bind them together.
The.
Sorry.
The what?
Right now, the one which I'm doing is I'm on.
I'm doing it on the service provider.
Yes.
To end because we will not be usually home.
Home based users will not use our in a company you will not use.
Why would you use it?
You just use two different routers.
Click here.
Let's do the other one.
These are.
Be beat out.
Knock, knock.
These are somewhere in the middle.
After the label has gone through.
What is this?
Do I need the other one?
Right?
I need to do the other one.
The other side.
Do I need to change this?
I need to create a new keyring though.
I need to create a new keyring.
I'll call it R2 for.
Side B.
Address is the same because the peer is the same and he is the same.
So this should be okay.
Transform set.
I'll use the same transform set.
No problems with that access list.
I need to create a new.
Or to permit IP going from 1033 33 zero.
Going to.
1044 44.0.
Correct.
What about the next part?
Is the cam profile?
I do need a new one.
Right.
I'll call it too.
The address is the same.
It's just that this is site.
Side, B and K is key to the other way.
Yeah.
Done.
Crypto map.
I would require a new one because it's a different, completely different interface.
So I have to apply it to a new interface.
I'll call it to the pier.
Address will remain the same though the set will remain the same.
Ik profile becomes two.
Address becomes two and the way you apply it is.
Interface Serial zero one.
Crypto map.
Map.
Okay, so let's start copying from here again, the ones which I made a change in this one.
It'll be pasted.
Access this 1 or 2, I would require it again.
Then the other profile.
Correct.
You have the map.
Interface Serial zero one Crypto Map iMap.
Let's have a look at the changes on the other side.
This becomes not five.
Access list.
I copied the whole thing, so I'm changing the whole thing.
Access, it gets reversed.
Press become dot five.
I guess becomes at five.
Got five.
Everything else is the same.
Though you apply it also.
So just copy it.
Correct.
Copy it again.
She overrides it again.
Hopefully it doesn't cause a problem.
Access list will be messed up though.
Show access list.
You know.
So access.
It's okay now.
Let's try the first tunnel is up on.
R6 needs to be pasted with the second one.
Short section crypto.
Okay.
Right.
The addresses are okay.
The maps are okay.
The way I've applied is also okay.
So at this point, our four should be able to go to 33.3.
Goes through Show Crypto IPsec.
You have two essays now.
One is for VF one, one is for VR to site a VR site.
The packets are going through it.
I don't see anything different.
So the crypto IPsec.
Gaps.
Send more traffic.
You've seen that It'll be going through the second tunnel.
Send more traffic from R2.
Be going from the first to.
Okay.
Any questions?
Any questions on this and how it works?
It's good, right?
That's what we are.
We are aware.
We call this we are aware VPNs.
So you have some routers with the RF enabled how to enable the VPNs, how to enable IPsec services on
that router.
This is how.
It's nothing complicated.