nvidia-shield-controller-driver icon indicating copy to clipboard operation
nvidia-shield-controller-driver copied to clipboard

Unable to connect to P2P interface on wpa_cli

Open SkyBladeCloud opened this issue 3 years ago • 0 comments

Hello all,

I understand the P2P connection itself might not really be within the scope of the project (as it's not part of the driver presented in this repository), however, I have been unsuccessful when trying to connect my 2015 Shield Controller wirelessly to my Linux PC and I was hoping I could get some support here, to eventually be able to use the Ozwpan driver as well.

My system:

Ubuntu 20.04.2 Linux 5.10.18-051018-generic Intel AX200 WiFi (it supports P2P-GO) wpa_supplicant v2.9

I can add the P2P group no problem:

5: p2p-wlp4s0-0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 68:54:5a:18:2d:76 brd ff:ff:ff:ff:ff:ff

However, when attempting to run wpa_cli commands on it I get:

Could not connect to wpa_supplicant: p2p-wlp4s0-0 - re-trying

Thus, I can't pair my controller. I've been trying with different wpa_supplicant versions and at one point I could connect to the P2P interface. However, upon issuing "wps_pbc", it would stay at "WPS-PBC-ACTIVE" until timing out, with the controller still flashing. In this case, I could see connection attempts in the wpa_supplicant log (referencing the correct MAC from the controller), but they were apparently ignored with a "no valid beacon" message.

Stucked in this situation I would like to ask: has anyone managed to use the controller in a similar system? Any more pointers?

Thank you very much and kind regards!

SkyBladeCloud avatar Jun 12 '21 21:06 SkyBladeCloud