Remote Computer-to-Network Configuration

The remote computer-to-network is the most common asynchronous PPP configuration. Use it to configure machines in remote offices or users' homes that dial out over a point-to-point PPP link to a dial-in server on a network.

• Network interface - This point-to-point link uses the ipdptpn virtual network interface. You need to specify it in the configuration files of all remote machines that dial out to a network.

• Addressing method - The configuration file must include the host names or IP addresses of the machines that communicate over the link. For remote hosts, you should use existing host names and IP addresses. Refer to "Determining IP Addressing for Your PPP Link" for complete details.

• Name service - NIS and NIS+ name services are not recommended for remote hosts. These services generate a great deal of network traffic, often at unexpected times. The DNS name service is more efficient for this type of configuration. You might want to set up DNS, as described in Solaris Naming Administration Guide, on each remote host. If you don't use DNS, PPP accesses the /etc/inet/hosts file on the remote machine.

• Dial-in and dial-out support - Remote hosts usually implement dial-out communications only. They do not allow other machines to dial in to them directly. Therefore, you must update the UUCP files on each to support dial-out communications, as explained in "Editing UUCP Databases".

• Routing requirements - Because RIP is part of the Solaris TCP/IP protocol stack, it runs by default on remote hosts. Turn off RIP to improve performance, if necessary, and instead use static routing. See "Routing Protocols" and "Turning Off RIP" for details.