Xperia Z device cannot detect ath9k device after a SCAN operation

[silverjam]

Issue by silverjam from Thursday Apr 03, 2014 at 17:03 GMT
Originally opened as cozybit/wpa_s_mesh_android#24

---

> Also, we did some test regarding scanning using ath9k device. The ath9k
> device uses the same wpa_supplicant as Xperia Z.
> Now, the ath9k device is operating an MBSS on channel 44 and transmit beacon
> frames. Then, Xperia Z orders scanning. However the ath9k deivce is not
> found by the Xperia Z. Looking at wireshark OTA signal capture result,
> Xperia Z transmited Probe Request frames as orderd. However, ath9k device
> does not respond with Probe Response.
> We suspect wpa_supplicant does not set how to respond to probe request
> frames.
> FYI, these 2 devices can establish mesh peering and communicate each other,
> if MESH_GROUP_ADD is issued at both devices.

[chunyeow]

For your information, we have a patch to limit the response to probe request to avoid the flooding of those frames in our mesh network but this is done in mac80211 not wpa_supplicant:
http://www.spinics.net/lists/linux-wireless/msg111464.html

So when doing the scanning, the following command should be used "iw mesh0 scan meshid"
http://www.spinics.net/lists/linux-wireless/msg106661.html

[bcopeland]

Isn't this bug fixed by using the wildcard meshid in the probe req?

[silverjam]

@bcopeland Maybe, I haven't had a chance to test yet.
@chunyeow OK, but we need to be able to scan from wpa_supplicant, the idea is to percolate these meshids up to the java layer-- are you saying we need to add a new type of scanning to wpa_s?

[chunyeow]

This patch should allow us to do active scanning with wildcard mesh id:
218b493

Otherwise, wpa_supplicant only relies on passive scanning which could be missed during the scanning process.

[bcopeland]

On Mon, Apr 28, 2014 at 01:17:06AM -0700, Chun-Yeow wrote:

This patch should allow us to do so with active scanning with wildcard mesh id:
218b493

Otherwise, wpa_supplicant only relies on passive scanning which could be missed during the scanning process.

Yes, to clarify I had already made a similar patch in the
wpa_s_mesh_android repository a few weeks ago, which solved it
in my testing.

Bob Copeland %% www.bobcopeland.com