You use the /etc/ppp/options file to define global options for all PPP communications on the local machine. /etc/ppp/options is a privileged file. /etc/ppp/options should be owned by root, although pppd does not enforce this rule. Options that you define in /etc/ppp/options have precedence over definitions of the same options in all other files and the command line.
Typical options that you might use in /etc/ppp/options include the following:
lock – Enables UUCP-style file locking
noauth – Indicates that the machine does not authenticate callers
You must create /etc/ppp/options by using a text editor, as shown in How to Define Communications Over the Serial Line. If a machine does not require global options, you can create an empty /etc/ppp/options file. Then, both root and regular users can run pppd on the local machine.
The /etc/ppp/options.tmpl contains helpful comments about the /etc/ppp/options file plus three common options for the global /etc/ppp/options file.
lock nodefaultroute noproxyarp
|
To use /etc/ppp/options.tmpl as the global options file, rename /etc/ppp/options.tmpl to /etc/ppp/options. Then, modify the file contents as needed by your site.
To find examples of the /etc/ppp/options file, refer to the following:
For a dial-out machine, see How to Define Communications Over the Serial Line.
For a dial-in server, see How to Define Communications Over the Serial Line (Dial-in Server).
For PAP support on a dial-in server, see How to Add PAP Support to the PPP Configuration Files (Dial-in Server).
For PAP support on a dial-out machine, see How to Add PAP Support to the PPP Configuration Files (Dial-out Machine).
For CHAP support on a dial-in server, see How to Add CHAP Support to the PPP Configuration Files (Dial-in Server).