[pkg-wpa-devel] cleaning up our suggested modes of use

[Marc Haber]

On Wed, Aug 02, 2006 at 10:24:14PM +1000, Kel Modderman wrote:
> On Wednesday 02 August 2006 21:55, Marc Haber wrote:
> > On Wed, Aug 02, 2006 at 09:36:45PM +1000, Kel Modderman wrote:
> > > On Wednesday 02 August 2006 21:13, Marc Haber wrote:
> > > > On Sat, Jul 22, 2006 at 11:22:57AM +1000, Kel Modderman wrote:
> > > > > Development of the "new order" wpasupplicant seems to be stabilising,
> > > > > and I see now two clear modes of operation, and would like to propose
> > > > > a clean up; consolidate documentation and code support for (IMO) the
> > > > > two preferred modes of operation.
> > > > >
> > > > >   1. managed mode, all WPA settings given via the interfaces stanza
> > > > > for any given network interface
> > > > >   2. roaming mode via wpa-roam/wpa_action: requires user supplied or
> > > > >      hand crafted wpa_supplicant.conf, and supports multiple
> > > > > locations and network profiles
> > > >
> > > > So the people who have moved from wpa_supplicant.conf to
> > > > /etc/network/interfaces a few releases ago when wpa_supplicant.conf
> > > > was deprecated are now asked to migrate back?
> > >
> > > No, absolutely not.
> >
> > How can I have roaming without wpa_supplicant.conf?
> 
> You cannot.

So I need to migrate back to wpa_supplicant.conf after migrating from
wpa_supplicant.conf to /e/n/i after learning that wpa_supplicant.conf
was deprecated.

> Even if a wpa_supplicant.conf file is provided again, it is required to edit 
> it *and* the /etc/network/interfaces file. We are writing an excellent 
> document that explains where and how to adapt a not-installed-by-deafult 
> wpa_supplicant.conf file you your needs. The amount of work is equal, imho.

As long as the way to do it is going to stay this time, I'm fine with
that.

> > In the "How it works" chapter, it shuold be mentioned that the magic
> > is hidden in a ifupdown action script,
> > /etc/network/if-pre-up.d/wpasupplicant.
> 
> Actually, it is /etc/wpa_supplicant/ifupdown.sh, with a wpasupplicant.links 
> file like so:
> 
> etc/wpa_supplicant/ifupdown.sh /etc/network/if-pre-up.d/wpasupplicant
> etc/wpa_supplicant/ifupdown.sh /etc/network/if-down.d/wpasupplicant 
> etc/wpa_supplicant/ifupdown.sh /etc/network/if-post-down.d/wpasupplicant

Ah, nice. Didn't see that.

> I will add this to the document.
> 
> >
> > "Notes about managed mode" has a typo, "automattically".
> >
> > What is the /usr/sbin/foo --bar mentioned in the /e/n/i chapter?
> 
> Ok, i should substitute that crap for a real world example of some common 
> pre-up action/command, any ideas of a good one?

So that action/command is not actually necessary here? Then I was
confused since siretart's example had whereami calls there, and I got
the impression they're actually needed.

> > In "Controlling the Roaming Daemon with wpa_action" it is said that
> > ifupdown shouldn't be called manually. Is it possible to associate a
> > eth1 "down" action with wpa_action eth1 stop so that the entire
> > interface can be cleanly taken down with ifdown eth1 as it would be
> > for a wired ethernet?
> 
> Not right now, this is tricky and there is an open bug for it (#373180).

I see.

> > whereami is not used at all, in difference to what siretart has
> > written in this thread.
> 
> I do not use it.

And how do you implement your wireless roaming? All controlled by
wpa_supplicant?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835