1) I should clarify the aim of my patch.<br> - This is a pacth for hostapd.<br> - This patch make hostapd to be connectable by Windows 7 supplicant<br> with WPS PBC.<br> - My patch changes a process of AP in Enrollee mode but this is not<br>
a patch for AP in Enrollee mode. This is because broken Windows<br> supplicant requires M1 message.<br><br>2) I have gotten new test plan.<br>I have used very old Wi-Fi test plan v 1.6. Now, I have a newest one<br>v 2.0.3. The v 2.0.3's test 4.1.1 says "check M2 message". Thus, now<br>
my patch does not affect the test because my patch changes only M1<br>message. And 4.1.2 checks only config methods attribute of probe<br>response, not M1. So, my patch doesn't affect to Wi-Fi certification.<br><br>> but it is strictly against the WPS specification<br>
> and would make the AP fail some certification tests. <br><br>Which test do you mean ? I found an Wi-Fi certified AP which sends<br>M1 message same as my patch. The AP which can connect to Windows 7<br>supplicant with WPS PBC. The AP is CG-WLR300NM. The AP's Config<br>
Methods attribute (0x1008) in M1 message enables PushButton method<br>same as my patch.<br><br>Regards,<br><font color="#888888"><font color="#888888">Masashi Honma.</font></font><br><br><br><div class="gmail_quote">2011/4/18 Masashi Honma <span dir="ltr"><<a href="mailto:masashi.honma@gmail.com">masashi.honma@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><div>> but it is strictly against the WPS specification and would make the<br>> AP fail some certification tests.<br>
<br></div></div>I see. The test 4.1.1. requires config method without PBC.<div class="im"><div><br>
<br>> What kind of use cases would this AP be used for?<br>
<br></div></div>I expected connection of AP+Registrar (i.e. without external Registrar) and<br>Enrollee (Enrollee is just STA, not AP). The AP has only PBC method<br>because it is a headless device. The physical device of the AP has only a push<br>
button and some LEDs.<br>
<br>
I will try to find out better way.<br><br>Regards,<br><font color="#888888"><font color="#888888">Masashi Honma. <br><br></font></font><div><div></div><div class="h5"><br><div class="gmail_quote">2011/4/16 Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Tue, Apr 12, 2011 at 12:00:09PM +0900, Masashi Honma wrote:<br>
> The Windows 7 has it's own supplicant (not wpa_supplicant). If I<br>
> configured the hostapd as only WPS PBC capable AP (i.e.<br>
> "config_methods=push_button" in hostapd.conf), the Windows 7<br>
> supplicant could not connect to the hostapd. Because the Windows 7<br>
> supplicant popped up PIN input dialog.<br>
><br>
> The attached patch solves this issue.<br>
<br>
</div>Well, it may work around a completely broken WPS discovery mechanism in<br>
Windows, but it is strictly against the WPS specification and would make<br>
the AP fail some certification tests. Then again, support of PIN method<br>
is mandatory in those tests, too. What kind of use cases would this AP<br>
be used for? Only to work as a Registrar and only allow use of PBC to<br>
connect Enrollees to the network? I.e., no support for use of PIN from<br>
a label or for entering an Enrollee PIN.<br>
<font color="#888888"><br>
--<br>
Jouni Malinen PGP id EFC895FA<br>
_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com" target="_blank">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>