WPS with wpa_supplicant dbus control interface
Wed Apr 8 06:54:53 PDT 2009
On Tue, 2009-04-07 at 13:36 +0200, Jaime Soriano Pastor wrote:
> I'm trying to use the dbus control interface of wpa_supplicant to
> connect to a WPS access point without any success.
> I could connect using the command line interface, with PIN and PBC
> modes, specifying always the bssid.
> The only options I'm setting using dbus are:
> - "ssid" set to the network ssid or "bssid" set to the AP MAC
> - "key_mgmt" set to WPS
> - "phase1" set to "pbc=1" or "pin=<pin>"
> Is it ok?
You can pretty much push whatever you would have put in a network block
through the dbus interface, though there are some oddities related to
handling binary data vs. strings, which the config file solves by using
quotes (or not using quotes).
> When sending the network information using dbus, are credentials also
> internally handled as especified by wps_cred_processing default
While I'm not completely aware of how the WPS processing works
internally, everything you send for the network config via the dbus
interface gets pushed to the wpa_supplicant network block pretty much
the same as it would be if you used a config file instead.
> And I'm also having problems to detect if a network is WPS enabled or
> not when scanning. Is it possible to know it using only dbus calls?
> I have seen that command line control interface receive WPS related
> events, but only WpsCred seems to be sent to dbus.
You'll get a "wpsie" entry in the returned BSSID properties dict that
contains any scanned WPS IE that the AP sends out. Not entirely sure
what version of wpa_supplicant that showed up in, but it's in 0.6.x head
More information about the Hostap