From owner-freebsd-isp Tue Feb 8 15:24:19 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail1.sol.net (mail1.sol.net [206.55.64.72]) by builder.freebsd.org (Postfix) with ESMTP id 312494309 for ; Tue, 8 Feb 2000 15:07:10 -0800 (PST) Received: from aurora.sol.net (jgreco@aurora.sol.net [206.55.65.76]) by mail1.sol.net (8.8.8/8.8.8/SNNS-1.03) with ESMTP id QAA18377 for ; Tue, 8 Feb 2000 16:05:03 -0600 (CST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id PAA70085; Tue, 8 Feb 2000 15:59:57 -0600 (CST) From: Joe Greco Message-Id: <200002082159.PAA70085@aurora.sol.net> Subject: Re: O/T: Foundry To: mholloway@flashmail.com, freebsd-isp@freebsd.org Date: Tue, 8 Feb 2000 15:59:56 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone here use Foundry switches in your ISP service? How do you = > like them? I'm migrating away from 3Com and I'm looking at Foundry, = > Cisco, and Extreme. For something a little more on topic, Foundry does = > have some nice server load balancing features..so if you're running = > FreeBSD based server farms, I guess it would be a nice add-on! The last Foundry product I saw had some serious filtering deficiencies. I know lots of people aren't paranoid enough to actually do router-level filtering, but that's something that I consider. The ability to do per-port filters is a necessity, and I believe the Foundry stuff can't do it. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message