> > Do you see any *kernel* messages after this? I'm half expecting to see > > that the beacon never arrives, or something like that? > > The kernel log is repeated. The next log line is again scanning start, > since NetworkManager (or wpa_supplicant, I'm not familiar with the machinery > involved) request scan again.
Ok, that's interesting. > > Are the hotels running similar equipment perhaps? If rebooting the AP > > helps then perhaps the APs aren't actually beaconing quite properly - > > maybe you could put the card into sniffer mode (monitor mode) and > > capture what's going on over the air for a bit after this happened? > > Can you give some more specific comments please? We just rebooted the > AP the next time, it all started working again, and I need to install > all the necessary tools while it is working ;) Since I'm not familiar > with wifi machinery, maybe you can give me specific command lines to > run? :) Oh, well, there's some information here: https://wireless.wiki.kernel.org/en/users/documentation/iw iw wlan0 set type monitor iw wlan0 set channel X ip link set wlan0 up tcpdump -i wlan0 -s0 -w /tmp/dump could capture this on another machine. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
