mykola/wpa-cute-freebsd
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Update behaviour about save/apply

Browse source
This commit is contained in:
loh.tar 2024-03-14 08:52:45 +01:00
parent 1f627cb749
commit a855b9672a
1 changed files with 2 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/wpa-cute.sgml
View file

@ -141,19 +141,8 @@
configuration. You have to save the changes explicit. This is different from configuration. You have to save the changes explicit. This is different from
the original wpa_gui. the original wpa_gui.
</para> </para>
<para>Right now is the behavior, which data are changed (send to <para>After each change, the old network block is always removed and a new one
wpa_supplicant) not coherent. It depends sometimes if they are visible when created. This prevents unwanted old configuration remnants from remaining.
you "Apply" or not. Your removed data are not every time forced to remove by
wpa_supplicant. It's a little messy, sorry. Needs love and reports.
</para>
<para>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 access point. I'm not sure if this is really a smart decision.
</para>
<para>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.
</para> </para>
<para>The data in the IDString field will be shown <para>The data in the IDString field will be shown
in the Flags column of the Networks list. This is a kind of ploy to make it in the Flags column of the Networks list. This is a kind of ploy to make it