Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!newsgate.duke.edu!zombie.ncsc.mil!nntp.coast.net!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Not Advertising RIP
Date: 13 Jul 1996 12:40:44 GMT
Organization: Private BSD site, Dresden
Lines: 72
Message-ID: <4s85gc$n33@uriah.heep.sax.de>
References: <4rkgcj$2hc@eplet.mira.net.au> <4rt1h3$4fl@uriah.heep.sax.de>
<4s7fpm$j0t@symiserver2.symantec.com>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E
tedm@agora.rdrop.com wrote:
> I could never get routed to advertise RIP either.
> My recommendation is to forget about advertising RIP anyway, unless
> you have a network of Unix clients at the client's site. Neither
> WfW311, Win95, WinNT or MacOS even listen to it, and OS/2 has to be
> specially configured to listen to it as well.
The idea is not to have all the clients listen to it. Only routers
and gateway are supposed to listen. Alas, there's much confusion
about the differentiation between both terms (see RFC1009 which makes
both almost equivalent). So let me give a picture of what i did in
our corporate network:
other Internet
corporate |
networks |
| |
+-----------+ +-----------+
| ISDN | | ISDN |
| router | | router |
+-----------+ +-----------+
| 1.2.3.4 | 1.2.3.5
| |
:-----+---------------------------+------------+ +------------+
| | Unix |
+---| |
| | host |
| +------------+
| 1.2.3.1
|
| +------------+
| | Unix |
+---| |
| | host |
| +------------+
:-----------+---------------------+------------+ 1.2.3.10
| |
| |
+-------------+ +------------+
| Windoze | | Windoze |
| machine | | machine |
+-------------+ +------------+
1.2.3.20 1.2.3.21
Now, instead of running routed -q on the Unix hosts, while the Windoze
machines would only see parts of the routes out the different ISDN
routers, i finally setup GateD on 1.2.3.1. Both ISDN routers
advertise their routes via RIP, the Internet router (naturally)
advertises the default route. GateD collects this information, and
adjusts the routing table on 1.2.3.1 accordingly. So if one of the
ISDN routers goes down, the routes will disappear after a short
period. Now, all other machines around use 1.2.3.1 as their default
route (gateway?), forwarding their packets first to this machine.
1.2.3.1 will, in turn, look the destination up in the routing tables,
and issue an ICMP redirect to the source host, therefore telling the
packet sender where to deliver future packets with the same
destination.
All i can say, it works really fine since. (I'm still stumpling
across a warning whenever somebody logs into 1.2.3.1 with PPP, but
that's a different matter.)
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)