From owner-freebsd-current@FreeBSD.ORG Tue Dec 17 17:58:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E3225E51 for ; Tue, 17 Dec 2013 17:58:26 +0000 (UTC) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C9CE21CBF for ; Tue, 17 Dec 2013 17:58:26 +0000 (UTC) Received: from [10.1.3.5] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id 221201A755F; Tue, 17 Dec 2013 12:58:26 -0500 (EST) Message-ID: <52B090C1.4040607@mail.lifanov.com> Date: Tue, 17 Dec 2013 12:58:25 -0500 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Allan Jude , freebsd-current@freebsd.org Subject: Re: 10-RC2 current wireless link aggregation not working correctly References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <52B08B28.6040402@allanjude.com> In-Reply-To: <52B08B28.6040402@allanjude.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 17 Dec 2013 17:58:26 -0000 On 12/17/13 12:34, Allan Jude wrote: > On 2013-12-17 10:54, Adrian Chadd wrote: >> Hi, >> >> The MAC of the lagg needs to be the same as the wireless interface. >> >> I'm going to just state right now that using lagg as the failover >> method for doing wireless/wired integration isn't supported by me. If >> someone wants to make it supported then they need to claim it. :) >> >> >> -a >> >> >> On 17 December 2013 05:06, dan_partelly wrote: >>> Hi all, >>> >>> I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as >>> described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. >>> >>> What happens is: >>> >>> If I boot the system with the Ethernet cable attached, I correctly get >>> lagg0 active port on master- bg0- and the network is working correctly. >>> (I mainly test pinging my gateway). When I pull the cable out, lagg0 >>> device correctly switches to wlan0 as shown by ifconfig (wlan0 is created >>> from wpi0), but at the same time I get no more ping replies from my >>> gateway. I can leave the system in this state for several minutes as an >>> example >>> and no replies are coming through. A simple list of interfaces with >>> ifconfig with no parameters brigs the network back to life, and I start to >>> get back the due ping replyes, this time thrugh wireless link. >>> >>> >>> Please, if possible en-light me on tis problem. I sat at your disposition >>> with any info you may deem necessary to get this fixed (if it needs a fix). >>> >>> >>> Dan >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > If I am am understanding correctly, Dan and Nikolai say that just > running 'ifconfig' brings the lagg back to life. Why would that make a > difference at all? Running ifconfig with no parameters shouldn't be > changing anything. > I see the same lagg behavior change going from 9.2->10.0, but for me the test is slightly different. My wired and wireless networks use different IP address ranges, so I need to re-run dhclient on lagg0, but I can't get an address on it. In fact, dhclient doesn't work at all with a lagg interface when it is only backed by my wireless card. Without a lagg interface, I can get addresses on both wired and wireless cards individually and act dual-homed just fine. - Nikolai Lifanov