From owner-freebsd-hackers Tue Jun 3 08:49:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05291 for hackers-outgoing; Tue, 3 Jun 1997 08:49:59 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05286 for ; Tue, 3 Jun 1997 08:49:55 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id JAA10451 for ; Tue, 3 Jun 1997 09:49:56 -0600 (MDT) Date: Tue, 3 Jun 1997 09:49:56 -0600 (MDT) From: Brandon Gillespie To: hackers@FreeBSD.ORG Subject: Re: Why routed and not gated by default? In-Reply-To: <19970603082931.JL57049@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 3 Jun 1997, J Wunsch wrote: > As Bill Fenner wrote: > > >I know that Bill Fenner will heavily object now > > > > Hm, I'm not sure that's the kind of name I want to have made for myself > > in the FreeBSD community =) > > :-) > > > I still believe that router discovery should be enabled by default > > on ethernet-connected end-systems that aren't acting as routers > > themselves. > > And my point is that the operator should be required to actively hit a > button before this is turned on. The operator could be automatically > guided to this question however, e.g. in Novice installation mode. > > There are a lot of ethernets on this planet where even running router > discovery is at best a waste of virtual memory (since there's simply > nothing to discover). I vehmenently agree 8) Or at the very least, EXPLAIN the difference between routed and gated in the docs. A year or so ago when I first installed these systems I had no idea what routed did (RIP/OSPF etc) so I just figured it was decent, and handled things in a modern context. Then we upgraded our router which came from our ISP with a 'standard' (by their terms) configuration--suddenly none of the FreeBSD boxes worked. Took me FOREVER to figure out that the reason was they were using RIP--enabling RIP on the ciscoPro fixed the problem, but it would have been wonderful if I had known that doing router=routed means I'm running RIP. In the docs perhaps explain that if you run routed, you are running an older-but-perfectly- acceptable-for-small-networks RIP protocol, and if you want something else you should probably install gated with its assundry problems and whatnot. As for the possibility of gated being mis-configured and not working? Welcome to unix :) Basically, other systems seem to be able to automatically setup gated just fine without problems (Digital Unix comes to mind). I mean, a basic configuration is trivial. The whole reason I didn't use gated is because (at least at the time) the basic package/port install DIDNT WORK, I still have to learn the magic configuration directives. [steps off soapbox] -Brandon Gillespie