From owner-freebsd-questions@FreeBSD.ORG Wed Apr 21 07:42:14 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F3A216A4CE for ; Wed, 21 Apr 2004 07:42:14 -0700 (PDT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 413C543D49 for ; Wed, 21 Apr 2004 07:42:14 -0700 (PDT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 8885037D; Wed, 21 Apr 2004 08:42:13 -0600 (CST) Date: Wed, 21 Apr 2004 08:42:13 -0600 From: Tillman Hodgson To: freebsd-questions@freebsd.org Message-ID: <20040421144213.GL476@seekingfire.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.6i Subject: Re: Is it worth using both gigabit ether ports? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 14:42:14 -0000 On Wed, Apr 21, 2004 at 03:11:55PM +0100, Andy Holyer wrote: > I work for a small special-purpose ISP, and right now I'm configuring > our main Web/Mail/DNS server. It's a Dell Poweredge 750, 2.4Gb with > 1Gig of memory and twp 80 GB drives mirrored using vinum. > > When I've prepped it up, it's due to go in our rack at Telecity in > Docklands. > > The box came with an Intel twin Gigabit network card, and I'd like to > use ng_one2many to load share so that the box uses both ports at once. > > There doesn't appear to be much about this on the web. My question: is > it worth doing? Will a get a better and/or more fault-tolerent > performance by doing this? Do I have to do anything clever with DNS or > the router (a Cisco 3660) to get requests evenly distributed, or can I > rely on sharing outgoing traffic? I'll reply to just the fault-tolerant question: You'll get less fault-tolerance, as ng_one2many doesn't implement any kind of connection checking. If an interface dies, 1/2 of your packets will still attempt to use it. -T -- Real men use "cat /var/spool/mail/$USER | more" and "telnet $SMTP_HOST 25" - Anonymous Unix geek "more /var/spool/mail/$USER" <-- don't waste a process, you idiot - Second anonymous Unix geek