2012/1/27 Giorgio Pioda <[email protected]>: > I also would argue that wicd is fairly less efficient > than network manager. I've tested it > recently on an fresh Wheezy-XFCE but at school I wasn't able to > connect and had to replace it with n-m. > > Cheers
I agree. Things have changed in the latest two years. The development of n-m has continued improving the application, while wicd has stalled, keeping some ugly bugs for months. I still think wicd has a more friendly interface for non-geek users, specially when you want the computer to get a network connection before login. That's something that will require root access in n-m while it's easy for any user without root access using wicd. However , the bugs wicd is keeping are making it less efficient with some wireless encription methods, so we have been migrating our machines to n-m in the last months. Regards. > > Giorgio > > On Fri, Jan 27, 2012 at 12:18:12PM +0100, Petter Reinholdtsen wrote: >> >> [Petter Reinholdtsen 2010-07-10] >> > * The wicd package is installed (instead of network-manager). Not >> > sure if this is a good idea or not, but the report from Extremadura >> > made me put it in there as a test. >> >> Based on todays tests, I am starting to suspect it might be better to >> use network-manager. >> >> I installed a roaming workstation using PXE in a Debian Edu/Squeeze >> network today, and the installation worked fairly well (partition size >> issues - updated d-e-install with new sizes). After installation, I can >> log in with the first user, and a local home directory is created and >> used after I log in for the second time. I can disconnect the network >> cable and still log in using cached credentials. All good so far. >> >> But, when I try to connect to the wireless networks around me, wicd do >> not see anything. I had to manually configure wicd to use wlan0 as the >> wireless interface to be able to see the wireless networks. And when I >> try to select the non-encrypted network I want to use, I am unable to >> get any IP address. >> >> After removing the wicd package and installing the network-manager-kde >> instead to get a KDE panel widget to control network-manager, I am able >> to connect to the wireless network. >> >> Anyone want to debug wicd in this setup, or should we just switch to >> network-manager on Roaming Workstation profiles? Possible advantages: >> >> - It will discover wireless interfaces without any configuration. >> >> - Roaming Workstation will use network manager the same way Standalone >> (and all other profiles?) do it now. >> >> Possible problems >> >> - Roaming Workstation will not work for new users because the network >> is not enabled at boot but only after first login, and thus no >> connection to LDAP and Kerberos can be made. >> >> The problems I see might be because wicd and network-manager are >> confusing each other. I did not have much time to debug. >> -- >> Happy hacking >> Petter Reinholdtsen >> >> >> -- >> To UNSUBSCRIBE, email to [email protected] >> with a subject of "unsubscribe". Trouble? Contact [email protected] >> Archive: http://lists.debian.org/[email protected] >> >> > > -- > Sysadmin SPSE-Tenero > Ufficio: +41 91 735 62 48 > Cellulare: +41 79 629 20 63 > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAHpm-q2htMGc5odB-9B=whd6nlr4h_yq_q_-lqpwfdnnx9o...@mail.gmail.com
