From owner-freebsd-current@FreeBSD.ORG Thu Apr 12 05:39:09 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 4114816A402 for ; Thu, 12 Apr 2007 05:39:09 +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 108C813C43E for ; Thu, 12 Apr 2007 05:39:08 +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:cc:From:Subject:In-Reply-To:X-Attribution:Date:Message-Id; b=sqfOzYCsZYtR7LDk3F90Z17lPJ1bntI0se8XuEU4PGjZ5mV2tpOb5liv+lnu/NgKNj8MO/FyIoTuF32LRM2w57AlIOgn4tqHsA6hGsaR8gzeHN5/bMGRldye70qnEbPfSL12IvWWn/hFkrgD492YjDPRw2oqI/HXIJjdUlUWLzeKMJVJnYRFgejhLqC+UpQNPTQiIL2znuTkQ2/XUUrW/7y1nj5rEcg8y/1oAusbjred4WQKr3orplQk/yBcIcuF; Received: from uucp by munchkin.clue.co.za with local (Exim 4.66) (envelope-from ) id 1Hbs1U-00025m-6h; Thu, 12 Apr 2007 05:39:08 +0000 Received: from dsl-241-41-27.telkomadsl.co.za ([41.241.41.27] helo=clue.co.za) by urchin.clue.co.za with esmtpa (Exim 4.66) (envelope-from ) id 1Hbs1J-0007Na-OU; Thu, 12 Apr 2007 05:38:57 +0000 Received: from localhost ([127.0.0.1]) by clue.co.za with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Hbs1M-000FWA-7Z; Thu, 12 Apr 2007 07:39:00 +0200 To: Peter Jeremy From: Ian FREISLICH In-Reply-To: Message from Peter Jeremy of "Thu, 12 Apr 2007 05:14:50 +1000." <20070411191450.GE815@turion.vk2pj.dyndns.org> X-Attribution: BOFH Date: Thu, 12 Apr 2007 07:39:00 +0200 Message-Id: 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: Thu, 12 Apr 2007 05:39:09 -0000 Peter Jeremy wrote: > > --HcAYCG3uE/tztfnV > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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 believe that the appropriate configuration for you is to have a > single VLAN within one of your GigE links for traffic to your > provider. Within the switch you assign that VLAN to multiple 100M > ports which are then trunked to the provider. This means that your > switch needs to understand trunking but FreeBSD doesn't. This is the configuration I'm going to be testing with our provider this morning because FreeBSD can't do link aggregation on VLAN interfaces. I'm hoping that not having IP data available to the switch will not prevent it from working in our scenario. Ian -- Ian Freislich