DNROUTE(8) System Manager's Manual DNROUTE(8)NAME
dnroute - DECnet Routing Daemon
SYNOPSIS
dnroute [options]
Options:
[-dvV2Dtnhr]
DESCRIPTION
dnroute is a daemon that manages the DECnet routing tables to provide a simple
but probably useful routing policy.
dnroute listens for incoming routing messages and adds routes in the kernel for non-local areas that it sees. Routes will be modifed
according to these messages so that the lowest cost route that is up will always be used. Routes to locally accessible nodes (it those in
the neighbour table) will also be added. If you want to keep manual control of the route to a particular area, then add a line into
dnroute.conf. eg:
manual 26
will disable dnroute's setting of routing tables for that area. dnetinfo will still show the route that would have been set with (M) on the
line to show it has been overidden.
To implement its routing policies dnroute assumes that all interfaces on the system have a cost of 4. To change this add lines in
/etc/dnroute.conf for each of the interfaces you need to change. eg
eth0 6
eth1 8
tap0 10
A script called dnetinfo is provided that gets the routing information from dnroute and displays it on stdout in a format similar to the
VMS command SHOW NET/OLD.
OPTIONS -d Don't fork and run the background. Use this for debugging.
-v Verbose. Log route changes to syslog.
-D Debug log. Writes debugging information to stderr. Only useful with -d.
-h -? Displays help for using the command.
-r Send DECnet routing messages showing the state of local nodes.
-2 Send DECnet level 2 (area) routing messages. Implies -r.
-t <secs>
Timer to send routing messages on. Defaults to 15 seconds.
-n Do not set up routes or send routing messages, just monitor the network. Useful for testing.
-V Show the version of dnroute.
SEE ALSO dnetd.conf(5), ip(8)DECnet utilities March 30 2006 DNROUTE(8)
Check Out this Related Man Page
IPXROUTED(8) BSD System Manager's Manual IPXROUTED(8)NAME
IPXrouted -- IPX Routing Information Protocol daemon
SYNOPSIS
IPXrouted [-N] [-q] [-s] [-S] [-t] [logfile]
DESCRIPTION
The IPXrouted utility is invoked at boot time to manage the IPX routing tables. The IPX routing daemon uses the Novell IPX Routing Informa-
tion Protocol in maintaining up to date kernel routing table entries.
Available options:
-N Do not reply on GetNearestServer SAP request.
-q Do not supply routing information (opposite of -s option below).
-s Forces IPXrouted to supply routing information whether it is acting as an internetwork router or not.
-S Do not supply Service Advertising Protocol (SAP) information. The default is to supply SAP information.
-t All packets sent or received are printed on the standard output. In addition, IPXrouted will not divorce itself from the control-
ling terminal so that interrupts from the keyboard will kill the process.
logfile Name of file in which IPXrouted'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 IPXrouted listens for routing information packets. If the host is connected to multiple IPX networks, it periodically
supplies copies of its routing tables to any directly connected hosts and networks.
When IPXrouted 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. The IPXrouted utility then transmits a request packet on each interface (using a broadcast packet if the interface supports it)
and enters a loop, listening for request and response packets from other hosts.
When a request packet is received, IPXrouted 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 sender.
Response packets received by IPXrouted are used to update the routing tables if one of the following conditions is satisfied:
o 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).
o The source host of the packet is the same as the router in the existing routing table entry. That is, updated information is being
received from the very internetwork router through which packets for the destination are being routed.
o 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.
o 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, IPXrouted records the change in its internal tables and generates a response packet to all directly connected
hosts and networks. The routed(8) utility 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, IPXrouted 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 ensure 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.
If IPXrouted receives a SIGINFO signal the current contents of the RIP and SAP tables are appended to the file /var/log/ipxrouted.dmp.
SEE ALSO ipx(3)HISTORY
The IPXrouted utility first appeared in FreeBSD 2.2.
BSD October 11, 1995 BSD