Re: One more clue

[David Abrahams <dave boost-consulting com>]

Dan Williams <dcbw redhat com> writes:

> On Wed, 2006-09-06 at 11:03 -0400, David Abrahams wrote:
>> NM is commonly not connecting -- or taking forever to connect -- to my
>> network, especially after the connection is dropped (e.g. if I go out
>> of range).  However, if I'm lucky enough to have an unprotected
>> network nearby, all I have to do is try to connect to that unprotected
>> network and wait for the first "green dot" in nm-applet (I don't even
>> need a full connection), then switch back to my preferred network, and
>> everything connects reasonably quickly.
>> 
>> It seems as though the answer must be discernable from all the data
>> I've provided.  Am I providing too much data about my problem?
>
> The only thing I can think of to diagnose this issue is to figure out
> what NM and wpa_supplicant are doing differently.  And that will require
> a small tool that mimics the behavior of NM controlling wpa_supplicant.
> So, I need to distill the wpa_supplicant controlling bits of NM into a
> small utility into which we can feed network configurations.  If I did
> this, would you be willing to test it for me?

Of course!

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com