From owner-freebsd-current@FreeBSD.ORG Wed Apr 11 19:15:00 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 6F19E16A4D5 for ; Wed, 11 Apr 2007 19:15:00 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id DB0C413C455 for ; Wed, 11 Apr 2007 19:14:59 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l3BJEpuJ004241; Thu, 12 Apr 2007 05:14:51 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l3BJEoaT004240; Thu, 12 Apr 2007 05:14:50 +1000 (EST) (envelope-from peter) Date: Thu, 12 Apr 2007 05:14:50 +1000 From: Peter Jeremy To: Ian FREISLICH Message-ID: <20070411191450.GE815@turion.vk2pj.dyndns.org> References: <20070402092830.GB28809@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.14 (2007-02-12) 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: Wed, 11 Apr 2007 19:15:00 -0000 --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. 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. BTW, you might like to study the fine print for whichever trunking protocol you are using. At least some of the proprietary protocols are fairly dumb and just round-robin MAC addresses between the physical links rather than dynamically sharing traffic across the available links. The former means that if most or all of your traffic is for a single MAC address, you don't actually gain anything by having multiple physical links. --=20 Peter Jeremy --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGHTOq/opHv/APuIcRAlwlAJ9aw2Vhus9e8lfuy/KcpDFDT7+qPgCaA8P1 RrXNAyFCesr8JYEbKm7MegA= =ZgOE -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--