From owner-freebsd-isp Fri Aug 6 9:42:17 1999 Delivered-To: freebsd-isp@freebsd.org Received: from ns.tcworks.net (ns.tcworks.net [216.61.218.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F62714CBE for ; Fri, 6 Aug 1999 09:42:10 -0700 (PDT) (envelope-from ccook@tcworks.net) Received: from tcworks.net (xcess@creed.tcworks.net [216.61.218.6]) by ns.tcworks.net (8.9.2/8.9.2) with ESMTP id LAA22887 for ; Fri, 6 Aug 1999 11:42:42 -0500 (CDT) (envelope-from ccook@tcworks.net) Message-ID: <37AC60F1.918DD6C2@tcworks.net> Date: Sat, 07 Aug 1999 11:38:09 -0500 From: Chris Cook X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: [Fwd: Re: 2 queries] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin wrote: > > > > > > > 1) If you can route traffic through a gateway machine, what is the > > > requirement for a router ? More IP's ? faster routing ? > > > a) Has anyone tried the Linux router project software ? > > > > The requirement for a router? I lost you here. > > Everything I have read talks about the need for a router, eg. cisco or > whatever, and it's pretty much left like that. Well, I try to keep things simple. Fact is, a router has less to break down than a "Gateway Machine", and the router is designed for that specific task. You don't usually have to worry about people compromising the router because of software issues, and well... it's smaller and more efficient. Just my .02 > I've heard that co-locating at the central office and interfacing to the > internet and from the customers off the switch is possible and probably the > best way to go. What central office are you referring to? Your provider? You are going to want to house your equipment at your location. Hope I could help. -- Chris Cook The Computer Works http://www.tcworks.net http://www.tcworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message