Comment 38 for bug 292054

On Tue, Dec 30, 2008 at 01:43:37AM -0000, Chris Bainbridge wrote:
> I tested again with a different AP, open AP so no WEP or WPA, borrowed
> this AP just for testing so no other users, AP next to test PC (64/70
> signal). Using wpasupplicant-0.6.4-2 and network-
> manager-0.7-0ubuntu1~nm1~intrepid1. Config in /etc/NetworkManager so no
> front-end delay. Hopefully this will eliminate any potential issues.
>
> Conclusions: associating with wpa_supplicant takes ~60 seconds. Total
> connect time with NetworkManager is ~70 seconds. Manual 'ifup' takes ~15
> seconds. wpa_supplicant goes through the same numerous states as before.
> Again, this is with no authentication necessary.
>
> > please try to put exactly the config paramaters you see in syslog by
> > NM in your wpa_supplicant.conf ... does that make the manual case
> > behave similar to NM?
>
> The config is exactly the same - there is not much to configure - only ssid, scan_ssid=1, key_mgmt=NONE, priority=1.
> The manual case associates in ~10 seconds.
>
> Steps to reproduce:
> In one terminal run: wpa_supplicant -u -d -t
> In another terminal run: NetworkManager --no-daemon
> You should see wpa_supplicant going through many states before associating.
> Then terminate both processes and try: wpa_supplicant -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -d -t
>

We should look into why wpasupplicant takes so much longer then.

Can you please enable debugging for wpasupplicant in both cases and
post the complete wpasupplicant snippet for both attempts (e.g. manual
+ through NM)?

For the NM wpasupplicant change the command in
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service
to output debug stuff and do a killall wpa_supplicant.

Thanks!

 - Alexander