Using `/etc/ppp/options.`ttyname on a Dial-out Machine

For a dial-out machine, you can create an /etc/ppp/options.ttyname file for the serial port with the modem, or elect not to use /etc/ppp/options.ttyname.

Note - Solaris PPP 4.0 does not require an /etc/ppp/options.ttyname file to work correctly. If the dial-out machine only has one serial line for PPP and requires few options, you can specify these options in another configuration file or on the command line.

`options.ttya.tmpl` Template File

The /etc/ppp/options.ttya.tmpl file contains helpful comments about the /etc/ppp/options.tty-name file. The template contains three common options for the /etc/ppp/options.tty-name file.

38400 
asyncmap 0xa0000 
:192.168.1.1

Option	Definition
`38400`	Use this baud rate for port ttya.
`asyncmap 0xa0000`	Assign the asyncmap value of 0xa0000 so that the local machine can communicate with broken peers.
:192.168.1.1	Assign the IP address 192.168.1.1 to all peers that are calling in over the link.

To use /etc/ppp/options.ttya.tmpl at your site, rename /etc/ppp/options.tmpl to /etc/ppp/options.ttya-name. Replace ttya-name with the name of the serial port with the modem. Then modify the file contents as needed by your site.

Where to Find Sample `/etc/ppp/options.`ttyname Files

Table 36-3 Examples of the /etc/ppp/options.ttyname File

Example `/etc/ppp/options.`ttyname	For Instructions
For a dial-out machine	"How to Define Communications Over the Serial Line"
For a dial-in server	"How to Define Communications Over the Serial Line (Dial-in Server)"

Configuring User-Specific Options

This section contains detailed information on setting up users on the dial-in server.

Configuring `$HOME/.ppprc` on a Dial-in Server

The $HOME/.ppprc file is intended for users who are configuring preferred PPP options. As administrator, you can also configure $HOME/.ppprc for users.

The options in $HOME/.ppprc are privileged only when the user who is invoking the file is privileged.

When a caller uses the pppd command to initiate a call, the .ppprc file is the second file that is checked by the pppd daemon.

See "Setting Up Users of the Dial-in Server" for instructions on setting up $HOME/.ppprc on the dial-in server.

Configuring `$HOME/.ppprc` on a Dial-out Machine

Note - The $HOME/.ppprc is not needed on the dial-out machine for Solaris PPP 4.0 to work correctly.

You do not need to have a $HOME/.ppprc on a dial-out machine, except for special circumstances. Create one or more .ppprc files if you do the following:

Allow multiple users with differing communications needs to call remote peers from the same machine. In such an instance, create individual .ppprc files in the home directories of each user who must dial out.
Need to specify options that control problems specific to your link, such as disabling Van Jacobson compression. See James Carlson's PPP Design, Implementation, and Debugging and the pppd(1M) man page for assistance in troubleshooting link problems.

Because the .ppprc file is most often used when configuring a dial-in server, refer to "How to Configure Users of the Dial-in Server" for configuration instructions for .ppprc.

Specifying Information for Communicating With the Dial-in Server

To communicate with a dial-in server, you need to gather information about the server and edit a few files. Most significantly, you must configure the communications requirements of all dial-in servers that the dial-out machine needs to call. You can specify options about a dial-in server, such as an ISP phone number, in the /etc/ppp/options.ttyname file. However, the optimum place to configure peer information is in /etc/ppp/peers/peer-name files.

`/etc/ppp/peers/`peer-name File

Note - The /etc/ppp/peers/peer-name file is not needed on the dial-out machine for Solaris PPP 4.0 to work correctly.

Use the /etc/ppp/peers/peer-name file to provide information for communicating with a particular peer. /etc/ppp/peers/peer-name allows ordinary users to invoke preselected privileged options that they are not allowed to set.

For example, a non-privileged user cannot override the noauth option if it is specified in the /etc/ppp/peers/peer-name file. Suppose the user wants to set up a link to peerB, which does not provide authentication credentials. As superuser, you can create a /etc/ppp/peers/peerB file that includes the noauth option. noauth indicates that the local machine does not authenticate calls from peerB.

The pppd daemon reads /etc/ppp/peers/peer-name when it encounters the following option:
call peer-name

You can create a /etc/ppp/peers/peer-name file for each target peer with which the dial-out machine needs to communicate. This practice is particularly convenient for permitting ordinary users to invoke special dial-out links without needing root privileges.

Typical options that you specify in /etc/ppp/peers/peer-name include the following:

user user_name

Supply user_name to the dial-in server, as the login name of the dial-out machine, when authenticating with PAP or CHAP.
remotename peer-name

Use peer-name as the name of the dial-in machine. remotename is used in conjunction with PAP or CHAP authentication, when scanning the /etc/ppp/pap-secrets or /etc/ppp/chap-secrets files.
connect "chat chat_script..."

Open communication to the dial-in server, by using the instructions in the chat script.
noauth

Do not authenticate the peer peer-name when initiating communications.
noipdefault

Set the initial IP address that is used in negotiating with the peer to 0.0.0.0. Use noipdefault when setting up a link to most ISPs to help facilitate IPCP negotiation between the peers.
defaultroute

Install a default IPv4 route when IP is established on the link.

See the pppd(1M) ) man page for more options that might apply to a specific target peer.

`/etc/ppp/peers/myisp.tmpl` Template File

The /etc/ppp/peers/myisp.tmpl file contains helpful comments about the /etc/ppp/peers/peer-name file. The template concludes with common options such as you would 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.


36. Solaris PPP 4.0 Reference Using PPP Options in Files and on the Command Line `/etc/ppp/options`.ttynameConfiguration File Using `/etc/ppp/options.`ttynameon a Dial-in Server

Using /etc/ppp/options.ttyname on a Dial-out Machine

options.ttya.tmpl Template File

Where to Find Sample /etc/ppp/options.ttyname Files

Configuring User-Specific Options

Configuring $HOME/.ppprc on a Dial-in Server

Configuring $HOME/.ppprc on a Dial-out Machine