On Thu, Oct 03, 2019 at 01:46:40PM -0700, Ben Greear wrote: > Someone reported to us that their APs would not answer our station's probe requests > because there is a zero-length Mesh ID element in it. Do you know which AP that is? It sounds like it would not be compliant with the IEEE 802.11 standard.. > It appears that supplicant is adding it in the wpa_supplicant_mesh_add_scan_ie > call. > > Is this actually supposed to be called when the station is not a mesh station? As far as the standard is concerned, the Mesh ID element is present in Probe Request frames whenever mesh support is activated (dot11MeshActivated is true). However, this is needed to discover active mesh BSSs even when the local device is not yet configured to enable or join a mesh. As such, there is not really any convenient way of dynamically deciding when the element should be added. So yes, that function is indeed supposed to be called if wpa_supplicant is built with CONFIG_MESH=y. In theory, it would be nice to reduce the length of the Probe Request frames by two octets if there is no need to discover any mesh BSS. However, without an explicit runtime configuration of that, there is no easy way of doing that. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
