path: root/wpa_supplicant
diff options
authorJouni Malinen <jouni.malinen@atheros.com>2009-06-10 12:53:35 (GMT)
committerJouni Malinen <j@w1.fi>2009-11-22 18:15:54 (GMT)
commit321a1b7081eb3d1859ffec0b0602c8d35081d8c3 (patch)
treee5a55133401d3e63691e15c49b77f1f2c1091e19 /wpa_supplicant
parentc01609d10e3e4206f269a64d1a5905737885d774 (diff)
WPS: Change wpa_supplicant wps_reg to not send out M8
Since we do not currently support changing the AP settings received from M7, there is no point in actually sending out the M8 that would likely trigger the AP to reconfigure itself and potentially reboot. For now, we just receive the AP settings in M7 and add a local network configuration block based on those, but NACK the message. This makes wps_reg work like wps_pin, but by using the AP PIN instead of a client PIN. (cherry picked from commit 4625a47f4bb722710a5e622085ccd2b32ebaf6c9)
Diffstat (limited to 'wpa_supplicant')
1 files changed, 6 insertions, 1 deletions
diff --git a/wpa_supplicant/README-WPS b/wpa_supplicant/README-WPS
index 7fd358d..6b826a7 100644
--- a/wpa_supplicant/README-WPS
+++ b/wpa_supplicant/README-WPS
@@ -131,13 +131,18 @@ negotiation which will generate a new WPA PSK in the same way as the
PIN method described above.
-If the client wants to operation in the Registrar role to configure an
+If the client wants to operate in the Registrar role to configure an
AP, wpa_supplicant is notified over the control interface, e.g., with
wpa_cli wps_reg <AP BSSID> <AP PIN>
(example: wpa_cli wps_reg 02:34:56:78:9a:bc 12345670)
+This is currently only used to fetch the current AP settings instead
+of actually changing them. The main difference with the wps_pin
+command is that wps_reg uses the AP PIN (e.g., from a label on the AP)
+instead of a PIN generated at the client.