On Wed, 2007-03-28 at 10:52 -0400, Dan Williams wrote: > There's been weird errors with wpa_supplicant that I can't quite wrap my > head around. There are two cases: > > 1) NM can't connect to wpa_supplicant's control socket sometimes; this > is fixed by using the D-Bus interface I'm pretty sure it is connected, looking at the strace I see some things sent to a socket. > 2) The _same_ settings sent to wpa_supplicant via NM, and those same > settings in the config file, produce different results. I've compared > the settings of quite a few cases of this and found no appreciable > differences, but still NM fails to associate. I was kind of hoping this > would all go away with the switch to the D-Bus interface in 0.7, because > the socket-based control interface has been so much of a hassle. But it > probably needs to be fixed for the 0.6.x branch. Strange stuff. > Could you possibly get some driver traces of what happens in the driver > for plain wpa_supplicant and then with NM+wpa_supplicant? If the config > that NM is sending to wpa_supplicant is the same, then the only thing I > can think of is some randomly different driver state or interaction > between the 3 unrelated to the specific config info that's causing > associations to fail. What exactly would you want? A printk in all the ioctl handlers in mac80211 that shows all the parameters set? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
