Date: Wed, 11 Apr 2007 15:43:04 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Andrew Thompson <thompsa@freebsd.org>, freebsd-current@freebsd.org Subject: Re: CFT: new trunk(4) Message-ID: <E1Hbd6G-0000LG-MX@clue.co.za> In-Reply-To: Message from Andrew Thompson <thompsa@freebsd.org> of "Mon, 02 Apr 2007 21:28:30 %2B1200." <20070402092830.GB28809@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Thompson wrote: > 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. 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. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Hbd6G-0000LG-MX>