From owner-freebsd-current@FreeBSD.ORG Fri Apr 13 16:49:30 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 325ED16A409 for ; Fri, 13 Apr 2007 16:49:30 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 95E9013C469 for ; Fri, 13 Apr 2007 16:49:29 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 7768 invoked from network); 13 Apr 2007 16:14:12 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 13 Apr 2007 16:14:12 -0000 Message-ID: <461FB498.4030407@freebsd.org> Date: Fri, 13 Apr 2007 18:49:28 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Andrew Thompson References: <20070411191450.GE815@turion.vk2pj.dyndns.org> <20070412210957.GA31864@heff.fud.org.nz> In-Reply-To: <20070412210957.GA31864@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , Ian FREISLICH , brooks@freebsd.org, freebsd-current@freebsd.org 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 16:49:30 -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! lacp(4)++ -- Andre