From owner-freebsd-current@FreeBSD.ORG Fri Apr 13 14:23:12 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 EE65516A400; Fri, 13 Apr 2007 14:23:12 +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 B711613C465; Fri, 13 Apr 2007 14:23:12 +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:From:Subject:In-Reply-To:X-Attribution:Date:Message-Id; b=zQ7Bowo3YILgWiWwq3r5Qb9EjrqDmP1v4EXwaxCjhWyBBfbEhwaygwZDO/IMklYd/xnyQ4zJfGu4QOwEFDRisO5LsDLebgr6eIcHdHAYrzn8I1/61G6wNnhXH1LRKx6xgnBR0HxSf3+MEjzR34dquSvlccSKBx/Aini70NL3F82+CD19LbK+5f9eq2Gz+bA19UWG/NPwfbAR6JcQSQhODqWKuk39TouuAWCqYtqkGBl6licgXTLa5F17l/lavMdh; Received: from uucp by munchkin.clue.co.za with local (Exim 4.66) (envelope-from ) id 1HcMgC-0004cd-95; Fri, 13 Apr 2007 14:23:12 +0000 Received: from cluetoy.clue.co.za ([10.0.0.19] helo=clue.co.za) by urchin.clue.co.za with esmtpa (Exim 4.66) (envelope-from ) id 1HcMg2-0001GJ-SQ; Fri, 13 Apr 2007 14:23:02 +0000 Received: from localhost ([127.0.0.1]) by clue.co.za with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HcMg1-0001Qf-OP; Fri, 13 Apr 2007 16:23:01 +0200 To: Andrew Thompson , freebsd-current@freebsd.org From: Ian FREISLICH In-Reply-To: Message from Ian FREISLICH of "Mon, 02 Apr 2007 11:17:29 +0200." X-Attribution: BOFH Date: Fri, 13 Apr 2007 16:23:01 +0200 Message-Id: Cc: Subject: Re: CFT: new trunk(4) [results] 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 14:23:13 -0000 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. The trunk(4) device establishes LACP with the (nasty) smitch that I have using my testbed. It also appears to utilise both links I put in the trunk. The setup is as follows: rl0: flags=8843 metric 0 mtu 1500 options=8 ether 00:50:bf:09:67:8b media: Ethernet autoselect (100baseTX ) status: active trunk: trunkdev trunk0 rl1: flags=8843 metric 0 mtu 1500 options=8 ether 00:50:bf:09:67:8b media: Ethernet autoselect (100baseTX ) status: active trunk: trunkdev trunk0 trunk0: flags=8843 metric 0 mtu 1500 ether 00:50:bf:09:67:8b media: Ethernet autoselect status: active trunk: trunkproto lacp trunkport rl1 =1c trunkport rl0 =1c vlan300: flags=8843 metric 0 mtu 1496 ether 00:50:bf:09:67:8b inet 10.0.0.210 netmask 0xffffff00 broadcast 10.0.0.255 media: Ethernet autoselect status: active vlan: 300 parent interface: trunk0 All is well even when one of the links goes down. The moment I plug the wire back in, the link may or may not continue working depending on which link the switch decides to send the traffic down. If I disconnect the other link, it starts working again until I plug it back in. This is not the way things behaved when I tested this switch with a Cisco 6509 at our provider's premises yesterday. When one wire has been unplugged and then plugged back again the trunk is left in the following state: trunk0: flags=8843 metric 0 mtu 1500 ether 00:50:bf:09:67:8b media: Ethernet autoselect status: active trunk: trunkproto lacp trunkport rl1 =18 trunkport rl0 =1c I'm not sure if this is a feature of the NICs I'm using (I know they're junk) or a bug in the switch or a bug in the trunk driver. I don't think it's the switch because this test worked when it was connected to the Cisco 6509. I don't have access to the cisco any more. If I remove and then re-add the "bad" trunk port, it starts working again. Ian -- Ian Freislich