Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!netnews.nwnet.net!symiserver2.symantec.com!usenet From: tedm@agora.rdrop.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Not Advertising RIP Date: 13 Jul 1996 06:30:14 GMT Organization: Symantec Corporation Lines: 23 Message-ID: <4s7fpm$j0t@symiserver2.symantec.com> References: <4rkgcj$2hc@eplet.mira.net.au> <4rt1h3$4fl@uriah.heep.sax.de> Reply-To: tedm%toybox@agora.rdrop.com NNTP-Posting-Host: 198.6.34.1 X-Newsreader: IBM NewsReader/2 v1.2 In <4rt1h3$4fl@uriah.heep.sax.de>, j@uriah.heep.sax.de (J Wunsch) writes: >robseco@wizard.teksupport.net.au (Rob Secombe) wrote: > >> I have just installed FreeBSD 2.1 at a downstream customer's site >> primarily as a router and mail server. All is working pretty well except >> it doesnt seem to want to advertise RIP. The link is using the dialup >> PPP interface, local ethernet is ed1 and running "routed -s". > >routed is ugly, as i understand it. If you really need RIP >advertising, use GateD instead. > 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. About the only thing that will pay any attention to it is Netware, or another router, which can be worked around with static routes. In my opinion, the extra broadcast traffic is not worth the extremely limited value RIP gives these days on an internal corporate net. Ted