On 05/27/2018 09:05 AM, Joel Roth wrote:
Hi Devuan network users and adminstrators,
I was recently suprised to observe network interfaces
(wlan0 and eth0) going up without my issuing commands for
it. I'd disable an interface, then see it go right back up.
I somehow guessed that the culprit might be wicd, and
confirmed that a wicd process was active. I never
ran any of the wicd admin tools.
The list of wicd features does not mention that it
interferes with managing networks using net-tools or
iproute2 commands.
Is this a bug, or a documentation bug? Certainly, the
behavior is less-than-awesome. If one wants to learn about
networking on linux, or to administer a system using
conventional command-line tools, one should know that wicd
needs to be removed.
Do net-tools and iproute2 need to warn against wicd?
Should wicd warn that it disrupts administration via net-tools?
I wonder if there is any parallel in how in linux we
administer /etc/resolv.conf.
Do you have any thoughts about clarifying how to expect the
networking environment to work under linux?
Hi Joel, treat Devuan like old school Debian and get rid of network
manager and it's ilk, use wicd-gtk, your internet device names are no
longer going to change, so what you see when you run 'ifconfig -a' is
the name of your devices and probably something like eth0 and wlan0.
Configure /etc/network/interfaces accordingly and add 'allow-hotplug'
for your devices. And make sure the device names are correct in wicd,
done. That's my opinion.
Cheers,
--
Jimmy Johnson
Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
