Add kbdcontrol and vidcontrol targets, migrated from /usr/src/usr.bin
[unix-history] / usr.sbin / XNSrouted / XNSrouted.8
CommitLineData
18916298
RG
1.\" Copyright (c) 1986, 1991 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)XNSrouted.8 6.4 (Berkeley) 3/16/91
33.\"
34.Dd March 16, 1991
35.Dt XNSROUTED 8
36.Os BSD 4.3
37.Sh NAME
38.Nm XNSrouted
39.Nd NS Routing Information Protocol daemon
40.Sh SYNOPSIS
41.Nm XNSrouted
42.Op Fl q
43.Op Fl s
44.Op Fl t
45.Op Ar logfile
46.Sh DESCRIPTION
47.Nm XNSrouted
48is invoked at boot time to manage the Xerox NS routing tables.
49The NS routing daemon uses the Xerox NS Routing
50Information Protocol in maintaining up to date kernel routing
51table entries.
52.Pp
53Available options:
54.Bl -tag -width logfile
55.It Fl q
56Do not supply routing information (opposite of
57.Fl s
58option below).
59.It Fl s
60Forces
61.Nm XNSrouted
62to supply routing information whether it is acting as an internetwork
63router or not.
64.It Fl t
65All packets sent or received are
66printed on the standard output. In addition,
67.Nm XNSrouted
68will not divorce itself from the controlling terminal
69so that interrupts from the keyboard will kill the process.
70.It Ar logfile
71Name of file in which
72.Nm XNSrouted Ns 's
73actions should be logged. This log contains information
74about any changes to the routing tables and a history of
75recent messages sent and received which are related to
76the changed route.
77.El
78.Pp
79In normal operation
80.Nm XNSrouted
81listens
82for routing information packets. If the host is connected to
83multiple NS networks, it periodically supplies copies
84of its routing tables to any directly connected hosts
85and networks.
86.Pp
87When
88.Nm XNSrouted
89is started, it uses the
90.Dv SIOCGIFCONF
91.Xr ioctl 2
92to find those
93directly connected interfaces configured into the
94system and marked
95.Dq up
96(the software loopback interface
97is ignored). If multiple interfaces
98are present, it is assumed the host will forward packets
99between networks.
100.Nm XNSrouted
101then transmits a
102.Em request
103packet on each interface (using a broadcast packet if
104the interface supports it) and enters a loop, listening
105for
106.Em request
107and
108.Em response
109packets from other hosts.
110.Pp
111When a
112.Em request
113packet is received,
114.Nm XNSrouted
115formulates a reply based on the information maintained in its
116internal tables. The
117.Em response
118packet generated contains a list of known routes, each marked
119with a
120.Dq hop count
121metric (a count of 16, or greater, is
122considered
123.Dq infinite ) .
124The metric associated with each
125route returned provides a metric
126.Em relative to the sender .
127.Pp
128.Em Response
129packets received by
130.Nm XNSrouted
131are used to update the routing tables if one of the following
132conditions is satisfied:
133.Bl -bullet
134.It
135No routing table entry exists for the destination network
136or host, and the metric indicates the destination is ``reachable''
137(i.e. the hop count is not infinite).
138.It
139The source host of the packet is the same as the router in the
140existing routing table entry. That is, updated information is
141being received from the very internetwork router through which
142packets for the destination are being routed.
143.It
144The existing entry in the routing table has not been updated for
145some time (defined to be 90 seconds) and the route is at least
146as cost effective as the current route.
147.It
148The new route describes a shorter route to the destination than
149the one currently stored in the routing tables; the metric of
150the new route is compared against the one stored in the table
151to decide this.
152.El
153.Pp
154When an update is applied,
155.Nm XNSrouted
156records the change in its internal tables and generates a
157.Em response
158packet to all directly connected hosts and networks.
159.Xr Routed 8
160waits a short period
161of time (no more than 30 seconds) before modifying the kernel's
162routing tables to allow possible unstable situations to settle.
163.Pp
164In addition to processing incoming packets,
165.Nm XNSrouted
166also periodically checks the routing table entries.
167If an entry has not been updated for 3 minutes, the entry's metric
168is set to infinity and marked for deletion. Deletions are delayed
169an additional 60 seconds to insure the invalidation is propagated
170to other routers.
171.Pp
172Hosts acting as internetwork routers gratuitously supply their
173routing tables every 30 seconds to all directly connected hosts
174and networks.
175.Sh SEE ALSO
176.Xr idp 4
177.Rs
178.%T "Internet Transport Protocols"
179.%R "XSIS 028112"
180.%Q "Xerox System Integration Standard"
181.Re
182.Sh HISTORY
183The
184.Nm
185command appeared in
186.Bx 4.3 .