diff --git a/.gitignore b/.gitignore index 22d6729..78045ef 100644 --- a/.gitignore +++ b/.gitignore @@ -5,3 +5,4 @@ src/Makefile.Release src/wpa-cute doc/manpage.links doc/manpage.refs +doc/*.html diff --git a/doc/wpa-cute.html b/doc/wpa-cute.html deleted file mode 100644 index 9142efd..0000000 --- a/doc/wpa-cute.html +++ /dev/null @@ -1,307 +0,0 @@ - -
wpaCute is a graphical Qt front end program for interacting - with wpa_supplicant. It's used to query current status, change - configuration and request interactive user input.
It supports (almost) all of the interactive status and - configuration features of the command line client, wpa_cli. Refer - to the wpa_cli man page for a comprehensive list of the interactive - mode features.
wpaCute is a fork from wpa_gui, shipped with wpa_supplicant - version 2.6
Specify the interface that is be configured.
- Without -i choose the first interface found in the socket path
- which start not with 'p2p-dev-' otherwise the last found interface is chosen.
Set an independent update interval in seconds for the signal - strength meter.
This value must be a positive integer. Without -m the
- signal meter is only updated at each status update.
- See also the notes about polling and pinging.
Force not to use QSocketNotifier, use only polling. - It's more for testing purposes.
Change the path where control sockets should - be found.
Run program in the quiet mode - do not display tray - icon pop-up messages.
Start program in the system tray only (if the window - manager supports it). By default the main status window is - shown.
Unset setting - Disable network after "WRONG_KEY"
This a workaround to a wpa_supplicant quirk where he endless tries to
- connect to a wrong configured network. There are cases where it is a good idea,
- but I believe it is mostly annoying due to it's implementation. If I'm wrong,
- use -W to have the original behavior. By default will now a
- network disabled after a "WRONG_KEY" message.
-
On systems where QSocketNotifier is not supported is wpa_supplicant only - polled to fetch status changes. -
One ambitious development goal was to drop the need for Polling & Pinging - on systems where QSocketNotifier is supported. But it turned out that this - was a road to ruin due to the lack of some 'Status Has Changed Message' from - wpa_supplicant. And finally would than still the problem be left that - wpa_supplicant could silently die without some sigh. So, we are doomed to poll! -
The polling is now not done in a fixed interval but depends on - current status and reach from high frequent polling in 1sec, when - probably changes are on the way, down to 20sec in some static status where - primally is checked if someone is still alive. -
With the main window visible is polled in 5sec. - Only in case of an fatal error is polling halted, which e.g. occurs when the user - not belongs to the configured 'ctrl_interface_group=foo'. -
The window morphs its look to show always only what is needed, or can be - used, to some selections you made. If you encounter some misbehaviour please - report. -
Entered secrets will not shown again when you edit a network. Only a - hint that there is a password or key saved. I'm not a friend of that because - while messing around to get a connect you can't check if you miss typed the - password or something different is the problem. -
When you add, delete or modify a network are these changes only made in - a temporary manner inside the running wpa_supplicant. They take effect as long - as the wpa_supplicant is not terminated or triggered to reload its - configuration. You have to save the changes explicit. This is different from - the original wpa_gui. -
Right now is the behaviour, which data are changed (send to - wpa_supplicant) not coherend. It depends sometimes if they are visible when - you "Apply" or not. Your removed data are not everytime forced to remove by - wpa_supplicant. It's a little messi, sorry. Needs love and reports. -
Right now will no data explicit removed when they are not visible. The - wpa_supplicant documentation describes that you can have a pretty mix of - possible settings which are all tested when wpa_supplicant tries to connect - to some accesspoint. I'm not sure if this is really a smart decison. -
Long story, short sense: Don't expect to have a "clean" configured - network block in your config file after you have clicked around to find a - working setup. -
This program is licensed under the BSD license (the one with - advertisement clause removed).
wpaCute - A graphical wpa_supplicant front end
-Copyright (C) 2018 loh.tar@googlemail.com
-
-wpa_gui for wpa_supplicant
-Copyright (C) 2003-2015 Jouni Malinen <j@w1.fi> and contributors.