Skip to content
Snippets Groups Projects
Commit 56a74053 authored by Jakob Olsson's avatar Jakob Olsson
Browse files

docs: update DPP via Wi-Fi using libdpp

parent e96f535c
No related branches found
No related tags found
1 merge request!580Jo docs
Pipeline #159333 passed
......@@ -491,7 +491,7 @@ Similarily in the wireless UCI configuration, map-agent will generate the
`wifi-mld` section with the respective configuration.
```
config wifi-mld 'mld'1
config wifi-mld 'mld1 '
option ifname 'wlan0'
option sae_pwe '2'
option ssid 'IOWRT-MLO-SSID'
......@@ -1333,15 +1333,16 @@ For layer 3 setup guide see [here](./docs/layer3_ts.md).
### Wi-Fi QR COde based Onboarding
To enable URI generation and DPP chirping map-agent must have `dpp_uri` UCI
To enable URI generation and DPP chirping map-agent must have `dpp_chirp` UCI
configuration sections provided.
```
config dpp_uri
config dpp_chirp
option device 'wl1'
option band '2'
option ifname 'wl1'
list chan '81/1'
list chan '1'
list chan '11'
option type 'qrcode'
option chirp_interval '10'
......@@ -1349,7 +1350,7 @@ config dpp_uri
option device 'wl0'
option band '5'
option ifname 'wl0'
list chan '128/36'
list chan '36'
option type 'qrcode'
option chirp_interval '10'
```
......@@ -1363,62 +1364,19 @@ The URI's can be retreived from the UBUS API
```
root@eagle-44d43771bb20:~# ubus call map.agent dpp_enrollee_uri
{
"enrollees": [
{
"ifname": "wl0",
"band": 2,
"device": "wl0",
"uri": "DPP:C:128/36;M:44d43771bb2f;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgAD/ebYNHPhud+3C/t47dLffnPCzKAI3RYsr7z0zz5pSHQ=;;",
"type": "qrcode",
"chirp_interval": 10,
"num_chan": 1,
"chan": [
{
"channel": 36,
"opclass": 128,
"freq": 0
}
]
},
{
"ifname": "wl1",
"band": 1,
"device": "wl1",
"uri": "DPP:C:81/1;M:44d43771bb2e;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgAD5ANLCEXDDO7vnLVgSDoiJJ5H2Mo7aPXVriSVZ0ygP7M=;;",
"type": "qrcode",
"chirp_interval": 10,
"num_chan": 1,
"chan": [
{
"channel": 1,
"opclass": 81,
"freq": 0
}
]
}
]
"uri": "DPP:M:44d43771bb2f;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgAD/ebYNHPhud+3C/t47dLffnPCzKAI3RYsr7z0zz5pSHQ=;;",
}
```
Once DPP onboarding is complete, credentials are provided as ubus events that
are picked up by map-agent and written to its configuration and used for future
connections.
Once DPP onboarding is completed the credentials are written to the wireless and
map-agent configuration and an event is published over UBUS:
```
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-confobj-akm","data":"sae"} }
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-confobj-ssid","data":"MAP-44D43771BF50-BH-2.4GHz"} }
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-connector","data":"eyJ0eXAiOiJkcHBDb24iLCJraWQiOiI4MUNrdEdFNW5qTXBRSVJaUFVRT2M2dUNzZDd0MUd0ZHc5bGFFaHlETU5RIiwiYWxnIjoiRVMyNTYifQ.eyJncm91cHMiOlt7Imdyb3VwSWQiOiIqIiwibmV0Um9sZSI6Im1hcEFnZW50In1dLCJuZXRBY2Nlc3NLZXkiOnsia3R5IjoiRUMiLCJjcnYiOiJQLTI1NiIsIngiOiJNN1BOaG5xZnZRNzlJQl9vRXpXcGx6dldKXzJVR3l5SUxhSjVWYWdaUGlzIiwieSI6IkJrM0d6ZXkyQU5XWXdNOThZdGZIeUdVR2ZYR2NqZU9hUzRTYk50bXFrRWsifX0.1V96nYzO2TAl8CSEI7AwQE9C2Wybf-zgnaZVifzIATbCcAaPEmMbxUqdlIT754PXwoCKgdN8iTeJL7Siw6GVtQ"} }
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-confobj-pass","data":"313231356330393634303739386239346262303164656663653964656537376139396666386163366137643738313162366362653133626336653931653565"} }
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-c-sign-key","data":"3039301306072a8648ce3d020106082a8648ce3d030107032200031ae7f42438e80a1b3a65df7855eb945125afe371182aa5f052a43859707089c9"} }
{ "wifi.bsta": {"ifname":"wl1","event":"dpp-net-access-key","data":"307702010104205b06ffdcfb8af6c7904731ec74c84a2789c0c37c86f111499451781ed99c1b66a00a06082a8648ce3d030107a1440342000433b3cd867a9fbd0efd201fe81335a9973bd627fd941b2c882da27955a8193e2b064dc6cdecb600d598c0cf7c62d7c7c865067d719c8de39a4b849b36d9aa9049"} }
```
{ "map.agent": {"event": "dpp", "data": { "status":"success", "reason":"completed"} }}
Today, BSS Configuration Request, Response and Result are not implemented. Thus,
while it is possible to onboard and use dpp AKM, it is effectively not
supported due to the lack of possibility to set dpp as exclusive AKM on the bbss.
```
Additionally, this means legacy akms (i.e. sae, sae-mixed, psk2) will be the
preferred connection type used by map-agent.
Today only legacy akms (i.e. sae, sae-mixed, psk2) are supported.
NOTE: Currently, `wpa_supplicant` will prioritize scanning over chirping. This
means 5GHz is much less reliable as it will scan a larger number of channels and
......
This diff is collapsed.
......@@ -566,23 +566,23 @@
]
},
{
"section": "dpp_uri",
"section": "dpp_chirp",
"required": "no",
"description": "Values necessary for proper DPP bootstrap URI generation and chirping",
"description": "DPP Chirping configuration",
"multi": true,
"options": [{
"name": "device",
"type": "string",
"required": "no",
"default": "",
"description": "The radio of that of the corresponding interface that wpa_supplicant is running on."
"description": "The radio that the interface belongs to."
},
{
"name": "band",
"type": "integer",
"required": "yes",
"default": "Unknown (0x10)",
"description": "Band of the radio of the radio at which wpa_supplicant is running on."
"required": "no",
"default": null,
"description": "Band of the interface to chirp on (2/5/6)"
},
{
"name": "ifname",
......@@ -592,18 +592,11 @@
"description": "Interface name of the backhaul station interface."
},
{
"name": "chan",
"name": "channel",
"type": "list",
"required": "yes",
"default": "",
"description": "Channel opclass pair provided in the format of '<channel>/<opclass> used for the DPP bootstrap URI."
},
{
"name": "type",
"type": "string",
"required": "no",
"default": "qrcode",
"description": "Type of the URI (qrcode, pkex nfc). NOTE: Today only qrcode is supported."
"description": "Channel on which to chirp on. If multiple list entries, it will iterate through these channels at the interval provided as the chirp interval."
},
{
"name": "chirp_interval",
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment