Week_2-Point-to-Point Connections Module
Week_2-Point-to-Point Connections Module
1
Week 2: Point-to-Point Connections
Introduction
One of the most common types of WAN connections, especially in long-distance
communications, is a point-to-point connection, also called a serial or leased-line connection.
Because these connections are typically provided by a carrier, such as a telephone company,
boundaries between what is managed by the carrier and what is managed by the customer
must be clearly established.
This chapter covers the terms, technology, and protocols used in serial connections. The
HDLC and Point-to-Point Protocols (PPP) are introduced. HDLC is the default protocol on a
Cisco router serial interface. PPP is a protocol that is able to handle authentication,
compression, error detection, monitor link quality, and logically bundle multiple serial
connections together to share the load.
At one time, most PCs included both serial and parallel ports. Parallel ports were used to
connect printers, computers, and other devices that required relatively high bandwidth.
Parallel ports were also used between internal components. For external communications, a
serial bus was primarily used to connect to phone lines and devices that could potentially be
further distance than a parallel transfer would allow. Because serial communications are less
complex and require simpler circuitry, serial communications are considerably less
expensive to implement. Serial communications use fewer wires, cheaper cables, and fewer
connector pins.
On most PCs, parallel ports and RS-232 serial ports have been replaced by the higher speed
serial Universal Serial Bus (USB) interfaces. For long-distance communication, many WANs
also use serial transmission.
When permanent dedicated connections are required, a point-to-point link is used to provide
a single, pre-established WAN communications path. This path goes from the customer
premises, through the provider network, to a remote destination, as shown in the figure.
A point-to-point link can connect two geographically distant sites, such as a corporate office
in New York and a regional office in London. For a point-to-point line, the carrier dedicates
specific resources for a line that is leased by the customer (leased line).
Note: Point-to-point connections are not limited to connections that cross land. There are
hundreds of thousands of miles of undersea fiber-optic cables that connect countries and
continents worldwide. An Internet search of “undersea Internet cable map” produces several
cable maps of these undersea connections.
Point-to-point links are usually more expensive than shared services. The cost of leased-line
solutions can become significant when used to connect many sites over increasing distances.
However, there are times when the benefits outweigh the cost of the leased line. The
dedicated capacity removes latency or jitter between the endpoints. Constant availability is
essential for some applications such as VoIP or video over IP.
Serial Bandwidth
Bandwidth refers to the rate at which data is transferred over the communication link. The
underlying carrier technology will dictate how much bandwidth is available. There is a
difference in bandwidth points between the North American (T-carrier) specification and
the European (E-carrier) system. Optical networks also use a different bandwidth hierarchy,
which again differs between North America and Europe. In the U.S., Optical Carrier (OC)
defines the bandwidth points.
In North America, the bandwidth is usually expressed as a digital signal level number (DS0,
DS1, etc.), which refers to the rate and format of the signal. The most fundamental line speed
is 64 kb/s, or DS0, which is the bandwidth required for an uncompressed, digitized phone
call. Serial connection bandwidths can be incrementally increased to accommodate the need
for faster transmission. For example, 24 DS0s can be bundled to get a DS1 line (also called a
T1 line) with a speed of 1.544 Mb/s. Also, 28 DS1s can be bundled to get a DS3 line (also
called a T3 line) with a speed of 44.736 Mb/s. Leased lines are available in different
capacities and are generally priced based on the bandwidth required and the distance
between the two connected points.
OC transmission rates are a set of standardized specifications for the transmission of digital
signals carried on SONET fiber-optic networks. The designation uses OC, followed by an
integer value representing the base transmission rate of 51.84 Mb/s. For example, OC-1 has
a transmission capacity of 51.84 Mb/s, whereas an OC-3 transmission medium would be
three times 51.84 Mb/s, or 155.52 Mb/s.
The figure lists the most common line types and the associated bit rate capacity of each.
Note: E1 (2.048 Mb/s) and E3 (34.368 Mb/s) are European standards like T1 and T3, but
with different bandwidths and frame structures.
HDLC Encapsulation
On each WAN connection, data is encapsulated into frames before crossing the WAN link. To
ensure that the correct protocol is used, the appropriate Layer 2 encapsulation type must be
configured. The choice of protocol depends on the WAN technology and the communicating
equipment. The figure displays the more common WAN protocols and where they are used.
The following are short descriptions of each type of WAN protocol:
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) - An ITU-T standard that defines how
connections between a DTE and DCE are maintained for remote terminal access and
computer communications in public data networks. X.25 specifies LAPB, a data link
layer protocol. X.25 is a predecessor to Frame Relay.
Frame Relay - An industry standard, switched, data link layer protocol that handles
multiple virtual circuits. Frame Relay is a next generation protocol after X.25. Frame
Relay eliminates some of the time-consuming processes (such as error correction and
flow control) employed in X.25.
ATM - The international standard for cell relay in which devices send multiple service
types, such as voice, video, or data, in fixed-length (53-byte) cells. Fixed-length cells
allow processing to occur in hardware; thereby, reducing transit delays. ATM takes
advantage of high-speed transmission media such as E3, SONET, and T3.
HDLC and PPP are the focus of this course. The other WAN protocols listed are considered
either legacy technologies or beyond the scope of this course.
HDLC Encapsulation
HDLC is a bit-oriented synchronous data link layer protocol developed by the International
Organization for Standardization (ISO). The current standard for HDLC is ISO 13239. HDLC
was developed from the Synchronous Data Link Control (SDLC) standard proposed in the
1970s. HDLC provides both connection-oriented and connectionless service.
control through the use of acknowledgments. Each frame has the same format, whether it is
a data frame or a control frame.
When frames are transmitted over synchronous or asynchronous links, those links have no
mechanism to mark the beginning or end of frames. For this reason, HDLC uses a frame
delimiter, or flag, to mark the beginning and the end of each frame.
Cisco has developed an extension to the HLDC protocol to solve the inability to provide
multiprotocol support. Although Cisco HLDC (also referred to as cHDLC) is proprietary, Cisco
has allowed many other network equipment vendors to implement it. Cisco HDLC frames
contain a field for identifying the network protocol being encapsulated. The figure compares
standard HLDC to Cisco HLDC.
Cisco HDLC is the default encapsulation method used by Cisco devices on synchronous serial
lines.
Use Cisco HDLC as a point-to-point protocol on leased lines between two Cisco devices. If
connecting non-Cisco devices, use synchronous PPP.
If the default encapsulation method has been changed, use the encapsulation
hdlc command in interface configuration mode to re-enable HDLC.
As shown in the figure, there are two steps to re-enable HDLC encapsulation:
Step 1. Enter the interface configuration mode of the serial interface.
Step 2. Enter the encapsulation hdlc command to specify the encapsulation protocol on the
interface.
The show interfaces serial x/x/x command displays information specific to serial
interfaces.
When HDLC is configured, “encapsulation HDLC” should be reflected in the output as
highlighted in the figure.
“Serial 0/0/0 is up, line protocol is up”, indicates that the line is up and functioning.
PPP Operation
Benefits of PPP
Introducing PPP
HDLC is the default serial encapsulation method when connecting two Cisco routers. With
an added protocol type field, the Cisco version of HDLC is proprietary. Thus, Cisco HDLC can
only work with other Cisco devices. However, when there is a need to connect to a non-Cisco
router, PPP encapsulation should be used, as shown in the figure.
PPP encapsulation has been carefully designed to retain compatibility with most commonly
used supporting hardware. PPP encapsulates data frames for transmission over Layer 2
physical links. PPP establishes a direct connection using serial cables, phone lines, trunk
lines, cellular telephones, specialized radio links, or fiber-optic links.
PPP contains three main components:
HDLC-like framing for transporting multiprotocol packets over point-to-point links.
Extensible Link Control Protocol (LCP) for establishing, configuring, and testing 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. The most common NCPs are IPv4 Control Protocol and IPv6 Control Protocol.
Note: Other NCPs include AppleTalk Control Protocol, Novell IPX Control Protocol, Cisco
Systems Control Protocol, SNA Control Protocol, and Compression Control Protocol.
Advantages of PPP
PPP originally emerged as an encapsulation protocol for transporting IPv4 traffic over point-
to-point links. PPP provides a standard method for transporting multiprotocol packets over
point-to-point links.
There are many advantages to using PPP, including the fact that it is not proprietary. PPP
includes many features not available in HDLC:
The link quality management feature (LQM) monitors the quality of the link. LQM can
be configured with the interface command ppp quality percentage. If the error
percentage falls below the configured threshold, the link is taken down and packets are
rerouted or dropped.
PPP supports PAP and CHAP authentication. This feature is explained and practiced in
a later section.
At the physical layer, you can configure PPP on a range of interfaces. The only absolute
requirement imposed by PPP is a full-duplex circuit, either dedicated or switched, that can
operate in an asynchronous or synchronous bit-serial mode. The physical layer standards
are transparent to PPP link layer frames. PPP does not impose any restrictions regarding
transmission rate.
Most of the work done by PPP happens at the data link and network layers, by LCP and NCPs.
LCP functions within the data link layer and has a role in establishing, configuring, and
testing the data-link connection. LCP establishes the point-to-point link. LCP also negotiates
and sets up control options on the WAN data link, which are handled by the NCPs.
After the link is established, PPP also uses LCP to agree automatically on encapsulation
formats such as authentication, compression, and error detection.
PPP permits multiple network layer protocols to operate on the same communications link.
For every network layer protocol used, PPP uses a separate NCP, as shown in Figure 2.11.
For example, IPv4 uses IP Control Protocol (IPCP) and IPv6 uses IPv6 Control Protocol
(IPv6CP).
NCPs include functional fields containing standardized codes to indicate the network layer
protocol that PPP encapsulates. Figure 2.12 lists the PPP protocol field numbers. 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.
A PPP frame consists of six fields. The following descriptions summarize the PPP frame
fields illustrated in the figure:
Flag - A single byte that indicates the beginning or end of a frame. The Flag field
consists of the binary sequence 01111110.
Address - A single byte that contains the binary sequence 11111111, the standard
broadcast address. PPP does not assign individual station addresses.
Control - A single byte that contains the binary sequence 00000011, which calls for
transmission of user data in an unsequenced frame.
Protocol - Two bytes that identify the protocol encapsulated in the information field
of the frame. The 2-byte Protocol field identifies the protocol of the PPP payload.
Data - Zero or more bytes that contain the datagram for the protocol specified in the
protocol field.
Frame Check Sequence (FCS) – This is normally 16 bits (2 bytes). If the receiver’s
calculation of the FCS does not match the FCS in the PPP frame, the PPP frame is
silently discarded.
LCPs can negotiate modifications to the standard PPP frame structure. Modified frames,
however, are always distinguishable from standard frames.
PPP Sessions
Error detection - Identifies fault conditions. The Quality and Magic Number options
help ensure a reliable, loop-free data link. The Magic Number field helps in detecting
links that are in a looped-back condition. Until the Magic-Number Configuration Option
has been successfully negotiated, the Magic-Number must be transmitted as zero. Magic
numbers are generated randomly at each end of the connection.
PPP Callback - PPP callback is used to enhance security. With this LCP option, a Cisco
router can act as a callback client or a callback server. The client makes the initial call,
requests that the server call it back, and terminates its initial call. The callback router
answers the initial call and makes the return call to the client based on its configuration
statements.
Multilink - This alternative provides load balancing over the router interfaces that PPP
uses. 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.
When options are configured, a corresponding field value is inserted into the LCP option
field.
LCP Operation
LCP operation includes provisions for link establishment, link maintenance, and link
termination. LCP operation uses three classes of LCP frames to accomplish the work of each
of the LCP phases:
Link establishment is the first phase of LCP operation, as seen in Figure 2.14. This phase must
complete successfully, before any network layer packets can be exchanged. During link
establishment, the LCP opens the connection and negotiates the configuration parameters.
The link establishment process starts with the initiating device sending a Configure-Request
frame to the responder. The Configure-Request frame includes a variable number of
configuration options needed to set up on the link.
The initiator includes the options for how it wants the link created, including protocol or
authentication parameters. The responder processes the request:
If the options are not acceptable or not recognized, the responder sends a Configure-Nak or
Configure-Reject message. If this occurs and the negotiation fails, the initiator must restart
the process with new options.
If the options are acceptable, the responder responds with a Configure-Ack message and the
process moves on to the authentication stage. The operation of the link is handed over to the
NCP.
When NCP has completed all necessary configurations, including validating authentication if
configured, the line is available for data transfer. During the exchange of data, LCP transitions
into link maintenance.
Link Maintenance
During link maintenance, LCP can use messages to provide feedback and test the link, as
shown in Figure 2.15:
Echo-Request, Echo-Reply, and Discard-Request - These frames can be used for testing the
link.
Code-Reject and Protocol-Reject - These frame types provide feedback when one device
receives an invalid frame. The sending device will resend the packet.
Link Termination
After the transfer of data at the network layer completes, the LCP terminates the link, as
shown in Figure 2.16. NCP only terminates the network layer and NCP link. The link remains
open until the LCP terminates it. If the LCP terminates the link before NCP, the NCP session
is also terminated.
PPP can terminate the link at any time. This might happen because of the loss of the carrier,
authentication failure, link quality failure, the expiration of an idle-period timer, or the
administrative closing of the link. The LCP closes the link by exchanging Terminate packets.
The device initiating the shutdown sends a Terminate-Request message. The other device
replies with a Terminate-Ack. A termination request indicates that the device sending it
needs to close the link. When the link is closing, PPP informs the network layer protocols so
that they may take appropriate action.
NCP Explained
After the LCP has configured and authenticated the basic link, the appropriate NCP is invoked
to complete the specific configuration of the network layer protocol being used. When the
NCP has successfully configured the network layer protocol, the network protocol is in the
open state on the established LCP link. At this point, PPP can carry the corresponding
network layer protocol packets.
IPCP Example
As an example of how the NCP layer works, the NCP configuration of IPv4 is shown in the
figure 2.18. After LCP has established the link, the routers exchange IPCP messages,
negotiating options specific to IPv4. IPCP is responsible for configuring, enabling, and
disabling the IPv4 modules on both ends of the link.
Compression - Allows devices to negotiate an algorithm to compress TCP and IP headers and
save bandwidth. The Van Jacobson TCP/IP header compression reduces the size of the
TCP/IP headers to as few as 3 bytes. This can be a significant improvement on slow serial
lines, particularly for interactive traffic.
IPv4-Address - Allows the initiating device to specify an IPv4 address to use for routing IP
over the PPP link, or to request an IPv4 address for the responder. Prior to the advent of
broadband technologies such as DSL and cable modem services, dialup network devices
commonly used the IPv4 address option.
After the NCP process is complete, the link goes into the open state and LCP takes over again
in a link maintenance phase. Link traffic consists of any possible combination of LCP, NCP,
and network layer protocol packets. When data transfer is complete, NCP terminates the
protocol link and LCP terminates the PPP connection.
PPP can be configured to support various optional functions, as shown in the figure. There
are three optional functions:
PPP Implementation
Configure PPP
PPP Configuration Options
In the previous section, configurable LCP options were introduced to meet specific WAN
connection requirements. PPP may include several LCP options:
Error detection - Identifies fault conditions. The Quality and Magic Number options help
ensure a reliable, loop-free data link. The Magic Number field helps in detecting links that
are in a looped-back condition. Until the Magic-Number Configuration Option has been
successfully negotiated, the Magic-Number must be transmitted as zero. Magic numbers are
generated randomly at each end of the connection.
PPP Callback - PPP callback is used to enhance security. With this LCP option, a Cisco router
can act as a callback client or a callback server. The client makes the initial call, requests that
the server call it back, and terminates its initial call. The callback router answers the initial
call and makes the return call to the client based on its configuration statements.
Multilink - This alternative provides load balancing over the router interfaces that PPP uses.
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.
When options are configured, a corresponding field value is inserted into the LCP option
field.
The figure shows that routers R1 and R2 have been configured with both an IPv4 and an IPv6
address on the serial interfaces. PPP is a Layer 2 encapsulation that supports various Layer
3 protocols including IPv4 and IPv6.
The ppp quality percentage command ensures that the link meets the quality requirement
set; otherwise, the link closes down.
The percentages are calculated for both incoming and outgoing directions. The outgoing
quality is calculated by comparing the total number of packets and bytes sent, to the total
number of packets and bytes received by the destination node. The incoming quality is
calculated by comparing the total number of packets and bytes received to the total number
of packets and bytes sent by the destination node.
If the link quality percentage is not maintained and the configured threshold, the link is
deemed to be of poor quality and is taken down. LQM implements a time lag so that the link
does not bounce up and down.
The configuration ppp quality 80, shown in Figure 2.21, sets minimum quality to 80%.
Multilink PPP (also referred to as MP, MPPP, MLP, MLPPP, or Multilink) provides a method
for spreading traffic across multiple physical WAN links. Multilink PPP also provides packet
fragmentation and reassembly, proper sequencing, multivendor interoperability, and load
balancing on inbound and outbound traffic.
MPPP allows packets to be fragmented and sends these fragments simultaneously over
multiple point-to-point links to the same remote address. The multiple physical links come
up in response to a user-defined load threshold. MPPP can measure the load on just inbound
traffic, or on just outbound traffic, but not on the combined load of both inbound and
outbound traffic.
Data Communication and Networking 4
IT-6300 Data Communications and Networking 4
21
Week 2: Point-to-Point Connections
Use the show interfaces serial command to verify proper configuration of HDLC or PPP
encapsulation. The command output in Figure 2.22 shows a PPP configuration.
When you configure HDLC, the output of the show interfaces serial command should
display encapsulation HDLC. When PPP is configured, the LCP and NCP states also display.
Data Communication and Networking 4
IT-6300 Data Communications and Networking 4
22
Week 2: Point-to-Point Connections
Notice that NCPs IPCP and IPV6CP are open for IPv4 and IPv6 because R1 and R2 were
configured with both IPv4 and IPv6 addresses.
The show ppp multilink command verifies that PPP multilink is enabled on R3, as shown in
Figure 2.24. The output indicates the interface Multilink 1, the hostnames of both the local
and remote endpoints, and the serial interfaces assigned to the multilink bundle.
PAP is a very basic two-way process. There is no encryption. The username and password
are sent in plaintext. 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, the peer is authenticated after
LCP establishes the link and chooses the authentication protocol. Authentication takes place
before the network layer protocol configuration phase begins.
The authentication options require that the calling side of the link enter authentication
information. This helps to ensure that the user has the permission of the network
administrator to make the call. Peer routers exchange authentication messages.
PAP Process
After PPP completes the link establishment phase, the remote node repeatedly sends a
username-password pair across the link until the receiving node acknowledges it or
terminates the connection.
At the receiving node, the username-password is checked by the device running PPP. This
device either allows or denies the connection. An accept or reject message is returned to the
requester, as shown in Figure 2.27.
PAP is not a strong authentication protocol. Using PAP, passwords are sent across the link in
plaintext and there is no protection from playback or repeated trial-and-error attacks. The
remote node is in control of the frequency and timing of the login attempts.
Nonetheless, there are times when using PAP can be justified. Despite its shortcomings, PAP
may be used in the following environments:
CHAP Process
After the PPP link establishment phase is complete, the local router sends a challenge
message to the remote node, as shown in Figure 2.28.
The remote node responds with a value that is calculated using a one-way hash function.
This is typically Message Digest 5 (MD5) based on the password and challenge message, as
shown in Figure 2.29.
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, as shown in Figure
2.30. If the values do not match, the initiating node immediately terminates the connection.
CHAP provides protection against a playback attack by using a variable challenge value that
is unique and unpredictable. Because the challenge is unique and random, the resulting hash
value is also unique and random. The use of repeated challenges limits the time of exposure
to any single attack. The local router, or a third-party authentication server, is in control of
the frequency and timing of the challenges.
PAP, CHAP, or both can be enabled. If both methods are enabled, the first method specified
is requested during link negotiation. If the peer suggests using the second method or simply
refuses the first method, the second method should be tried. Some remote devices support
CHAP only and some PAP only. The order in which you specify the methods is based on your
concerns about the ability of the remote device to correctly negotiate the appropriate
method as well as your concern about data line security.
PAP provides a simple method for a remote node to establish its identity using a two-way
handshake. This is done only on initial link establishment. The hostname on one router must
match the username the other router has configured for PPP. The passwords must also
match. Specify the username and password parameters, use the following command: ppp
pap sent-username name password password.
CHAP periodically verifies the identity of the remote node using a three-way handshake. The
hostname on one router must match the username the other router has configured. The
passwords must also match. This occurs on initial link establishment and can be repeated
any time after the link has been established.
The debug command is used for troubleshooting and is accessed from privileged EXEC mode
of the command-line interface. A debug output displays information about various router
operations, related traffic generated or received by the router, and any error messages. It
can consume a significant amount of resources, and the router is forced to process-switch
the packets being debugged. The debug command must not be used as a monitoring tool;
rather, it is meant to be used for a short period of time for troubleshooting.
Use the debug ppp command to display information about the operation of PPP. The figure
shows the command syntax. Use the no form of this command to disable debugging output.
Use the debug ppp command when trying to search the following:
Debug PPP
In addition to the debug ppp command, there are other commands that are available for
troubleshooting a PPP connection.
A good command to use when troubleshooting serial interface encapsulation is the debug
ppp packet command, as shown in Figure 2.34. The figure example depicts packet
exchanges under normal PPP operation, including LCP state, LQM procedures, and the LCP
magic number.
Figure 2.35 displays the output of the debug ppp negotiation command in a normal
negotiation, where both sides agree on NCP parameters. In this case, protocol types IPv4 and
IPv6 are proposed and acknowledged. The debug ppp negotiation command enables the
network administrator to view the PPP negotiation transactions, identify the problem or
stage when the error occurs, and develop a resolution. The output includes the LCP
negotiation, authentication, and NCP negotiation.
The debug ppp error command is used to display protocol errors and error statistics
associated with PPP connection negotiation and operation, as shown in Figure 2.36. These
messages might appear when the Quality Protocol option is enabled on an interface that is
already running PPP.
Note: Never assume your authentication configuration works without testing it using the
previously covered show commands. If there are issues, debugging allows you to verify the
issue is with authentication and correct any deficiencies. For debugging PPP authentication,
use the debug ppp authentication command.
The figure 2.37 shows an example output of the debug ppp authentication command. The
following is an interpretation of the output:
4 - Failure
id - 3 is the ID number per LCP packet format
len - 48 is the packet length without the header
Conclusion
Serial transmissions sequentially send one bit at a time over a single channel. A serial port is
bidirectional. Synchronous serial communications require a clocking signal.
Point-to-Point links are usually more expensive than shared services; however, the benefits
may outweigh the costs. Constant availability is important for some protocols, such as VoIP.
SONET is an optical network standard that uses STDM for efficient use of bandwidth. In the
United States, OC transmission rates are standardized specifications for SONET.
The bandwidth hierarchy used by carriers is different in North America (T-carrier) and
Europe (E-carrier). In North America, the fundamental line speed is 64 kbps, or DS0. Multiple
DS0s are bundled together to provide higher line speeds.
The demarcation point is the point in the network where the responsibility of the service
provider ends and the responsibility of the customer begins. The CPE, usually a router, is the
DTE device. The DCE is usually a modem or CSU/DSU.
Cisco HDLC is a bit-oriented synchronous data link layer protocol extension of HDLC and is
used by many vendors to provide multiprotocol support. This is the default encapsulation
method used on Cisco synchronous serial lines.
Synchronous PPP is used to connect to non-Cisco devices, to monitor link quality, provide
authentication, or bundle links for shared use. PPP uses HDLC for encapsulating datagrams.
LCP is the PPP protocol used to establish, configure, test, and terminate the data link
connection. LCP can optionally authenticate a peer using PAP or CHAP. A family of NCPs are
used by the PPP protocol to simultaneously support multiple network layer protocols.
Multilink PPP spreads traffic across bundled links by fragmenting packets and
simultaneously sending these fragments over multiple links to same remote address, where
they are reassembled.
PPP optionally supports authentication using PAP, CHAP, or both PAP and CHAP protocols.
PAP sends authentication data in plaintext. CHAP uses a 3-way handshake, periodic
challenge messaging, and a one-way hash that helps protect against playback attacks.