PPPoE/v6 Administrator s Guide HP-UX 11i Edition 1 Manufacturing Part Number: 5971-4750 E0703 United States Copyright 2003 Hewlett-Packard Development Company L.P. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. U.S. Government License Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice Copyright 2003 Hewlett-Packard Development Company L.P. All rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws. Trademark Notices ActivePerl is a registered trademark of ActiveState Tool Corporation. exodus is a trademark of White Pine Software, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. 2
Contents About This Manual 1. Introduction PPPoE Overview....................................................... 11 How PPPoE Works...................................................... 12 Protocol Overview...................................................... 13 Packet Types........................................................... 15 Software Architecture................................................... 16 Software Binaries....................................................... 18 2. Installing PPPoE Prerequisites.......................................................... 21 Using swinstall to Install PPPoE.......................................... 22 3. Configuring PPPoE Before You Begin....................................................... 27 Setting Up the Server................................................... 28 Server Configuration File................................................ 29 Sample pppoesd.conf File................................................ 32 Setting Up the Client.................................................... 33 Client Configuration File................................................. 35 Sample pppoec.conf File.................................................. 37 Setting Up the Relay.................................................... 38 Relay Configuration File................................................. 39 Sample pppoerd.conf File................................................. 40 4. Troubleshooting PPPoE Server Log File......................................................... 43 Sample pppoesd.log File................................................. 44 Client Log File......................................................... 45 Sample pppoec.log File................................................... 46 Relay Log File.......................................................... 47 Sample pppoerd.log File................................................. 48 Log Message Types..................................................... 49 5. IPv6 Support for PPP Overview.............................................................. 53 Conformance to RFC 2472.............................................. 53 3
Contents New pppd Changes.................................................... 53 New Command-Line Options............................................ 54 Neighbor Discovery for IPv6............................................ 55 Using PPPv6......................................................... 56 4
About This Manual Table 1 This manual describes how to install and configure the Point-to-Point Protocol over Ethernet (PPPoE/v6) software on your HP-UX 11i operating system. This manual assumes that the HP-UX 11i operating system software and the appropriate files, scripts, and subsets are installed. Audience This manual is intended for system and network administrators responsible for installing, configuring, and managing the Point-to-Point Protocol (PPPoE/v6) software. Administrators are expected to have knowledge of operating system concepts, commands, and Point-to-Point Protocol (PPP) configuration. It is also helpful to have knowledge of Transmission Control Protocol/Internet Protocol (TCP/IP) networking concepts and network configuration; this manual is not a TCP/IP or PPPoE tutorial. Organization PPPoE/v6 Administrator s Guide is divided into several chapters, each of which contains information about installing or configuring PPPoE. The following list describes the content in more detail. Document Contents Chapter Introduction Installing PPPoE Configuring PPPoE Troubleshooting PPPoE Description Presents an overview of PPPoE and lists the components that the PPPoE software contains. Describes the tasks to install the PPPoE software on the HP-UX 11i operating system. Describes the tasks to configure the PPPoE client and the server. Describes how to troubleshoot the PPPoE software. 5
Table 1 Document Contents (Continued) Chapter IPv6 Support for PPP Description Presents an overview of the IPv6 support for PPP and describes how to use the PPPv6 software. Related Documents For more information about HP-UX networking and communications, see the following books: Installing and Administering PPP Provides information about configuring and using the PPP product. The manual also describes how to migrate SLIP connections from earlier HP-UX releases to the SLIP mode of the PPP product. You can access this manual at the following URL: http://docs.hp.com/hpux/onlinedocs/b2355-90137/b2355-90137.html Request for Comments (RFC) Many sections of this manual refer to RFCs (for example, RFC 2516) for more information about certain networking topics. These documents publicize Internet standards, new research concepts, and status memos about the Internet. You can access the full range of RFC documents and more information about the Internet Engineering Task Force (IETF) at the following URL: http://www.ietf.org/rfc.html iknow Topics of Interest HP iknow Topics of Interest describe some networking concepts and tasks, as well as other topics. You can find these documents on the HP-UX networking communications homepage at the following URL: http://docs.hp.com/iknow HP Welcomes Your Comments HP welcomes any comments and suggestions you have on this manual. You can send your comments in the following ways: Internet electronic mail: netinfo_feedback@cup.hp.com 6
A feedback form located at the following URL: http://docs.hp.com/assistance/feedback.html Please include the following information along with your comments: The full title of the manual and the part number. (The part number appears on the title page of printed and PDF versions of a manual.) The section numbers and page numbers of the information on which you are commenting. The version of HP-UX that you are using. Please note that the HP-UX networking communications publications group does not provide technical support for HP products. If your inquiry concerns technical support for an HP product, please use the Assistance directory page located at: http://www.hp.com/ghp/assist/directory.html or call HP support at (208) 323-2551 or pre-merger Compaq support at (800) OK-COMPAQ (800-452-6672). Typographic Conventions This document uses the following typographic conventions: $ A dollar sign represents the system prompt for the C and POSIX shells. # A number sign represents the superuser prompt. file Italic (slanted) type indicates document and book names. daemon Courier font type indicates daemons, files, commands, manual reference pages, and option names. { } In syntax definitions, brackets indicate items that are optional and braces indicate items that are required. (Ctrl+A) This symbol indicates that you hold down the first named key while pressing the key or mouse button that follows the plus. 7
8
1 Introduction This chapter describes how to install and configure the Point-to-Point Protocol over Ethernet (PPPoE) software, a part of Transport Optional Upgrade Release (TOUR) release, on your HP-UX 11i operating system. Chapter 1 9
Introduction This chapter discusses the following topics: PPPoE Overview on page 11 How PPPoE Works on page 12 Protocol Overview on page 13 Packet Types on page 15 Software Architecture on page 16 Software Binaries on page 18 10 Chapter 1
Introduction PPPoE Overview PPPoE Overview PPPoE allows you to connect multiple hosts at a remote location through the same customer access device, and to reduce the cost of providing dial-up services using Point-to-Point Protocol (PPP). PPPoE, as described in RFC 2516, enables broadband service providers to authenticate users and to maintain the familiar dial-up experience for users when they connect to the Internet through a broadband modem. This framework allows each host to use its own PPP stack and provide a user-friendly interface to implement access control and other functionality on a per-user basis. You can discard permanent connections and make optimal use of the IP address pool. With a cost-effective LAN technology such as Ethernet, and the demonstrated scalability and administrative controls of PPP, you can deploy Internet services in your network environment with ease. Chapter 1 11
Introduction How PPPoE Works How PPPoE Works Figure 1-1 depicts how PPPoE enables you to connect to the Internet via a Digital Subscriber Line (DSL). Figure 1-1 PPPoE Framework DSL providers use PPPoE to provide faster access to the Internet via an Ethernet line. PPPoE eliminates the need for a serial line to connect users. It authenticates the users and analyzes the volume of network traffic each user generates. 12 Chapter 1
Introduction Protocol Overview Protocol Overview Any PPPoE session typically comprises two peers communicating over an Ethernet link. Each peer must learn the Ethernet address of the remote peer and also establish a unique session identifier that identifies the PPPoE session between the peers. Figure 1-2 depicts how the PPPoE client and the server, on the same link, communicate with each other. Figure 1-2 When Client and Server Are on the Same Link 1.2.3.4 5.6.7.8 PPPoE Client PPPoE Server fe80::10 fe80::9 You need an optional relay when there is a router in between the PPPoE client and the server. In such cases, the relay receives packets from the clients and transmits them on the other link to the server and from the server to the client. See Figure 1-3 for information on how the client connects to the server via a relay. Figure 1-3 When Client and Server Are on Different Links 1.2.3.4 5.6.7.8 PPPoE Client lan4 Relay lan0 PPPoE Server fe80::10 fe80::9 Chapter 1 13
Introduction Protocol Overview Each PPPoE session includes the following stages: Discovery stage PPPoE functions as a client/server model in the discovery stage. Before a host tries to initiate a PPP session, it searches for a suitable PPPoE server (access concentrator) that can provide the services required by the host. The host then learns the server s Media Access Control (MAC) address and a unique session number called the session ID. During this process, if the host finds more than one access concentrator, it chooses the most appropriate one with which to establish connection. After the host selects the access concentrator, both the host and the chosen access concentrator have the necessary information to establish their PPP connection over the Ethernet. The host and the server exchange packets as follows: 1. The host broadcasts the initiation packet, PPPoE Active Discovery Initiation (PADI). 2. One or more access concentrators (servers) send offer packets, PPPoE Active Discover Offer (PADO), to the host. 3. The host sends the unicast session request packet, PPPoE Active Discovery Request (PADR), to the access concentrator from which it requests service. 4. The selected access concentrator sends the confirmation packet, PPPoE Active Discovery Session-confirmation (PADS), to the host. 5. Either the host or the access concentrator sends the termination packet, PPPoE Active Discovery Terminate (PADT), to indicate the close of a session. Session stage PPPoE functions as a peer-peer protocol in the session stage. After learning the Ethernet address and the session number, both the host and the server start the pppd daemon. The PPPoE session frames encapsulate the PPP frames. All Ethernet packets are unicast. 14 Chapter 1
Introduction Packet Types Packet Types Table 1-1 Table 1-1 lists the packets exchanged between the host and the access concentrator during the discovery stage. Packet Types Packet PADI PADO PADR PADS PADT Description The host sends the PPPoE Active Discovery Initiation (PADI) packet with the destination address set to the broadcast address. When an access concentrator receives a PADI that it can serve, it responds to the host by sending a PPPoE Active Discover Offer (PADO) packet. The destination address is the unicast address of the host that sent the PADI. Since the PADI was broadcast, the host may receive more than one PADO. The host examines the PADO packets it receives and selects one. The host then sends one PPPoE Active Discovery Request (PADR) packet to the access concentrator that it has selected. The destination address field is set to the unicast Ethernet address of the access concentrator that sent the PADO. When the access concentrator receives the PADR packet, it prepares to start a PPP session. It generates a unique session ID for the PPPoE session and responds to the host with a PPPoE Active Discovery Session-confirmation (PADS) packet. The destination address field is the unicast Ethernet address of the host that sent the PADR. Either the client or the server sends a PPPoE Active Discovery Terminate (PADT) packet to terminate a PPP session. The destination address field is a unicast Ethernet address. When a PADT is received, no further PPP traffic is sent through that session. Chapter 1 15
Introduction Software Architecture Software Architecture Figure 1-4 illustrates the architecture of the PPPoE software. Figure 1-4 PPPoE Architecture Client pppd 1 PADI 2 PPPoE Server pppd pppd PADO 3 PADR MUX dlpi 4 PADS 5 dlpi PADT The numbers 1,2,3,4, and 5, in Figure 1-4, depict the interactions between the client and the server before and after establishing a PPPoE connection. See PPPoE Overview, on page 11 for more information. The PPPoE client initially searches for an access concentrator in a separate process, which forks a pppd process on discovering the appropriate server. It also notifies the pppd process that the basic device is Ethernet. Several pppd processes may be running on the server, waiting for PPPoE packets. When a client sends a packet, all the pppd processes running on the server receive it and filter it based on the session ID within the PPPoE packet. A multiplexor (MUX) installed on the server prevents all the pppd processes from receiving the packet. The multiplexor is linked to a 16 Chapter 1
Introduction Software Architecture Data Link Provider Interface (DLPI). DLPI examines each PPPoE packet and delivers it to the corresponding pppd process based on the session ID. Chapter 1 17
Introduction Software Binaries Software Binaries Table 1-2 Table 1-2 lists the software binaries that the PPPoE software package contains. PPPoE Software Binaries File /usr/sbin/pppoesd /usr/bin/pppoec /usr/sbin/pppoerd /usr/bin/pppd /dev/pppoe Description The PPPoE server daemon. The PPPoE client daemon. The PPPoE relay daemon. The PPP daemon. The Dynamically Linked Kernel Module (DLKM) installed on the access concentrator. 18 Chapter 1
2 Installing PPPoE This chapter describes how to install the Point-to-Point Protocol over Ethernet (PPPoE) software on the HP-UX 11i operating system. It discusses the following topics: Chapter 2 19
Installing PPPoE Prerequisites on page 21 Using swinstall to Install PPPoE on page 22 20 Chapter 2
Installing PPPoE Prerequisites Prerequisites The following lists the prerequisites for installing PPPoE: HP 9000 computer HP-UX 11i operating system Chapter 2 21
Installing PPPoE Using swinstall to Install PPPoE Using swinstall to Install PPPoE PPPoE is a part of Transport Optional Upgrade Release (TOUR) 1.0. You can download the TOUR 1.0 software bundle from the following URL: http://www.software.hp.com After downloading the software bundle, use the swinstall command to install the package on your system. You do not need to create or modify any system file while installing the PPPoE software on your system. The swinstall command creates and modifies the necessary files on your system automatically. For more information about the swinstall command, type man 1 swinstall at the HP-UX prompt. To install the PPPoE software, complete the following steps: Step 1 Type swinstall -s <destination path> on the command line. <destination path> is the absolute path used to download the TOUR software bundle. The following screen appears: Figure 2-1 The swinstall Window 22 Chapter 2
Installing PPPoE Using swinstall to Install PPPoE Step 2 Step 3 Use arrow keys to select the TOUR product, as shown in Figure 2-1. Invoke the Actions (Alt+A) menu and select the Install option. swinstall installs TOUR and its components on your HP-UX 11i system and is now available for use. NOTE The swinstall command installs the pppoe.o and pppoe modules in the /stand/dlkm/mod.d/pppoe/ and /dev/ directories, respectively. You cannot run the PPPoE server daemon without pppoe.o and pppoe. If you attempt to use the server without these modules, the server shuts down immediately. Chapter 2 23
Installing PPPoE Using swinstall to Install PPPoE 24 Chapter 2
3 Configuring PPPoE This chapter describes how to configure the Point-to-Point Protocol over Ethernet (PPPoE) software on your HP-UX 11i operating system. It discusses the following topics: Chapter 3 25
Configuring PPPoE Before You Begin on page 27 Setting Up the Server on page 28 Server Configuration File on page 29 Sample pppoesd.conf File on page 32 Setting Up the Client on page 33 Client Configuration File on page 35 Sample pppoec.conf File on page 37 Setting Up the Relay on page 38 Relay Configuration File on page 39 Sample pppoerd.conf File on page 40 26 Chapter 3
Configuring PPPoE Before You Begin Before You Begin Before you set up the PPPoE server or the client, complete the following steps: 1. Obtain information about the PPPoE server from your service provider. 2. Assemble all the necessary devices used by the client (DSL modem, hub, router, and other devices). Chapter 3 27
Configuring PPPoE Setting Up the Server Setting Up the Server Table 3-1 The pppoesd daemon, on the server, performs discovery activities as described in RFC 2516. pppoesd responds to the client s PADI and PADR packets about its willingness to offer services. It generates a unique session ID for every client it services. In addition, pppoesd forks a pppd daemon to perform a set of activities in the session phase. To invoke pppoesd, run the following command on the command line: pppoesd [-c config-file] [-d debug-level] [-l log-file] [-c config-file] specifies the configuration file for the PPPoE server. The default file is /etc/ppp/ppoesd.conf. See Table 3-1 for information about debug levels. [-d debug-level] specifies values for various debug levels. [-l log-file] specifies the file to which pppoesd logs messages. The default log file is /var/adm/pppoesd.log. Debug Levels Level LOG_ERROR LOG_WARN LOG_DEBUG Description Logs all error messages. To log these messages, type -d 0 on the command line. Logs all warning messages. To log these messages, type -d 1 on the command line. Logs all function level error messages. To log these messages, type -d 2 on the command line. Following is an example of pppoesd usage: /usr/sbin/pppoesd -d 1 -l /tmp/pppoesd.log For more information, type man 1m pppoesd at the HP-UX prompt. See Server Log File, on page 43 for more information on how pppoesd logs messages to its log file. 28 Chapter 3
Configuring PPPoE Server Configuration File Server Configuration File Table 3-2 You cannot run pppoesd without a configuration file. The default configuration file is /etc/ppp/pppoesd.conf. Use this file to set the server parameters. A blank line separates each entry in the pppoesd.conf file. pppoesd.conf ignores lines that begin with #. Each entry is of the following format: <parameter>=<value> Table 3-2 lists the parameters that the server configuration file supports. Server Parameters interface Parameter Description Specifies the name of an interface and related parameters. Following is an example usage of this parameter: [lan0] service= acname=...... [lan1] service= acname= service acname Specifies the name of the service that the server is ready to offer to the client. A value of any means that the server is ready to offer any of the services available. Specifies a unique name of the address concentrator. Chapter 3 29
Configuring PPPoE Server Configuration File Table 3-2 Server Parameters (Continued) ac_cookie Parameter Description Specifies a tag that the access concentrator may encapsulate in the AC-Cookie tag in a PADO packet. pppoesd generates a unique digest using the MD5 algorithm. This tag aids in protecting against denial of service attacks. If a host receives this tag, it must return the tag unmodified in the following PADR. The tag value is binary data of any value and length; the host cannot interpret this value. If you set this parameter to 0, pppoesd does not add the AC-Cookie tag in a PADO packet. timeout retry_number local-ipv4-address ipv4-address-pool local-ipv6-identifier ipv6-identifier-pool Specifies the timeout value for PPP session traffic in seconds. This is passed as the idle timeout option for pppd. Specifies the number of times pppoesd retransmits a PADI or PADR packet when the client does not receive a valid PADO or PADS packet in response to its request. Specifies the address of the local interface. Specifies a range of valid IP addresses that the server allocates to its clients. Specifies the interface identifier of the local IPv6 interface. Specifies a range of valid IPv6 interface identifiers that the server allocates to its clients. 30 Chapter 3
Configuring PPPoE Server Configuration File Table 3-2 Server Parameters (Continued) Parameter pppd-options Description Specifies the command-line options of pppd. For more information, type man 1m pppd at the HP-UX prompt. For more information about the pppoesd.conf file, type man 4 pppoesd.conf at the HP-UX prompt. Chapter 3 31
Configuring PPPoE Sample pppoesd.conf File Sample pppoesd.conf File You can use the sample pppoesd.conf file, available in the /etc/ppp/ directory, as your server configuration file. The sample pppoesd.conf file is as follows: [ lan4 ] service=any acname=gatt3 ac_cookie=1 #host_unique=0 timeout=1200 #retry-number=3 local-ipv4-address=1.2.3.4 ipv4-address-pool=5.6.7.8-5.6.7.101 pppd-options=mru 1492 debug 11 #Following entries are related to PPPoEv6 local-ipv6-identifier=::9 ipv6-identifier-pool=::10 - ::100 32 Chapter 3
Configuring PPPoE Setting Up the Client Setting Up the Client The pppoec daemon, on the client, discovers an access concentrator that is able to offer services. It obtains a unique session ID from the chosen access concentrator. Also, it forks a pppd daemon to perform session stage functions as mentioned in RFC 2516. To run pppoec, run one of the following commands on the command line: pppoec -i interface-name or pppoec -i interface-name [-c config-file] [-d debug-level] [-l log-file] [-r retry-time] [-i interface-name] specifies the name of the network interface to be used for the PPPoE session. [-c config-file] specifies the name of the configuration file to be used by pppoec. The default file is /etc/ppp/pppoec.conf. [-d debug-level] specifies the various debug levels. See Table 3-1 on page 28for more information. [-l log-file] specifies the name of the log file to be used for logging messages. The default log file is /var/adm/pppoec.log. [-r retry-time] specifies the time in seconds, after which a PADI or PADR packet is retransmitted when there is no response from the access concentrator. The default value is 3. Following are examples of pppoec usage: /usr/bin/pppoec -i lan0 /usr/bin/pppoec -i lan4 -c /tmp/ppp/pppoec.conf -d 2 -l /tmp/pppoec.log -r 5 For more information, type man 1 pppoec at the HP-UX prompt. See Client Log File, on page 45 for more information on how pppoec logs messages to its log file. IMPORTANT The [-i interface-name] option is mandatory. You must specify a valid interface name to be used for the PPPoE session. Chapter 3 33
Configuring PPPoE Setting Up the Client Do not use SIGKILL to terminate the pppoec daemon. Instead, use SIGTERM. 34 Chapter 3
Configuring PPPoE Client Configuration File Client Configuration File Table 3-3 /etc/ppp/pppoec.conf is the configuration file for the pppoec daemon. Upon startup, pppoec reads pppoec.conf to initialize itself. Also, it uses the parameters specified in this file during the PPPoE session. Table 3-3 lists the parameters that the client configuration file supports. Client Parameters Parameter service acname host-unique Description Specifies the name of the service that the client requires. A value of any means that the client is ready to accept any of the available services. Specifies the name of the access concentrator from which the client wishes to avail service. This name uniquely identifies an access concentrator from its peers. Specifies a tag that the host uses to uniquely associate an access concentrator response (PADO or PADS) to a particular host request (PADI or PADR). To include the tag, set host-unique=1. To exclude the tag, set host-unique=0. retry-number timeout Specifies the number of times a PADI or PADR packet is transmitted when the access concentrator does not respond to the client s request. Specifies the timeout value in seconds. pppoec waits for this duration to receive either a PADO or PADS packet before retransmitting a PADI or PADR packet. The default value is 15. Chapter 3 35
Configuring PPPoE Client Configuration File Table 3-3 Client Parameters (Continued) Parameter pppd-options Description Specifies the command-line options of pppd. For more information, type man 1m pppd at the HP-UX prompt. Each entry in pppoec.conf is of the following format: <parameter>=<value> A blank line separates each entry in the configuration file. The pppoec.conf file ignores lines that begin with a number sign (#). 36 Chapter 3
Configuring PPPoE Sample pppoec.conf File Sample pppoec.conf File You can use the sample pppoec.conf file, available in the /etc/ppp/ directory, as your client configuration file. The sample pppoec.conf file is as follows: [ lan4 ] service=any acname=gatt3 #host_unique=0 timeout=1200 retry-number=4 pppd-options=mru 1492 debug 11 enable_ipv6=1 [ lan0 ] service=any acname=gatt3 #host_unique=0 timeout=1200 retry-number=4 pppd-options=mru 1492 debug 11 #enable_ipv6=1 Chapter 3 37
Configuring PPPoE Setting Up the Relay Setting Up the Relay To set up the /etc/ppp/pppoerd daemon, run the following command at the HP-UX prompt: pppoerd [-c config-file] [-d debug-level] [-l log-file] [-c config-file] specifies the name of the relay configuration file. The default file is /etc/ppp/pppoerd.conf. [-d debug-level] specifies the debug level. [-l log-file] specifies the name of the log file to which pppoerd logs messages. The default file is /var/adm/pppoerd.log. Following is an example of pppoerd usage: /usr/sbin/pppoerd -c /tmp/pppoerd.conf -d 0 For more information on pppoerd, type man 1m pppoerd at the HP-UX prompt. See Relay Log File, on page 47 for more information on how pppoerd logs messages to its log file. 38 Chapter 3
Configuring PPPoE Relay Configuration File Relay Configuration File Table 3-4 /etc/ppp/pppoerd.conf is the configuration file for the pppoerd daemon. pppoerd reads this file to initialize the relay. A blank line separates each entry in the pppoerd.conf file. pppoerd ignores lines that begin with a number sign (#). You can use the pppoerd.conf file to set the relay parameters. Table 3-4 lists the parameters that the relay supports. Relay Parameters Parameter server-intf client-intf-list Description Specifies the name of the server interface. Specifies a list of client interfaces. For more information, type man 4 pppoerd.conf at the HP-UX prompt. Chapter 3 39
Configuring PPPoE Sample pppoerd.conf File Sample pppoerd.conf File You can use the sample pppoerd.conf file, available in the /etc/ppp/ directory, as your relay configuration file. The sample pppoerd.conf file is as follows: server-intf=lan4 client-intf-list=lan2 lan0 40 Chapter 3
4 Troubleshooting PPPoE This chapter describes how to troubleshoot the Point-to-Point Protocol over Ethernet (PPPoE) software using log messages. It discusses the following topics: Chapter 4 41
Troubleshooting PPPoE Server Log File on page 43 Sample pppoesd.log File on page 44 Client Log File on page 45 Sample pppoec.log File on page 46 Relay Log File on page 47 Sample pppoerd.log File on page 48 Log Message Types on page 49 42 Chapter 4
Troubleshooting PPPoE Server Log File Server Log File pppoerd, the PPPoE server daemon, logs three types of messages to its log file. The default log file is /var/adm/pppoesd.log. To use an alternate log file, specify the name and path with the -l option on the command line while running the server daemon. See Table 3-1 on page 28 for information on log message types. Chapter 4 43
Troubleshooting PPPoE Sample pppoesd.log File Sample pppoesd.log File A sample pppoesd.log file is as follows: Feb 06 16:06:48 No PPPOE configuration file: /etc/ppp/pppoesd.conf. Exiting Feb 06 00:21:27 parse_config_file: Ignoring line 5 --> #host_unique=0 Feb 06 00:21:27 parse_config_file: Ignoring line 7 --> #retry-number=3 Feb 06 00:21:27 parse_config_file: Ignoring line 11 --> # Following entries are related to PPPoEv6 Feb 06 00:21:27 parse_config_file: Ignoring line 12 --> #enable_ipv6=1 Feb 06 00:21:27 parse_config_file: Ignoring line 13 --> #local-ipv6-identifier=::9 Feb 06 00:21:27 parse_config_file: Ignoring line 14 --> #ipv6-identifier-pool=::10 - ::100 Feb 06 00:21:27 parse_config_file: Ignoring line 15 --> Feb 06 00:21:27 attach_ppa: Attached to ppa:4 Feb 06 00:21:27 bound to sap : 8863 Feb 06 00:21:27 dlpi_init: Initialized lan4 for PPPoE discovery packets Feb 06 00:21:27 attach_ppa: Attached to ppa:4 Feb 06 00:21:27 bound to sap : 8864 Feb 06 00:21:27 pppoe_init: Initialized lan4 for PPPoE session packets Feb 06 00:22:41 process_padi: PADI packet from 00:10:83:03:5a:20 Feb 06 00:22:41 process_padi: PADO packet sent to 00:10:83:03:5a:20 Feb 06 00:22:41 process_padr: PADR packet from 00:10:83:03:5a:20 Feb 06 00:22:41 process_padr: client allocated address : 5.6.7.8 44 Chapter 4
Troubleshooting PPPoE Client Log File Client Log File pppoec, the PPPoE client daemon, logs three types of messages to its log file. The default log file is /var/adm/pppoec.log. To use an alternate log file, specify the name and path with the -l option on the command line while running the client daemon. See Table 3-1 on page 28 for information on log message types. Chapter 4 45
Troubleshooting PPPoE Sample pppoec.log File Sample pppoec.log File A sample pppoec.log file is as follows: Feb 06 00:15:22 parse_config_file: Ignoring line 4 --> #host_unique=0 Feb 06 00:15:22 fill_entry: invalid timeout tag value. Feb 06 00:15:22 parse_config_file: Ignoring line 8 --> #enable_ipv6=1 Feb 06 00:15:22 parse_config_file: Ignoring line 9 --> Feb 06 00:15:22 attach_ppa: Attached to ppa:4 Feb 06 00:15:22 bound to sap : 8863 Feb 06 00:15:22 dlpi_init: Initialized lan4 for PPPoE discovery packets Feb 06 00:15:22 send_padi: Sending PADI packet on lan4 Feb 06 00:15:22 main: Packet with code : 9. Ignoring packet Feb 06 00:15:22 process_pado: PADO packet received from 00:10:83:b9:d1:51 Feb 06 00:15:22 process_pado: valid PADO packet Feb 06 00:15:22 send_padr: Sending PADR packet to 00:10:83:b9:d1:51 Feb 06 00:15:22 process_pads: PADS packet received from 00:10:83:b9:d1:51 46 Chapter 4
Troubleshooting PPPoE Relay Log File Relay Log File pppoerd, the PPPoE relay daemon, logs three types of messages to its log file. The default log file is /var/adm/pppoerd.log. To use an alternate log file, specify the name and path with the -l option on the command line while running the relay daemon. See Table 3-1 on page 28 for information on log message types. Chapter 4 47
Troubleshooting PPPoE Sample pppoerd.log File Sample pppoerd.log File A sample pppoerd.log file is as follows: Feb 06 01:53:50 sending PADI on lan4 Feb 06 01:53:50 PADI not from a PPPoE Client. Ignoring packet Feb 06 01:53:50 relaying packet from lan4 on lan0 Feb 06 01:53:50 relaying packet from lan0 on lan4 48 Chapter 4
Troubleshooting PPPoE Log Message Types Log Message Types Table 4-1 You can identify and pinpoint a problem by seeing the PPPoE log messages. Table 4-1 lists the different types of messages that PPPoE logs. PPPoE Log Messages Message Type LOG_WARN Message Text process_pado: packet not from a unicast address. Ignoring packet. Error tag present in PADR. Ignoring packet. LOG_ERROR No PADO s receieved. exiting. process_padr: Unable to allocate memory. Exiting. LOG_DBG process_padr: client allocated address : 1.2.3.4. process_padt: PADT packet recieved from ab:cd:ef:gh:ij. Chapter 4 49
Troubleshooting PPPoE Log Message Types 50 Chapter 4
5 IPv6 Support for PPP This chapter describes how to enable the new IPv6 functionality for existing or new users of Point-to-Point Protocol (PPP). It discusses the following topics: Chapter 5 51
IPv6 Support for PPP Overview on page 53 Conformance to RFC 2472 on page 53 New pppd Changes on page 53 New Command-Line Options on page 54 52 Chapter 5
IPv6 Support for PPP Overview Overview Point-to-Point Protocol (PPP) provides connectivity between individual hosts used at remote location, including homes and small offices, to ISPs networks. It is also making an entry into the wireless domain where the connectivity between devices and service providers is mostly through a point-to-point connection. The key function of the HP-UX PPPv6 software is to handle IPv6 datagrams in addition to IPv4 datagrams, and provide all the required connectivity to end-users from a remote network. Transport Optional Upgrade Release (TOUR) 1.0 includes IPv6 support for PPP. The TOUR software is available as a web release on http://www.software.hp.com. The following lists the key features of PPPv6: Conformance to RFC 2472 Changes to pppd Conformance to RFC 2472 PPP now conforms to RFC 2472 - IPv6 over PPP. This RFC defines how to transmit IPv6 packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring IPv6 over PPP. It also describes how to form IPv6 link-local addresses on PPP links and to negotiate the type compression protocol to be used for compressing or decompressing IPv6 headers transmitted over serial lines. New pppd Changes The pppd daemon shipped with HP-UX 11.0 core operating system and later, works with both PPPv4 and PPPv6. The daemon transmits IPv4 as well as IPv6 datagrams over PPP links. The following lists the changes to pppd: Two dedicated interfaces for IPv4 and IPv6. Number of pppd instances increased to 128 from 64. Chapter 5 53
IPv6 Support for PPP Overview pppd startup for IPv6 through an automated script, namely, /etc/ppp/autostart.ex. Dial-in configuration through a login script, namely, /etc/ppp/login.ex. Support for filtering IPv4 packets with an IPv6 datagram. New Command-Line Options Table 5-1 Table 5-1 lists the new command-line options added to the existing /usr/bin/pppd daemon. New Command-Line Options Daemon Management Options Option exec6 exec-cmd router6 noipv4 Description Pass a script as an argument to this option. When the IPv6 interface comes up, it invokes the rtradvd daemon. Specify this option for clearing, the private flag, on the IPv6 interface being configured by pppd. This option clears the private flag on the interface where router advertisement messages will be sent. Specify this option to disable IPCP (NCP for IPv4 over PPP) negotiation. No IPv4 datagram will pass through the link. You need to specify this option to establish a point-to-point link for IPv6 packets, that is, to negotiate only IPV6CP messages. Note: To look up the systems file, you must specify the IPv4 destination address, even if you wish to configure only IPv6 datagrams by choosing the ipv6 and noipv4 options on the command line. 54 Chapter 5
IPv6 Support for PPP Overview Table 5-1 New Command-Line Options (Continued) Option Description IP Options noipv6 ipv6 local-fid, remote-ifid need-ip6-ifid rfc2472-ifid-neg Specify this option to disable IPV6CP negotiation. No IPv6 datagram will pass through the link. Use this option when you do not want to negotiate IPV6CP messages sent by a peer pppd. Specify two 64-bit interface identifiers separated by a comma, the interface identifier of the local machine, and the expected interface identifier of the remote machine. Both the interface identifiers are optional. However, you need to specify the remote interface identifier, if the auto option is specified. Specify this option to obtain a 64-bit IPv6 interface identifier assigned by the peer for local use. Specify this option if you do not want to send NAK to an option for which you have already sent a NAK while processing the previous IPV6CP configuration options. NOTE All the existing IPv4 options work with IPv6 as well. IPv4 VJ compression and decompression options do not work with IPv6. For information on configuring and using PPP, see Installing and Administering PPP, available at http://www.docs.hp.com/hpux/netcom/index.html/#hp-ux%20lan. Neighbor Discovery for IPv6 rtradvd, the router advertisement daemon for IPv6, implements router functionality as specified in RFC 2461- Neighbor Discovery for IP Version 6. The daemon listens to router solicitation and sends router advertisement messages on demand and periodically, as described in the Chapter 5 55
IPv6 Support for PPP Overview RFC. These advertisements allow any listening host to configure their addresses and some other parameters automatically without manual intervention. They can also choose a default router based on these advertisements. For more information, see Enabling rtradvd section in HP-UX IPv6 Transport Administrator s Guide for TOUR 1.0, available on http://www.docs.hp.com/hpux/netcom/index.html. Using PPPv6 After you install the TOUR 1.0 software package, you need to complete the following steps to obtain an IP address using the stateless or stateful autoconfiguration method: If you are an rtradvd user, modify the sample script, /etc/ppp/exec6.rtradvd.ex, according to your configuration requirements for obtaining a global address. Run pppd on the command line with the exec6 option as follows: /usr/bin/pppd exec6 <name and path of the script> where <name and path of the script> is /etc/ppp/exec6.rtradvd.ex or a script of your choice. pppd executes this script, which invokes the IPv6 autoconfiguration daemons that assign an address to a PPP end-point. For more information on the rtradvd options specified in the sample script, type man 4 rtradvd.conf or type man 1m rtradvd at the HP-UX command prompt. 56 Chapter 5
Index A ac_cookie, 30 acname, 29 C client-intf-list, 39 swinstall, 22 T timeout, 30 D Discovery stage, 14 H host-unique, 35 I interface, 29 ipv4-address-pool, 30 ipv6-identifier-pool, 30 L local-ipv4-address, 30 local-ipv6-identifier, 30 LOG_DBG, 49 LOG_DEBUG, 28 LOG_ERROR, 28, 49 LOG_WARN, 28, 49 P PADI, 15 PADO, 15 PADR, 15 PADS, 15 PADT, 15 pppd-options, 31 pppoe, 23 pppoe.o, 23 pppoec, 33 pppoec.log, 46 pppoerd.log, 48 pppoesd, 28 pppoesd.log, 44 R retry_number, 30 S server-intf, 39 service, 29 Session stage, 14 1
Index 2
Index 3
Index 4
Index 5
Index 6
Index 7