Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!usenet From: robseco@wizard.teksupport.net.au (Rob Secombe) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Not Advertising RIP Date: Sun, 14 Jul 96 14:12:13 EST Organization: Teksupport Internet Access Lines: 70 Message-ID: <4s9s45$ki0@eplet.mira.net.au> References: <4rkgcj$2hc@eplet.mira.net.au> <4rt1h3$4fl@uriah.heep.sax.de> <4s7fpm$j0t@symiserver2.symantec.com> NNTP-Posting-Host: magician.teksupport.net.au Mime-Version: 1.0 X-Newsreader: WinVN 0.93.9 In article <4s7fpm$j0t@symiserver2.symantec.com>, tedm@agora.rdrop.com says... > >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 -- Rob Secombe Teksupport Pty. Ltd. Email robseco@wizard.teksupport.net.au Melbourne Australia World Wide Web http://www.teksupport.net.au/ ************************************************************************* Hi, The reason I want it to advertise rip is that the customer dials in on demand to our annex via a rotary group and could come in on a different line and hence have a diferernt ip address each time. I know we can use dialup address with the annex but I wish to keep these type of customers outside our normal accounting system by not using the annex security. If the FreeBSD box advertises rip it doesn't matter which line or ip address is assigned. My basic problem seems to be getting the BSD box to advertise rip and forward packets at the same time. If I have the annex and the user ppp interface on the same network (ie same class C) and the ethernet card in the BSD box on the customers class C along with the MACs an PCs etc. The BSD box will forward packets but the annex sees no rip and I have to plug a static route for the duration of the call. If on the other hand I assign the user ppp interface an ip address from the customers class C the BSD box will not forward packets to the ethernet but it advertises rip to the annex. They seem to be mutally exclusive. I must admit I haven't tried GateD yet but it is starting to look as if I may have no choice. If any one has a similar configuration actually up and running I would really appreciate hearing from you. Thanks.