[pkg-wpa-devel] Bug#455548: Bug#455548: README.modes: wpa_cli and wpa_gui work for the two modes.

[Kel Modderman]

tags wontfix 455548
thanks

On Saturday 15 December 2007 00:21:14 bb.zhang at free.fr wrote:
> Selon Kel Modderman <kel at otaku42.de>:
> > Hi Bin,
> >
> > I have restored the reply list.
> >
> > On Thursday 13 December 2007 18:06:54 Bin Zhang wrote:
> > > Kel Modderman wrote:
> > > > On Tuesday 11 December 2007 06:06:50 Bin Zhang wrote:
> > > >> Package: wpasupplicant
> > > >> Version: 0.6.1~git20071119-1
> > > >> Severity: wishlist
> > > >>
> > > >> Hi,
> > > >>
> > > >> wpa_cli and wpa_gui ("Fine Tuning the Roaming Setup") don't depend
> > > >> on roaming mode.
> > > >
> > > > No they do not, but the document that your proposed patch changes
> > > > talks about two modes: managed + roaming, and the fine tuning tips
> > > > are talked about in the context of usefulness for the roaming mode.
> > > > Therefore, I do not think it makes sense to change it in the way that
> > > > is proposed.
> > >
> > > My english is very bad. So I have not proposed a good change. Just did
> > > a copy and paste.
> > > Talking wpa_cli and wpa_gui only in roaming mode may let one thinking
> > > they don't work in managed mode. I use them in maged mode for fine
> > > tuning.
> >
> > The changes in the document need to change to reflect why and how they
> > are useful in managed mode, as it is not immediately obvious to me how
> > they could be. Examples of usage would be a good too.
>
> You can use wpa_cli or wpa_gui in the same way in both modes.
>
> Example: I have a wpa config file only for my home adsl.
> ============================================
> iface eth1 inet dhcp
>   wpa-conf /home/zhang/.wpa/wpa_supplicant.conf
>   pre-up modprobe bcm43xx
>   post-down modprobe -r bcm43xx
>   post-down modprobe -r ieee80211_crypt_tkip
> =========================================
>
> and
> =========================================
> ctrl_interface=/var/run/wpa_supplicant
> network={
>   ssid="myssid"
>   key_mgmt=WPA-PSK
>   proto=WPA
>   pairwise=TKIP
>   group=TKIP
>   psk="mypasswd"
>   priority=5
> }
> =======================================
>
> When I am not at home, if I run 'ifup eth1', I can not get a connection and
> I see
> =======================================
> # ifup eth1
> Internet Systems Consortium DHCP Client V3.0.6
> Copyright 2004-2007 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/eth1/00:11:24:22:f5:04
> Sending on   LPF/eth1/00:11:24:22:f5:04
> Sending on   Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
> ...
> ...
> =======================================
>
> But if I run then wpa_gui (or wpa_cli), I can scan the network and add new
> config found (if I know password or open network). And the new
> configuration gets the connection immediately if 'ifup eth1' is not yet
> over.
> If 'ifup eth1' is already finished:
> ========================================
> ...
> ...
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> ========================================
> Just wake dhclient with 'dhclient eth1' to get the connection.
>

Thats not the kind of networking workflow I'd like to promote. The wpa-roam 
mode exists to allow access to various network profiles, and thats the way 
I'd like to keep the documentation.

Thanks, Kel.