From owner-freebsd-current@FreeBSD.ORG Fri Dec 20 17:17:24 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 876F5BD6 for ; Fri, 20 Dec 2013 17:17:24 +0000 (UTC) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4211616DF for ; Fri, 20 Dec 2013 17:17:24 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id cy11so2669308qeb.27 for ; Fri, 20 Dec 2013 09:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nyZM4aFPT04HOaxkAjoKXVeQOG2dxpt14fjRPWovVhA=; b=dOF8ZwF5tc7gWXRJ+fCdNVxDf+1Uy38B+aZVtl2lLCQsB0yiKz7QG8/Zh7ljy5sg5y G6gBFU/OfVTaSwQF2xNqD2sfaszr+9kmF5EJ2aRsbZVYW3Mt1pPznliCLxe/LcyKAa+y Ad3fPJ+1Een6qgpC4PHd3nNumBaHXEDX67a4uH0y6+ySLHIRPbTZJBKLPKwwS2g3hRvr 5Rlg7HDBajJ86C74zodWHMNj3B0C4T5+EOqSY1qTXHU4JONF+RXC/04EPqYb8b8brSM2 7Fo6KO5c3f4Rn/QZSfxgqit2GSMTXdpxJOBdjhLRz9b8/3tdbwNv1djmfOunaymHIJ3e y4Dg== MIME-Version: 1.0 X-Received: by 10.224.46.8 with SMTP id h8mr16061403qaf.49.1387559843476; Fri, 20 Dec 2013 09:17:23 -0800 (PST) Received: by 10.224.53.200 with HTTP; Fri, 20 Dec 2013 09:17:23 -0800 (PST) In-Reply-To: <17b8e16e956514f8f1383b61821ac3dc@rdsor.ro> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <52B08B28.6040402@allanjude.com> <1ec561b6d4357d782d46126f0a13443a@rdsor.ro> <17b8e16e956514f8f1383b61821ac3dc@rdsor.ro> Date: Fri, 20 Dec 2013 09:17:23 -0800 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: Fri, 20 Dec 2013 17:17:24 -0000 Hi! On 20 December 2013 01:52, dan_partelly wrote: > Guys, > > > Id like to work a bit on this issue in my free time, I have 2 weeks > holiday > after Xmass. > > First an update on lagg for the case you boot with wired coupled: > > 1. I previously said lagg0 switches correctly when I unplug the wired > interface, but it is not so. It appeared so because I used "ifconfig" > and listed all interfaces. If I do a ifconfig lagg0 specifically > the network activity DOES NOT resume, and the output shows that the > interface was not switched. > 2. network activity resumes when you specifically do ifconfig bge0 ( > master wired). Hm. Well, doing an ifconfig bge0 will likely do a bunch of queries to the NIC to figure out what the current link status is. I bet what's happening is that the link status isn't being updated correctly, so lagg doesn't flip over. > > Second: > > 1. Please tell me if one of the developers made on their personal pages > a intro how to set up a solid kernel development intro. It would save me > a lot of time considering I never set up such an environment for > any Unix like OS. I only worked in kernel development for NT and later > derived kernels. I can allocate two core 2 machines for this task , with > fire-wire, USN and Ethernet connectivity > > 2. Any other resources which you can come up from your head which I can > print and read are also appreciated. Have a read of the FreeBSD handbook: https://www.freebsd.org/doc/handbook/ And if you have questions about the networking side of things, please don't hesitate to email the list(s). We can turn whatever question/answers you have into a chapter or two in the handbook. -a > Dan > > > On Tue, 17 Dec 2013 12:11:49 -0800, Adrian Chadd > wrote: >> Ive no idea sorry. Its likely an ifnet change and not anything WiFi >> specific. :( On Dec 17, 2013 12:04 PM, "dan_partelly" wrote: >> >> Yes, this is correct. A simple list of the interfaces with ifconfig >> makes the system recover and restart activity on the secondary port. >> Its a good starting point to hunt down the problem. One of the ioctls >> sent >> has this "side effect". >> >> Dan >> >> > 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 shouldnt be >> > changing anything. >> _______________________________________________ >> freebsd-current@freebsd.org [2] mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current [3] >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org [4]" >> >> >> Links: >> ------ >> [1] mailto:dan_partelly@rdsor.ro >> [2] mailto:freebsd-current@freebsd.org >> [3] http://lists.freebsd.org/mailman/listinfo/freebsd-current >> [4] mailto:freebsd-current-unsubscribe@freebsd.org