1. Add a RequiresWifiNetwork type to the provider 2. Add API to the connectivity object to get the BSSID [1] 3. Pass the BSSID to the backends for them to use (plazes, localnet and skyhook) This would allow better error reporting (as in, we know it wouldn't work on wired LANs). For 3., we might also be able to pass lists of known BSSIDs, which might help with detection (or at least allow detecting location using WLAN data even though we're connected via a WWAN). Comments? [1]: This is easy with NetworkManager, as seen in nm-tool.
s/BSSID/AP MAC/
Created attachment 27050 [details] [review] 0001-Use-NetworkManager-to-export-the-AP-MAC-address.patch
Bastien: as discussed on chat change the BSSID logic and I think it's good for committing.
Looks good to me, I have pushed it into the master branch, Thanks for the patch
Forgot one detail, the code needs a slight change to use the currently associated AP MAC instead of just the strongest one (or the strongest of the associated AP signal, if there's multiple ones).
(In reply to comment #5) > Forgot one detail, the code needs a slight change to use the currently > associated AP MAC instead of just the strongest one. I think using the strongest one is a reasonable choice. You might be get better location results on that.
Fine then. Closing as the code already does that.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.