You are not logged in.
Pages: 1
Since the recent update (a few days ago) my Ascii system looses network connectivity pretty much instantly after boot. I can re-establish a network connection using the wcid widget, but before said update, my network was always connected to my LAN. After a period of inactivity, the network disconnects again, despite my settings (in wcid) to re-establish a connection when lost. The system has a Gigibyte F2A88XM-D3H mainboard, with a Realtec RTL8111/8168/8411 Gbit network chipset, no wireless.
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
/etc/network/NetworkManager.conf:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
Hope this can be resolved quickly, as it's getting old now :-\
Offline
using the wcid widget,
/etc/network/NetworkManager.conf:
you have both wicd and NetworkManager installed? maybe try removing one of those..
also the latter should be "/etc/NetworkManager/NetworkManager.conf", right?
Offline
Yup, my bad, it's indeed in /etc/networkmanager.
Oddly enough, the issues I had even yesterday don't seem to manifest themselves today. However, I doubt removing either of the managers as you suggest would solve it, as it has worked flawlessly before with both installed. But thx for the suggestion anyway, should it re-occur I might ditch wcid to see if there's a conflict between the two.
Offline
The other standard suggestion in this case is to either use one network manager or configure in /etc/network/interfaces. Not both. If it's not a laptop that travels around to different networks, you may as well ditch both network managers.
Offline
Note that eth0 is being controlled by ifupdown rather than NetworkManager: https://wiki.debian.org/NetworkManager# … _Unmanaged
So try replacing "allow-hotplug eth0" with "auto eth0". Or use NetworkManager instead of ifupdown.
Don't bother with wicd, it's crap.
Brianna Ghey — Rest In Power
Offline
Thx gentlemen. On reflection, I have purged both network managers from my system, adjusted /etc/network/interfaces as suggested and will await the next boot for results. This machine is indeed my regular desktop, which is on for most of the day when I'm home.
Offline
Don't bother with wicd, it's crap.
I have good success with wicd. I have used NetworkManager before and it was OK. I think I even successfully used NM to connect with those complicated auth schemes like EAP v2 (that AD RADIUS auth stuff) but that was back in my Fedora days.
While /etc/network/interfaces is fine with me, and I prefered the old Red Hat /etc/sysconfig/network-scripts because it was shell scripts, I have found wicd-cli and wicd-gtk quite sufficient!
What do you dislike about wicd?
This space intentionally left blank.
Offline
Offline
wicd is already being ported to python3, and there is a -buggy- python3 version in debian experimental , so it's got a future...
https://packages.debian.org/search?keyw … thon3-wicd
Offline
Pages: 1