XNSrouted man page on 4.4BSD

Man page or keyword search:  
man Server   1065 pages
apropos Keyword Search (all sections)
Output format
4.4BSD logo
[printable version]

XNSROUTED(8)		  BSD System Manager's Manual		  XNSROUTED(8)

     XNSrouted — NS Routing Information Protocol daemon

     XNSrouted [-q] [-s] [-t] [logfile]

     XNSrouted is invoked at boot time to manage the Xerox NS routing tables.
     The NS routing daemon uses the Xerox NS Routing Information Protocol in
     maintaining up to date kernel routing table entries.

     Available options:

     -q	      Do not supply routing information (opposite of -s option below).

     -s	      Forces XNSrouted to supply routing information whether it is
	      acting as an internetwork router or not.

     -t	      All packets sent or received are printed on the standard output.
	      In addition, XNSrouted will not divorce itself from the control‐
	      ling terminal so that interrupts from the keyboard will kill the

     logfile  Name of file in which XNSrouted's actions should be logged.
	      This log contains information about any changes to the routing
	      tables and a history of recent messages sent and received which
	      are related to the changed route.

     In normal operation XNSrouted listens for routing information packets.
     If the host is connected to multiple NS networks, it periodically sup‐
     plies copies of its routing tables to any directly connected hosts and

     When XNSrouted is started, it uses the SIOCGIFCONF ioctl(2) to find those
     directly connected interfaces configured into the system and marked “up”
     (the software loopback interface is ignored).  If multiple interfaces are
     present, it is assumed the host will forward packets between networks.
     XNSrouted then transmits a request packet on each interface (using a
     broadcast packet if the interface supports it) and enters a loop, listen‐
     ing for request and response packets from other hosts.

     When a request packet is received, XNSrouted formulates a reply based on
     the information maintained in its internal tables.	 The response packet
     generated contains a list of known routes, each marked with a “hop count”
     metric (a count of 16, or greater, is considered “infinite”).  The metric
     associated with each route returned provides a metric relative to the

     Response packets received by XNSrouted are used to update the routing
     tables if one of the following conditions is satisfied:

     ·	 No routing table entry exists for the destination network or host,
	 and the metric indicates the destination is ``reachable'' (i.e. the
	 hop count is not infinite).

     ·	 The source host of the packet is the same as the router in the exist‐
	 ing routing table entry.  That is, updated information is being
	 received from the very internetwork router through which packets for
	 the destination are being routed.

     ·	 The existing entry in the routing table has not been updated for some
	 time (defined to be 90 seconds) and the route is at least as cost
	 effective as the current route.

     ·	 The new route describes a shorter route to the destination than the
	 one currently stored in the routing tables; the metric of the new
	 route is compared against the one stored in the table to decide this.

     When an update is applied, XNSrouted records the change in its internal
     tables and generates a response packet to all directly connected hosts
     and networks.  Routed(8) waits a short period of time (no more than 30
     seconds) before modifying the kernel's routing tables to allow possible
     unstable situations to settle.

     In addition to processing incoming packets, XNSrouted also periodically
     checks the routing table entries.	If an entry has not been updated for 3
     minutes, the entry's metric is set to infinity and marked for deletion.
     Deletions are delayed an additional 60 seconds to insure the invalidation
     is propagated to other routers.

     Hosts acting as internetwork routers gratuitously supply their routing
     tables every 30 seconds to all directly connected hosts and networks.


     Internet Transport Protocols, XSIS 028112, Xerox System Integration

     The XNSrouted command appeared in 4.3BSD.

4.3 Berkeley Distribution	 June 5, 1993	     4.3 Berkeley Distribution

List of man pages available for 4.4BSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net