DPP: Mention ssid and pass parameters for DPP_AUTH_INIT in documentation
These parameter use hexdump values over the control interface, so mention them in the DPP example documentation. Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
4cab417af0
commit
6c2f70cc6a
1 changed files with 3 additions and 1 deletions
|
@ -118,7 +118,9 @@ On successfully adding QR Code, a bootstrapping info id is returned.
|
||||||
|
|
||||||
Send provisioning request to enrollee. (conf is ap-dpp if enrollee is an
|
Send provisioning request to enrollee. (conf is ap-dpp if enrollee is an
|
||||||
AP. conf is sta-dpp if enrollee is a client)
|
AP. conf is sta-dpp if enrollee is a client)
|
||||||
> dpp_auth_init peer=<qr-code-id> conf=<ap-dpp|sta-dpp> configurator=<configurator-id>
|
> dpp_auth_init peer=<qr-code-id> conf=<ap-dpp|sta-dpp> ssid=<SSID hexdump> configurator=<configurator-id>
|
||||||
|
or for legacy (PSK/SAE) provisioning for a station Enrollee:
|
||||||
|
> dpp_auth_init peer=<qr-code-id> conf=sta-psk ssid=<SSID hexdump> pass=<passphrase hexdump>
|
||||||
|
|
||||||
The DPP values will be printed in the console. Save this values into the
|
The DPP values will be printed in the console. Save this values into the
|
||||||
config file. If the enrollee is an AP, we need to manually write these
|
config file. If the enrollee is an AP, we need to manually write these
|
||||||
|
|
Loading…
Reference in a new issue