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

p
pppd(1) pppd(1)
(echo -n ’ backbonesystem’) >/dev/console
pppd oursystem:backbonesystem ipv6 <local-ifid>,<remote-ifid> auto up
<echo -n ’ backbonesystem’) >/dev/console
pppd oursystem:theirsystem auto noipv6 idle 120
(echo -n ’ theirsystem’) >/dev/console
pppd oursystem:theirsystem ipv6 <local-ifid>,<remote-ifid> auto idle 120
<echo -n ’ theirsystem’> >/dev/console
To allow a PPP implementation running on "theirsystem" to dial into "oursystem", insert the following into
/etc/passwd on "oursystem":
Pthem:?:105:20:Their PPP:/etc/ppp:/etc/ppp/Login
where group 20 is the gid of the ppp group which owns
/usr/etc/pppd
, and /etc/ppp/Login is an
executable shell script that looks something like
#!/bin/sh
PATH=/usr/bin:/usr/etc:/bin
mesg n
stty -tostop
exec pppd noipv6 ‘hostname‘:
To enable IPV6CP negotiation, insert the following:
#!/bin/sh
PATH=/usr/bin:/usr/etc:/bin
mesg n
stty -tostop
exec pppd ipv6 <local-ifid>,<remote-ifid> ‘hostname‘:
RECOMMENDATIONS
Use host names when running
/etc/ppp/Autostart
from /sbin/rc2.d/S522ppp only if they
are known locally. If a PPP connection to a DNS server would be required to resolve a host name, use its
literal IP address instead.
EXTERNAL INFLUENCES
Environment Variables
The environment variable
PPPHOME, if present, specifies the directory in which pppd looks for its
configuration files (
Filter and Auth for all connections, along with Systems,
Devices, and
Dialers if the connection is "outbound"). You can specify
PPPHOME either in the Autostart script or
in an incoming connection’s
Login
script. If PPPHOME is not present, pppd will expect to find its
configuration files in
/etc/ppp/* .
SECURITY CONCERNS
pppd should be mode 4750, owned by root, and executable only by the members of the group containing all
the incoming PPP login "users".
AUTHOR
pppd was developed by the Progressive Systems.
SEE ALSO
ppp.Auth(4), ppp.Devices(4), ppp.Dialers(4), ppp.Filter(4), ppp.Keys(4), ppp.Systems(4).
RFC 1548, RFC 1549, RFC 1332, RFC 1333, RFC 1334, RFC 1172, RFC 1144, RFC 1055.
ds.internic.net:/internet-drafts/draft-ietf-pppext-compression-04.txt.
STANDARDS CONFORMANCE
HP PPP implements the IETF Proposed Standard Point-to-Point Protocol and many of its options and
extensions, in conformance with RFCs 1548, 1549, 1332, 1333, 1334, and 1144. It can be configured to be
conformant with earlier specifications of the PPP protocol, as described in RFCs 1134, 1171, and 1172. It
implements the nonstandard SLIP protocol as described in RFCs 1055 and 1144.
HP-UX 11i Version 2: December 2007 Update − 7 − Hewlett-Packard Company 161