From owner-freebsd-isp Thu Feb 4 10:25:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27958 for freebsd-isp-outgoing; Thu, 4 Feb 1999 10:25:06 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27953 for ; Thu, 4 Feb 1999 10:25:04 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id LAA23079; Thu, 4 Feb 1999 11:30:18 -0800 (PST) Date: Thu, 4 Feb 1999 11:30:18 -0800 (PST) From: Jim Shankland Message-Id: <199902041930.LAA23079@biggusdiskus.flyingfox.com> To: tim@iafrica.com.na Subject: Re: Info for newbie Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <36B96A63.67BC@iafrica.com.na> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > FreeBSD works fine for routing between Ethernet segments, but my > experiance is that you will be happier with a router for WAN links. The archives threaten to overflow with "router vs. sync. card" wars past, so I'll just note that there is no consensus on the above statement. Personally, I've got FreeBSD driving ... umm ... I guess 7 T-1 links at various sites now, and I'm happy. Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message