Hello. I need help please. I have a ZBTLink WE 1326 computer with a mt7621 processor. I want to activate WPS through the rear button and I can't do it.
Wpad and Hostapd-utils are already installed.
The equipment is reset by pressing and releasing the rear button once.
How can I configure the button so that it associates and works with WPS?
At one point, the entire population of the planet believed that the Earth was flat, it didn't make it right.
After a little googling, I believe you can repurpose reset button to initiate the WPS mode for a specific WiFi. How good are you with SSH, editing files on the router and shell scripting?
Hello, thanks for the answer. I also think you can reprogram the reset button. I'm getting started on the subject, but I think I can edit files with the help of Google, of course. Thanks.
Hello. Thank you very much for the instructions. These were carried out and we are currently like this.
Uninstalled WPAD-basic-wolfssl. There was no WPAD-MINI.
WPAD and Hostapd-utils installed
Additionally, kmod-button-hotplug was installed
When trying to connect to the WIFI network, we are suggested to press the WPS button. We press it but the equipment does not send the password to the laptop.
The content of the reset file was deleted in /etc/rc.button/reset and the indicated was placed:
The equipment no longer performs the reset when pressing the button and it does not go to factory settings if it is pressed for 8 seconds.
By placing in the console the instruction: logread -f
and release the button. It is noted
the indication of button press, WPS activation and button release.
I hope you have understood me. Concluding the laptop does not receive the password that the WIFI equipment must send and thus proceed to the connection.
Thank you very much for the help, I think it is missing just a little.
Just for reference, it is not secure, as noted by the very article you linked -- 3rd paragraph reads:
A major security flaw was revealed in December 2011 that affects wireless routers with the WPS PIN feature, which most recent models have enabled by default. The flaw allows a remote attacker to recover the WPS PIN in a few hours with a brute-force attack and, with the WPS PIN, the network's WPA/WPA2 pre-shared key (PSK).[2] Users have been urged to turn off the WPS PIN feature,[3] although this may not be possible on some router models.[4]
That is why OpenWrt (and most other) router OS's no longer include (default) support for it. Obviously there is still a need in some situations where a wifi client device can only use WPS for configuration. This is really the only reason to use this now-deprecated technology. Fortunately, it looks like the OP may have a path to a solution.
After replacing wpad, it is necessary to fully reboot for the new version to start running.
Try activating WPS manually from the console by running the command: hostapd_cli wps_pbc
If this throws an error message, determine the problem. If it works and starts a WPS handshake, then something is wrong with the button script.
WPS-PBC is only secure if your neighbors aren't waiting for you to press the button.
Hello, thanks for answering, the hostapd_cli wps_pbc command was placed on the console, according to your recommendation, the results are displayed on the screen.
The password is not received from the equipment as proof of initiation of the WPS exchange process. The laptop stays waiting like this.
I don't know what happens. It will be because my operating system is Linux-Zorin. It is that I have tried with Huawei AP and the WPS has worked well against my laptop. Thanks for the help.
@vizoso the instructions I've seen recommend picking just one WiFi interface to have option wps_pushbutton '1'.
To test if it's working properly, I'd recommend you delete the option wps_pushbutton '1' from the config wifi-iface 'default_radio1' and also changing the SSID for that interface to something like ETECSA_PRUEBA5g. Then try to use the WPS console command while trying to connect to ETECSA_PRUEBA.
Also, don't forget to restart wifi after making changes in the config file and before trying.
The protocol is not secure. And it has been deprecated as a result.
of course. You do use it at your own risk. And that's fine if you are comfortable with that risk. But I think it makes sense to ensure that the risks are documented and known to those who choose to use this technology -- each user can make an informed decision. I personally would advise against it and I'd never use it on my own networks. However, I recognize that there are some devices out there that have WPS but no other means of being setup... so in those cases, obviously enabling WPS becomes a necessity.