WPS Button Activation is required

Right... just to be clear, I'm not saying you personally (or others with similar situations) shouldn't use WPS. I just want to make sure that people are aware that the technology is not secure, and that it does carry some risk if enabled.

In situations where WPS is optional, it would be advisable to avoid it. Where it is necessary, it is best to ensure that users do have knowledge about the potential risks as well as the idea that there are some possible mitigation strategies (such as isolated networks) that they can consider.

-> psherman

With my two models of boxes that I have it's not an option it is not possible otherwise

I understand that. As I said...

Hello, I still can't activate the WPS mechanism. The equipment does not send the password to the PC in order to establish the connection.

Through the hostapd_cli -i wlan0 wps_pbc command, we were able to activate the wps service.


The WPS service will be active for two minutes. This was checked using the command. hostapd_cli -i wlan0 wps_get_status


At the end of the WPS section, the following is displayed on the console.


Something is happening between the computer and the laptop that there is no successful exchange.


Sorry, I don't know enough about WPS to provide further help, my intention was to help you map WPS trigger to a reset button.

Hello, ok thank you very much for everything.

Not an expert on those, but maybe experimenting with different flavours of wpad/hostapd might help. I can't imagine WPS being broken in OpenWrt period.

Hello, thank you very much for the advice. I tried the variants of WPAD and HOSTAPD-UTILS, but we didn't get positive results, so we must continue testing and research. Thank you very much for the help.

There's a developers mailing list (links should be in the wiki), you may want to post there, detailing packages installed, your /etc/config/wireless file and the CLI command you invoke to see if you get a better response there.

Like I said, I can't imagine WPS being broken in OpenWrt, it's probably a misconfiguration or a missing configuration.

Hello, thank you very much for your help. I'll do what he tells me. Greetings.


There's additional information on WPS is available in wiki: https://openwrt.org/docs/guide-user/network/wifi/basic#wps_options

I'd experiment with some of these options and maybe even downgrade encryption to psk vs psk2.

Hello, I varied the modulations as you told me and I did not get any results. I am looking for information in the place where you indicated me. Thanks.

Well, actually you are supposed to know the 8-digit pin code and enter it to the dialog on the client device, and send it to the router to confirm that the device is legit...
The router does not send it. It waits for it :wink:

Typically the OEM PIN is written to the printed label and is stored in the OEM settings. But that is not used. OpenWrt does not read the pin code set in the OEM firmware, as the location and storage style of the code varies so much and as WPS is seen as insecure. (I have programmed my own community builds to read the OEM PIN in R7800 and WNDR3700 , but I am not actively using WPS. See How to read TP-Link factory wireless pin from flash - art - #2 by hnyman )

You need to set wps_pin option, 8 numbers, to the WiFi interface config. Just set it to whatever your like. (And possibly also set wps_label method option to 1)

Otherwise your WPS experiments look good.

for the WPS all my devices do not use a PIN code but only the method of the 2 WPS buttons ...

The laptop screenshot by @vizoso shows the PIN entering dialog, so the laptop is apparently not using the pushbutton method, but instead it uses the label PIN.

if I translated correctly

If you receive ciphered passwords to access the wireless network , ETECSA

alternatively you can connect by pressing the WPS button on your router

In the picture it is key WIFI - ETECSA ??? or WPS button