The slattach command establishes a connection over a
pre-defined SLIP link. Each time slattach is executed,
a new slattach process is created
to control the additional SLIP link in use.
slattach creates a
network interface based on the local and remote IP addresses
that are passed to it as parameters.
Parameters to the slattach command define:
the serial communication path for a link by specifying either a tty device
or a UUCP site name.
an IP address for the local side of the communication path and an
IP address for the remote side of the communication path.
other IP and serial line attributes for the link.
Before slattach can create a SLIP link,
the SLIP protocol stack (a linked chain of software
modules and drivers) must have been configured
the kernel, and the system must have been rebooted.
Multiple applications (or multiple instances of the same
application) on a local host can communicate with the same remote host using
the same SLIP link.
Use of the same SLIP link requires only that the applications use
the same IP address to specify the remote host.
By using different IP addresses to specify the
same remote host, two applications can also use individual
SLIP links to the same host, provided a separate SLIP link
exists for each remote IP address.
Once a SLIP link is established, it remains active until:
Once the link has been removed, root should
remove the route associated with the SLIP link
from the routing table using the
root kills the associated slattach process to remove
the SLIP interface.
root marks the associated SLIP interface down
for example: ifconfig slip_interface down.
Marking an interface down using ifconfig does not remove the
link. Therefore, marking down the interface for a dynamic outgoing link
that uses a modem and telephone line does not hang up the line.
The costs of the line usage continue until the link is removed.
route delete destination_address gateway_address
Running slattach for users other than root
Removing the SLIP stack
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003