Unable to initiate WPS

I have read the documentation and googled extensively but, when I try to initiate WPS (via CLI), I always receive a response of “FAIL”. Nobody else seems to have this issue, so what am I doing wrong?

I only want to enable this temporarily as it is the only way I know to connect a doorbell camera that I obtained for free and need to “hack”.

> uci show wireless | grep wps
wireless.wifinet6.wps_pushbutton='1'

> hostapd_cli wps_pbc
Selected interface 'phy1-ap3'
FAIL

wifinet6 == phy1-ap3

I have tried on both a Turris Omnia (OpenWRT 23.05.3) and TP-Link Archer C7 (OpenWRT 23.05.2). On each, and per the instructions, I installed hostapd-utils and replaced the stock wpad-basic-mbedtls with the full-featured version (I tried both wpad and wpad-mbedtls).

I have 4 WLANs on each radio. I tried configuring the single WLAN of interest with the option wps_pushbutton '1' as well as setting it on all WLANs on that radio (per a suggestion I found), but same result.

I’ve tried adding other wps_… options, rebooting, and everything in between, but same result. I don’t see anything relevant in the syslog, and can’t find a way to increase verbosity for hostapd. I’ve even looked at the source code for hostapd_cli which didn’t really help.

I also tried the physical button on the TP-Link and have seen reports of people successfully using the CLI on the Omnia. So what's wrong in my case?

Any thoughts?

Arw you sure pushbutton is enabled in config/wireless for phy1-ap3, likely a 5ghz device?
Highly recommended to use more remarkable than auto-generated name.

Please post output of

ub&s call system board
cat /etc/config/wireless
iwinfo {remove MAC addresses,}

cleanin passwords, changing AP names to ABC etc, and removing 2nd halgf¡ (f mac and ip addresses.

Thanks for the interest, @brada4. I actually just figured it out through the course of providing the info you requested.

The issue was that the SSID cannot be hidden.

I didn't realize that it was required to be visible as not a single reference I found stated that it needed to be. While it isn't immediately intuitive as to why it would need to be visible, I suppose it makes sense as I believe the client is using the ESSID to associate rather than the BSSID, thus needs to be seen by the client.

I now get a response of "OK". Now I'll go actually try to connect the device and then disable WPS afterward.

Thanks again.

Hidden SSID just makes all clients ever connected to it broadcast SSID for eternity.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.