WPS with wpa_supplicant dbus control interface

Jaime Soriano Pastor jsoriano
Wed Apr 15 07:22:01 PDT 2009

On Tue, Apr 14, 2009 at 6:15 PM, Jouni Malinen <j at w1.fi> wrote:
> On Tue, Apr 14, 2009 at 10:40:22AM -0400, Dan Williams wrote:
>> What's the usage for 'any' in all the added calls? ?What would the flow
>> look like when using 'any' instead of a real BSSID? ?I tend to think we
>> should probably use ff:ff:ff:ff:ff:ff:ff there instead of 'any' since it
>> really should be a MAC address. ?But does the normal config file stuff
>> accept 'any' for those options?
For the dbus interface implementation for WPS I just copied the
behaviour of the control interface. Anyway, "any" doesn't collide with
any valid BSSID, and "ff:ff:ff:ff:ff:ff:ff" can still be used.

> The ctrl_iface calls use 'any' to indicate a mode where the user did not
> select any particular AP and just asked WPS to be completed with any
> available AP. In other words, the UI is free to either make the user
> select the BSS based on scan results (in which case the BSSID is known
> and should be passed to wpa_supplicant) or allow the user to request WPS
> negotiation with automatic AP selection (i.e., do need to show the scan
> results to the user and just pass 'any' as the BSSID to make
> wpa_supplicant find a suitable AP).
As I see in wps_supplicant.c, wpas_wps_add_network() does the same for
both cases (bssid=NULL and bssid='ff:ff:ff:ff:ff:ff'), it isn't? But
for 'ff:ff:ff:ff:ff:ff' it loops over the scan results looking for an
AP with this bssid (that is not going to find).

Should I use NULL bssid when 'ff:ff:ff:ff:ff:ff' is received as I do
with 'any' now?

More information about the Hostap mailing list