Public bug reported:
Binary package hint: network-manager
With a completely updated Feisty install, NetworkManager fails to
associate to my AP running WPA2. My network card is an Atheros-based
AR5212 PCI NIC from Netgear (model WG311T).
This seems to be a timing/race condition problem whereby NetworkManager
doesn't seem to understand that it can proceed with the association and
the rest of its startup process. The reason I state this is that if I
run "ifdown ath0" and immediately run "ifup ath0" at the "right time"
after NetworkManager has started, NetworkManager will finish and ath0
comes up associated with the AP, dhcp'ed address and all. I can't
clearly define "right time" at present. These seems to be a narrow
window of opportunity right after the "CTRL_IFACE monitor attached" log
statement from NetworkManager appears to pull off this workaround. If
you miss the window, restarting NetworkManager (via /etc/init.d/dbus
restart and or directly restarting NetworkManager when running it
manually) and getting the timing just right with the ifdown/ifup pair
will bring the network up.
I will be happy to provide any log files that you wish to see. Please
indicate what I can send to help you understand this problem.
Items of note: I've already checked /etc/network/interfaces. I've
commented out everything except ath0 and wifi0 entries. Those two are
auto dhcp. I have no manually defined wpasupplicant.conf.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
NetworkManager fails to finish association to AP
https://bugs.launchpad.net/bugs/133966
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
