aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/README-WPS
diff options
context:
space:
mode:
authorJouni Malinen <j@w1.fi>2009-09-06 10:58:15 (GMT)
committerJouni Malinen <j@w1.fi>2009-09-06 10:58:15 (GMT)
commit52eb293dd25aec61cf0ada27c073b04fde15e563 (patch)
tree58f33176d8e0f2449873e15eecbafde174d258ed /wpa_supplicant/README-WPS
parente6965d4e5daf00f5d7910fbade1681e0e6ad85e2 (diff)
downloadhostap-52eb293dd25aec61cf0ada27c073b04fde15e563.zip
hostap-52eb293dd25aec61cf0ada27c073b04fde15e563.tar.gz
hostap-52eb293dd25aec61cf0ada27c073b04fde15e563.tar.bz2
WPS: Add support for AP reconfiguration with wps_reg
wpa_supplicant can now reconfigure the AP by acting as an External Registrar with the wps_reg command. Previously, this was only used to fetch the current AP settings, but now the wps_reg command has optional arguments which can be used to provide the new AP configuration. When the new parameters are set, the WPS protocol run is allowed to continue through M8 to reconfigure the AP instead of stopping at M7.
Diffstat (limited to 'wpa_supplicant/README-WPS')
-rw-r--r--wpa_supplicant/README-WPS24
1 files changed, 18 insertions, 6 deletions
diff --git a/wpa_supplicant/README-WPS b/wpa_supplicant/README-WPS
index 6b826a7..2b1ded0 100644
--- a/wpa_supplicant/README-WPS
+++ b/wpa_supplicant/README-WPS
@@ -131,17 +131,29 @@ negotiation which will generate a new WPA PSK in the same way as the
PIN method described above.
-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
+If the client wants to operate in the Registrar role to learn the
+current AP configuration and optionally, to configure an AP,
+wpa_supplicant is notified over the control interface, e.g., with
wpa_cli:
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.
+This is 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.
+
+In order to change the AP configuration, the new configuration
+parameters are given to the wps_reg command:
+
+wpa_cli wps_reg <AP BSSID> <AP PIN> <new SSID> <auth> <encr> <new key>
+examples:
+ wpa_cli wps_reg 02:34:56:78:9a:bc 12345670 testing WPA2PSK CCMP 12345678
+ wpa_cli wps_reg 02:34:56:78:9a:bc 12345670 clear OPEN NONE ""
+
+<auth> must be one of the following: OPEN WPAPSK WPA2PSK
+<encr> must be one of the following: NONE WEP TKIP CCMP
Scanning