Networking Tutorial Goes to Basic PPP Configuration

Networking Tutorial Goes to Basic PPP Configuration
Here we will be going over Basic Configuration of PPP (Point-to-Point Protocol). It
includes Basic Configuration tasks on a router, configuring OSPF routing protocol, and
configuring PPP PAP and CHAP authentication. …

Make sure that the IP addressing is correct and the interfaces are active by issuing the
show ip interface brief command.
Look at the above diagram, we will be using three routers, a loop back connection, two
switches (which we will leave them at their default configuration) and two PCs if you are
using packet tracer or using real devices than cable the network. The next couple of
steps are assuming you already know the material.
Next perform Basic Router Configurations (hostname, disable DNS lookup, EXEC
password, message-of-the-day banner, and password for console and VTY connections,
along with synchronous logging).
After that, configure the interfaces on R1, R2, and R3 (with the IP addresses from the
addressing table (remember to include the clock rate on serial DCE interfaces).
Test and configure ethernet interfaces on PC1 and PC3 (test by pinging the default
gateway)

1

OK, now that all devices are connected we can start by configuring OSPF (so that each
router knows about each other network). (On the R1 we are going to use the process ID
of 1)
1
2
3
4
5
6

R1(config)#router ospf 1
R1(config-router)#network 192.168.10.0 0.0.0.255 area 0
*Aug 17 17:49:14.689: %OSPF-5-ADJCHG: Process 1, Nbr 209.165.200.225 on
Serial0/0/0 from LOADING to FULL, Loading Done
R1(config-router)#

Next we will move to R2 and configure OSPF the output is:
01
02
03
04
05
06
07
08
09
10

R2(config-router)#
R2(config-router)#

The last router (R3) is ready to be configured with OSPF (Again remember to use the
process ID of 1)
1
2
3
4
5
6

R3(config-router)#network 10.2.2.0 0.0.0.3 area
R3(config-router)#

With OSPF setup you want to verify that you have full network connectivity (Every device
should be able to ping each other) This is R1′s output of the command show ip route Also
R1 was able to ping 192.168.30.1
01
02
03
04
05
2

R1#show ip route
<output omitted>
O 192.168.30.0/24 [110/1563] via 10.1.1.2, 00:33:56, Serial0/0/0
C 192.168.10.0/24 is directly connected, FastEthernet0/1
209.165.200.0/27 is subnetted, 1 subnets

06
07
08
09
10
11
12
13
14
15
16
17

O 209.165.200.225 [110/782] via 10.1.1.2, 00:33:56, Serial0/0/0
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
O 10.2.2.0/30 [110/1562] via 10.1.1.2, 00:33:56, Serial0/0/0
C 10.1.1.0/30 is directly connected, Serial0/0/0
R1#ping 192.168.30.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms
R1#

This output of R2 when issuing the command show ip route also R2 is able to ping
192.168.30.1 and 192.168.10.1
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23

R2#show ip route
<output omitted>
O 192.168.30.0/24 [110/782] via 10.2.2.2, 00:33:04, Serial0/0/1
O 192.168.10.0/24 [110/782] via 10.1.1.1, 00:33:04, Serial0/0/0
C 209.165.200.224 is directly connected, Loopback0
R2#ping 192.168.30.1
!!!!!
R2#ping 192.168.10.1
!!!!!
R2#

This last output of R3 when using the command show ip route. R3 is able to ping
209.165.200.225 and 192.168.10.1
3

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23

R3#show ip route
<output omitted>
C 192.168.30.0/24 is directly connected, FastEthernet0/1
O 192.168.10.0/24 [110/1563] via 10.2.2.1, 00:32:01, Serial0/0/1
O 209.165.200.225 [110/782] via 10.2.2.1, 00:32:01, Serial0/0/1
O 10.1.1.0/30 [110/1562] via 10.2.2.1, 00:32:01, Serial0/0/1
R3#ping 209.165.200.225
!!!!!
R3#ping 192.168.10.1
!!!!!
R3#

Now that all devices can ping each other we can start configuring PPP encapsulation on
the serial interfaces. Type the command show interface serial0/0/0 in R1 notice in the
output the encapsulation type, which is HDLC. This is the default encapsulation on serial
interfaces with Cisco Routers. (let’s change that to PPP)
1
2
3
4
5
6
7
8
9

R1#show interface serial0/0/0
Serial0/0/0 is up, line protocol is up
Hardware is GT96K Serial
Internet address is 10.1.1.1/30
MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
<output omitted>

R2′s output from the show interface serial0/0/0 and show interface serial0/0/1:
01
02
4


03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19

<output omitted>
<output omitted>

R3′s output from the show interface serial 0/0/1 command:
1
2
3
4
5
6
7
8
9

<output omitted>

So you see that all routers have the encapsulation of HDLC, if we were to put PPP on
one end of a serial interface say R2′s S0/0/0 interface and leave HDLC on the other end
what would happen? If you guessed that the link would go down you are correct. But also
OSPF would get rid of that route in the routing table. You have to be careful when
configuring PPP especially on a production network. You run the risk of making you
network inoperable if you are not careful setting the different encapsulations.
To change the encapsulation from HDLC to PPP on R1, R2, and R3. Go to the interface
of the serial connection and type encapsulation ppp. (yes it is really that simple). This is
the following output from R1 on interface s0/0/0 (notice that OSPF will go down if you
don’t configure the other side of the serial interface in this case R2′s serial0/0/0)
1
5

R1(config)#interface serial 0/0/0

2
3
4
5
6
7

R1(config-if)#encapsulation ppp
R1(config-if)#
Serial0/0/0 from FULL to DOWN, Neighbor Down: Interface down or
detached
R1(config-if)#

This is R2′s output for the encapsulation change from HDLC to PPP, again notice how
OSPF is going down because of the different encapsulation. R3 is still running HDLC
therefore the link is down.
1
2
3
4
5
6
7

R2(config)#interface serial0/0/1
R2(config-if)#
Serial0/0/1 from FULL to DOWN, Neighbor Down: Interface down or
detached
R2(config-if)#

Change R1 and R3 to the proper encapsulation type so communication between the
routers are again connected and to get OSPF working again. (This example on R3 notice
that once the encapsulation was changed to PPP the link went back up and OSPF found
an adjacent neighbor.)
1
2
3
4
5
6
7

R3(config)#interface serial 0/0/1
R3(config-if)#
*Aug 17 20:04:27.152: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Serial0/0/1, changed state to up

Verify that all routers are now running PPP by typing the command show interface
[interface ID] (This example shows that R1 is running PPP for the encapsulation)
01
02
03
04
05
06
07
08
6

Encapsulation PPP, LCP Open
Open: CDPCP, IPCP, loopback not set

09
10

<output omitted>

This shows both of R2′s serial interfaces, when issuing the show interface serial0/0/0 and
show interface serial0/0/1 commands:
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21

R2#show interface serial 0/0/0
<output omitted>
<output omitted>

R3′s output when issuing the show interface serial0/0/1 command:
01
02
03
04
05
06
07
08
09
10

<output omitted>

Now that all routers are using a different encapsulation protocol (PPP) we can also give
the protocol some authentication. The first one we will use is (PAP) password
7

authentication protocol. PAP is not a secure authentication protocol. Passwords are sent
using plain text and only authenticates once.
To set up PAP the username and password must match the other router.
So for this example R1′s username is R1 and the password is knowing.
1
R1(config)#username R1 password knowing
Keep in mind that this information needs to be typed on R2 for PAP to work.
The example from R2′s username is R2 and the password is knowing.
1
Again this information needs to be typed on R1 for PAP to work.
Back to R1 we want to go to the interface that R2 is connected to(interface s0/0/0) then
we would type ppp authentication pap hit enter (notice the link went down between R1
and R2). Typeppp pap sent-username R2 password knowing This will send the
username of R2 and the password of “knowing” to R2. R2 will check the username and
password and because they match R2′s username and password PPP will be
authenticated.
1
2
3
4
5
6
7
8
9

R1(config)#int s0/0/0
R1(config-if)#ppp authentication pap
R1(config-if)#
Interface Serial0/0/0, changed state to down
R1(config-if)#
Serial0/0/0 from FULL to DOWN, Neighbor Down: Interface down or detached
R1(config-if)#ppp pap sent-username R2 password knowing

Let’s do the same thing with R2 as we did with R1 but remember to type R1′s username
(R1) and password (knowing) on R2′s interface that connects to R1 (serial0/0/0) Also
notice that the link between R1 and R2 went back up.
1
2
3
4
5
6

8

R2(config)#interface Serial0/0/0
R2(config-if)#ppp authentication pap
R2(config-if)#ppp pap sent-username R1 password knowing
R2(config-if)#

The way to set up CHAP is fundamentally the same. Looking at R2 we are still going to
be using the username and password. However in this case the username will be R3
instead of R2 because of the three-way handshake CHAP uses. The password will be
“knowing”. We than go into the serial interface that R3 is connected to (s0/0/1) and type
ppp authentication chap(Notice how the link went down) Now that R1 and R2 are working
with PAP with PPP we can put CHAP between R2 and R3. CHAP stands for (Challenge
Handshake Authentication Protocol) because of the challenge CHAP is a stronger
authentication than PAP. CHAP also encrypts the password so it is not sent in plain text.
01
02
03
04
05
06
07
08
09
10

R2(config-if)#ppp authentication chap
R2(config-if)#
Interface Serial0/0/1, changed state to down
R2(config-if)#
Serial0/0/1 from FULL to DOWN, Neighbor Down: Interface down or detached
R2(config-if)#

Let’s do the same thing for R3 as we did for R2′s serial interface link (0/0/1) The
username will be R2 and the password will be “knowing”. (because of the three-way
handshake CHAP uses) Also notice the link between R3 and R2 it went back up and
OSPF is working again.
1
2
3
4
5
R3(config-if)#
6
7
8
R3(config-if)#ppp authentication chap
9
R3(config-if)#
More Related Topics:
That’s that! You know have PPP setup and some authentication. Between R1 and R2 the
authentication is PAP and between R2 and R3 the authentication is CHAP. You should be
able to ping all the devices within the topology diagram.
More related:
How Cisco 3560 Block IP Adress
9

A sample configuration of how to setup Netflow on a Cisco 3560 Switch
More Cisco products and Reviews you can visit: http://www.3anetwork.com/blog
It is referred from: http://ciscoskills.net/2011/01/18/basic-ppp-configuration/

3Anetwork.com is a world leading Cisco networking products wholesaler, we wholesale
original new Cisco networking equipments, including Cisco Catalyst switches, Cisco
routers, Cisco firewalls, Cisco wireless products, Cisco modules and interface cards
products at competitive price and ship to worldwide.
Our website: http://www.3anetwork.com
Telephone: +852-3069-7733
Email: info@3Anetwork.com
Address: 23/F Lucky Plaza, 315-321 Lockhart Road, Wanchai, Hongkong

10

Networking Tutorial Goes to Basic PPP Configuration

More Related Content

What's hot (19)

Similar to Networking Tutorial Goes to Basic PPP Configuration (20)

More from 3Anetwork com (20)

Recently uploaded (20)

Networking Tutorial Goes to Basic PPP Configuration