From owner-freebsd-current@FreeBSD.ORG Fri Apr 13 05:21:12 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D9DA16A402; Fri, 13 Apr 2007 05:21:12 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id 2B9EC13C4BB; Fri, 13 Apr 2007 05:21:11 +0000 (UTC) (envelope-from ianf@clue.co.za) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za; h=Received:Received:Received:To:From:Subject:In-Reply-To:X-Attribution:Date:Message-Id; b=SnW+puJdIQR2EFTi8ZfdPxa4Pc4nOQALHg3uHKc1DEK4tCfLdIoUCV3lSKKL95zngYaXTueeQd2C8dKyUOr56ruWVF7XEZbSec6gO1hSwsV8JVYWg2/x71FEhI/k5I88nYtwKXmH84uwogEEkXD4lfdvrkvpnhrbtadl3ka96mz9N7gGU7SiiwHnkSrEIXWM8/Q7S1PTr0PY2pf6I+ZVEHeZq7P3+lAP53pCCuwjHO/ui7zwf6BoWaCNE0bF66a0; Received: from uucp by munchkin.clue.co.za with local (Exim 4.66) (envelope-from ) id 1HcEDf-00078x-Mh; Fri, 13 Apr 2007 05:21:11 +0000 Received: from cluetoy.clue.co.za ([10.0.0.19] helo=clue.co.za) by urchin.clue.co.za with esmtpa (Exim 4.66) (envelope-from ) id 1HcED1-0005mk-K7; Fri, 13 Apr 2007 05:20:31 +0000 Received: from localhost ([127.0.0.1]) by clue.co.za with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HcED5-0000IS-2S; Fri, 13 Apr 2007 07:20:35 +0200 To: Andrew Thompson , Peter Jeremy , freebsd-current@freebsd.org, brooks@freebsd.org From: Ian FREISLICH In-Reply-To: Message from Andrew Thompson of "Fri, 13 Apr 2007 09:09:58 +1200." <20070412210957.GA31864@heff.fud.org.nz> X-Attribution: BOFH Date: Fri, 13 Apr 2007 07:20:35 +0200 Message-Id: Cc: Subject: Re: CFT: new trunk(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2007 05:21:12 -0000 Andrew Thompson wrote: > On Thu, Apr 12, 2007 at 07:39:00AM +0200, Ian FREISLICH wrote: > > Peter Jeremy wrote: > > > On 2007-Apr-11 15:43:04 +0200, Ian FREISLICH wrote: > > > >Andrew Thompson wrote: > > > >> On Mon, Apr 02, 2007 at 11:17:29AM +0200, Ian FREISLICH wrote: > > > >> > We're making extensive use of vlans to increase the number of > > > >> > interfaces availabble to us using switches to break out gigE into > > > >> > 100M interfaces. The bandwidth problem we're having is to our > > > >> > provider, a 100M connection, and we're looking at doing exactly > > > >> > this. However, it appears that this interface can't trunk vlan > > > >> > interfaces. > > > =2E.. > > > >No, I'm sure I want it the way I said. I know it sounds wrong, but > > > >I just don't have enough PCI-X slots to waste 2 on physical 100M > > > >NICs for the uplink from the routers. > > > > > > Trunking is a way of combining multiple physical interfaces to increase > > > the bandwidth. Trunking multiple VLANs on a single interface doesn't > > > make sense to me. > > > > 802.1q is VLAN tagging and trunking. This interface is LACP - link > > aggregation. I really think that it makes no sense to be able to > > aggregate some ethernet interfaces and not others. I suppose some > > pedant will tell me vlan interfaces are not ethernet. > > I think the unfortunate name of trunk(4) that we inherited from OpenBSD > is causing quite some confusion. trunk(4) actually has nothing to do > with vlan trunking which I think you are after. > > I can see this topic coming up again so it could save some time to > rename the driver now. It would mean that we lose the naming link to the > same driver in OpenBSD but you cant win em all. > > Some names that have been suggested are: > > linkag(4) > agr(4) > bond(4) <- same as linux > > Any suggestions! I, for one don't find the name confusing. My correction above applied to Peter Jeremy's "Trunking multiple VLANs on a single interface doesn't make sense to me". The switches I have call this trunking in the manual and product sheet, but on the CLI the command to configure it is "channel". If you leave the name the same, it'll be easy to reuse documentation. Ian -- Ian Freislich