Description of problem: When wpa_supplicant is started with -u switch (dbus mode), both wpa_cli and wpa_gui fail to connect to it. Version-Release number of selected component (if applicable): wpa_supplicant-gui-0.6.3-5.fc9.i386 wpa_supplicant-0.6.3-5.fc9.i386 How reproducible: Always. Steps to Reproduce: 1. Start wpa_supplicant service, making sure -u flag is used 2. Try to start wpa_cli or wpa_gui Actual results: wpa_cli v0.6.3 Copyright (c) 2004-2008, Jouni Malinen <j> and contributors ... Could not connect to wpa_supplicant - re-trying Expected results: wpa_cli and wpa_gui should have the switch (same -u?) to be able to talk to wpa_supplicant over dbus interface instead of default socket interface. Additional info:
Hmm; you may want to ensure that the right bits are in /etc/wpa_supplicant/wpa_supplicant.conf about ctrl_interface? They should be there by default, what does yours have in it, and what does "ps ax | grep wpa" show when the service is started? This isn't intentional, you should be able to at least talk to it with the socket control interface if -u is used.
Debugged it further. It appears that it's not "-u" flag that prevents the socket control from functioning. The pass/fail condition matrix is as follows: "-ieth1 -u" works fine "-ieth1" works fine "-u" : socket control doesn't work, supplicant works. "" : supplicant doesn't start at all, either -i or -u option must be present. So it used to work before because I had "-ieth1" in my /etc/sysconfig/wpa_supplicant. Switching to NetworkManager I saved my old config and used the default one provided by rpm package instead, which has no "-i" flag. Perhaps some glitch in startup code that skips part of initialization when started without -i?
Analysed the source code. wpa_supplicant considers config files (given by -c options) per interface. If no -i option is given, no config file is read. Global control interface file name is taken either from config file, or from -C/-g command line option, with no built-in default. The global control interface can ONLY be given through -g option, since there's NO global config file. This also means that for global config file, no group control is possible (ctrl_interface_group). Usually wpa_supplicant refuses to start unless at least one -i is specified. However, if -u is present, it will start and disregard any config files. Considering the above, it might not be a real bug, but just a not very intuitive set of command line options that is also adequately documented. Man page specifically fails to mention the fact that in certain cases the -c option will have no action, or the limitations of global control interface. Some of that information is present in wpa_supplicant/README in source code, but that file is not %doc'd in RPM build (another generic README with no useful information is %doc'd instead). My recommendation: at least update the spec to %doc the proper README, and update the man page to mark the options which are per-interface and are ignored in "externally controlled" mode.
Created attachment 308313 [details] Add a proper README file to docdir Replace README with %{name}/README in %doc, so wpa_supplicant README is included instead of hostap top-level stub.
Created attachment 308314 [details] Man page update highlighting per-interface options.
These patches got pushed upstream, right? ISTR something like this going past on the hostap mailing lists. If that's correct, I'll pull in the git commits that Jouni did. Thanks for the debugging!
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Fedora 25: wpa_cli , with or without the -i parameter gives the same error message, that it could not connect to wpa_supplicant. Verified that wpa_supplicant daemon is running..