On Fri, Dec 18, 2015 at 12:13:49PM GMT, Raf Czlonka wrote: > On Thu, Dec 17, 2015 at 12:38:59PM GMT, Stuart Henderson wrote: > > > So the only new issue I have with this diff is with manual scans > > (as I mentioned before, but now with logs) - the scan runs and > > ifconfig displays the expected output (at the point around where 'scan > > finished' is logged, marked with > in the paste below), the radio > > status LED remains flashing (expected as there's nothing to change the > > LED state until it associates), it keeps logging 'received beacon', > > and won't reassociate. > > Exactly the same behaviour here on: > > iwn0 at pci3 dev 0 function 0 "Intel WiFi Link 5100" rev 0x00: msi, MIMO > 1T2R, MoW
And on another one: iwn0 at pci1 dev 0 function 0 "Intel WiFi Link 1000" rev 0x00: msi, MIMO 1T2R, BGS > > "ifconfig iwn0 -chan" clears this and lets me re-associate (re-inits > > the device; ifconfig down+up clears it as well but -chan is less > > disruptive as dhclient stays running that way). So I do have a usable > > workaround. > > This fixes it here as well - thanks for the tip Stuart! On this one, I had to run the command twice - first time it "stuck" and had to kill it, the second time it worked as above. > > I'm not quite sure what's different between the automatic scans when > > looking for a network to associate with, and the manually triggered > > ones. > > My /etc/hostname.iwn0 runs a script which uses 'scan' and that works > fine - no idea why manual one is "special". > > Other than that, it seems to be working fine - tested briefly on > 'eduroam' with Aruba AP 214. > > Regards, > > Raf > > P.S. I've noticed that new snapshots are now built with the patch :^) Working fine so far - only tested on a home Virgin Media-branded Super Hub (Netgear) router/AP. Raf
