SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Which Do You Use, NetworkManager or Wicd?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Rep:
Do You Use NetworkManager or Wicd?
This poll is for Slackware users only. Please do not vote if you don't use Slackware. Thank you.
A claim made by a board member in another thread prompted this poll.
So, in Slackware, do you use NetworkManager or Wicd?
If neither, what do you use?
Thank you.
Last edited by cwizardone; 07-02-2018 at 10:44 AM.
I have used NetworkManager in the past but now am using Wicd. This is on my laptop and I have had problems with wifi at some hotels so I tried this and tried that and in the process have found that I like Wicd and am comfortable using it. My desktop also has Wicd but it is wired so it matters not what I use
I use raw wpa_supplicant and dhcpcd (in master mode) via this custom rc.inet1:
Code:
#!/bin/sh
case "${1:-start}" in
start) ip -batch - <<-EOF
address flush dev lo
address add 127.0.0.1 dev lo
link set lo up
EOF
if [ ! -e /var/run/wpa_supplicant/wlan0 ]; then
iw reg set GB
wpa_supplicant -B -c /etc/wpa_supplicant/wlan0.conf -i wlan0 >/dev/null
fi
dhcpcd -q -b -L -M wlan0
;;
stop) dhcpcd -q -k
ip link set wlan0 down
if [ -e /var/run/wpa_supplicant/wlan0 ]; then
wpa_cli -i wlan0 terminate >/dev/null
fi
;;
esac
With my current network card, and router, i have been using NetworkManager for quite a while now without any problems. I've also stuck to using NetworkManager for it's additional features provided by the NetworkManager-openvpn slackbuild, which makes it effortless to switch my location for privacy.
Before i got a hold of a "Qualcomm Atheros AR93xx" wifi card, i was having many problems with a Belkin dongle which used the "rt2800usb" driver, where i would get constant unexplainable disconnects, unless i were to use wicd.
So for me, it depends on the device in question. I've found some dongles/cards play better with wicd / vice versa.
I've never been too sure how I would use NetworkManager in TWM but then neither have I looked into it. Netconfig suggests adding the applet to the desktop, I run dropbox in stalonetray so maybe I could somehow.
Anyway, wicd offers me wicd-curses which is easy, so I just use that.
I find no need for either. I perform my needs from the cli. I use scripts to control my LAN needs.
Slackware64 does have the scripts to use for my needs and I compose my own scripts to use '/etc/rc.d/rc.inet1' via the '/etc/rc.d/rc.inet1.conf' files.
I use NM and the other tools in the suite like the applet and the openvpn plugin. I started using Slackware long after working in other distros, so part of it was being already familiar.
Also I use nmcli and nmtui sometimes if I'm not in a GUI or lack a tray for the applet.
Laptops must use NetworkManager (or wicd)
Desktops can use rc.inet1 as a 3rd option to the above.
I say this because my desktop uses NetworkManager with no difficulty, although I do know how to configure rc.inet1 to use DHCP (or a static address), should the need arise (and has several times in the past).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.