Comment 90 for bug 93360

Dudes. This is /really/ frustrating. How has this not been fixed yet? I have NO WIRELESS at the moment!

I did for a day or so after I freshly installed Ubuntu, but now, all of a sudden, it's fucked up. How hard can it possibly be to set up a network connection? Answer: not very. I can do it manually via "iwconfig wlan0 essid MyEssid" then "ifconfig wlan0 10.0.0.69" and pronto. But somehow Ubuntu's NetworkManager manages to fuck it up.

It could be a ndiswrapper specific issue. The reason I suspect it might have something to do with that is that sometimes the signal strength of my wireless router (the bar graph in the applet) is at 100%, and when I see this, I usually can't even connect or get an IP address (the signal should be around 33%). Otherwise, what happens is I DO actually connect (iwconfig shows a working link, and ifconfig shows a proper IP address, and I can surf the net), but the applet continues to spin, trying to "connect", with one of those tear drops lit up, and then after a few minutes it kills the connection (loses IP and link to the router), and my router releases (the lease?) on it's ip address.

Whether I can obtain a link or not via the Network Manager, I get that COMPLETELY USELESS error message in my syslog about "dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason". Just that! I don't get those slightly more informative errors about lease times as a few earlier posts have mentioned. The change that myric mentioned above has no affect for me. The exact same error and message persist.

Arrrrrrrgh!