vtc.addrs(4M) DG/UX 5.4.2 vtc.addrs(4M)
NAME
vtc.addrs - SYAC VTC configuration file
SYNOPSIS
/etc/tcload/vtc.addrs
DESCRIPTION
The vtc.addrs file contains network configuration information for
SYAC VTC boards. The information contained in this file is
communicated to the board when rc.tcload is run or when the SYAC
board is reset.
The vtc.addrs file contains entries for VTC specific information and
entries for tty specific information. Each tty entry in this file
must be for a tty that is associated with a VTC, and tty entries must
immediately follow the VTC entry with which the tty is associated.
Fields in all entries are whitespace separated. There must be one
VTC specific entry for each configured SYAC that is a VTC. Tty
specific entries are optional.
The tty specific entries allow the system administrator to alter the
behavior of ttys associated with a VTC. By default, ttys associated
with a VTC answer telnet connections to the default Internet address
for that VTC. Ttys can also be configured to answer connections for
different Internet addresses. This behavior is useful when it is
necessary to associate a specific terminal entry with a specific
device via a telnet connection (see syac_ttyaddrs(1M)).
Tty specific entries also allow the system administrator to determine
how telnet binary mode affects onboard input processing (see
termio(7)). By default, onboard input processing is unaffected by
the state of telnet binary mode, and can only be enabled or disabled
by changing the line discipline settings (see termio(7)). Ttys
associated with a VTC can be configured such that when the telnet
connection is in telnet binary mode, onboard input processing is also
disabled. Note, however, that input processing performed by the host
for a tty associated with a VTC will always be unaffected by the
state of telnet binary mode. Very rarely will an application require
that onboard input processing be disabled when telnet binary mode is
in effect, as input processing is normally controlled exclusively via
the line discipline settings.
VTC-specific Entries
The VTC-specific entries have the following format:
<SYAC node> <Inet Addr> <BAddr> <Netmask> <Route Info>
The SYAC node field specifies the full pathname of a SYAC control
node [see syac(7)], which must refer to a VTC device [e.g.,
/dev/async/syac@60(60000000)].
The Inet Addr field specifies the Internet address that will be
assigned to the VTC. The Internet address is specified in dot format
(see inet(3N)). By default, all ttys associated with this VTC will
respond to telnet connections to this address. This behavior may be
Licensed material--property of copyright holder(s) 1
vtc.addrs(4M) DG/UX 5.4.2 vtc.addrs(4M)
altered via tty entries in this file or by using the syac_ttyaddrs
command.
The BAddr field specifies, in dot format (see inet(3N)), the
broadcast address for the network to which the VTC is attached.
The Netmask field specifies, in dot format (see inet(3N)), the
netmask for the network to which the VTC is attached.
The Route Info field specifies the location of the routing
information that should be communicated to the VTC. The value of
this field should be either the keyword default or the full pathname
of a file containing routing information. If the keyword default is
specified, then the routing information read from the host routing
table will be communicated to the VTC. If a pathname is specified,
then the named file is read and the routing information in the file
is communicated to the VTC. The format of the file should be
identical to that of /etc/gateways (see gateways(4M)).
It is an error if a configured SYAC VTC does not have a VTC specific
entry in this file or if any of the fields are missing or blank.
Tty-specific Entries
The tty-specific entries are in the following format:
<Tty path> <Inet Addr> [<Binary flag> [<Input flag>]]
The Tty path specifies the full pathname of the tty device for the
entry (eg /dev/tty34).
The Inet Addr specifies the Internet address to which the tty should
respond to telnet connections. The Internet address should be in dot
format (see inet(3N)).
The Binary flag field is an optional field which can have either the
keyword on or the keyword off as its value. If the field is not
present or if the keyword on is specified, then the VTC will attempt
to negotiate telnet binary mode whenever a telnet connection is
accepted for the tty in question. If the keyword off is specified,
then the VTC will not attempt to negotiate telnet binary mode when a
connection is accepted for the tty in question.
The Input flag field is an optional field which can have either the
keyword on or the keyword off as its value. If the field is not
present or if the keyword on is specified, then input processing will
be unaffected by the state of telnet binary mode. If the keyword off
is specified, then onboard input processing will be disabled when
telnet binary mode is in effect on the line. Note that if this field
is specified, then the Binary flag field must also be specified.
It is not necessary for each tty controlled by a VTC to have an entry
in this file. By default, a tty will answer to connections to the
Internet address of the VTC which controls the tty, telnet binary
mode will be negotiated on when a connection is established, and
input processing will be unaffected by the state of telnet binary
Licensed material--property of copyright holder(s) 2
vtc.addrs(4M) DG/UX 5.4.2 vtc.addrs(4M)
mode. A tty should have an entry in this file only if this default
behavior needs to be changed. The most common case would be to
associate an Internet address with the tty that differs from the
Internet address of the VTC that controls the tty.
Tty specific entries must be located after the VTC specific entry for
their controlling VTC and before any other VTC specific entries.
EXAMPLE
/dev/async/syac@60(60000000) 128.222.3.112 128.222.3.255 255.255.255.0 default
/dev/tty34 128.222.3.113
/dev/tty112 128.222.3.84
/dev/async/syac@61(60020000) 128.222.3.96 128.222.3.255 255.255.255.0 /etc/syac1
/dev/tty260 128.222.3.97 off on
In this example, syac@60 will have an Internet address of
128.222.3.112, a broadcast address of 128.222.3.255, and a netmask of
255.255.255.0. It will use the same routing information as the host
computer. It should control /dev/tty34 and /dev/tty112, each of
which will answer telnet connections to a different Internet address
than the VTC with which they are associated. The default behavior as
regards telnet binary mode will apply to these two ttys and all other
ttys controlled by syac@60.
Syac@61 will use the Internet address, broadcast address, and netmask
specified above. The routing information in /etc/syac1 will be
communicated to the board (the file should have the same format as
/etc/gateways.) Syac@61 should control /dev/tty260, which will
respond to telnet connections to the specified Internet address. For
/dev/tty260, when a connection is established telnet binary mode will
not be negotiated on, however, if the connection is negotiated into
telnet binary mode (by a termserver, for example), on board input
processing will be unaffected (this is the default).
FILES
/etc/tcload/vtc.addrs SYAC VTC configuration file
SEE ALSO
syac_routes(1M), syac_ttyaddrs(1M), inet(3N), gateways(4M), syac(7),
termio(7).
Licensed material--property of copyright holder(s) 3