HP-UX Reference (11i v3 07/02) - 1 User Commands N-Z (vol 2)

p
pppd(1) pppd(1)
rfc2472-ifid-neg
Do not send nak (negative acknowledgement) if the IPV6CP interface identifier
option has already been sent negative acknowledgements during previous
replies.
Authentication Options
requireauth Require either PAP or CHAP authentication.
requirechap Require CHAP authentication as described in RFC 1334.
requiremschap
Require MS-CHAP authentication.
requirepap Require PAP authentication.
rechap interval Demand that the peer re-authenticate itself (using CHAP) every interval
seconds. If the peer fails the new challenge, the link is terminated.
name identifier Provide the identifier used during PAP or CHAP negotiation. This option is
necessary if the PPP peer requires authentication. The default value is the value
returned by the gethostname(2) system call or the hostname(1) command.
MicroSoft Compatibility Options
ms-dns address Set the MS DNS address to provide to the peer. First occurrence of this option
on the command line sets the primary address; the second occurrence sets the
secondary address.
ms-nbns address Set the MS NBNS address to provide to the peer. First occurrence of this option
on the command line sets the primary address; the second occurrence sets the
secondary address.
Encryption Options
Encryption is not currently available in software exported from the USA. However, customer may contact
[e-mail] to obtain encryption functionality.
Link Compression Options
compress Offer all supported link compression types (currently only Predictor-1) when
negotiating. The default is to propose and accept no link compression type.
compress-pred1 Accept any supported compression type, but prefer Predictor type 1 compression.
nopred1 Never use Predictor-1 compression.
LOG FILE
Status information is recorded in the log file (/var/adm/pppd.log
by default) by each copy of pppd
running on a single machine. Each line in the file consists of a message preceded by the date, the time, and
the process ID number of the daemon writing the message. The quantity and verbosity of messages are
controlled with the debug option and with the log filter (see ppp.Filter(4)).
Each packet that brings up the link (at debug level 1 or more), each packet that matches the
log filter (at
any debug level), or any packet when the debug level is 7 or more writes a one-line description of the
packet to the log file. The first item of the message is the protocol (
tcp, udp, icmp, or a numeric protocol
value).
For ICMP packets, the keyword
icmp is followed by the ICMP message type and sub code, separated by
slashes. After the protocol comes an IP address and optionally a TCP or UDP port number, followed by an
arrow indicating whether the packet was sent (->) or received (<-), followed by another address and port
number, followed by the length of the packet in bytes before VJ TCP header compression, followed by zero
or more keywords.
For transmitted packets, the first IP address is the source address, while for received packets, the first IP
address is the destination address. Well known TCP and UDP port numbers will be replaced by the name
returned by the getservbyport() library function. The keywords and their meanings are:
frag The packet is a middle or later part of a fragmented IP frame.
syn The packet has the TCP SYN bit set.
fin The packet has the TCP FIN bit set.
bringup The transmitted packet matches the bringup filter and is bringing up the link.
134 Hewlett-Packard Company − 5 − HP-UX 11i Version 3: February 2007