|
|
Use the Network Configuration Manager or slconf to configure SLIP links after you configure the SLIP stack.
If you are using slconf to configure SLIP links, enter /usr/bin/slconf at the shell prompt and begin with step 4.
To add a SLIP link:
If you want to add the SLIP drivers to the kernel without performing any link configuration, select the manual link option, and then skip to step 8.
To enter advanced configuration options for either the dynamic outgoing or dedicated links such as compression, authentication, and filtering options, select the Advanced Options button.
If you configured a dynamic incoming link, enter the SLIP login account's user ID and password at the prompts.
After your choose No, a message appears indicating that the link was configured successfully.
The links you configured are available the next time you reboot your system or restart TCP/IP.
When you use the Network Configuration Manager or slconf to configure a dynamic incoming link, you must provide the following information:
You must create the login shell script you enter in the Network Configuration Manager. It should contain an slattach line similar to the following:
/etc/slattach /dev/tty1a 10.0.118.6 10.0.246.12 255.255.0.0 38400&In this example, SLIP accepts incoming requests from the system 10.0.246.12 via the interface 10.0.118.6 on a modem connected to /dev/tty1a. The baud rate in this example is 38400. For more information on slattach command line syntax, see slattach(ADMN).
When you use the Network Configuration Manager or slconf to configure a dynamic outgoing link, you must provide the following information:
If both a local name and an IP address are entered, the IP address takes precedence.
If both a destination name and an IP address are entered, the IP address takes precedence.
Link configuration information is stored in a line in /etc/tcp which calls the slattach program. Here is a sample slattach entry, broken over two lines for ease of reading:
/etc/slattach -d slipsite 10.0.118.55 10.0.246.77\ 255.255.255.0&
This link connects to a UUCP host named slipsite. The remote system's IP address is 10.0.246.77, the local address is 10.0.118.55. The netmask is specified as 255.255.255.0.
See ``Advanced SLIP configuration'' for more information about using the Advanced Options or directly editing the slattach entry in /etc/tcp to configure SLIP.
Dynamic outgoing SLIP links use the UUCP facilities as the physical media over which the link is made. These media usually consist of modems at the remote and local hosts, and the telephone lines connecting the modems.
After you configure a dynamic outgoing SLIP link with the Network Configuration Manager, you must edit the UUCP Systems and Devices files to define information about the remote site. You can also use uuinstall(ADM) to perform this task.
A dynamic outgoing SLIP link, defined in /etc/tcp, must specify the UUCP name for the remote site (uucp_sitename) as the argument to the -d option. (slattach will fail if you specify -d but not uucp_sitename. If you do not specify -d, slattach erroneously tries to configure a dedicated link instead of a dynamic outgoing link.) uucp_sitename must exist as a ``sitename'', listed in the UUCP file /usr/lib/uucp/Systems, which identifies the remote host. This forms the link between SLIP and UUCP.
An entry for uucp_sitename may be entered in the /usr/lib/uucp/Systems file (see Systems(F)) by manually editing this file or by running uuinstall(ADM), which prompts you for the necessary information. The login name and password associated with the account must match those defined by the SLIP configuration at the remote end.
SLIP's use of UUCP in establishing a connection requires that UUCP can be used alone to connect the local and remote hosts without using SLIP. When a dynamic outgoing SLIP link is brought up, SLIP requests a UUCP link to the remote host. UUCP must be able to establish a UUCP link using only UUCP information, such as that found in the files /usr/lib/uucp/Systems, /usr/lib/uucp/Devices, and /usr/lib/uucp/Dialers. During UUCP link establishment, characteristics such as baud rate and flow control are determined by the UUCP information and not by the SLIP link configuration. Once UUCP has established a link, it informs SLIP of the tty to use for that link. At this point SLIP takes over the link. Therefore, it is best to test a UUCP link between the local and remote hosts before trying to run SLIP over the link.
For complete information on configuring a UUCP link, see ``Connecting to other computers with UUCP''.
When you use the Network Configuration Manager or slconf to configure a dedicated link, you must provide the following information:
If both a local name and an IP address are entered, the IP address takes precedence.
If both a destination name and an IP address are entered, the IP address takes precedence.
Link configuration information is stored in a line in /etc/tcp which calls the slattach program. Here is a sample slattach entry, broken over two lines for ease of reading:
/etc/slattach /dev/tty1a 10.0.118.55 10.0.246.77\ 255.255.255.0 9600&This link uses tty1a at 9600 baud. It communicates with a remote system, 10.0.246.77, via the interface 10.0.118.55. The netmask is specified as 255.255.255.0.
See ``Advanced SLIP configuration'' for more information about using the Advanced Options or directly editing the slattach entry in /etc/tcp to configure SLIP.