On Sun, 2012-09-02 at 20:01 -0500, Larry Finger wrote: > On 09/02/2012 06:20 PM, Johannes Berg wrote: > > > > Just FYI -- that's not guaranteed if "iw scan" returns results, you'd > > have to run "iw scan passive" to make sure you pick up beacons rather > > than just probe responses. > > That is good to know. Unfortunately, 'iw wlan0 scan passive' run as an > unprivileged user results in "command failed: Operation not permitted (-1)". > When I run it as root, then I get "command failed: Operation not supported > (-95)". I am assuming that my version of iw (0.9.22) is not new enough. Seems like, though it's a bit strange that'd you'd get operation not supported. Not sure why that is. > When I run 'iwlist scan' in unprivileged mode, I did see the beacon, thus I got > the right answer. You can't run "iwlist scan" in unprivileged mode either, in this mode it'll just return the existing results list that is still there due to wpa_supplicant (or some other process) triggering a scan. If you want to check if you saw a beacon, you can run iw wlan0 scan dump -b and check if it prints "Information elements from Beacon frame:" for that AP. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html