DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Configuring the Point-to-Point Protocol (PPP)

PPP configuration files

SCO PPP uses the following configuration files directly. When the PPP STREAMS stack is installed, a file with only headers is created for each of these:


/etc/ppphosts
This file holds the information that is needed to define each PPP endpoint configuration. Each endpoint is defined as a separate entry in the file. The PPP daemon reads this file as part of its startup procedure. The daemon can also be signaled to reread this file (see ``Signaling the PPP daemon''). This file can be edited (see the manual reference page ppphosts(SFF)) or updated using the PPP Manager as described in ``Configuring PPP''.

/etc/pppauth (optional)
This file is required only if authentication will be required for establishing any PPP links. Such a requirement may be initiated by either the local host or the remote host. This file holds the data required for authentication and is read by the PPP daemon only if authentication is required. See ``PPP authentication methods'' and the pppauth(SFF) manual page for more information on authentication and the /etc/pppauth file. The PPP daemon reads this file during PPP negotiation if authentication is required for the PPP link being negotiated. This file can be edited (see the pppauth(SFF) manual page) or updated using the PPP Manager as described in ``Configuring PPP''.

/etc/pppfilter (optional)
This is the file for PPP packet filter specifications. This file is required only if packet filtering will be required for one or more PPP links. Packet filtering may be specified on a per-endpoint basis. The PPP daemon reads the packet filter file as part of its startup procedure. The daemon can also be signaled to reread this file (see ``Signaling the PPP daemon''). See ``PPP packet filtering'' and the packetfilter(SFF) manual page for more information on packet filtering and the /etc/pppfilter file. This file must be edited.

/etc/ppppool (optional)
This file is required only if IP addresses for incoming links to remote access endpoints will be assigned from a pool when the link is brought up. See ``Configuring an endpoint for remote access'' for more information on this option and the ppppool(SFF) manual page for the file format. This file can be configured from the PPP Manager.

/etc/pppstack (optional)
This file defines the serial driver and associated STREAMS module(s) for a third-party smart serial card that is capable of performing the packetization and framing required by PPP. See ``Configuring PPP asynchronous serial driver support'' for more information on this option and the pppstack(SFF) manual page for the file format. This file must be edited.
SCO PPP uses the following configuration files indirectly:

/etc/hosts
Any remote IP address to which a PPP link will be established can be listed here with any host names by which a user may specify the remote host. If the Domain Name Service (DNS) is being used on the local host, then host name to IP address mapping is done by that system instead of using this file.

/usr/lib/uucp/Systems, /usr/lib/uucp/Devices, /usr/lib/uucp/Dialers
These three files are UUCP systems files. Outgoing PPP links from automatic and manual dialup endpoints require entries in these files for PPP to be able to use UUCP facilities for these links. This dependency is described in ``How UUCP is configured for outgoing dialup''.

Next topic: Signaling the PPP daemon
Previous topic: PPP negotiation

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003