> I am trying to use connmanctl to connect via WPS_PIN entry.
Latest git code is not able to connect. ( pushbutton works though)
> connmanctl> agent on
> Agent registered
> connmanctl> connect wifi_0016ea684dcc_496e7370697265_managed_psk
> Agent RequestInput wifi_0016ea684dcc_496e7370697265_managed_psk
> Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
> WPS = [ Type=wpspin, Requirement=alternate ]
> WPS PIN (empty line for pushbutton)? 12345678
WPS PIN is checked for valid checksum in WPA Supplicant. So you can't use
anything as WPS PIN. You can check wps_generate_pin() function to generate
valid WPS PIN.
I agree that any 8-digit number cannot be used as PIN but
wpa_supplicant does not perform the checksum verification when it
receives the request from ConnMan to start WPS-PIN session, however
most of the common APs do perform such a verification. Therefore, in
Harish's case, the external AP is probably who is refusing the
connection because of the invalid PIN.
Just to make a quick example, in an scenario with a devices acting as
AP by means of wpa_supplicant and another one acting as STA using
wpa_supplicant + ConnMan, you will WRONGLY be able to get them
connected using the same toy PIN 12345678. All of this, because of
wpa_supplicant does not perform any verification on the PIN.
> Agent ReportError wifi_0016ea684dcc_496e7370697265_managed_psk
> Agent request cancelled by ConnMan
> Error /net/connman/service/wifi_0016ea684dcc_496e7370697265_managed_psk: Operation
> Can anyone please inform if this is not yet implemented properly in connman?
Yes, it is already implemented and it works. However, current
implementation is not compliant with WFA WPS Technical Specifications,
we have been working on a new implementation to make it compliant and
we will send new version hopefully soon.