*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages -> rtquery (1)              


RTQUERY(1)							    RTQUERY(1)

NAME    [Toc]    [Back]

     rtquery - query routing daemons for their routing tables

SYNOPSIS    [Toc]    [Back]

     rtquery [-np1] [-w	timeout] [-r addr] [-a secret] host ...

     rtquery -t	op host	...

DESCRIPTION    [Toc]    [Back]

     Rtquery is	used to	query a	RIP network routing daemon, routed(1M) or
     gated(1M),	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.

     Rtquery by	default	uses the request command.  When	the -p option is
     specified,	rtquery	uses the poll command, an undocumented extension to
     the RIP specification supported by	gated(1M).  When querying gated(1M),
     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.	Routed
     does not answer the Poll command, but recognizes Requests coming from
     rtquery and so answers completely.

     Rtquery is	also used to turn tracing on or	off in routed.

OPTIONS    [Toc]    [Back]

     -n	  Normally network and host numbers are	displayed both symbolically
	  and numerically.  The	-n option displays only	the numeric network
	  and host numbers.

     -p	  Uses the Poll	command	to request full	routing	information from
	  gated(1M).  This is an undocumented extension	of the RIP protocol
	  supported only by gated(1M).

     -1	  query	using RIP version 1 instead of RIP version 2.

     -w	timeout
	  changes 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=XXX

     -a	md5_passwd=XXX|KeyID
	  cause	the query to be	sent with the indicated	cleartext or MD5

     -t	op
	  change tracing, where	op is one of the following.  Requests from
	  processes not	running	with UID 0 or on distant networks are

									Page 1

RTQUERY(1)							    RTQUERY(1)

	  generally ignored by the daemon except for a message in the system
	  log.	gated(1M).  is likely to ignore	these debugging	requests.

	       turn tracing on into the	specified file.	 That file must
	       usually have been specified when	the daemon was started or be
	       the same	as a fixed name, often /etc/routed.trace.

	  more increases the debugging level.

	  off  turns off tracing.

	  dump dumps the daemon's routing table	to the current tracefile.

SEE ALSO    [Toc]    [Back]

     routed (1M), gated(1M)
     RFC 1058 -	Routing	Information Protocol, RIPv1
     RFC 1723 -	Routing	Information Protocol, RIPv2

									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
routes Tru64 Specifies Internet routing information to the routing tables
route OpenBSD manually manipulate the routing tables
route FreeBSD manually manipulate the routing tables
routed Tru64 Manages network routing tables
route HP-UX manually manipulate the routing tables
route IRIX manually manipulate the routing tables
route Tru64 Manipulates the routing tables manually
dcecp_log HP-UX A dcecp object that manages serviceability routing and debug routing
netstat Linux Print network connections, routing tables, interface statistics, masquerade connections, and multica...
multicast FreeBSD Multicast Routing
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service