4.4BSD/usr/share/man/cat8/route.0
ROUTE(8) BSD System Manager's Manual ROUTE(8)
NNAAMMEE
rroouuttee - manually manipulate the routing tables (Interim)
SSYYNNOOPPSSIISS
rroouuttee [--nn] [--qq] [--vv] _c_o_m_m_a_n_d [[_m_o_d_i_f_i_e_r_s] _a_r_g_s]
DDEESSCCRRIIPPTTIIOONN
RRoouuttee is a program used to manually manipulate the network routing ta-
bles. It normally is not needed, as the system routing table management
daemon, routed(8), should tend to this task.
Options supported by rroouuttee:
--nn Prevent attempts to print host and network names symbolically
when reporting actions.
--vv (verbose) Print additional details.
--qq Suppress all output.
Commands accepted by rroouuttee:
aadddd Add a route.
fflluusshh Remove all routes.
ddeelleettee Delete a specific route.
cchhaannggee Change aspects of a route (such as its gateway).
ggeett Lookup and display the route for a destination.
mmoonniittoorr Continuously report any changes to the routing information
base, routing lookup misses, or suspected network partion-
ings.
The monitor command has the syntax
rroouuttee [--nn] mmoonniittoorr
The flush command has the syntax
rroouuttee [--nn] fflluusshh [_f_a_m_i_l_y]
Where the address family may be specified by any of the --oossii, --xxnnss, or
--iinneett keywords.
The other commands have the following syntax:
rroouuttee [--nn] _c_o_m_m_a_n_d [--nneett | --hhoosstt] _d_e_s_t_i_n_a_t_i_o_n _g_a_t_e_w_a_y
where _d_e_s_t_i_n_a_t_i_o_n is the destination host or network, _g_a_t_e_w_a_y is the
next-hop gateway to which packets should be addressed. Routes to a par-
ticular host are distinguished from those to a network by interpreting
the Internet address associated with _d_e_s_t_i_n_a_t_i_o_n. The optional keywords
--nneett and --hhoosstt force the destination to be interpreted as a network or a
host, respectively. Otherwise, if the _d_e_s_t_i_n_a_t_i_o_n has a ``local address
part'' of INADDR_ANY , or if the _d_e_s_t_i_n_a_t_i_o_n is the symbolic name of a
network, then the route is assumed to be to a network; otherwise, it is
presumed to be a route to a host.
For example, 128.32 is interpreted as --hhoosstt 128.0.0.32; 128.32.130 is in-
terpreted as --hhoosstt 128.32.0.130; --nneett 128.32 is interpreted as
128.32.0.0; and --nneett 128.32.130 is interpreted as 128.32.130.0.
If the route is via an interface rather than via a gateway, the
--iinntteerrffaaccee modifier should be specified; the gateway given is the address
of this host on the common network, indicating the interface to be used
for transmission.
The optional modifiers --xxnnss, and --oossii specify that all subsequent ad-
dresses are in the XNS or OSI address families, and the names must be nu-
meric specifications rather than symbolic names.
The optional --nneettmmaasskk qualifier is intended to achieve the effect of an
OSI ESIS redirect with the netmask option. One specifies an additional
ensuing address parameter (to be interpreted as a network mask). The im-
plicit network mask generated in the inet case can be overridden by mak-
ing sure this option follows the destination parameter.
The optional modifiers --rrtttt, --rrttttvvaarr, --sseennddppiippee, --rreeccvvppiippee, --mmttuu,
--hhooppccoouunntt, --eexxppiirree, and --sssstthhrreesshh provide initial values to metrics main-
tained in the routing entry. These may be individually locked by preced-
ing each such modifier to be locked by the --lloocckk meta-modifier, or one
can specify that all ensuing metrics may be locked by the --lloocckkrreesstt meta-
modifier.
In a cchhaannggee or aadddd command where the destination and gateway are not suf-
ficient to specify the route (as in the ISO case where several interfaces
may have the same address), the --iiffpp or --iiffaa modifiers may be used to de-
termine the interface or interface address.
All symbolic names specified for a _d_e_s_t_i_n_a_t_i_o_n or _g_a_t_e_w_a_y are looked up
first as a host name using gethostbyname(3). If this lookup fails, get-
netbyname(3) is then used to interpret the name as that of a network.
RRoouuttee uses a routing socket and the new message types RTM_ADD,
RTM_DELETE, RTM_GET, and RTM_CHANGE. As such, only the super-user may
modify the routing tables.
If the fflluusshh command is specified, rroouuttee will ``flush'' the routing ta-
bles of all gateway entries. One can choose to flush only those routes
whose destinations are of a given address family, by specifying an op-
tional keyword describing which address family.
DDIIAAGGNNOOSSTTIICCSS
aadddd [[hhoosstt || nneettwwoorrkk ]] %%ss:: ggaatteewwaayy %%ss ffllaaggss %%xx
The specified route is being added to the tables. The values
printed are from the routing table entry supplied in the ioctl(2)
call. If the gateway address used was not the primary address of
the gateway (the first one returned by gethostbyname(3)), the
gateway address is printed numerically as well as symbolically.
ddeelleettee [[ hhoosstt &&|| nneettwwoorrkk ]] %%ss:: ggaatteewwaayy %%ss ffllaaggss %%xx
As above, but when deleting an entry.
%%ss %%ss ddoonnee
When the fflluusshh command is specified, each routing table entry
deleted is indicated with a message of this form.
NNeettwwoorrkk iiss uunnrreeaacchhaabbllee
An attempt to add a route failed because the gateway listed was
not on a directly-connected network. The next-hop gateway must
be given.
nnoott iinn ttaabbllee
A delete operation was attempted for an entry which wasn't pre-
sent in the tables.
rroouuttiinngg ttaabbllee oovveerrffllooww
An add operation was attempted, but the system was low on re-
sources and was unable to allocate memory to create the new en-
try.
SSEEEE AALLSSOO
netintro(4), route(4), esis(4), routed(8), XNSrouted(8)
HHIISSTTOORRYY
The rroouuttee command appeared in 4.2BSD.
BBUUGGSS
The first paragraph may have slightly exaggerated routed's abilities.
4.2 Berkeley Distribution June 5, 1993 3