现在的位置: 首页 > 综合 > 正文

WPS support in NM (client mode)

2018年04月16日 ⁄ 综合 ⁄ 共 1156字 ⁄ 字号 评论关闭

Simple push-button (PBC) support

The most simple is push-button support, it could look like this:

WPS-mockup.png

The AP name is obtained from the WPS scan results (see new versions of iw for how to parse this).

Then once the button on the AP is pushed, wpa_supplicantsends an event
WPS-AP-AVAILABLE-PBC.
At that point, the scan results are checked (akinwpa_cli scan_results) whether the selected BSS containsWPS-PBC, like this:

00:1d:7e:4a:a1:ab       2432    69      [WPA2-PSK-TKIP+CCMP][WPS-PBC]   jo

If it does, the button "Connect withWPS" becomes available.
When pressed, we do the equivalent ofwpa_cli wps_pbc 00:1d:7e:4a:a1:aband wpa_supplicant does the
rest, finally connecting to the network. We then obtain the network key from wpa_supplicant's network config stanzaand save it. Alternatively, we could do
wps_cred_processing=1 and then connect to the network once we have the credentials.

/!\ This is how I got it working, I think it's supposed to work the other way around, you dowpa_cli wps_pbc <BSSID>
first, then it probes the AP until the AP enables PBC. The other way around works for me as well, but how do you discover that the AP is ready?

PIN mode

Cf. for example
http://kb.netgear.com/app/answers/detail/a_id/39
. The odd thing is that for instance my AP claims to support PIN (or is this not discoverable?!?) but there's nowhere in the web interface to enter the client's PIN.

抱歉!评论已关闭.