Date: Tue, 17 Dec 2013 12:11:49 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: dan_partelly <dan_partelly@rdsor.ro> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: 10-RC2 current wireless link aggregation not working correctly Message-ID: <CAJ-Vmomtv3EkVEFFssOttk0kH64ZHCvUEm%2BZjLx2LkXRMO7xKQ@mail.gmail.com> In-Reply-To: <1ec561b6d4357d782d46126f0a13443a@rdsor.ro> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> <CAJ-VmonwU6nySMPdtBcL2TpOH01av5sfvz=4Co28r%2BiWYH85Nw@mail.gmail.com> <52B08B28.6040402@allanjude.com> <1ec561b6d4357d782d46126f0a13443a@rdsor.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
Ive no idea sorry. Its likely an ifnet change and not anything WiFi specific. :( On Dec 17, 2013 12:04 PM, "dan_partelly" <dan_partelly@rdsor.ro> 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmomtv3EkVEFFssOttk0kH64ZHCvUEm%2BZjLx2LkXRMO7xKQ>