I've used both and if wicd it didn't have a 'refresh' button it would be completely worthless. NM, on the other hand, seems to do a better job of making the connection and hanging on to it.

I've used both. I'm using wicd on my slackware-current acer netbook. I prefer wicd; it does what I need it to do.

For my comparison of NetworkManager and wicd, see here http://www.linuxquestions.org/questi...0/#post4803085
Due to USB modem support and automatic reconnection, I am using NetworkManager in preference to wicd on my netbook.

1 members found this post helpful.

I use both. Network-manager for personal 3G USB dongle and wicd for the wi-fi.

Regards.

Thanks.
Didn't know it had ncurses interface.

I mostly use NM since Wicd doesn't support everything in my home network.

Now that netconfig proposes NetworkManager, I use it (on my laptop, with Fluxbox.)

At first reboot after installation:
(1) I am automatically connected by wire, if available
(2) I just have just to run once nm-applet to get the widget on the tray after installation.

Then getting a wireless connection is just a left-click away, plus possibly typing the password the first time when demanded.

It could hardly be simpler to use IMO.

Wicd

Maybe its just my weird old laptops (Compaq and Dell), but NM has one hell of a time switching back to wired from wireless; wired TO wireless is fine, but the reverse requires more button clicks than I care for. For systems without wifi, I disable NM: easier to just edit the appropriate files in /etc/rc.d

I use both. Each has it's own glitches, but I get used to "wicd way" so now I find NetworkManager's applet the weird one Although I'm pretty sure anyone coming from NetworkManager to Wicd will feel the same about wicd.

I use networkmanager for VPN and wicd for everything else.

So far wicd always worked flawless, while networkmanager sometimes acts weird (can connect to wired network but didn't even try to connect to wireless network, although it connected fine just few minutes ago). Besides, wicd doesn't intentionally hide informations (like complete list of available wifi AP's, so I can choose AP if it operates on both 2.4 GHz and 5 GHz band) to simplify GUI. Which I find as advantage, but someone else could take it as disadvantage. It's matter of preferences.

Neither. Wired eth0 here.

At one point (maybe fixed now?) wicd had a bug that meant automatic wifi reconnections sometimes didn't work (maybe after reawakening from hibernation?). I remember I had to actually restart for the connection to be accepted with the stored credentials.

Since NetworkManager appeared I have used it for my laptop and this problem has not occurred.

Michael

I can't get NM to connect automatically on boot if X isn't running, so it's no choice for me, Wicd.

I use wicd, with the dhcpcd backend. The dhclient backend changes my computer's hostname without my permission, which (aside from being rude) wreaks havoc on the desktop session.

I like that Wicd gives me more options and easier access to configuration. The interface is a little sluggish (it likes to refresh a lot?), but I find it works better for me than NM. NM didn't always play nicely with a multi-user setup and kept forgetting passwords in a way that made no sense to me. Wicd works fine, so long as I don't use the dhclient backend :P

I switched to NetworkManager for the same reason but soon found NetworkManager forces me to accept too many things. e.g. It forces me to let it manager my ethX while in wicd I can disable this. NetworkManager also disallows the use of "/etc/resolv.conf.{head,tail}".

After quite some struggles, I had to switch back to wicd+blueman. Blueman also gives more stable 3G modem connection than NetworkNamager does.

I dislike both of them because of bloat, so I use wpa_supplicant and hand edit its config as needed.

If I had to choose, it would be wicd, but I very much dislike its design decisions. I mean, c'mon, it expects me to run a full Python interpreter as a daemon? Along with a bunch of third-party libraries. And as root? WT...?

It's been on my To-do list for ages: write a simple wireless manager in C that would interface with iwlist and iwconfig or iw to bring up and close down wireless connections. It would automatically remember certain APs and would offer to connect when one comes in range, all user configurable.

I think it is something that is really lacking in Slackware land at the moment, especially for those of us who don't use a Desktop and have no concept of a systray or applets.

1 members found this post helpful.

Yessirree! Same on the desktop.

On the laptop, however, I use NetworkManager because it is the default in KDE and works very well out of the box. It has been a solid performer for me.

It wasn't that long ago that the kernel didn't have many wireless drivers built in. I had a wireless card which used an Atheros chipset. Had to download the Madwifi drivers and compile them, as well as wpa_supplicant which wasn't a stock Slackware package. Things have certainly come a long way since 2004!