Re: NM -- does it actually work?

[Adrian Vasile <yoyo opennet ro>]

On Sat, 2007-02-24 at 00:43 +0200, Adrian Vasile wrote:
> On Fri, 2007-02-23 at 15:56 -0500, Ryan Novosielski wrote:
> > 6f70656e6e6574'
> actually that's hexa for 'opennet'
> ...
> and the same happens after a reboot
> ...
> still hanging... thinking it doesn't associate to the AP
> 
In a "brilliant" fashion, I discovered that actually it's
wpa_supplicant's fault.. while asking NM to connect to my AP, I used
wpa_cli to connect and see what it's actually trying to do. Here's the
result:

<2>Trying to associate with 00:0f:66:57:20:8a (SSID='opennet' freq=0
MHz)
<2>Authentication with 00:00:00:00:00:00 timed out.
....................................................................
<2>Trying to associate with 00:0f:66:57:20:8a (SSID='opennet' freq=0
MHz)
<2>CTRL-EVENT-TERMINATING - signal 15 received

The signal is given after 40s of timeout by NM.


Being new to this NM/wpa_supplicant I ask, is this how it's supposed to
connect? Cause the only "problematic" thing here is that wpa_s doesn't
know on which freq it should connect (although it knows even my AP mac
address).

Anybody has any ideas about this?

And secondly, which is better.. to run a separate instance of
wpa_supplicant along side NM or let NM run it's own instance (anyway it
does that) and it doesn't connect to the first wpa daemon's control
socket.

Thank you,
Adrian