Cisco CCNA Packet Tracer Ultimate labs: PPP & PPP CHAP: Answers Part 3

Cisco CCNA Packet Tracer Ultimate labs: PPP & PPP CHAP: Answers Part 3

Packet Tracer file (PT Version 7.1): https://goo.gl/iJg2cJ
Get the Packet Tracer course for only $10 by clicking here: https://goo.gl/vikgKN
Get my ICND1 and ICND2 courses for $10 here: https://goo.gl/XR1xm9 (you will get ICND2 as a free bonus when you buy the ICND1 course).

For lots more content, visit http://www.davidbombal.com – learn about GNS3, CCNA, Packet Tracer, Python, Ansible and much, much more.

The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP is comprised of three main components:

● A method for encapsulating multi-protocol datagrams.
● A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection.
● A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.

The Challenge Handshake Authentication Protocol (CHAP) (defined in RFC 1994) verifies the identity of the peer by means of a three-way handshake. These are the general steps performed in CHAP:

After the LCP (Link Control Protocol) phase is complete, and CHAP is negotiated between both devices, the authenticator sends a challenge message to the peer.

The peer responds with a value calculated through a one-way hash function (Message Digest 5 (MD5)).

The authenticator checks the response against its own calculation of the expected hash value. If the values match, the authentication is successful. Otherwise, the connection is terminated.

This authentication method depends on a “secret” known only to the authenticator and the peer. The secret is not sent over the link. Although the authentication is only one-way, you can negotiate CHAP in both directions, with the help of the same secret set for mutual authentication.

For more information on the advantages and disadvantages of CHAP, refer to RFC 1994

Translation:
So in Customer Router 1
show ip route
at the moment shows us that we only see connected and local routes on the routing table.
So ip route default route looks like this.
Next hop is going to be 8.8.10.1

So show ip route
now shows us that we’ve got the default route in the routing table.
We now need to ping the Google DNS server which is 8.8.4.4

So ping 8.8.4.4
let’s see if that works, yes it does. So that’s good.

We also need to ping Cisco.com but that means we need to configure the main server to be the DNS server. So 8.8.4.4 and hopefully now we’ll be able to ping Cisco.com which we can.

In this packet tracer lab it’s resolving to the same IP address as the Google DNS server. But that’s ok. It proves that we’ve successfully configured things properly in our lab. I’ll save my configuration.

Again for the exam, you’re going to use copy running-config startup-config
For the real world, we’ll use this command because it’s lot shorter.

Something similar needs to be done on Customer Router 2.
So show ip route
no static route is shown in the routing table, no gateway the last resort.
So IP route create a static default route pointing to 8.8.11.1

So show ip route again
notice the gateway of last resort has been configured. We’ve got a static default route or candidate default route in routing table. So we should be able to ping Google, which we can. Notice we won’t be able to ping Cisco.com because we don’t have a name server configured.

So ip name server 8.8.4.4 ping Cisco.com; that now works.
So we’ve completed the required tasks in this lab.
How did you do?
Were you able to get the lab to work?
Were you able successfully complete the lab?
Now I’m going to show you how to complete the bonus tasks which makes the lab more real world.

subscribe