the next authentication protocol we're gonna cover
is challenge Handshake with Indication particle or chap.
sends a message Digest five or MD five. Digest off the original password or the link.
The original password. Cisco, we're gonna peck.
We'll never be exchanged over that link.
For that reason, both sides must know the password and have a database
have a user name and password in their database to begin with.
the user name and password for each side authenticating the other side on both sides.
Will challenge handshake authentication protocol.
The original password or the actual clear text password is never sent across the link.
However, a message digest five
or an nd five hash of the password is exchanged over the length
chap, you must create a user name password database on both sides of the length.
So I'm going to go to outer one, which I'm here.
It's a user user name, aren't you? Password
and I'm going to go to our two
user name are one password.
Now I'm going to make a router one, though 10 Decatur again.
So in rather one I'm going to say
000 encapsulation P p p
I have taken it with encapsulation ppp from both ends before I started this part of the lecture. So router to is still HDL. See, at this point, which is why
the interface state has been changed to down.
Then I'm going to say PPP authentication chap.
And then I'm going to go to Router One and changed encapsulation two ppp.
And at that point, the link should come up.
give it a minute and the link came up paying the other side 201 11 which is rather one I'm sitting on route to
and my link is up. So, as you see, chap is a little bit easier to configure
then perhaps because you only need to assign the user name and password on both ends.
And then it changed encapsulation to P p pee on both ends and then make one side. The authenticator on the other side is going to be the authenticated. This point if we check our interface, breathe,
I keep forgetting the word I p
mind to face a cz up, up. This concludes the PPP lecture