Chabot college
Download
1 / 28

Chabot College - PowerPoint PPT Presentation


  • 98 Views
  • Uploaded on

Chabot College. Point-to-Point Protocol. Point-to-Point Protocol. Point-to-Point Protocol. successor to SLIP router-to-router host-to-network synchronous or asynchronous developed in the 80’s. Layering PPP Elements. PPP Operation. PPP Physical Interfaces.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Chabot College' - montana-ochoa


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Chabot college
Chabot College

Point-to-Point Protocol



Point to point protocol1
Point-to-Point Protocol

  • successor to SLIP

  • router-to-router

  • host-to-network

  • synchronous or asynchronous

  • developed in the 80’s




Ppp physical interfaces
PPP Physical Interfaces

PPP runs on the following types of WAN physical interfaces:

  • Asynchronous serial

  • ISDN

  • Synchronous serial


Ppp datagram transmission
PPP Datagram Transmission

Encapsulation - supports HDLC protocol to provide encapsulation.

Link Control Protocol (LCP) - used to establish, configure, and test the data link.

Network Control Protocols (NCPs) - used to establish and configure different network layer protocols.




Ppp stages
PPP stages

  • LCP frames configure and test the data link

  • The link is established, and facilities are negotiated.


Ppp stages1
PPP stages

  • NCP frames are sent to choose and configure network layer protocols.

  • The chosen network layer protocols (IP, IPX, etc.) are configured, and packets from each network layer protocol are sent.




Ppp lcp configuration options1
PPP LCP Configuration Options

  • PPP options:

    • Authentication

    • Compression

    • Error Detection

    • Callback

    • Multilink

  • Only Authentication is covered on the CCNA exam.


Ppp compression
PPP Compression

  • Compression should only be used on low speed WAN interfaces (typically 56 Kbps and less).

  • When compression is performed in software, it might substantially degrade system performance.

    • Disable compression if the router CPU load exceeds 40 percent.


Compression algorithms
Compression Algorithms

  • Predictor - Determines whether the data is already compressed. If so, the data is just sent-no time is wasted trying to compress already compressed data.

  • Stacker - A Lempel-Ziv (LZ)-based compression algorithm looks at the data, and sends each data type only once with information about where the type occurs within the data stream. The receiving side uses this information to reassemble the data stream.


Compression algorithms1
Compression Algorithms

  • MPPC - This protocol (RFC 2118) allows Cisco routers to exchange compressed data with Microsoft clients. MPPC uses an LZ-based compression algorithm.

  • TCP header compression - This type of compression is used to compress the TCP headers. (Good for Telnet)





Authentication phase optional
Authentication Phase (optional)

Takes place before entering the network-layer protocol phase.

PPP supports two authentication protocols:

  • PAP (RFC 1334)

  • CHAP (RFC 1334 and 1994)


Chabot college
PAP

  • simple

  • two-way handshake

  • done only upon initial link establishment

  • passwords are sent across the link in cleartext

  • remote node is in control of the frequency and timing of the login attempts



Chabot college
CHAP

  • used at the startup of a link, and periodically

  • three-way handshake

  • the local router sends a “challenge” message to the remote node

  • local router (or a third-party authentication server such as TACACS) is in control of the frequency and timing of the challenges