The /etc/ppp/peers/myisp.tmpl file contains helpful comments about the /etc/ppp/peers/peer-name file. The template concludes with common options that you might use for an /etc/ppp/peers/peer-name file:
connect "/usr/bin/chat -f /etc/ppp/myisp-chat" user myname remotename myisp noauth noipdefault defaultroute updetach noccp |
Option |
Definition |
---|---|
connect "/usr/bin/chat -f /etc/ppp/myisp-chat" |
Call the peer by using the chat script /etc/ppp/myisp-chat. |
user myname |
Use this account name for the local machine. myname is the name for this machine in the peer's /etc/ppp/pap-secrets file. |
remotename myisp |
Recognize myisp as the name of the peer in the local machine's /etc/ppp/pap-secrets file. |
noauth |
Do not require calling peers to provide authentication credentials. |
noipdefault |
Do not use a default IP address for the local machine. |
defaultroute |
Use the default route that is assigned to the local machine. |
updetach |
Log errors in the PPP log files, rather than on the standard output. |
noccp |
Do not use CCP compression. |
To use /etc/ppp/peers/myisp.tmpl at your site, rename /etc/ppp/peers/myisp.tmpl to /etc/ppp/peers/.peer-name. Replace peer-name with the name of the peer to be called. Then modify the file contents as needed by your site.