From owner-freebsd-current@FreeBSD.ORG Wed Dec 18 07:48:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62980AA1 for ; Wed, 18 Dec 2013 07:48:44 +0000 (UTC) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2129010E0 for ; Wed, 18 Dec 2013 07:48:43 +0000 (UTC) Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4]) by mail.rdsor.ro (Postfix) with ESMTP id 0560415D8C; Wed, 18 Dec 2013 09:48:43 +0200 (EET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Wed, 18 Dec 2013 09:48:49 +0200 From: dan_partelly To: Subject: Re: 10-RC2 current wireless link aggregation not working correctly In-Reply-To: <52B15124.10409@delphij.net> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <52B08B28.6040402@allanjude.com> <52B0F40B.7020501@delphij.net> <0906290ad6b5e6c9f9bd181130c606c3@rdsor.ro> <52B15124.10409@delphij.net> Message-ID: <986189d1401785fb4fba49d324fd7137@rdsor.ro> X-Sender: dan_partelly@rdsor.ro User-Agent: RoundCube Webmail/0.4-beta Cc: freebsd-current@freebsd.org 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: Wed, 18 Dec 2013 07:48:44 -0000 I guarantee you that a simple interface list with ifconfig un-stucks the net on my setup, at lest in the case (master is wired, unplug ethernet, fail to wireless) I agree that it doesn't makes much sense, but no matter how unlikely it seems, it is a **fact**. > > I don't believe in merely doing 'ifconfig' would workaround the issue, > it does not make sense, plus I have tested and it didn't work for my > case (iwn+em on my laptop). > > I'm aware of the issue but thought it was compatibility issue with my > own weirdly setup wireless AP at the time, and looks like it's not > just me, but I'm not interested nor have time to fix the problem so I > replied the thread and offered what I have tested as a workaround in > the hope that it's useful for someone who is interested and have the > ability to fix the problem. > > Cheers, > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJSsVEkAAoJEJW2GBstM+nswTsP/Rs0hdyXNejf2Z98GbSGns0n > lsI+UmjwWUSg0h+8QzCce7/80mwEw0tZH1btoRr6I0tPKXwdUYDO2C3LPM2a/jSV > hvN6aay0ppnldtsqMZcuDv1OznSGfEIt0A04/m/RUTDBYaPKY+F1iqZYNE960zes > u6mbR2elpAUCHjpV3lEchnP5V1v/yLpVziGYabR4WLwohtlOMGVbL92ejLAeKVnr > Ar7SiWA7GVar6lSGBWyyGwoErveb8TaZxRiSKgjHuvciMLgy+KrlyxqZq6gNd7nP > isBDMEe2NsnUawR/gfcxvvzpyHTPYPtSlEJjejdbnGlP4YGy5BT2vm3HqyAgK/iX > N1iRBhx8zuH9UDNN8XiSuvuYuxAw9OfeBoh/2aGifj5dcrEP+IeyYUoAWBoXgny+ > IcoitmUwYE4xLduLnIpf2b5KG8Yw1r2bKoZJVOw8+ixJAqCWR0xXONcywB56MXoE > 8r9A11D6ASdRmozKjcEQH9+j6/4VuVeydCBfXQSZHIlVL3pTFZAlH0Q0JSZq4NXA > Pb5YGcdYDONi3gPxNIvUn1WeqTfpgJhGveKV5PhI3NY2d+GEB3fBBuBhvlAlrwxg > CPCqH4YC0sntvqMqcOooz44OfiLpB1ARGGTwtKATLNIzpS/iMsS1swW1NZEeaN19 > uFZw/dY3w5uhDQ7u2Buc > =4ByJ > -----END PGP SIGNATURE----- > _______________________________________________ > 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"