Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    This looks a bit like wpa_supplicant and the driver don't match, and the first tries to use operations the second doesn't support. The "association request to driver failed" followed by a "associated" message certainly looks wrong. Are you sure it's an incorrect key? What happens if you disable_network the offending network with wpa_cli? (BTW, do wpa_cli help, the man-page doesn't contain all commands). Commented Dec 4, 2017 at 15:16
  • 1
    @dirkt I'm sure because I run the same code with a correct password and it works. My current solution for case user enters wrong password with the above behavior is to use timeout on the whole process. If I could more quickly detect a wrong password I could lower the wrong password scenario from 85 seconds to 45 seconds. So yes I know the password is wrong because I'm purposely testing that scenario, correct password works fine. Commented Dec 4, 2017 at 15:21
  • Does the CTRL-EVENT-DISCONNECTED event show up in wpa_cli? Can you try to add a wrapper to /sbin/wpa_action (or modify it directly) and in this way catch the event/ Commented Dec 5, 2017 at 13:54
  • Take a look at w1.fi/wpa_supplicant/devel/ctrl_iface_page.html you should be able to use ``` wpa_ctrl_attach()``` to detect your CTRL-EVENT-DISCONNECTED event. Commented Dec 9, 2018 at 15:26