From owner-freebsd-net Thu Apr 26 10:32:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 9973B37B422 for ; Thu, 26 Apr 2001 10:32:40 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 81012 invoked by uid 1001); 26 Apr 2001 17:32:36 +0000 (GMT) To: mike@sentex.net Cc: freebsd-net@freebsd.org Subject: Re: number of interfaces and performance ? From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 26 Apr 2001 11:21:17 -0400" References: <5.1.0.14.0.20010424145602.05c353a0@marble.sentex.ca> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 26 Apr 2001 19:32:36 +0200 Message-ID: <81010.988306356@verdi.nethelp.no> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have the need to put together a somewhat largish VLAN router (larger than > I have done before) with about 35 interfaces. Has anyone put anything like > this together ? The box would be routing about 25-30Mb at peak rate. I > recall reading something about LINUX being very inefficient when it comes > to multiple interfaces. Does FreeBSD suffer from the same fate ? I also > recall someone running into problems with 16 physical interfaces (4 x 4 > multiport nics). Not sure how much of that was an hardware resource issue > and how much a software resource issue . Will it work OK in theory, or > should I spend the $8K on a 3640 ? As long as you're just doing Ethernet, you might want to consider the 2948G-L3 as an alternative to a 3640. IP routing in hardware, 48 10/100 ports and 2 Gigabit ports. *Way* more backplane bandwidth and pps than the 3640. Con: No access lists on the 10/100 ports. We're using these as pure routers (no bridging), and they're working very well. (We used to have the 2948G-L3 do bridging also, that did *not* work very well.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message