Re: NM -- does it actually work?

[Adrian Vasile <adrian vasile opennet ro>]

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

Adrian
> 
> > =R
> > 
> > yoyo opennet ro wrote:
> > > Hi list,
> > > 
> > > First of all, I'm not sure that this is the correct list to ask this, but
> > > since this is the NM-list...
> > > 
> > > Secondly, sorry for the "offending" subject.
> > > 
> > > The problem: FC 6 on a dell d820 with a tg3 and a ipw3945. Both are
> > > configured to get their ip addresses by dhcp and not to start at boot. My
> > > problem is with the wireless configuration. Running by hand the 2-3
> > > commands to connect to the ap (which is open by the way - no wep no
> > > nothing, just connect to it and your done) but since redhat/the
> > > community(FC)/gnome is giving away this brilliant (at least in theory)
> > > piece of software that allows you to roam through any kind of connection
> > > types I wanted to have it run and not bother with anything that's not "out
> > > of the box" (UI wise). Running with nm-applet trying to connect to my AP
> > > is a no go every time. When I click on the applet I can see the AP, the
> > > signal strength everything. After it associates to the AP, it seems like
> > > it forgets to start the dhcp client request.