Re: NM -- does it actually work?

[Ryan Novosielski <novosirj umdnj edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adrian Vasile wrote:
> On Fri, 2007-02-23 at 14:06 -0500, Dan Williams wrote: 
>> On Fri, 2007-02-23 at 13:56 -0500, Ryan Novosielski wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> wpa_supplicant is unnecessary for an open non-WPA connection anyway, really.
>> NM uses wpa_supplicant for all wireless connections, open, WEP, WPA,
>> whatever.  It's just silly to have two paths for bringing up a wireless
>> connection, one in NM and one in wpa_supplicant.
> 
>>> Second off, it should not be running on its own as a daemon if you're
>>> running any of the current stable releases -- NM launches it on demand.
>>> I wouldn't be surprised if this were causing you trouble.
>> Right; don't run your own copy if you want to use NM.
>>
>> Dan
>>
> 
> Ok. same result without running wpa_supplicant. I'm afraid of the thread
> "networkmanager fails to associate (ipw3945)". But I don't understand
> what's going on.. it associates to the AP and the only thing it has to
> do is run a dhclient on that interface (or signal the dhcp-dbus
> interface to do that).
> 
> I'll try now just with wpa_supplicant

Consider running NetworkManager --no-daemon or whatever the correct
option is if I've got it correct. You may get a lot more information out
of it to see where you're possibly having the problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF302Qmb+gadEcsb4RAuFwAJ9fvZ9MZgxME3k0AhiRGBrYXwBN+gCfd948
hFdPL0PnXYj3ONPgq8LcIJc=
=kLfC
-----END PGP SIGNATURE-----