From owner-freebsd-current@FreeBSD.ORG Thu Aug 28 23:12:52 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CC901065670; Thu, 28 Aug 2008 23:12:52 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 97B518FC1E; Thu, 28 Aug 2008 23:12:51 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 765522BD96; Fri, 29 Aug 2008 11:12:50 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6Qb+Vy0BBcZ; Fri, 29 Aug 2008 11:12:46 +1200 (NZST) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Fri, 29 Aug 2008 11:12:46 +1200 (NZST) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id A9EC11142A; Fri, 29 Aug 2008 11:12:45 +1200 (NZST) Date: Thu, 28 Aug 2008 16:12:45 -0700 From: Andrew Thompson To: Daniel Eischen Message-ID: <20080828231245.GF98483@citylink.fud.org.nz> References: <20080828151006.GE98483@citylink.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.17 (2007-11-01) Cc: current@freebsd.org Subject: Re: How to use lagg and wlan together 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, 28 Aug 2008 23:12:52 -0000 On Thu, Aug 28, 2008 at 04:32:02PM -0400, Daniel Eischen wrote: > On Thu, 28 Aug 2008, Andrew Thompson wrote: > >> On Tue, Aug 26, 2008 at 11:41:20AM -0400, Daniel Eischen wrote: >>> I'm trying to get a lagg interface with failover to work with bfe0 >>> and wlan0. The master port is bfe0, with failover to wlan0. The >>> wlan0 interface is ath0. >>> >>> I can get both wlan0 and bfe0 to work independently without being >>> lagg devices, but only bfe0 works when wlan0 and bfe0 are in a >>> lagg interface. In other words, when I pull the plug on bfe0, it >>> does not failover to wlan0. >>> >>> $ ifconfig -a >>> ath0: flags=8802 metric 0 mtu 2290 >>> ether 00:11:f5:9d:54:f5 >> ^^^^^^^^^^^^^^^^^^^^^^^ >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>> status: associated >>> bfe0: flags=8843 metric 0 mtu 1500 >>> options=8 >>> ether 00:14:22:ae:bc:98 >>> media: Ethernet autoselect (100baseTX ) >>> status: active >>> lagg: laggdev lagg0 >>> lo0: flags=8049 metric 0 mtu 16384 >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 >>> inet6 ::1 prefixlen 128 >>> inet 127.0.0.1 netmask 0xff000000 >>> lagg0: flags=8843 metric 0 mtu 1500 >>> ether 00:14:22:ae:bc:98 >> ^^^^^^^^^^^^^^^^^^^^^^^ >>> inet 10.0.0.7 netmask 0xffffff00 broadcast 10.0.0.255 >>> media: Ethernet autoselect >>> status: active >>> laggproto failover >>> laggport: wlan0 flags=0<> >>> laggport: bfe0 flags=5 >>> wlan0: flags=8843 metric 0 mtu 1500 >>> ether 00:14:22:ae:bc:98 >> ^^^^^^^^^^^^^^^^^^^^^^^ >> >> I wonder if it becuase the lagg driver sets the mac address of all its >> interfaces to the same value, this has not been propagated back up to >> the ath0 interface. > > Ahh, I didn't notice this. > >> I wonder if this is the right way to do things. > > Well, it stops complaints on routers, and perhaps switches, > when an IP's MAC address changes. > > Or perhaps wlan (or any cloned device?) should relay the > MAC address change down to the lower level device? To verify this you could set the mac to the wireless interaces value, ifconfig lagg0 ether 00:11:f5:9d:54:f5 ifconfig lagg0 down/up Andrew