Query routing daemons for their routing tables
rtquery [-1np] [-a secret] [-r addr] [-w timeout] host ...
[-t op] host ...
- Query using RIP version 1 instead of RIP version 2.
- -a passwd=XXX
- Send the query with the specified RIPv2 cleartext or RIPv2 MD5 password.
- Display only the numeric network and host numbers instead of both the numeric and symbolic values.
- Use the poll command to request full routing information from gated.
This is an undocumented extension RIP protocol supported only by gated.
- -r addr
- Ask about the route to destination addr.
- -w timeout
- Change the delay for an answer from each host.
By default, each host has 15 seconds to respond.
- -t op
- Change the tracing settings.
Requests from processes that aren't running with root privileges, or are on distant networks,
are generally ignored by the daemon except for having a message logged in the system log.
- Turn on tracing to the tracefile.
The tracefile was either specified when the daemon started, or is the same as a fixed name,
- Increase the debugging level.
- Turn off tracing.
- Dump the daemon's routing table to the current tracefile.
The rtquery utility is used to query a RIP network routing daemon,
routed or gated,
for its routing table by sending a request or poll command.
The routing information in any routing response packets returned is displayed numerically and symbolically.
By default, it uses the request command.
When -p is specified, rtquery uses the poll command,
an undocumented extension to the RIP protocol supported by gated.
When querying gated,
the poll command is preferred over the request command because the response
is not subject to split-horizon and/or Poisoned Reverse,
and because some versions of gated do not answer the request command.
Although routed doesn't answer the poll command,
it recognizes requests coming from rtquery and answers them completely.
The utility is also used to turn tracing on or off in routed.
gated (an unsupported version is available on the QDN),
- RFC 1058 Routing Information Protocol, RIPv1
- RFC 1723 Routing Information Protocol, RIPv2