Sponsored Content
Full Discussion: Linux Router Project
Special Forums IP Networking Linux Router Project Post 2315 by Neo on Monday 7th of May 2001 04:04:27 PM
Old 05-07-2001
You may notneed RIP on such a small network, static routing may be good enough. How may routers do you have and what is the topology?
 

3 More Discussions You Might Find Interesting

1. IP Networking

Linux Router?

I am trying to set up a linux box as a router, but I am a little confused on how to do this. I am using Red Hat 9.0 on a machine that has 2 nic cards. Also, I am using a DSL pppoe connection. I have installed rp-pppoe and I am connected to the internet via the pseudo pppoe interface. I have... (1 Reply)
Discussion started by: cstovall
1 Replies

2. Solaris

building solaris-based enterprise router-firewall project

hi guys, its been a while since my last visit here, could not keep up the pace on this ever changing industry :) i'd just doing my home research under vmware to make a solaris-based router-firewall using zones - doing a lot of reading about zones & review solaris zone functionality. and... (4 Replies)
Discussion started by: stdout
4 Replies

3. News, Links, Events and Announcements

A new project was posted on The UNIX and Linux Forums project board.

A new project was posted on your project board. Project title: Bash Shell Tutoring Estimated Budget: $50/hr Start date: Immediately Required skills: Linux, Bash, Shell, UNIX I work as a datawarehouse designer and developer. Although I usually stick to the role of an analyst,... (0 Replies)
Discussion started by: Neo
0 Replies
rtquery(1M)                                               System Administration Commands                                               rtquery(1M)

NAME
rtquery - query routing daemons for their routing tables SYNOPSIS
rtquery [-np1] [-w timeout] [-r addr] [-a secret] host... rtquery [-t operation] host... DESCRIPTION
The rtquery command is used to query a RIP network routing daemon, in.routed(1M) 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, rtquery uses the request command. When the -p option 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. in.routed does not answer the poll command, but recognizes requests coming from rtquery and so answers completely. The rtquery command is also used to turn tracing on or off in in.routed. OPTIONS
The following options are supported: -a passwd=XXX Causes the query to be sent with the indicated cleartext or MD5 password. -a md5_passwd=XXX|KeyID -n Displays only the numeric network and host addresses instead of both numeric and symbolic names. -p Uses the poll command to request full routing information from GateD. This is an undocumented extension RIP proto- col supported only by GateD. -r addr Asks about the route to destination addr. -t operation Changes tracing, where operation is one of the actions listed below. Requests from processes not running with UID 0 or on distant networks are generally ignored by the daemon except for a message in the system log. GateD is likely to ignore these debugging requests. on=tracefile Turns tracing on, directing tracing into the specified file. That file must have been specified when the daemon was started or have the name, /var/log/in.routed.trace. more Increases the debugging level. off Turns off tracing. dump Dumps the daemon's routing table to the current trace file. -w timeout Changes the delay for an answer from each host. By default, each host is given 15 seconds to respond. -1 Queries using RIP version 1 instead of RIP version 2. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWroute | +-----------------------------+-----------------------------+ SEE ALSO
in.routed(1M), route(1M), gateways(4), attributes(5), icmp(7P), inet(7P), udp(7P) Routing Information Protocol, RIPv1, RFC 1058 Routing Information Protocol, RIPv2, RFC 2453, STD 0056 SunOS 5.10 24 Apr 2002 rtquery(1M)
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy