Planning for Remote Network Configuration

After the initial configuration, you can place IP addresses in remote networks under DHCP management. However, because the system files are not local to the server, DHCP Manager and dhcpconfig cannot look up information to provide default values, so you must provide the information. Before you attempt to configure a remote network, be sure you know the following information:

• Remote network's IP address.

• Subnet mask of the remote network – This can be obtained from the netmasks table in the name service. If the network uses local files, look in /etc/netmasks on a system in the network. If the network uses NIS+, use the command niscat netmasks.org_dir. If the network uses NIS, use the command ypcat -k netmasks.byaddr. Make sure the netmasks table contains all the topology information for all the subnets you want to manage.

• Network type – Do the clients connect to the network through a local area network (LAN) connection or point-to-point protocol (PPP)?

• Routing – Can the clients use router discovery? If not, you must determine the IP address of a router they can use.

• NIS domain and NIS servers, if applicable.

• NIS+ domain and NIS+ servers, if applicable.

See Adding DHCP Networks for the procedure for adding DHCP networks.