From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Q: iw - how to scan for a specific ssid / AP mode scan
Date: Fri, 03 Jul 2015 18:51:55 +0200 [thread overview]
Message-ID: <5596BDAB.4020001@neratec.com> (raw)
Folks,
I have difficulties using iw for a specific use case or fail to understand the
documentation correctly.
My platform is a recent OpenWRT, running ath9k.
First use case is scanning for a given ssid in managed mode. According do iw's
documentation (and the attribute description in nl80211.h), issuing
iw dev wlan0 scan flush ssid <SSID>
should do exactly this, but I keep receiving a full list of visible APs. I double
checked that NL80211_SCAN_FLAG_FLUSH and NL80211_ATTR_SCAN_SSIDS are set
correctly, so am puzzled whether there is some bug left or I miss some detail.
The second issue is about scanning in AP mode. Where I want to go is having two
APs operating on arbitrary DFS channels with periodic scans to discover each
other. What I observe is
a) passive scanning: iw dev wlan0 scan flush ap-force passive
=> does not work - no scan results are provided
b) active scanning: iw dev wlan0 scan flush ap-force
* finds only a subset of APs compared to a scan in managed mode
* finds only APs on non-DFS channels
Again, I might be missing some relevant documentation, but to me the observed
results look rather like 'not yet implemented' than inherent limitations.
Any hint / feedback is appreciated.
Thanks,
Zefir
next reply other threads:[~2015-07-03 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 16:51 Zefir Kurtisi [this message]
2015-07-03 18:38 ` Q: iw - how to scan for a specific ssid / AP mode scan Johannes Berg
2015-07-06 8:31 ` Zefir Kurtisi
2015-07-13 8:18 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5596BDAB.4020001@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).