tcpip.params(4M) TCP/IP R4.11 tcpip.params(4M)
NAME
tcpip.params - TCP/IP network parameter database for rc scripts
DESCRIPTION
The tcpip.params(4M) file contains parameters for various commands
invoked by the rc scripts to initialize the network.
The hostname(1C) command is run by the rc.tcpipport script. The
following parameter is used by the hostname command:
hostnameARG The name you assign to the local host. For
example, a host named hostb could be
represented as follows:
hostnameARG="hostb"
The hostidARG value must match the hostidARG
value in the hosts database.
The hostid(1C) command is run by the rc.tcpipport script. The
following parameter is used by the hostid command:
hostidARG The ID is a hexadecimal number formed by the
concatenation of the hexadecimal representation
of the fields of the local host's internet
address. For example, an internet address
85.0.0.31 would be represented by 1) converting
each field to hexadecimal (which is
0x55.0x00.0x00.0x1f) and 2) concatenating these
four fields (which is 0x5500001f). Therefore,
hostidARG="0x5500001f"
The admipinterface(1M) command is run by the rc.tcpipport script to
start and stop the network interfaces. Each line between the
START_INTERFACE and STOP_INTERFACE delimiters contains a network
interface entry. Each line contains a subset of the following
parameters.
Parameter values for HOSTNAME, NETMASK, and BROADCAST can be
expressed in Internet address dot notation or hexadecimal format. In
addition, HOSTNAME can be expressed as a symbolic name. Any symbolic
name used must be defined in the local /etc/hosts file for the name
to be resolved correctly except for SLIP interfaces whose hostname
must be defined in /etc/slipdialinfo. The use of symbolic name
references is recommended.
HOSTNAME The name that associates an Internet address
with the network interface to be configured.
If a symbolic name is entered, the name must
have an entry in the local /etc/hosts file or,
for SLIP interfaces, in the local
/etc/slipdialinfo file.
All network interfaces require a value for
HOSTNAME.
DEVICE The name of the device to be configured.
For Ethernet(for example dgen0, cien0), token
ring(for example vitr0), and FDDI (for example,
pefn0) the device MUST have a corresponding
entry in the /dev directory. When you add,
modify, or delete the device name for Ethernet,
token ring, or FDDI network interfaces, you may
need to reconfigure the kernel.
For IXE and loopback interfaces, there is only
one entry in the /dev directory. These are
/dev/ixe and /dev/loop respectively. This is
because /dev/ixe and /dev/loop can be cloned.
Note that TCP/IP requires the devices entered
in this field to have a unit number.
Therefore, to be valid for this field IXE and
loopback devices must be of the form: (ixe0,
ixe1, etc.) and (loop0, loop1, etc.).
Admipinterface will create an instance of the
clonable device using this name.
Also, when bringing up TCP/IP, the system
creates a symbolic link in the /dev directory
(for example /dev/ixe1) to the corresponding
IXE template files to preserve the mapping
between instances of the ixe device and the
template files.
All network interfaces require a value for
DEVICE.
NETMASK The network(subnet) mask assigned to the
configured network interface. If no value is
entered, admipinterface uses the default
netmask which prevents subnetting.
SLIP interfaces do not use this field. All
other network interfaces on subnetted networks
require a value for NETMASK.
BROADCAST The broadcast Internet address assigned to the
configured network interface. The network
portion of the broadcast address must be the
same as the network portion of the interface's
Internet address. The host portion should be
all ones (BSD 4.3 compatible) or all zeros (BSD
4.2 compatible).
Ethernet and token ring network interfaces
require a value for BROADCAST.
LINKPROTO The data link level protocol to be employed by
the configured network interface.
Ethernet network interfaces require a value for
LINKPROTO; specify the value ether unless you
intend to use 802.3.
SLIP network interfaces require a value of slip
for LINKPROTO.
TEMPLATE The IXE template file associated with the
network interface.
IXE network interfaces require a value for
TEMPLATE. The template filename is two to
eleven characters in length. The template
filename is not a full pathname; template files
are located in the /usr/opt/x25/etc/template
directory.
BAUD The baud rate for SLIP interfaces.
This is a required field for SLIP interfaces.
BAUD may be one of the following: 300, 1200,
2400, 4800, 9600, or 19200.
GROUP The name of the group of interfaces to which
this interface belongs. This provides for
management of a group of interfaces as opposed
to all interfaces or an individual interface.
If GROUP is not specified for an interface's
entry then the interface is assumed to belong
to the default group: default. The default
group is the group of interfaces started by
rc.tcpipport at system initialization.
INTERFACE The interface name for the interface.
By default, the interface name is the same as
the device name, except for interfaces with a
LINKPROTO of "802.3" or "slip". A link
protocol of "802.3" defaults the interface name
to the device name prefixed with "snap_". A
link protocol of "slip" indicates that the
interface name will be what slipd(1C) assigns
(slip0, slip1, etc.).
The interface name serves as the identifier for
the interface when using commands such as
netstat(1M) and ifconfig(1M).
For example, the lines below define the following network interface
entries:
the name localhost using device loop0 with interface name
myloop0,
the name hostb using device hken0 on the subnetted network
128.222.8 belonging to group failover,
the name hostb-alt using device hken1 on the subnetted network
128.222.3,
the name hostb-ixe using device ixe0 with the template file
ixefile, and
the name hostb-ring using device vitr0 on the subnetted network
128.222.5.
the name hostb-slip using device tty00 with a baud rate of
19200.
STARTINTERFACE
HOSTNAME=localhost DEVICE=loop0 INTERFACE=myloop0
HOSTNAME=hostb DEVICE=hken0 NETMASK=0xffffff00 \
BROADCAST=128.222.8.255 LINKPROTO=ether GROUP=failover
HOSTNAME=hostb-alt DEVICE=hken1 NETMASK=0xffffff00 \
BROADCAST=128.222.3.255 LINKPROTO=ether
HOSTNAME=hostb-ixe DEVICE=ixe0 TEMPLATE=ixefile
HOSTNAME=hostb-ring DEVICE=vitr0 NETMASK=0xffffff00 \
BROADCAST=128.222.5.255
HOSTNAME=hostb-slip DEVICE=tty00 LINKPROTO=slip BAUD=19200
STOPINTERFACE
The route(1M) command is run by the rc.tcpipport script to add and
delete routing table entries. Each line between the START_ROUTE and
STOP_ROUTE delimiters contains a routing table entry. Each line
contains a subset of the following parameters.
Parameter values for DESTINATION and GATEWAY can be expressed in
symbolic name, Internet address dot notation, or hexadecimal format.
Any symbolic name used must be defined in the local /etc/hosts or
/etc/networks file for the name to be resolved correctly. The use of
symbolic name references is recommended.
TYPE Indicates whether the route is to a host or a
network. The possible values are host and net.
If no value is specified, the route command
will default the type of route.
If the DESTINATION's Internet address host part
is all zeros, TYPE will default to net.
If the DESTINATION's Internet address host part
is NOT all zeros, TYPE will default to host.
Routes to subnetted networks require a value
for TYPE.
The use of the TYPE parameter is recommended
for all routes.
DESTINATION The hostname or network name of the destination
of the route.
A default route may be entered by specifying 0
or default.
All routes require a value for DESTINATION.
GATEWAY The hostname of the interface or gateway
through which traffic is routed to DESTINATION.
All routes require a value for GATEWAY.
METRIC Specifies either an interface route or a
gateway route.
A value of 0 specifies an interface route.
A value of 1 specifies a gateway route.
The default value for METRIC is 0.
All gateway routes require a value for METRIC.
The use of the METRIC parameter is recommended
for all routes.
RTT Specifies the round trip time used to
initialize a TCP connection. The value is
normally set the RTT to 1 second and adjust the
value as a particular route is used. Network
routes known to have a high delay may benefit
from having a larger RTT seed. Units are in
microseconds.
RTTVAR Specifies the variance in round trip time used
to initialize a TCP connection. The variance
is normally calculated by the operating system
and is used to adjust the round trip time.
Units are in microseconds.
SENDPIPE Specifies the size of the endpoint send buffer.
A large value may improve performance by
reducing the system latency when transmitting
large amounts of data. A small value will
reduce system resource consumption and may
reduce system resource shortfalls. Units are
in bytes.
RECVPIPE Specifies the size of the endpoint receive
buffer. A large value may improve performance
over high bandwidth, high delay networks. A
small value will reduce system resource
consumption and may reduce system resource
shortfalls. Units are in bytes.
SSTHRESH Specifies the value for the TCP congestion
threshold. This value is used to control TCP
behavior in the face of network congestion.
Normally the operating system maintains this
value based on network route usage. A large
value slows TCP recovery from lost packets and
may reduce further network congestion. A small
value allows TCP to quickly recover from lost
packets though it may increase network
congestion. Units are in bytes.
NETMASK Specifies the subnetwork mask associated with a
particular route. Normally the route command
will determine the network mask to use based on
the route type and the number of non-zero
bytes. However, if the network mask is not on
a byte boundary, the netmask must be specified.
The netmask may be specified in either hex or
internet dot format.
For example, the lines below define the following routing table
entries:
route traffic to host far-host through router,
route traffic to network far-net through router, and
route all other traffic through gateway.
START_ROUTE
TYPE=host DESTINATION=far-host GATEWAY=router METRIC=1
TYPE=net DESTINATION=far-net GATEWAY=router METRIC=1
TYPE=net DESTINATION=default GATEWAY=gateway METRIC=1
STOP_ROUTE
The hosts far-host, router, and gateway must have entries in the
local /etc/hosts file. The network far-net must have an entry in the
local /etc/networks file.
NOTE: When admipinterface configures a network interface, an
interface route to the directly connected network is added.
Therefore, interface routes are not required here.
The network servers are started and stopped by the rc.tcpipserv
script. Each line between the START_DAEMON and STOP_DAEMON
delimeters contains a network server entry. Each line contains the
DAEMONNAME parameter. If the server requires arguments, the line
contains the DAEMONARGS parameter.
DAEMONNAME Name of the executable server program located
in /usr/bin.
DAEMONARGS Arguments to pass the server when starting.
The arguments MUST be enclosed by double
quotes.
For example, the lines below define the following server entries:
the inetd server,
the snmpd server, and
the smtp server with argument -q30m.
STARTDAEMON
DAEMONNAME=inetd
DAEMONNAME=snmpd
DAEMONNAME=smtp DAEMONARGS="-q30m"
STOPDAEMON
The TCP/IP tunable parameters are reconfigured by the rc.tcpipport
script during system initialization. Each line between the
START_PARAMETER and STOP_PARAMETER delimeters contains a TCP/IP
tunable parameter entry. Each entry contains the PARAMETERNAME
field and a VALUE field.
The TCP/IP tunable parameters are managed via the admtcpipparams
command. The DG/UX operating system will initialize any parameters
that do not have entries in the PARAMETER section of tcpip.params to
their kernel defaults.
PARAMETERNAME Name of the TCP/IP tunable parameter to be
configured.
VALUE The new value to which the parameter is to be
configured.
For example, the lines below do the following:
set the Default Time-to-Live for IP packets to 255 hops,
set the switch to allow Forwarding of IP packets to on,
set the switch to allow Forwarding of Non-Local Source Routed
Packets to on,
set the Default TCP Keep-Alive Idle Time to 7200 seconds,
set the Base ARP Cache Timeout to 60 seconds.
STARTPARAMETER
PARAMETERNAME=ipttl VALUE=255
PARAMETERNAME=ipforwarding VALUE=on
PARAMETERNAME=ipsrcrtforward VALUE=on
PARAMETERNAME=tcpkeepalive VALUE=7200
PARAMETERNAME=arptimeout VALUE=60
STOPPARAMETER
SEE ALSO
hostname(1C), hostid(1C), admipinterface(1M), admtcpipparams(1M),
netinit(1M), ifconfig(1M), route(1M), hosts(4), slipdialinfo(4M),
Managing TCP/IP on the DG/UX System.
Licensed material--property of copyright holder(s)