[Top] [Prev] [Next]


ip - TCP, UDP network protocols over IP


bind -a '#I' /net


The IP device provides the interface for protocols that run over IP. TCP and UDP provide the standard internet protocols for reliable stream and unreliable datagram communication.

Each of the protocols is served by the IP device, which represents each connection by a set of device files. The top level directory of each protocol contains a clone file and subdirectories numbered from 0 to the number of connections configured for this protocol.

Opening the clone file reserves a connection. The file descriptor returned from the open will point to the control file, ctl, of the newly allocated connection.


Reading the ctl file returns a text string representing the number of the connection. Connections may be used either to listen for incoming calls or to initiate calls to other machines.

A connection is controlled by writing text strings to the associated ctl file.


After a connection has been established data may be read from and written to the data file. For the datagram service UDP, a read of less than the length of a datagram will cause the entire datagram to be consumed. Each write to the data file will send a single datagram on the network. The TCP protocol provides a stream connection that does not preserve read/write boundaries.

Prior to sending data, remote and local addresses must be set for the connection. For outgoing calls the local port number will be allocated randomly if none is set. Addresses are set by writing control messages to the ctl file of the connection. The connection is not established until the data file is opened. For TCP, the process will block until the remote host has acknowledged the connection. UDP opens always succeed.

The following control messages are supported:

"connect ipaddress! port [!r]"

Set the remote IP address and port number for the connection. If the r flag is supplied and no local address has been specified the system will allocate a restricted port number (less than 1024) for the connection to allow communication with Unix machines' login and exec services.


Terminate the connection.

"announce X"

X is a decimal port number or *. Set the local port number to X and accept calls to X. If X is *, accept calls for any port that no process has explicitly announced. The local IP address cannot be set. The announce attempt fails if the connection is already announced or connected.

"bind X"

X is a decimal port number or *. Set the local port number to X. This exists to support emulation of BSD sockets and is not used otherwise.

"header" (UDP only)

Skip headers on reads and writes.

Port numbers must be in the range 1 to 32767. If a local port has not been announced prior to a connect a local port number will be allocated automatically. Local ports are allocated from 5000 up.

Several files report the status of a connection.

The remote file provides the IP address and port number for the remote side of the connection.


The local files contain the IP address and port number for the local side of the connection.


The status file contains protocol-dependent information to help debug network connections.


A process may accept incoming connections by opening the listen file. The open will block until a new connection request arrives. Then open will return an open file descriptor that points to the control file of the newly accepted connection. This procedure will accept all calls for the given protocol.

In general it should not be necessary to use the file system interface to the networks. The dial, announce, and listen functions in the sys module perform the necessary I/O to establish and manipulate network connections.

See Also


[Top] [Prev] [Next]

Copyright © 1996,Lucent Technologies, Inc. All rights reserved.