From owner-freebsd-current@FreeBSD.ORG Tue Dec 17 20:11:50 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 5A791C9B for ; Tue, 17 Dec 2013 20:11:50 +0000 (UTC) Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1589916E0 for ; Tue, 17 Dec 2013 20:11:50 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id 1so5793978qec.9 for ; Tue, 17 Dec 2013 12:11:49 -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=la+aoT5/d6ch+Q36/oY5byLB/L/oY+0Nn4p6f8TNCQw=; b=ZgMINH88RnSict2hVYhtAcJ7Wgigm1SBmt2lLInuIVrU5wbIWMQktUln669c37TxB1 RP6sXIKMQ3xsIUQsYEkxe21OO3IswLDVmZ2jucODc/PYYL/Q66X2KWUN3uaDJkLTugd/ 3aUBDd76YMMlO2axFWHEslAD74HCmRoqt837CsdZsvtN+resA0FT1FHAAWxFoRHKjiMy f0WARK39iTKc1+Rxd7uZOBdDYgEjGlpe2hpyf4UzTtBpiXq3MzM2tHGySkkaWHliyOPy hKXwxO9XyOl+/0Sia+ZlUdQ0946az/HCeBtMN+yLvH7bWEUr8v+gE8r4To/SdcQ1xBm6 rd5g== MIME-Version: 1.0 X-Received: by 10.224.67.200 with SMTP id s8mr46161591qai.75.1387311109253; Tue, 17 Dec 2013 12:11:49 -0800 (PST) Received: by 10.224.53.200 with HTTP; Tue, 17 Dec 2013 12:11:49 -0800 (PST) Received: by 10.224.53.200 with HTTP; Tue, 17 Dec 2013 12:11:49 -0800 (PST) In-Reply-To: <1ec561b6d4357d782d46126f0a13443a@rdsor.ro> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <52B08B28.6040402@allanjude.com> <1ec561b6d4357d782d46126f0a13443a@rdsor.ro> Date: Tue, 17 Dec 2013 12:11:49 -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 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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 20:11:50 -0000 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 shouldn't be > > changing anything. > _______________________________________________ > 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" >