Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ tcpip.params(4M) — DG/UX 5.4.2A

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

hostname(1C)

hostid(1C)

ifconfig(1M)

route(1M)

hosts(4)



tcpip.params(4M)                TCP/IP 5.4.2                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 ifconfig(1M) command is run by the rc.tcpipport script to start
       and stop network interfaces.  Each line between the START_INTERFACE
       and STOP_INTERFACE delimeters 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.  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.

                             All network interfaces require a value for
                             HOSTNAME.

       DEVICE                The name of the device to be configured.



Licensed material--property of copyright holder(s)                         1




tcpip.params(4M)                TCP/IP 5.4.2                tcpip.params(4M)


                             For Ethernet(for example dgen0, cien0), token
                             ring(for example vitr0), FDDI (for example,
                             pefn0) and loopback(loop0) network interfaces,
                             the device MUST have a corresponding entry in
                             the /dev directory.  When you add, modify, or
                             delete the device name for Ethernet, token
                             ring, FDDI, or loopback network interfaces, you
                             must reconfigure the kernel.

                             For IXE interfaces, there is only one entry in
                             the /dev directory, namely /dev/ixe.  This is
                             because /dev/ixe is a cloneable device.  When
                             you bring up TCP/IP, the system creates a
                             symbolic link in the /dev directory (for
                             example, /dev/ixe1) to the corresponding IXE
                             template file to preserve the mapping between
                             instances of the ixe device and 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, the ifconfig command uses the default
                             netmask which prevents subnetting.

                             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.

       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



Licensed material--property of copyright holder(s)                         2




tcpip.params(4M)                TCP/IP 5.4.2                tcpip.params(4M)


                             filename is not a full pathname; template files
                             are located in the /usr/opt/x25/etc/template
                             directory.

       For example, the lines below define the following network interface
       entries:
             the name localhost using device loop0,
             the name hostb using device hken0 on the subnetted network
       128.222.8,
             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.

             STARTINTERFACE
             HOSTNAME=localhost DEVICE=loop0
             HOSTNAME=hostb DEVICE=hken0 NETMASK=0xffffff00 \
       BROADCAST=128.222.8.255 LINKPROTO=ether
             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
             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.




Licensed material--property of copyright holder(s)                         3




tcpip.params(4M)                TCP/IP 5.4.2                tcpip.params(4M)


       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.

       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 ifconfig 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.




Licensed material--property of copyright holder(s)                         4




tcpip.params(4M)                TCP/IP 5.4.2                tcpip.params(4M)


                             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

SEE ALSO
       hostname(1C), hostid(1C), ifconfig(1M), route(1M), hosts(4), Managing
       TCP/IP on the DG/UX System.








































Licensed material--property of copyright holder(s)                         5


Typewritten Software • bear@typewritten.org • Edmonds, WA 98026