wpa_cli interactive mode - "automatic" connect try
 

After few detours I have managed to actually run wpa_cli in "interactive " mode.

When it runs it always does this:

But at one time only it did this.
Run "automatically " trying to "connect" - three times.
I did expected failure to connect, but it NEVER run this way again.

The question is - I like to find out why.

It may be impossible for anyone to answer that question. Both raspi-config and wpa_cli work on my headless pi but its configuration is basically the same as the original installation. While raspi-config was designed to quickly configure the system after install there is no reason it can't be used whenever but it depends on how you changed its setup.

You have mentioned in your previous threads that you are trying to create a menu to diagnose wifi connections. I don't remember if anyone has asked why but that it might be easier said then done. All I can gather from your post is that it appears that wpa_supplicant has stopped for some reason.

There are several reasons for me writing my own "raspi-config -DEBUG ".
I was initially looking for single command to activate WiFi.
That turned out to be a pipe dream. There are at least four very basic commands to accomplish that. So it became a pain for slow typist like me to keep at the keyboard. So I used "raspy-config" as a template to create menu driven bash script. Never wrote one before !
Initially I used "read only " status commands. In the process learned few things about writing script.

Then I run into a snag trying to make "interactive" script. While at that I went thru rasip-config "WiFi setup" to discover how "they" use "wpa_cli" and how there are no real feedbacks in setting up WiFi.
That is where "I need to know HOW it works" came from.

At this point I finally got my RPi WiFi cooperating with crosscompling my "real" app.

I am convinced that even advanced "users" have very little knowledge about HOW RPi WiFi is configured and why. They commonly refer to somewhat obsolete "official" procedures and as long as it works they do not care.

Nothing wrong with such "attitude" , as long as they are happy.

I on the other hand appreciate few things I have learned. I do not claim I know it all, but I would say that "wpa_supplicant" appears to be a service , managed by wpa_cli or wpa_gui.

Its starting is defined, its run is temperamental ( case of "3 tries and you are out" I posted, flaky "interactive" etc. ) and its termination non existent - reboot required.

you can simply gather those commands in a script.
not as elegant as a "menu driven", but easier nevertheless.

that sure sounds like a bug, or in any case something that should be brought to developers' and maintainers' attention.
if you do, make sure you can back it up with facts.