REDES WAN

Tema 3. Point to Point Protocols

HDLC&PPP
Alberto Arellano A. Ing. Msc.
aarellano@espoch.edu.ec
CCNA – CCNP - CCSP
 Serial Communication
Standards
 In a serial communication process.
• Data is encapsulated by the sending router.
• The frame is sent on a physical medium to the WAN.
• There are various ways to traverse the WAN,
• The receiving router uses the same communications
protocol to de-encapsulate the frame when it arrives.
 There are three key serial communication standards affecting
LAN-to-WAN connections:
 RS-232 - Most serial ports on personal computers conform
to the RS-232C standards. Data Rate 64 kpbs
 Both 9-pin and 25-pin connectors are used.
 V.35 – It is used for modem-to-multiplexer communication.
 V.35 is used by routers and DSUs that connect to T1 /E1
carriers. Data Rate 48 -2048 kbps
 43 pines connectors are used
 HSSI (EIA/TIA 612/613)- A High-Speed Serial Interface
supports transmission rates up to 52 Mb/s.
 HSSI is used to connect routers on LANs with WANs over
high-speed lines such as T3/E3 lines.
 60 pines connectors are used
 DTE and DCE

 In order to be connecting to the WAN, a serial connection

has a DTE device at one end of the connection and a DCE
device at the other end.

 The DTE, which is generally a router.

 The DTE could also be a terminal, computer, printer,
or fax machine.
 DTE and DCE
 The DCE, commonly a modem or CSU/DSU(Channel Service
Unit/Data Service Unit), is the device used to convert the user
data from the DTE into a form acceptable to the WAN service
provider transmission link.
 This signal is received at the remote DCE, which decodes
the signal back into a sequence of bits.
 The remote DCE then signals this sequence to the remote
DTE.
 The connection between the two DCE devices is the WAN service
provider transmission network.
 WAN Encapsulation

 WAN technologies operate at both Physical and

Data-link layers of the OSI models, and that higher-
layer protocols such as IP are encapsulated when
sent across the WAN link.
 A WAN is usually terminated on a Multivendor
device’s serial interface.
 Serial interfaces support a wide variety of WAN
encapsulation types
 By default, a serial interface will utilize HDLC
(Cisco) or PPP(Others) for encapsulation.
 WAN Encapsulation Protocols
 HDLC - The default encapsulation type on point-to-point connections, when the
link uses two Cisco devices.
 PPP - Provides router-to-router and host-to-network connections over
synchronous and asynchronous circuits.
 PPP works with several network protocols, such as IP and IPX. PPP also
has built-in security mechanisms such as PAP and CHAP.
 Serial Line Internet Protocol (SLIP) - A standard protocol for point-to-point serial
connections using TCP/IP.
 SLIP has been largely displaced by PPP.
 X.25/Link Access Procedure, Balanced (LAPB) - X.25 specifies LAPB, a data link
layer protocol.
 X.25 is a predecessor to Frame Relay.
 Frame Relay - Frame Relay eliminates some of the time-consuming processes
(such as error correction and flow control) employed in X.25.
 ATM - The cell relay in which devices send multiple service types (voice, video, or
data) in fixed-length (53-byte) cells.
 Fixed-length cells allow processing to occur in hardware, thereby reducing
transit delays.
 HDLC Encapsulation
 In 1979, the ISO agreed on HDLC as a standard bit-oriented data link
layer protocol that encapsulates data on synchronous serial data links.
 Since 1981, ITU-T has developed a series of HDLC derivative protocols.
 Link Access Procedure, Balanced (LAPB) for X.25

 Link Access Procedure on the D channel (LAPD) for ISDN

 Link Access Procedure for Modems (LAPM) and PPP for modems

 Link Access Procedure for Frame Relay (LAPF) for Frame Relay
 HDLC Encapsulation

 Standard HDLC does not inherently support multiple protocols on

a single link, as it does not have a way to indicate which protocol is
being carried.
 The Cisco HDLC frame uses a proprietary ‘type’ field that acts as a
protocol field.
 HDLC is the default Layer 2 protocol for Cisco router serial interfaces.
 PPP actually uses HDLC as a basis for encapsulating datagrams.
Configuring HDLC
Router AR 3260
 Configuring HDLC
Router AR 3260
1. Configure Protocol HDLC (R2)
 <Huawei> system-vie
 [Huawei] sysname R2
 [R2] interface serial 1/0/0
 [R2-Serial1/0/0] link-protocol hdlc
 [R2-Serial1/0/0] ip address 10.10.12.1 24
 [R2-Serial1/0/0] quit
 [R2] interface giga 0/0/0
 [R2-GigabitEthernet0/0/0] ip address 192.168.10.1 24
 [R2-GigabitEthernet0/0/0] quit
 [R2] display ip interface brief
 Configuring HDLC
Router AR 3260
1. Configure Protocol HDLC (R1)
 <Huawei> system-vie
 [Huawei] sysname R1
 [R1] interface serial 1/0/0
 [R1-Serial1/0/0] link-protocol hdlc
 [R1-Serial1/0/0] ip address 10.10.12.2 24
 [R1-Serial1/0/0] quit
 [R1] interface serial 1/0/1
 [R1-Serial1/0/1] link-protocol hdlc
 [R1-Serial1/0/1] ip address 10.10.10.2 24
 [R1-Serial1/0/1] quit
 Configuring HDLC
Router AR 3260
1. Configure Protocol HDLC (R3)
 <Huawei> system-vie
 [Huawei] sysname R3
 [R3] interface serial 1/0/0
 [R3-Serial1/0/0] link-protocol hdlc
 [R3-Serial1/0/0] ip address 10.10.10.1 24
 [R3-Serial1/0/0] quit
 [R3] interface giga 0/0/0
 [R3-GigabitEthernet0/0/0] ip address 192.168.12.1 24
 [R3-GigabitEthernet0/0/0] quit
 [R3] display ip interface brief
 Configuring HDLC
Router AR 3260
Verify Connectivity (R1)
 Configuring HDLC
Router AR 3260
Configure OSPF Protocol

[R2]router id 2.2.2.2
[R2]ospf
[R2-ospf-1]area 0
[R2-ospf-1-area-0.0.0.0]network 10.10.12.0 0.0.0.255
[R2-ospf-1-area-0.0.0.0]network 192.168.10.0 0.0.0.255
[R2-ospf-1-area-0.0.0.0]quit

[R1]router id 1.1.1.1
[R21ospf
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]network 10.10.12.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]network 10.10.10.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]quit
Configuring HDLC
Router AR 3260
Configuring HDLC
Router AR 3260
Configuring HDLC
Router AR 3260
 SLIP
Serial Line IP
• RFC 1055 (June 1988)
• Common protocol used to transmit IP packets over serial lines and
telephone connections
• Designed to handle just TCP/IP traffic – not other protocols
• Must know your IP address and the IP address of the remote computer
• SLIP does not provide for data compression
 SLIP
Serial Line IP
SLIP deficiencies:

1. SLIP does not have error detection mechanism (left to

TCP to detect and recover from errors on the
transmission line).
2. SLIP only supports IP (no other layer 3 protocols).
3. SLIP does not provide dynamic IP address assignment.
4. SLIP does not provide authentication.

SOLUTION
PPP (Point to Point Protocol)
 What is PPP?
 RFC 1661-1663
 PPP includes many features not available in HDLC:
 The link quality management feature monitors the quality of the link. If

too many errors are detected, PPP takes the link down.
 PPP supports PAP and CHAP authentication. (HDLC does NOT

support any type of authentication)

 PPP contains three main components:
 HDLC protocol for encapsulating datagrams over point-to-point links.

 Extensible Link Control Protocol (LCP) to establish, configure, and test

the data link connection.

 Family of Network Control Protocols (NCPs) for establishing and

configuring different network layer protocols.

 PPP allows the simultaneous use of multiple network layer protocols.
 Some of the more common NCPs are Internet Protocol Control Protocol,
Appletalk Control Protocol, Novell IPX Control Protocol, Cisco Systems
Control Protocol, SNA Control Protocol, and Compression Control
Protocol.
PPP Protocol Suite
 PPP Layered Architecture

 At the physical layer, you can configure PPP on:

 Asynchronous serial (RS-232)
 Synchronous serial (V.35)
 HSSI
 ISDN
 Most of the work done by PPP is at the data link and network layers by the LCP
and NCPs.
 The LCP sets up the PPP connection and its parameters
 The NCPs handle higher layer protocol configurations, and the LCP terminates
the PPP connection.
 PPP Architecture –
Link Control Protocol Layer
 The LCP sits on top of the physical layer and has a role in
establishing, configuring, and testing the data-link connection.
 The LCP establishes the point-to-point link. (link-quality and
authentication)
 The LCP also negotiates and sets up control options on the
WAN data link, which are handled by the NCPs.
 The LCP provides automatic configuration of the interfaces at each
end, including:
 Handling varying limits on packet size
 Detecting common mis-configuration errors
 Terminating the link
 Determines if a link quality is sufficient to bring it up
 PPP also uses the LCP to agree automatically on encapsulation
formats (authentication, compression, error detection) as soon as
the link is established.
 PPP Architecture –
Link Control Protocol Layer
 The LCP sits on top of the physical layer and has a role in
establishing, configuring, and testing the data-link connection.
 The LCP establishes the point-to-point link. (link-quality and
authentication)
 The LCP also negotiates and sets up control options on the
WAN data link, which are handled by the NCPs.
 The LCP provides automatic configuration of the interfaces at each
end, including:
 Handling varying limits on packet size
 Detecting common mis-configuration errors
 Terminating the link
 Determines if a link quality is sufficient to bring it up
 PPP also uses the LCP to agree automatically on encapsulation
formats (authentication, compression, error detection) as soon as
the link is established.
 PPP Architecture –
Network Control Protocol Layer
 PPP permits multiple network layer protocols to operate on the same
communications link. For every network layer protocol used, PPP uses a
separate NCP.
 For example, IP uses the IP Control Protocol (IPCP),
 IPX uses the Novell IPX Control Protocol (IPXCP).
 NCPs include functional fields containing standardized codes (PPP
protocol field numbers shown in the figure) to indicate the network layer
protocol that PPP encapsulates.
 Each NCP manages the specific needs required by its respective network layer
protocols.
 The various NCP components encapsulate and negotiate options for multiple
network layer protocols.
PPP Frame Structure (1)
PPP Frame Structure (2)
PPP Frame Structure (3)
PPP Frame Structure (4)
PPP Frame Structure (5)
PPP Frame Structure (6)
 Establishing a PPP Session
 The three phases of establishing a PPP session:
 Phase 1: Link establishment and configuration negotiation –

 The LCP must first open the connection and negotiate

configuration options.
 Phase 2: Link quality determination (optional) –

 The LCP tests the link to determine whether the link quality is
sufficient to bring up network layer protocols.
 Phase 3: Network layer protocol configuration negotiation –

 After the LCP has finished the link quality determination phase, the
appropriate NCP can separately configure the network layer
protocols, and bring them up and take them down at any time.

 The link remains configured for communications until explicit LCP or NCP
frames close the link, or until some external event occurs.
 This happen because of the loss of the carrier, authentication

failure, link quality failure, the expiration of idle-period timer, or

administrative closing the link.
 Establishing a Link with LCP
 LCP operation uses three classes of LCP frames to accomplish the work of each of
the LCP phases:
 Link-establishment frames establish and configure a link (Configure-Request,
Configure-Ack, Configure-Nak, and Configure-Reject)
 During link establishment, the LCP opens the connection and negotiates the configuration
parameters.
 The Configure-Request frame includes a variable number of configuration options needed to set
up on the link.

 Link-maintenance frames manage and debug a

link (Code-Reject, Protocol-Reject, Echo-
Request, Echo-Reply, and Discard-Request)
 Echo-Request, Echo-Reply, and Discard-Request -
These frames can be used for testing the link.
 Link-termination frames terminate a link
(Terminate-Request and Terminate-Ack)
 The link remains open until the LCP terminates it. If
the LCP terminates the link before the NCP, the NCP
session is also terminated.
 The device initiating the shutdown sends a Terminate-
Request message. The other device replies with a
Terminate-Ack.
 LCP Packet
 Each LCP packet is a single LCP message
consisting of
Code field identifying the type of LCP
packet, the code field of the LCP packet
identifies the packet type according to the
table.
Identifier field so that requests and replies
can be matched,
Length field indicating the size of the LCP
packet
Data: Packet type-specific data.
 PPP Configuration Options

 PPP can be configured to support:

 Authentication using either PAP or CHAP
 Compression using either Stacker or Predictor
 Multilink which combines two or more channels
to increase the WAN bandwidth (for load
balancing purposes)
 To negotiate the use of these PPP options, the LCP
link-establishment frames contain Option information in
the Data field of the LCP frame.
 This phase is complete when a configuration
acknowledgment frame has been sent and received.
 NCP Process
 After the LCP has configured and authenticated the
basic link, the appropriate NCP of the network layer
protocol being used.
 There are NCPs for IP, IPX, AppleTalk, and others.
 IPCP Example
After LCP has established the link, the routers
exchange IPCP messages, negotiating options specific
to the protocol.
IPCP negotiates two options:

 Compression - Allows devices to negotiate an

algorithm to compress TCP and IP headers and
save bandwidth.
 IP-Address - Allows the initiating device to specify
an IP address to use for routing IP over the PPP
link, or to request an IP address for the responder.
Dialup network links commonly use the IP address
option.
When the NCP process is complete, the link goes into

the open state and LCP takes over again.

 PPP Configuration Options

 PPP may include the following LCP options:

Authentication - Peer exchange authentication messages.

 Two choices are Password Authentication Protocol (PAP) and Challenge

Handshake Authentication Protocol (CHAP).
Compression - Increases the effective throughput on PPP connections by

reducing the amount of data in the frame that must travel across the link.
 Two compression are Stacker and Predictor.
Error detection - Identifies fault conditions.

 The Quality and Magic Number options help ensure a reliable, loop-free
data link.
Multilink – Multiple links

 This alternative provides load balancing over the router interfaces that
PPP uses.
PPP Callback - To enhance security, the client makes the initial call,

requests that the server call it back, and terminates its initial call.
 PPP Configuration Commands
 Example 1: Enabling PPP on an Interface
To set PPP as the encapsulation method used by a serial or ISDN interface,

use the encapsulation ppp interface configuration command.

R3#configure terminal
R3(config)#interface serial 0/0
R3(config-if)#encapsulation ppp
 You must first configure the router with an IP routing protocol to use PPP
encapsulation. If you do not configure PPP on a Cisco router, the default
encapsulation for serial interfaces is HLDC.
 Example 2: Compression
 You can configure point-to-point compression on serial interfaces after you
have enabled PPP. Because this option invokes a software compression
process, it can affect system performance. If the traffic already consists of
compressed files (.zip, .rar, or .mpeg, for example), do not use this option.
R3(config)#interface serial 0/0
R3(config-if)#encapsulation ppp
R3(config-if)#compress [predictor | stac]
 PPP Configuration Commands

 Example 3: Link Quality Monitoring

 LCP provides an optional link quality determination phase.
 If the link quality percentage is not maintained, the link is deemed to be
of poor quality and is taken down.
 This example configuration monitors the data dropped on the link and
avoids frame looping:
R3(config)#interface serial 0/0
R3(config-if)#encapsulation ppp
R3(config-if)#ppp quality 80
 Example 4: Load Balancing Across Links
 Multilink PPP (also referred to as MP, MPPP, MLP, or Multilink) provides
a method for spreading traffic across multiple physical WAN links while
providing packet fragmentation and reassembly, proper sequencing,
multivendor interoperability, and load balancing on inbound and
outbound traffic.
Router(config)#interface serial 0/0
Router(config-if)#encapsulation ppp
Router(config-if)#ppp multilink
 PPP Authentication Protocols
 PPP defines an extensible LCP that allows negotiation of an authentication
protocol for authenticating its peer before allowing network layer protocols to
transmit over the link.
 PAP is a very basic two-way process.
 There is no encryption-the username and password are sent in plain text. If it is accepted, the
 connection is allowed.

 CHAP is more secure than PAP. It involves a three-way exchange of a shared secret.

 The authentication phase of a PPP session is optional.

 If used, you can authenticate the peer after the LCP establishes the link.
 If it is used, authentication takes place before the network layer protocol configuration
phase begins.
 Password Authentication
Protocol (PAP)
 PPP can performs Layer 2 authentication in
addition to other layers of authentication
PAP provides method for a remote node to
establish its identity using a two-way
handshake.
ppp authentication pap command is used,

 the remote node repeatedly sends a username-

password pair across the link until the sending
node acknowledges it or terminates the
connection.
 Using PAP, you send passwords across the
link in clear text and there is no protection.
 There are times when using PAP is justified.
Client applications that do not support CHAP
Incompatibilities between different vendor

implementations of CHAP
 Challenge Handshake Authentication
Protocol (CHAP)
 CHAP conducts periodic challenges to make sure that the remote node still has a
valid password value.
 The password value is variable and changes unpredictably while the link exists.
 After the PPP link establishment phase is complete,
.
 The router sends a challenge to the remote
node.
The remote node responds with a value

calculated using a one-way hash function using

MD5.
The local router checks the response against

its own calculation of the expected hash value.

If the values match, the initiating node
acknowledges the authentication. Otherwise, it
immediately terminates the connection.
Because the challenge is unique and random,

the resulting hash value is also unique and

random.
 PPP Multilink

 Use MLP with applications in which bandwidth requirements

are dynamic, such as remote LAN access applications for
telecommuters or small office, home office (SOHO)
environments
 Creates bundles
 RFC 1717 and 1990
 Combine multiple physical links into one logical link (bundle)
 Receive and reassemble upper-layer protocol data units
(PDUs)
 Receive PDUs of a negotiated size
PPP Basic Configuration
Multivendor
Activate IPv6 Support on
Mikrotik
Configure IPv6, PPP on
Cisco Routers
Configure IPv6, PPP on
Cisco Routers
Configure IPv6, PPP on
Cisco Routers
Configure IPv6 on
Brocade_1
Configure IPv6 on
Juniper_1
Configure IPv6 on
Juniper_1
Configure IPv6 on
Mikrotik_1
Configure IPv6 on
Mikrotik_1
Configure IPv6 Routes on
Cisco Routers
Configure IPv6 Routes on
Brocade_1

55
 Configure IPv6 Routes on
Juniper_1
set routing-options rib inet6.0 static route 2001:1:2:10::/64 next-hop 2001:1:2:22::1
set routing-options rib inet6.0 static route 2001:1:2:30::/64 next-hop 2001:1:2:22::1
set routing-options rib inet6.0 static route 2001:1:2:34::/64 next-hop 2001:1:2:22::1
commit
Configure IPv6 Routes on
Mikrotik_1
Verify Connectivity
Capture PPP traffic
 Homework
Lab. PPP Huawei&IPv6