rtquery(1Mtcp)

rtquery -- query routing daemons for their routing tables

Synopsis

rtquery [ -np1 ] [ -w timeout ] [ -r addr ] [ -a passwd=secret | md5_passwd=secret | md5_passwd=KeyID ] host ...

rtquery [ -t op ] op host ...

Description

rtquery is used to query a RIP network routing daemon, routed(1Mtcp) or gated(1Mtcp), 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, rtquery uses the request command. When the -p option is specified, rtquery uses the poll command, an extension to the RIP protocol supported by gated(1Mtcp). When querying gated, the poll command is preferred to the request command. This is because the response to the poll command is not subject to Split Horizon and/or Poisoned Reverse, and because some versions of gated do not answer the request command. routed does not answer the poll command, but it recognizes requests coming from rtquery and so answers completely.

rtquery can also be used to turn tracing on or off in routed.

rtquery understands the following options:

-n

Display only the numeric network and host numbers. Normally, network and host numbers are displayed both symbolically and numerically.

-p

Use the poll command to request full routing information from gated(1Mtcp), This is an extension to the RIP protocol supported by gated.

-1

Query using RIP version 1 instead of RIP version 2.

-w timeout

Change the delay for an answer from each host. By default, each host is given 15 seconds to respond.

-r addr

Ask about the route to destination addr.

-a passwd=secret

-a md5_passwd=secret

-a md5_passwd=KeyID

Send the query with the indicated cleartext or MD5 password.

-t op

Change the tracing level of routed(1Mtcp) according to the specified operation, op. Requests from processes which are not running with UID 0 or which are on distant networks are generally ignored by the daemon except for a message in the system log. gated(1Mtcp) ignores these debugging requests. op is one of the following operations:

on=tracefile: Turn on tracing to the specified trace file. The file must have been specified when the daemon was started or it must have the same name as an existing file.
more: Increase the debugging level.
off: Turn off tracing.
dump: Dump the daemon's routing table to the current trace file.

References

ripquery(1Mtcp), routed(1Mtcp), gated(1Mtcp)

RFC 1058, RFC 1723