path: root/wpa_supplicant/README-WPS
diff options
authorJouni Malinen <jouni.malinen@atheros.com>2009-06-10 12:53:35 (GMT)
committerJouni Malinen <j@w1.fi>2009-06-10 12:53:35 (GMT)
commit4625a47f4bb722710a5e622085ccd2b32ebaf6c9 (patch)
treeea04c050d96de1e25d6ac2ce23a007d4d86177e4 /wpa_supplicant/README-WPS
parenta5b73cc49d0b80ab388618b99ac8210f329daa8e (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.
Diffstat (limited to 'wpa_supplicant/README-WPS')
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.