serial ethernet device servers
   Home   |  Sitemap
serial ethernet device servers
EtherPAD PPP Configuration
serial ethernet device servers
Introduction

The Point-to-Point Protocol is the Internet standard for transporting IP Packets over standard asynchronous serial lines. PPP extends TCP/IP networking over a serial line thereby enabling all network applications normally performed on an Ethernet network to be extended over the serial PPP connection. If there is no direct serial line, the EtherPAD supports connection establishment using an external modem and a telephone network. The EtherPAD implements the standard PPP authentication protocol called PAP (Password Authentication Protocol). To aid the user in configuring a PPP connection, we have added a brief explanation of the protocol.

Top of page
serial ethernet device servers
How PPP Works

PPP is essentially an assortment of protocols that work together to supply a full complement of serial-based networking features. The PPP standard at present is RFC 1661, which divides the components of PPP into three general categories:
- A method for encapsulating multi-protocol datagrams, PPP can support datagrams from more than one protocol system.
- A Link Control Protocol (LCP) for establishing, configuring, and testing the connection. PPP negotiates configuration settings and thus eliminates compatibility problems.
- A family of Network Control Protocols (NCPs) supporting upper-layer protocol systems. PPP can include separate sub-layers that provide separate interfaces to TCP/IP.

The following sections discuss these components of PPP.


PPP Data
The primary purpose of PPP is to forward datagrams, which could be of more than one protocol type. For example an IP or another OSI network layer datagram. PPP must also forward data relevant to the protocols that establish and manage the serial/modem connection. Devices exchange several types of messages and requests during a PPP connection. These are: LCP packets, used to establish, manage, and close the connection; authentication packets, which support PPP's optional authentication protocols; and NCP packets, which interface PPP with various protocol stacks.

The LCP data exchanged at the beginning of the connection configures the common connection parameters. NCP protocols then configure network protocol-specific parameters that are supported by the PPP connection.


PPP Connections
A PPP connection is established as follows:
A connection is established and the LCP negotiation process starts.
If this negotiation process specifies that authentication should take place, the communicating devices enter an authentication phase, which is managed by the Password Authentication Protocol (PAP).
PPP then uses NCP packets to specify protocol-specific configuration information for the supported protocol stacks. For example IPCP for TCP/IP.
PPP then transmits datagrams received from upper-layer protocols.
The PPP connection is closed using LCP termination packets.


Link Control Protocol (LCP)
Much of the versatility of the PPP protocol comes from the internal LCP functions that establish, manage, and terminate connections. There are three types of LCP packets:
- Link configuration packets
- Link termination packets
- Link maintenance packets

The following describes how LCP configuration packets enable the communicating devices to establish a connection. Device A sends an LCP Configure-request packet to Device B. The configure-request packet includes a proposal for any connection parameters Device A would like to negotiate for the connection. These parameters include the Maximum Receive Unit (MRU), which defines a maximum length for data enclosed in a PPP frame, the authentication protocol, and the quality control protocol. The quality control protocol defines how the connection monitors for reliable delivery, compression protocol settings, and other configuration choices.

Should Device B accept all the configuration options submitted in the Configure-Request packet, it would respond with a Configure-Ack (Acknowledge) packet. If all configuration options transmitted with the Configure-Request are recognizable but some are not acceptable to Device B then it would respond with a Configure-Nak (Not Acknowledged) packet. Device B then returns a list of unacceptable parameters with alternative values. Device A then responds to the Configure-Nak with a new configuration request using adjusted values. This process continues until all values are accepted.

If the Configure-Request packet includes unrecognizable options, Device B would return a Configure-Reject packet listing all unacceptable options. There are other types of LCP packets as well. These assist in the overseeing of modem connections.

A code field identifies the LCP packet type. An Identifier field identifies the packet and matches up requests with acknowledgments. As previously mentioned, LCP controls the configuration, maintenance and termination of a PPP connection. For example, the Terminate-Request and Terminate-Ack packets are used to request and acknowledge termination of the connection. Code-Reject and Protocol-Reject reject requests for an unknown code or protocol. Echo-Request, Echo-Reply, and Discard-Request provide maintenance, quality assurance, and troubleshooting capabilities.

Top of page
serial ethernet device servers
IP Addressing and Authentication

The configuration of these paramaters is now discussed in more detail.
IP Addressing and Authentication

IP Addressing and Authentication


In the above Illustration both the EtherPAD and the PC have been allocated IP addresses in the subnet 192.168.1.X where X is any value from 0 to 255. When the PPP connection is being established two further IP addresses many be required. These are used to create the connection through the modems and across the telephone network.Depending on the application requiring the PPP connection, these IP addresses may be allocated by the Networked PC. If not, they have to be configured on the EtherPAD.

Should you require the PC to authenticate itself with the EtherPAD, the Remote PAP Authentication parameters should be configured. The PC then has to send these details to the EtherPAD before the PPP connection will transfer the network packets. If the Networked PC should require the EtherPAD to Authenticate itself before allowing a PPP connection to be established, the EtherPAD would send the Local PAP Authentication details to the PC. Both of these Authentication options might be implemented as security precautions.

Top of page
serial ethernet device servers
Setting up the EtherPAD PPP configuration via Web Browser

Adding a PPP Entry
From the Home page click on Serial Application.

Setting up the EtherPAD PPP configuration via Web Browser

Setting up the EtherPAD PPP configuration via Web Browser

From the Serial Application click on Change Serial Parameters.

Serial Applications

Serial Applications

In the Protocol drop-down box select PPP.

PPP Application Settings

PPP Application Settings

Click Change. If you are usng a Modem, click the Modem Options button and configure these parameters. If not click the the Back button. Select PPP interface and click Add to add an entry to the PPP Interface table.

Add a PPP Application

Add a PPP Application

You are now given the opportunity to configure the PPP parameters.

Top of page
serial ethernet device servers
General PPP Configuration Options

General Configuration Options

General Configuration Options

The following general options are configurable:

Serial Interface - The serial port on which this PPP interface is created. The serial port's Protocol field must also be set to PPP.

Note: Serial ports are used by PPP and Applications, but cannot be used simultaneously by both.

Idle Timeout - the number of seconds of network inactivity after which the PAD will automatically close the PPP connection. A value of 0 will disable this feature.

PAP Authentication
Local ID - the username to send to the peer. If the PAD is not required to authenticate itself with the peer, then this field must be empty.

Local Password - the password to send to the peer.

Remote ID - the username that the peer must send to the EtherPAD. If the peer is not required to authenticate itself with the EtherPAD, then this field must be empty.

Remote Password - the password that is sent to the EtherPAD by the peer.

Internet Protocol (IP)
Local Address - the initial local IP Address of the PPP connection. If the peer is responsible for assigning the IP Address, this field must be set to 0.0.0.0.

Remote Address - the initial remote IP Address of the PPP connection. If the peer is responsible for assigning the IP Address, this field must be set to 0.0.0.0.

Default Route - when enabled, a default route will be added over this PPP interface.

Top of page
serial ethernet device servers
Advanced PPP Configuration

The following section will only be accessible once a PPP Interface has been added. The default values of these parameters are sufficient for most applications and should be modified only by experienced users.

PPP advanced configuration option

PPP advanced configuration option

Protocol Options
MRU - Initial Maximal Receive Unit: - this specifies the maximum sized packets that the peer should send. The minimum value is 128, and the maximum is 1500. The default is 1500.

Receive ACCM - the Asynchronous Control Character Map (ACCM) describes which control characters cannot be successfully received over the serial line. This field is a 32-bit hexadecimal number with each bit representing a character to escape. The default value (FFFFFFFFH) specifies that all control character are escaped.

Example: If the software flow control characters (XON/XOFF) should be escaped, then the ACCM should be configured to exclude bytes 17 and 19. A value of 0A0000H (binary 101000000000000000000) specifies that bytes 17 and 19 should be escaped.

Magic Numbers - enable or disable magic number negotiation. With this option enabled, PPP can detect a looped-back connection. In other words when the peer is echoing received data.

Protocol Compression - enable or disable Protocol Compression. Disable this option only when absolutely necessary.

A&CF Compression - enable or disable Address/Control Field Compression. Disable this option when absolutely necessary.

Connection Options
- Silent Mode - when enabled, the PAD will not start the PPP negotiation until a valid PPP packet is received from the peer. This is disabled by default.
- Passive Mode - when enabled, the PAD will start the PPP negotiation immediately. If no reply is received from the peer, the PAD will wait passively for a valid PPP packet from the peer. This is disabled by default.

Note: Serial ports are used by PPP and Applications, but cannot be used simultaneously by both. If a PPP Interface is required and none is available, the following procedure can be followed to make a PPP Interface available:
- Delete all Device Applications configured to use this interface.
- Configure the Device Interface's Protocol field to PPP.

Top of page
Setting up the EtherPAD PPP Configuration via Telnet/Serial Connection

From the EtherPAD Custom Configuration Menu select 2. Networking…

PPP Configuration via Telnet/Serial Connection

PPP Configuration via Telnet/Serial Connection

From the EtherPAD Networking Menu select 6. PPP…

PPP Configuration Menu

PPP Configuration Menu

Extended PPP Configuration Menu

The following section is accessible by selecting P. Page Down… from the PPP Configuration Options Menu illustrated above.

Extended PPP Configuration Menu

Extended PPP Configuration Menu

PPP Configuration Options

Refer to General PPP Configuration and Advanced PPP Configuration for an explanation of the Configuration parameters.

Top of page
               Copyright © SAN People 2005
Serial-to-Ethernet Devices