WICD let me down
I blogged a while back about WICD, the wireless manager that I had switched to a because it seemed to do better than network-manager. All that has changed.
There have been several little issues.
First, I was dissappointed that wicd would let me use the wireless or wired. Not both. I realize there is not often when I need to do that, but when you need to test a wired network for connectivity and still having internet. When trying to avoid wicd and just using the command line for a quick ‘eth0 up; dhclient3′ wicd would disconnect the wireless.
Second, when coming from resume there would be occasions where wicd reported no wireless AP’s. I wrote a little script to get me wireless back which stopped the wicd daemon, removed the wireless driver module, modprobed the wireless driver and then started the wicd daemon. After doing this I could get back on the web.
The last one though was to much. I have a Motorola DROID and love it as a smart phone. I have rooted the phone to give me tethering capability. When you do that the Droid sets up an ad-hoc wireless network which bridges to the 3G connection in the phone. The problem lies in the fact that wicd won’t connect to ad-hoc networks. I google searched and even the mighty google only said “wicd won’t let you”.
So much disappointment there. All three of those issues are solved with network-manager again. If anyone has any solutions for wicd let me know.
Tags: Application Review, Networking