wicd vs. networkmanager
 

Which do you choose, and why?

I've always used networkmanager, because I've appreciated being able to connect to wireless networks directly from the nm-applet in the systray, without opening a window, such as with wicd.

But it seems to me that most Slackers (and some others) prefer wicd. Is it mostly a matter or wicd's relative light weight/lack of dependencies compared to networkmanager (Gnome, ugh)?

I've used both but prefer wicd because it's lighterweight and seems simpler to me.

Well, I've used both. Originally I preferred wicd, but after some buggy UI changes I now prefer network manager.

Member Response
 

Hi,

I use 'wicd' via ''wicd-curses' when on console'cli' or 'wicd Network Manager' when using KDE.

No issues to date. I did try '/etc/rc.d/rc.networkmanager' with KDE NetworkManager via 'nm-applet' but '/etc/rc.d/rc.wicd' for 'wicd' seems better to me using applet. Just personal taste & opinion. :)

I experieced more errors using '/etc/rc.d/rc.networkmanager'. No errors to date using 'wicd'.

I use both depending on circumstances. Mostly to do with 3G dongles being recognised and usable with NM. But on the whole, it seems that Wicd is just more stable and reliable.

A PITA having to swap about, so the sooner Wicd gets 3G support the sooner I can ditch Nm.

I believe I read somewhere that this is planned for wicd 2.0.

Edit: No, it was VPN support:

https://answers.launchpad.net/wicd/+faq/1867

Aha! Edit, again: 3G support is also slated for wicd 2.0:

https://answers.launchpad.net/wicd/+faq/1866

I've had no problems with either - but run wicd (with fluxbox).

I use raw wpa_supplicant and dhclient - but I'm weird like that. :)

They both worked equally...but I cannot say they worked well, unless it was something else on my system causing problems.

No matter which I'd use, it seemed to randomly (length of time-wise) lose the connection to the router.

I use a dongle that's supported by linux kernel and have tried two different routers. I would sometimes stay connected for two and sometimes (rarely) three days, but more often than not I would lose connection in just a few hours and have to unplug the usb to the dongle and re-plug it in to get wicd or nm to even start up again as either would lock up solid.

The dongle is a tp-link wn-821n, and the routers were a tp-link wr-841n and a linksys E-2500.

Simply got so frustrated after a few months of this that I ordered some nice cat6 ethernet cable and haven't had a hiccup since, though I hate that I've now got a big ol' ugly length of cable running along the wall.

Hopefully either of them will work well/better for you.

They both actually work just fine for me, I was just interested in hearing about the experiences/opinions of others on the matter. I do like that wicd is lighter and has less dependencies, but I also like the ease-of-use of NM.

wicd and fluxbox with no issues, but it is only on one system. I do not use wireless access at home and only use it occasionally when traveling with my laptop.

I have a newer desktop running -current with wifi hardware but have not yet configured the wifi. Maybe a weekend comparison test is in order...

I use wicd with Slackware and Fluxbox on two machines and have been quite happy with it. I prefer it to network manager.

For Fluxbox, I put wicd-client & in my .fluxbox/startup file so that the wicd client application starts when I startx.

Where's the poll?

Network Manager for me.

NetworkManager, mainly because it is de facto. ModemManager was also a factor, but became less so when I started using my Android phone as a WiFi hotspot.

Done and done! Vote on!