blob: 6496733735d4de2ca3aa36caed2615cabd2a1dc8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
|
Device Provisioning Protocol (DPP)
==================================
This document describes how the Device Provisioning Protocol (DPP)
implementation in wpa_supplicant and hostapd can be configured and how
the STA device and AP can be configured to connect each other using DPP
Connector mechanism.
Introduction to DPP
-------------------
Device provisioning Protocol allows enrolling of interface-less devices
in a secure Wi-Fi network using many methods like QR code based
authentication( detailed below ), PKEX based authentication etc. In DPP
a Configurator is used to provide network credentials to the devices.
The three phases of DPP connection are authentication, configuration and
network introduction.
Build config setup
------------------
The following changes must go in the config file used to compile hostapd
and wpa_supplicant.
wpa_supplicant build config
---------------------------
Enable DPP and protected management frame in wpa_supplicant build config
file
CONFIG_IEEE80211W=y
CONFIG_DPP=y
hostapd build config
--------------------
Enable DPP and protected management frame in hostapd build config file
CONFIG_IEEE80211W=y
CONFIG_DPP=y
Configurator build config
-------------------------
Any STA or AP device can act as a Configurator. Enable DPP and protected
managment frames in build config. For an AP to act as Configurator,
Interworking needs to be enabled. For wpa_supplicant it is not required.
CONFIG_INTERWORKING=y
Sample supplicant config file before provisioning
-------------------------------------------------
ctrl_interface=DIR=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
pmf=2
dpp_config_processing=2
Sample hostapd config file before provisioning
----------------------------------------------
interface=wlan0
driver=nl80211
ctrl_interface=/var/run/hostapd
ssid=test
channel=1
wpa=2
wpa_key_mgmt=DPP
ieee80211w=1
wpa_pairwise=CCMP
rsn_pairwise=CCMP
Pre-requisites
--------------
It is assumed that an AP and client station are up by running hostapd
and wpa_supplicant using respective config files.
Creating Configurator
---------------------
Add a Configurator over the control interface (wpa_cli/hostapd_cli)
> dpp_configurator_add
(returns id)
To get key of Configurator
> dpp_configurator_get_key <id>
How to configure an enrollee using Configurator
-----------------------------------------------
On enrollee side:
Generate QR code for the device. Store the qr code id returned by the
command.
> dpp_bootstrap_gen type=qrcode mac=<mac-address-of-device> chan=<operating-channel> key=<key of the device>
(returns bootstrapping info id)
Get QR Code of device using the bootstrap info id.
> dpp_bootstrap_get_uri <bootstrap-id>
Make device listen to DPP request (The central frequency of channel 1 is
2412) in case if enrollee is a client device.
> dpp_listen <frequency>
On Configurator side:
Enter the QR Code in the Configurator.
> dpp_qr_code "<QR-Code-read-from-enrollee>"
On successfully adding QR Code, a bootstrapping info id is returned.
Send provisioning request to enrollee. (conf is ap-dpp if enrollee is an
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>
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
values to the hostapd config file. If the enrollee is a client device,
these details can be automatically saved to config file using the
following command.
> save_config
To set values in runtime for AP enrollees
> set dpp_connector <Connector-value-printed-on-console>
> set dpp_csign <csign-value-on-console>
> set dpp_netaccesskey <netaccess-value-on-console>
To set values in runtime for client enrollees, set dpp_config_processing
to 2 in wpa_supplicant conf file.
Once the values are set in run-time (if not set in run-time, but saved
in config files, they are taken up in next restart), the client device
will automatically connect to the already provisioned AP and connection
will be established.
Self-configuring a device
-------------------------
It is possible for a device to configure itself if it is the
Configurator for the network.
Create a Configurator in the device and use the dpp_configurator_sign
command to get DPP credentials.
> dpp_configurator_add
(returns configurator id)
> dpp_configurator_sign conf=<ap-dpp|sta-dpp> configurator=<configurator-id>
Sample AP configuration files after provisioning
------------------------------------------------
interface=wlan0
driver=nl80211
ctrl_interface=/var/run/hostapd
ssid=test
channel=1
wpa=2
wpa_key_mgmt=DPP
ieee80211w=1
wpa_pairwise=CCMP
rsn_pairwise=CCMP
dpp_connector=<Connector value provided by Configurator>
dpp_csign=<C-Sign-Key value provided by Configurator>
dpp_netaccesskey=<Net access key provided by Configurator>
Sample station configuration file after provisioning
----------------------------------------------------
ctrl_interface=DIR=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
pmf=2
dpp_config_processing=2
network={
ssid="test"
key_mgmt=DPP
ieee80211w=2
dpp_connector="<Connector value provided by Configurator>"
dpp_netaccesskey=<Net access key provided by Configurator>
dpp_csign=<C-sign-key value provided by Configurator>
}
|
