Ive no idea sorry. Its likely an ifnet change and not anything WiFi specific. :( On Dec 17, 2013 12:04 PM, "dan_partelly" <dan_parte...@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-unsubscr...@freebsd.org" > _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
