Ignore html files in doc/ for now

To have some html help file available from the GUI would be nice,
but ATM I'm not in the mood to look closer at this topic.

At the end of the day, you don't really need a help page at your
finger tips. Documentation is important, but it's more than enough
to have it as man page. You look at it once, then probably
never again.
This commit is contained in:
loh.tar 2024-03-27 19:17:17 +01:00
parent ea5f0c6110
commit e79dd00178
2 changed files with 1 additions and 307 deletions

1
.gitignore vendored
View file

@ -5,3 +5,4 @@ src/Makefile.Release
src/wpa-cute
doc/manpage.links
doc/manpage.refs
doc/*.html

View file

@ -1,307 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>wpa-cute</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="AEN1"
></A
>wpa-cute</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN5"
></A
><H2
>Name</H2
>wpaCute&nbsp;--&nbsp;A graphical wpa_supplicant front end</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>wpa-cute</B
> [-i <TT
CLASS="REPLACEABLE"
><I
>ifname</I
></TT
>] [-m <TT
CLASS="REPLACEABLE"
><I
>seconds</I
></TT
>] [-N] [-p <TT
CLASS="REPLACEABLE"
><I
>path-to-ctrl-sockets</I
></TT
>] [-q] [-t] [-W]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN21"
></A
><H2
>Overview</H2
><P
>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.</P
><P
>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.</P
><P
>wpaCute is a fork from wpa_gui, shipped with wpa_supplicant
version 2.6</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN26"
></A
><H2
>Command Arguments</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>-i ifname</DT
><DD
><P
>Specify the interface that is be configured.
Without <CODE
CLASS="OPTION"
>-i</CODE
> choose the first interface found in the socket path
which start not with 'p2p-dev-' otherwise the last found interface is chosen.</P
></DD
><DT
>-m seconds</DT
><DD
><P
>Set an independent update interval in seconds for the signal
strength meter.</P
><P
>This value must be a positive integer. Without <CODE
CLASS="OPTION"
>-m</CODE
> the
signal meter is only updated at each status update.
See also the notes about polling and pinging.</P
></DD
><DT
>-N</DT
><DD
><P
>Force not to use QSocketNotifier, use only polling.
It's more for testing purposes.</P
></DD
><DT
>-p path</DT
><DD
><P
>Change the path where control sockets should
be found.</P
></DD
><DT
>-q</DT
><DD
><P
>Run program in the quiet mode - do not display tray
icon pop-up messages.</P
></DD
><DT
>-t</DT
><DD
><P
>Start program in the system tray only (if the window
manager supports it). By default the main status window is
shown.</P
></DD
><DT
>-W</DT
><DD
><P
>Unset setting - Disable network after "WRONG_KEY"</P
><P
>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 <CODE
CLASS="OPTION"
>-W</CODE
> to have the original behavior. By default will now a
network disabled after a "WRONG_KEY" message.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN62"
></A
><H2
>Things Of Interest</H2
><DIV
CLASS="REFSECT2"
><A
NAME="AEN64"
></A
><H3
>Polling And Pinging</H3
><P
>On systems where QSocketNotifier is not supported is wpa_supplicant only
polled to fetch status changes.
</P
><P
>One ambitious development goal was to drop the need for Polling &#38; 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!
</P
><P
>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.
</P
><P
>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'.
</P
></DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN70"
></A
><H3
>Edit Network</H3
><P
>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.
</P
><P
>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.
</P
><P
>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.
</P
><P
>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.
</P
><P
>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.
</P
><P
>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.
</P
></DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78"
></A
><H3
>Peers</H3
><P
>While transforming some code from old-school C/C++ to a more Qt like
style, I noticed some wpa control request that are not, or in a different way,
supported by wpa_cli. So you may encounter some disappointments. I haven't
played much with the peers window.
</P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN81"
></A
><H2
>See Also</H2
><P
> <SPAN
CLASS="CITEREFENTRY"
><SPAN
CLASS="REFENTRYTITLE"
>wpa_cli</SPAN
>(8)</SPAN
>
<SPAN
CLASS="CITEREFENTRY"
><SPAN
CLASS="REFENTRYTITLE"
>wpa_supplicant</SPAN
>(8)</SPAN
>
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN90"
></A
><H2
>Legal</H2
><P
>This program is licensed under the BSD license (the one with
advertisement clause removed).</P
><P
CLASS="LITERALLAYOUT"
>wpaCute&nbsp;-&nbsp;A&nbsp;graphical&nbsp;wpa_supplicant&nbsp;front&nbsp;end<br>
Copyright&nbsp;(C)&nbsp;2018&nbsp;loh.tar@googlemail.com<br>
<br>
wpa_gui&nbsp;for&nbsp;wpa_supplicant<br>
Copyright&nbsp;(C)&nbsp;2003-2015&nbsp;Jouni&nbsp;Malinen&nbsp;<CODE
CLASS="EMAIL"
>&#60;<A
HREF="mailto:j@w1.fi"
>j@w1.fi</A
>&#62;</CODE
>&nbsp;and&nbsp;contributors.</P
></DIV
></BODY
></HTML
>