From owner-freebsd-current@FreeBSD.ORG Mon Apr 2 09:28:32 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 8E85416A401 for ; Mon, 2 Apr 2007 09:28:32 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 2D57013C457 for ; Mon, 2 Apr 2007 09:28:32 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 93C351CC58; Mon, 2 Apr 2007 21:28:30 +1200 (NZST) Date: Mon, 2 Apr 2007 21:28:30 +1200 From: Andrew Thompson To: Ian FREISLICH Message-ID: <20070402092830.GB28809@heff.fud.org.nz> Mail-Followup-To: Andrew Thompson , Ian FREISLICH , freebsd-current@freebsd.org References: <20070330011354.GE97061@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Cc: 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: Mon, 02 Apr 2007 09:28:32 -0000 On Mon, Apr 02, 2007 at 11:17:29AM +0200, Ian FREISLICH wrote: > Andrew Thompson wrote: > > Here is a patch to add OpenBSD's trunk(4) interface, and also includes > > LACP support which came from agr(4) on NetBSD. Im interested in anyone > > who wants to test this and in particular lacp mode if you have a switch > > that supports it. > > > > http://people.freebsd.org/~thompsa/if_trunk-20070330b.diff > > This looks very interesting. I'm busy testing with a switch that > claims 802.3ad support. > > 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. It sounds like you want it the other way around. The trunk should be the lowest component in any setup so you should vlan the trunk interface rather than trunk a vlan. ifconfig trunk0 create ... ifconfig vlan0 vlan 10 vlandev trunk0 (or use ifconfig trunk0.10 create which is a better syntax) regards, Andrew