On Mon, Dec 22, 2008 at 03:00:39PM -0000, 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
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? - Alexander -- Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase) https://bugs.launchpad.net/bugs/292054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
