From owner-freebsd-current@FreeBSD.ORG Tue Dec 17 16:43:10 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 29C5FA99 for ; Tue, 17 Dec 2013 16:43:10 +0000 (UTC) Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB5B215BE for ; Tue, 17 Dec 2013 16:43:09 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id nd7so5472857qeb.31 for ; Tue, 17 Dec 2013 08:43:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=pwDNPt5hnBGRl72Q3aZVbw1dJZ+fhVkwT1ZLuKOo9kQ=; b=V3xWvZ2twhZ/LJ0jcjf38RqPQQRp4HY27DuNesKQeLnD3kCQgpHhKrkvMkDLxihYSH eyMHnnUI5NUQpJmLpDFdVS3mxZHDxdAhDVwbSJiysncB0cPR+pKWf9DoBMjN2oeGw0bu etOY7fBo3AyJbwPSsYUpeaD4F8AVzQsfYFsqSuLiU3Is7+ZMeT8n5vfMx1LXceyi95Ti Bp4Oj26yIHInuoT+PLYqj7muTVujJDy8PM8Lpdz40oqkN3LENkEoxCIK6gFY+bOHPF64 Z9Soc3wU+/fPsNcJilmpCljDjo0UVSnPhGiAPR206DjtTihUaUFV/hnlr1UYM6b185MP j/qw== MIME-Version: 1.0 X-Received: by 10.224.24.194 with SMTP id w2mr34326946qab.48.1387298589137; Tue, 17 Dec 2013 08:43:09 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Tue, 17 Dec 2013 08:43:09 -0800 (PST) In-Reply-To: <0bd233d9a6af0ef79cbd5c74c99a9ad5@rdsor.ro> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <0bd233d9a6af0ef79cbd5c74c99a9ad5@rdsor.ro> Date: Tue, 17 Dec 2013 08:43:09 -0800 X-Google-Sender-Auth: f3ZDaguLwJSQ4HpL22XP3McVUoc Message-ID: Subject: Re: 10-RC2 current wireless link aggregation not working correctly From: Adrian Chadd To: dan_partelly Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current 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 16:43:10 -0000 I'm the wireless stack maintainer and I currently don't support that. Sorry. -a On 17 December 2013 08:10, dan_partelly wrote: > On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd > wrote: >> Hi, > > All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the > MAC of > wpi0. Lagg0 is set up to the MAC of master. So everything checks out. All > are the same. > > I have to check if the systems sends packets to the gateway after the > switch on wlan0, > but fails to get any packets back. I didnt had time yet for this. > >>> If someone wants to make it supported then they need to claim it. :) > > Who from the FreeBSD team supports it ? > > Dan > > > >> >> 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"