query regarding ctrl_iface for WPS PIN method

Abbhishek Misra abhishekfishy2000
Thu Sep 19 04:58:00 PDT 2013

Hello All,

I guess it will be ok not to scan and determine bssid from ssid instead one
could use 'any' in the above call.

I do not think that is going to cause any conflict as either user would be
providing PIN or supplicant will randomly generate it and that will easily
resolve which AP we wish to connect.

This however raises another question
Why is there a provision to provide bssid at all?


On Thu, Sep 19, 2013 at 4:58 PM, Abbhishek Misra <
abhishekfishy2000 at gmail.com> wrote:

> Hello All,
> I'm new to this list please don't mind my ignorance, will soon catch up
> with acceptable standards.
> I wish to understand following
> Why the control interface for pin method expects used to provide BSSID?
> static int wpa_cli_cmd_wps_pin(struct wpa_ctrl *ctrl, int argc, char *argv[])
> {
> 	if (argc == 0) {
> 		printf("Invalid WPS_PIN command: need one or two arguments:\n"
> 		       "- BSSID: use 'any' to select any\n"
> 		       "- PIN: optional, used only with devices that have no "
> 		       "display\n");
> 		return -1;
> 	}
> 	return wpa_cli_cmd(ctrl, "WPS_PIN", 1, argc, argv);
> }
> I was expecting that user would be providing SSID and associated PIN.
> Please help me understand why bssid is needed, here.
> I'm working on user interface that requests human user to provide ssid, do you recommend that one should do a scan and determine bssid for the provided ssid and then use this interface.
> --
> Regards
> Abhishek Misra

Abhishek Misra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20130919/1229a328/attachment.htm>

More information about the Hostap mailing list