I'm using wpa\_supplicant with `wpa_cli` and manually entering SSID and passphrase to connect to network works without problems.

When using `wpa_cli` with command `wps_pbc` it sees the WPS enabled access point and tries to connect but fails with

```
> wps_pbc
OK
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE-PBC 
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2Play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Authentication with xx:xx:xx:xx:xx:xx timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE-PBC 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE-PBC 
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Authentication with xx:xx:xx:xx:xx:xx timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1

```

Where `xx:xx:xx:xx:xx:xx` is the correct bssid of the access point.

I am guessing that the driver of the Raspberry Pi 3 Wi-Fi Chipset (BCM43438) doesn't support WPS-connections? Anyone knows how to get WPS running on the Pi 3?

Before Pi 3, I got WPS running on Raspberry Pi 2 with different external Wi-Fi sticks without problems.

When WPS authentication works (with external Wi-Fi sticks also on RPi-3) the wps\_pbc command output is this:

```
> wps_pbc
OK
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE-PBC 
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2Play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Associated with xx:xx:xx:xx:xx:xx
<3>CTRL-EVENT-EAP-STARTED EAP authentication started
<3>CTRL-EVENT-EAP-STATUS status='started' parameter=''
<3>CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1
<3>CTRL-EVENT-EAP-STATUS status='accept proposed method' parameter='WSC'
<3>CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected
<3>WPS-CRED-RECEIVED 
<3>WPS-SUCCESS 

```