inet(4) inet(4)
NAME
inet - configuration file
SYNOPSIS
/etc/default/inet
DESCRIPTION
The /etc/default/inet file contains information which is analyzed or
defined at system startup or when working with the SIfmllan menu sys-
tem.
In the case of network interfaces, the /etc/default/inet file is
changed by calling sysadm(1M) and selecting Configuration. This menu
item is used to select the settings you want to change. The hash #
initiates a comment which extends to the end of the line. Programs
which check these files ignore comments. There are four types of vari-
able in this file:
- General variables
- Route-specific variables
- Network interface variables
- RPC, NFS, and NIS variables
General variables
RWHOD The values yes and no are valid for RWHOD.
If RWHOD is set to yes, the system status server
in.rhwod is automatically started at system startup.
For information on in.rhwod, see rwhod(1M). If no value
is specified, the value no is assumed.
STATE The values active and inactive are valid for STATE.
If the value of STATE is active, the host is mounted in
the network at system startup. If no value is specified
or if the variable does not appear in /etc/default/inet,
the value active is assumed at system startup.
TIMESYNC The values master, yes, and no are valid for TIMESYNC.
If the value of this variable is yes or master, the
time synchronization daemon in.timed is started at sys-
tem startup. If its value is master, the in.timed dae-
mon is started so that the host can function as a mas-
ter for network-wide time synchronization. If no value
is specified or if the variable does not appear in
/etc/default/inet, the value no is assumed at system
startup.
Page 1 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
NTP The values yes and no are valid for NTP. If its value
is yes, the time synchronization daemon in.xntpd(1M) is
started automatically at system startup.
Route-specific variables
GATED The values yes and no are valid for GATED.
If GATED is assigned the value yes and the
/usr/sbin/gated file exists, the routing daemon
/usr/sbin/gated is started and the GATEWAY variable
(see below) is ignored. If GATED is assigned the value
no or the /usr/sbin/gated does not exist, further rout-
ing operations depend on the value of the GATEWAY vari-
able.
GATEWAY The values yes, no, and passive are valid for GATEWAY.
If GATEWAY is assigned the value yes, the in.routed
daemon is automatically started without options at sys-
tem startup. If GATEWAY is assigned the value passive,
the routing daemon in.routed is started with the q
option, i.e. the host notes any route information
received over the connected networks, but does not send
any route information itself. If GATEWAY is not speci-
fied, the value no is assumed for GATEWAY and routed is
not started.
DEFAULTGATEWAY If the variable DEFAULTGATEWAY is assigned a value,
this value is set as the default route at system
startup, i.e. "route add default $DEFAULTGATEWAY 1" is
executed.
Example
Input:
DEFAULTGATEWAY="131.23.12.18"
At system startup, "route add default 131.23.12.18 1"
is executed [see route(1M)].
Network interface variables
The following variables are valid for the network interface:
ETHERFLAGS
OLDBROADCAST
INTERFACES
Page 2 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
The INTERFACES variable contains a description of all interfaces to be
configured. When the system is started up, an attempt is made to con-
figure the interface specified in each description. Configuration is
handled by ifconfig(1M). If an interface description in the INTERFACES
variable contains no broadcast address specification or no point-to-
point specification (i.e. ipdst), the value of the OLDBROADCAST vari-
able is evaluated for that interface. In the ETHERFLAGS variable,
default values may be specified for the network interface parameters.
These values are only used for an interface if they have not been
specified in the INTERFACES variable. If the INTERFACES variable has
not been assigned a value, the interfaces to be configured are deter-
mined automatically (see INTERFACES).
ETHERFLAGS This variable can be assigned values with the follow-
ing format:
[[-]trailers] [[-]arp] [metric n] [netmask mask]
[[-]multicast]
In this variable, default values may be specified for
the network interface parameters [see ifconfig(1M)].
If no value has been specified or if the variable does
not appear in /etc/default/inet, -trailers and
-multicast are taken as the default value, i.e. IP
trailer encapsulation is to be deactivated at Ethernet
level. The values trailers, multicast, and arp can be
redefined using the interface description in
INTERFACES. The remaining parameters from ifconfig
should be defined here only if they are not overwrit-
ten by any interface description in INTERFACES. Reli-
ant UNIX systems from Siemens Nixdorf only support
-trailers.
Examples
ETHERFLAGS=
Since ETHERFLAGS is assigned null values, the default
values -trailers and -multicast are used.
ETHERFLAGS="arp multicast"
The value means: arp and multicast. If, for example,
-multicast is also applicable to an interface, this
must be specified specifically in the INTERFACES vari-
able for that interface.
Page 3 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
OLDBROADCAST The values yes and no are valid for OLDBROADCAST.
The OLDBROADCAST variable defines the default format
for the broadcast address. This value can be overwrit-
ten by broadcast:[address] in the INTERFACES variable
for each interface. If no value has been specified or
if the variable does not appear in /etc/default/inet,
no is taken as the default value. The way in which the
broadcast address is transmitted via the interface is
determined by ifconfig at system startup. This is nor-
mally done as follows:
yes: ifconfig ... oldbroadcast ...
no: ifconfig ...
The broadcast address has the following format,
depending on the OLDBROADCAST variable and the network
class:
____________________________________________
| no | yes | Network class |
|_______________|__________|________________|
| x.255.255.255 | x.0.0.0 | Class A |
|_______________|__________|________________|
| x.y.255.255 | x.y.0.0 | Class B |
|_______________|__________|________________|
| x.y.z.255 | x.y.z.0 | Class C |
|_______________|__________|________________|
x, y, and z correspond to the parts of the network
address.
INTERFACES A list of interface parameters can be specified as the
value. The individual entries in the list must be
separated by blanks and/or tabs.
A host should not use more than one interface per net-
work, even if several interfaces can run on one host.
If the value of the variable does not exist or the
variable does not appear in the /etc/default/inet
file, the interfaces to be configured are automati-
cally determined using etherstat -e and uname -n.
etherstat -e determines the interface parameter
interface and uname -n determines the interface param-
eter address for the ifconfig call. Each interface
specification is in turn another parameter list. The
parameter groups for each interface must be separated
by commas. If the parameter list starts with slip, the
parameters that follow define a slip configuration.
The slip specification must have the following format:
slip:tty:[baudrate]:[mtu]:[ip-source]:[ip-dest]:[:options]
Page 4 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
Example:
EXTIF=slip:/dev/tty00:38400:578:orion:139.22.228.100
Default values:
baudrate 9600
mtu 256
ip-source hostname
hostname is defined using uname -n. If the parameter
list does not start with slip, the parameters must be
specified as for ifconfig. The parameters from
ifconfig can be used. If there is only one entry in
the parameter list, it must specify the interface
(interface parameter). The address (address parameter)
is determined automatically using uname -n. If the
parameter list contains more than one entry, the first
two entries are assumed to be interface and address.
parameter entries (trailers, arp, multicast etc.) in
the parameter list override the entries in ETHERFLAGS.
If more than one interface is to be configured, the interface parame-
ters must always include values for the interface parameters interface
and address.
Example of a network interface:
OLDBROADCAST=yes
STANDARDIF=lce0
EXTIF="lce1:193.51.47.11:netmask:0xffffff00:\
broadcast:193.51.47.255:multicast"
INTERFACES="$STANDARDIF $EXTIF"
In this case, the interfaces lce0 and lce1 are configured.
lce0:
"address": hostname (determined automatically)
"parameter":
-trailers because ETHERFLAGS is not yet defined
-multicast default
oldbroadcast because OLDBROADCAST=yes
lce1:
"address": 193.51.47.11
"parameter":
-trailers because ETHERFLAGS is not yet defined
-multicast because explicitly specified
broadcast 193.51.47.255 overrides the default value
implied by OLDBROADCAST=yes
If the hostname is danzig, the following commands are executed at
system startup:
Page 5 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
ifconfig lce0 danzig -trailers oldbroadcast up
ifconfig lce1 193.51.47.11 -trailers multicast\
netmask 0xfffff00 broadcast 193.51.47.255 up
NFS and NIS variables
DOMAIN The value specifies the name of the NIS domain which is
valid at system startup.
GLOBALPW This variable controls both whether and the way in
which the local files /etc/passwd, /etc/shadow and
/etc/group are updated with the contents of the associ-
ated maps of the NIS server.
The values new, auto, yes and no are valid for
GLOBALPW.
The local files are only updated with the contents of
the NIS map when the GLOBALPW variable is set to new,
auto or yes.
When GLOBALPW is set to new, the files are updated in
accordance with the entries in /etc/passwd.local and
/etc/group.local. This variant is also described else-
where as the "new" procedure for managing global users.
However, the "old" procedure, which is set with the
GLOBALPW values auto or yes, is still supported.
When GLOBALPW is set to auto, the files are updated in
accordance with the contents of the /var/yp/pwpattern
file.
When GLOBALPW is set to yes, only user names and their
IDs are updated. This setting is only useful when user
names and IDs have to be assigned uniquely throughout
the network, but global users should not automatically
have a valid ID on every NIS client.
YPMIXERCHECKDIR
The values nocheck, create, and default are valid.
YPMIXERCHECKDIR controls how an NIS client will handle
a global user's HOME directory entry in the local
/etc/passwd.
nocheck A global user's HOME directory pathname is
copied into the local /etc/passwd file
without checking whether the directory
exists on the client.
create If a global user's HOME directory does not
exist on the client, it is created and the
contents of /etc/skel are copied into it.
Page 6 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
default If a global user's HOME directory does not
exist on the client, the local /etc/passwd
entry will contain /tmp as the HOME direc-
tory.
YPMODE The values client, clientauto, server, master, and
inactive are valid for YPMODE.
This variable shows the NIS status of the host.
AUTOBINDING The values yes and no are valid for AUTOBINDING.
If the value of this variable is yes, the file
/var/yp/binding/domainname/ypservers of an NIS client
is automatically updated to match the list of current
NIS servers. The previous entries are ignored.
The current NIS servers are transferred to the
ypservers file as "plus-entries" [see ypservers(4)].
NFS variables
MASTERMAP Values are absolute pathnames or nomap. If the file
specified in the pathname does not exist, if the file
is not a regular file, or if MASTERMAP is not defined,
the same behavior is generated as for specification of
nomap.
file The pathname of a master map of the NFS auto-
mounter. If file is available, the automounter
is started by the NFS start script. file usu-
ally has the value /etc/auto.master.
nomap The NFS automounter is not started automati-
cally.
RPC variables
PORTMAPONLY The values yes and no are valid for PORTMAPONLY. Any
other value or the absence of a definition implies the
same behavior as for no.
yes RPC clients call the "Portmapper" utility of the
server (RPC program 100000, Version 2) instead of
the rpcbind utility (RPC program 100000, Version
3). This avoids problems with servers that do not
respond to Version 3 commands. The local version
of rpcbind also supports servers of Versions 2
and 3.
no RPC clients first call the rpcbind utility. If
this fails, the Portmapper utility is called.
Page 7 Reliant UNIX 5.44 Printed 11/98
inet(4) inet(4)
FILES
/etc/default/inet
SEE ALSO
slattach(1M), timed(1M), group.local(4), passwd.local(4),
pwpattern(4), ypservers(4).
Page 8 Reliant UNIX 5.44 Printed 11/98