Comment 34 for bug 292054

Revision history for this message
Chris Bainbridge (chris-bainbridge) wrote :

The bug seems to be in some interaction to do with NetworkManager or the DBUS interface. If I put a WEP config in /etc/wpa_supplicant/ and do:

/sbin/wpa_supplicant -d -t -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf

Then wpa_supplicant will associate in just over 10 seconds. Log attached. Comparing the State changes to operating via NetworkManager/DBUS: with lone wpa_supplicant we get states:

1229956617.602179: State: DISCONNECTED -> SCANNING
1229956617.608634: State: SCANNING -> ASSOCIATING
1229956626.819271: State: ASSOCIATING -> ASSOCIATED
1229956626.819527: State: ASSOCIATED -> COMPLETED

With NetworkManager/DBUS we get states:

1229894071.010839: State: DISCONNECTED -> SCANNING
1229894071.011231: State: SCANNING -> INACTIVE
1229894071.013447: State: INACTIVE -> SCANNING
1229894080.172201: State: SCANNING -> DISCONNECTED
1229894081.145672: State: DISCONNECTED -> SCANNING
1229894086.262912: State: SCANNING -> ASSOCIATING
1229894096.265724: State: ASSOCIATING -> DISCONNECTED
1229894096.266842: State: DISCONNECTED -> SCANNING
1229894101.378873: State: SCANNING -> ASSOCIATING
1229894111.381811: State: ASSOCIATING -> DISCONNECTED
1229894111.383023: State: DISCONNECTED -> SCANNING
1229894131.663788: State: SCANNING -> ASSOCIATING
1229894131.675183: State: ASSOCIATING -> ASSOCIATED
1229894131.676322: State: ASSOCIATED -> COMPLETED

Clearly something odd is going on with NetworkManager interaction that causes these disconnected states whilst trying to associate. I think bug #272185 might be related and some people reported the same issue in bug #264881.