Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
Control: retitle -1 wired_connect_mode behavior doesn't match the
wicd-manager-settings.conf(5) man page
Control: tags -1 patch
On 2009-11-19 23:41:10 +0100, Vincent Lefevre wrote:
> Note: in manager-settings.conf, I have "wired_connect_mode = 1",
> in order not to connect automatically. [...]
I wanted to see where the problem came from. In the
wicd-manager-settings.conf(5) man page:
wired_connect_mode = <0|1>
0 = connect to wired interface automatically
1 = do not connect to wired interface automatically
which corresponds to what I expected, but in
/usr/share/wicd/daemon/wicd-daemon.py, one has:
def SetWiredAutoConnectMethod(self, method):
""" Sets which method to use to autoconnect to wired networks. """
# 1 = default profile
# 2 = show list
# 3 = last used profile
self.config.set("Settings", "wired_connect_mode", int(method),
write=True)
self.wired_connect_mode = int(method)
self.wired_bus.connect_mode = int(method)
This doesn't seem to be the same range of values!
This is confirmed here:
def GetWiredAutoConnectMethod(self):
""" Returns the wired autoconnect method. """
return int(self.wired_connect_mode)
[...]
def _wired_autoconnect(self, fresh=True):
""" Attempts to autoconnect to a wired network. """
wiredb = self.wired_bus
if self.GetWiredAutoConnectMethod() == 3 and \
not self.GetNeedWiredProfileChooser():
# attempt to smartly connect to a wired network
# by using various wireless networks detected
# and by using plugged in USB devices
print self.LastScan
if self.GetWiredAutoConnectMethod() == 2 and \
not self.GetNeedWiredProfileChooser():
self.LaunchChooser()
return True
# Default Profile.
elif self.GetWiredAutoConnectMethod() == 1:
network = wiredb.GetDefaultWiredNetwork()
if not network:
print "Couldn't find a default wired connection," + \
" wired autoconnect failed."
self.wireless_bus._wireless_autoconnect(fresh)
return
# Last-Used.
else:
network = wiredb.GetLastUsedWiredNetwork()
if not network:
print "no previous wired profile available, wired " + \
"autoconnect failed."
self.wireless_bus._wireless_autoconnect(fresh)
return
Actually wired_connect_mode corresponds to the 3 radio buttons of
"Wired automatic connection" in the preferences.
So, I suppose that the real problem is wrong documentation, and the
real solution to ignore the wired interface is to set
wired_interface = None
i.e. make sure that the "Wired interface" box in the preferences is
blank.
Assuming that this is a documentation bug, I've attached a patch.
--
Vincent Lefèvre - Web:
.TP
.BI "always_show_wired_interface = "
.TP
-.BI "wired_connect_mode = " <0|1>
-0 = connect to wired interface automatically
+.BI "wired_connect_mode = " <1|2|3>
+1 = default profile
.br
-1 = do not connect to wired interface automatically
+2 = show list
+.br
+3 = last used profile
.TP
.BI "prefer_wired = "
True = Switch to wired interface if a link is detected, even if already
connected to wireless
.br
False = Do not switch to wired interface automatically
.TP
-.BI "wireless_interface = "
+.BI "wireless_interface = "
.TP
.BI "wpa_driver = "
The default (and best supported) is wext. It should work properly in most
cases.
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
I also ran into this one. On Wed, May 23, 2012 at 02:14:03AM +0200, Javier Fernández-Sanguino Peña wrote: A mistake here: wicd was pulled in because I installed the xfce-desktop task, not because of Network Manager. I think that's how I installed wicd, too. I have never configured wicd and don't use it (my PC doesn't have wireless connections at all). Still, I've always managed my interfaces using /etc/network/interfaces and have *never* configured them using wicd. Similar story: I have two wired interfaces: eth0 for my internet provider and eth1 with a static IP, configured via /etc/network/interfaces. I run a DHCP server on eth1 where I connect my laptop for internet access. What happened: Whenever I disconnected my laptop, wicd did run dhclient on eth1. Probably as a result, the static IP on eth1 was un-configured. Dhclient did exit again, realizing that the interface was down. Sometimes the local dhcp server even decided to answer the local dhcp client's request, giving itself a new IP from its own pool, and a new default route to the internet which did not work. I had to kill the extra dhcp client started by wicd to fix this situation (not realizing how it happened, of course). Please take note that it took me quite a lot of debugging of the pm-suspend scripts until I found out that the reason why my interfaces were reconfigured was because of wicd. Indeed, it took me quite some time to figure this out. After blaming several other components (like NetworkManager), I finally traced it to wicd when I replaced /sbin/dhclient with a script that prints the PID of the parent process. Solved now with 'apt-get remove wicd-daemon'. -- Martin Renold signature.asc Description: Digital signature
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
On Mon, May 21, 2012 at 07:14:08PM +0200, Javier Fernández-Sanguino Peña wrote: - I have not configured wicd at all, it was just pulled in as a dependency because GNOME's NetworkManager depends on it A mistake here: wicd was pulled in because I installed the xfce-desktop task, not because of Network Manager. Still, I've always managed my interfaces using /etc/network/interfaces and have *never* configured them using wicd. As I cannot disable the /usr/lib/pm-utils/sleep.d/55wicd script I've introduced another script in /etc/pm/sleep.d/00_restart_network that stops dhclient and (...) Please take note that it took me quite a lot of debugging of the pm-suspend scripts until I found out that the reason why my interfaces were reconfigured was because of wicd. Once the culprit has been found, a much simpler way to prevent this bug would be using apt-get or dpkg, I could remove wicd since it is only Recommended: by xfce-desktop. For me it probably an option, but a regular user that steps into this bug will find that this will make more friendly package management frontends, such as aptitude, to *always* try to remove the xfce-desktop task (unless configured to ignore Recommends). Regards Javier signature.asc Description: Digital signature
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
On 2012-05-23 02:14:03 +0200, Javier Fernández-Sanguino Peña wrote: Once the culprit has been found, a much simpler way to prevent this bug would be using apt-get or dpkg, I could remove wicd since it is only Recommended: by xfce-desktop. I think that by default, the wicd daemon shouldn't modify anything at all, as it can be installed via a dependency. Fixing this bug would go in that way, but one may wonder whether there are other default operations that would have an influence on the network connection... -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
Package: wicd-daemon Version: 1.7.2.3-1 Followup-For: Bug #557156 I can confirm that this bug is still present and it completely breaks my network setup when resuming from suspend. In my case, I have a desktop system that uses 'eth1' as its wired interface: - this interface is configured through /etc/network/interfaces (since Woody, or even earlier) - I have not configured wicd at all, it was just pulled in as a dependency because GNOME's NetworkManager depends on it - there is no way to disable the suspend script (I have filed a separate bug on this) When resuming from suspend the following happens: - /usr/lib/pm-utils/sleep.d/55wicd is run - the script calls /usr/share/wicd/daemon/autoconnect.py - this script calls dhclient - the interface is auto reconfigured to use a dynamic (instead of static IP address) Please see the attached file generated using 'script' (wicd-test-resume.log) that shows the behaviour. The /var/log/wicd/wicd.log file (attached is an extract) shows that seems to be the behaviour when resuming from suspend. I'm attaching also my current /etc/wicd/wired-settings.conf configuration file for review. As I cannot disable the /usr/lib/pm-utils/sleep.d/55wicd script I've introduced another script in /etc/pm/sleep.d/00_restart_network that stops dhclient and reconfigures the interface. Writting this script was a little bit tricky as there is a race condition in how the power management scripts are run (as wicd dettachs to a background process). It seems to work well in my system and prevents this bug. I'm attaching it also here for the benefit of those affected by this bug. Please feel free to ask for additional information. By the way: this bug is pretty serious, in my opinion it makes this package unsuitable for release. Regards Javier -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu1 ii dbus1.5.12-1 ii debconf 1.5.42 ii ethtool 1:3.1-1 ii iproute 20120319-1 ii iputils-ping3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.2.2.dfsg.1-4 ii lsb-base4.1+Debian2 ii net-tools 1.60-24.1 ii psmisc 22.16-1 ii python 2.7.2-10 ii python-dbus 0.84.0-3 ii python-gobject 3.2.0-3 ii python-wicd 1.7.2.3-1 ii wireless-tools 30~pre9-8 ii wpasupplicant 0.7.3-6 Versions of packages wicd-daemon recommends: ii wicd-gtk [wicd-client] 1.7.2.3-1 Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-9 Versions of packages wicd depends on: ii wicd-gtk [wicd-client] 1.7.2.3-1 Versions of packages wicd-gtk depends on: ii python 2.7.2-10 ii python-glade2 2.24.0-3 ii python-gtk22.24.0-3 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 Versions of packages python-wicd depends on: ii python 2.7.2-10 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 -- debconf information: * wicd/users: jfs [wired-default] ip = None broadcast = None netmask = None gateway = None search_domain = None dns_domain = None dns1 = None dns2 = None dns3 = None beforescript = None afterscript = None predisconnectscript = None postdisconnectscript = None encryption_enabled = None default = True dhcphostname = silicio lastused = True Script iniciado (lun 21 may 2012 18:19:36 CEST ) fetchmail: background fetchmail at 12848 awakened. jfs@silicio:log$ jfs@silicio:log$ ps -ef |grep dhcl jfs@silicio:log$ ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:c0:df:03:c5:e9 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:dfff:fe03:c5e9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7336517 errors:0 dropped:0 overruns:0 frame:0 TX packets:16048323 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:963483172 (918.8 MiB) TX bytes:2499792887 (2.3 GiB) Interrupt:20 Base address:0xd000 jfs@silicio:log$ cat /etc/network/interfaces |grep eth1 auto eth1 iface eth1 inet static #mapping eth1 # iface eth1:1 inet dhcp jfs@silicio:log$ sudo -s silicio:/var/log# /usr/share/wicd/daemon/autoconnect.py silicio:/var/log# ps -ef |grep dhc root 19460 2769 0 18:21 ?00:00:00 /sbin/dhclient -v -r eth1 root 19462 18898 0 18:21 pts/000:00:00 grep dhc root 19463 19460 0 18:21 ?00:00:00 /bin/bash
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
found 557156 1.7.1~b3-3 thanks This still occurs, at least when the Ethernet cable is unplugged. In the wicd logs: [...] 2012/01/06 10:24:34 :: ifconfig eth0 up 2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/avahi-autoipd with params 2012/01/06 10:24:36 :: /etc/network/if-down.d/avahi-autoipd returned 0 2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/bind9 with params 2012/01/06 10:24:36 :: /etc/network/if-down.d/bind9 returned 0 2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/postfix with params 2012/01/06 10:24:36 :: /etc/network/if-down.d/postfix returned 0 2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/wpasupplicant with params 2012/01/06 10:24:36 :: /etc/network/if-down.d/wpasupplicant returned 0 2012/01/06 10:24:36 :: attempting to set hostname with dhclient 2012/01/06 10:24:36 :: using dhcpcd or another supported client may work better 2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0 2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0 2012/01/06 10:24:37 :: ifconfig eth0 down 2012/01/06 10:24:37 :: ifconfig eth0 up [...] My config has changed a bit, and I now use netplug, but wicd also confuses netplug, meaning that I lose the network connection. Note: in the wicd preferences, Always switch to a wired connection when available is unticked. So, wicd should never attempt to modify the eth0 settings. As a workaround, one can leave the wired interface blank in the preferences. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
Hello Vincent, I thought I at least replied to your other mails. Shame on me, I'm very sorry. :( Let me reply also to your 2009 mail -- a bit late though :) On Thu, 19 Nov 2009 23:41:10 +0100, Vincent Lefevre wrote: When I suspend my laptop or unplug the Ethernet cable, wicd deconfigures the wired (eth0) interface, even though I wasn't connected via wicd. I don't know whether wicd does that directly or whether this is done by dhclient (the logs show that dhclient is started at this time, and it is started by wicd, because if I stop the wicd daemon, this no longer happens). In any case, wicd is the culprit, because starting dhclient when I suspend my laptop or unplug the Ethernet cable makes no sense! Ok, I need to check this. I don't connect via cable since some time, so I could've easily missed this bug. [..] I don't use wicd for eth0 because it is too limited: depending on the environment (remote router), I sometimes need a static IP address and sometimes need to use DHCP (this is possible with ifup + guessnet, but not with wicd). There are wired profiles you can use for that -- each profile has its own settings, and you can switch them basing on the network you're trying to connect to. I guess that guessnet automatically understand which network you're on: if it is true, then this is the only thing missing to wicd. :) On Fri, 6 Jan 2012 10:57:02 +0100, Vincent Lefevre wrote: This still occurs, at least when the Ethernet cable is unplugged. So the suspend bug is gone? In the wicd logs: [...] 2012/01/06 10:24:34 :: ifconfig eth0 up 2012/01/06 10:24:36 :: [..] 2012/01/06 10:24:36 :: attempting to set hostname with dhclient 2012/01/06 10:24:36 :: using dhcpcd or another supported client may work better 2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0 2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0 2012/01/06 10:24:37 :: ifconfig eth0 down 2012/01/06 10:24:37 :: ifconfig eth0 up [...] In this log, I don't understand when you unplug your cable. Could you please re-take it so that it is a bit clearer? I'd suggest doing: $ tail -f /var/log/wicd/wicd.log // send some newlines // write something I'm unplugging the cable, and some more newlines // unplug the cable // copy-paste My config has changed a bit, and I now use netplug, but wicd also confuses netplug, meaning that I lose the network connection. (btw, I've had some requests to use NETLINK in wicd too :)) Note: in the wicd preferences, Always switch to a wired connection when available is unticked. So, wicd should never attempt to modify the eth0 settings. As a workaround, one can leave the wired interface blank in the preferences. If you don't want wicd to mess with eth0 at all then yes, that's the way of doing it. Obviously, if you have that box unticked, wicd shouldn't attempt a connection on plug, nor a disconnection on unplug (unless the connection was started by itself). I can't remember if originally it didn't touch interfaces listed in /etc/network/interfaces -- but it would be nice to support that too. However I'm quite busy releasing 1.7.1, so this feature might come with 1.7.2 or later :) Thanks, and sorry for not replying for so long, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
Hi David, On 2012-01-06 11:37:31 +0100, David Paleino wrote: On Thu, 19 Nov 2009 23:41:10 +0100, Vincent Lefevre wrote: [..] I don't use wicd for eth0 because it is too limited: depending on the environment (remote router), I sometimes need a static IP address and sometimes need to use DHCP (this is possible with ifup + guessnet, but not with wicd). There are wired profiles you can use for that -- each profile has its own settings, and you can switch them basing on the network you're trying to connect to. I guess that guessnet automatically understand which network you're on: if it is true, then this is the only thing missing to wicd. :) Yes, guessnet allows one to do various tests. In particular, I test the MAC address of 192.168.0.1, and I have a special config for that. On Fri, 6 Jan 2012 10:57:02 +0100, Vincent Lefevre wrote: This still occurs, at least when the Ethernet cable is unplugged. So the suspend bug is gone? I'm not sure, or it doesn't have always an effect (due to a bug in the current video driver, I think, the screen remains off, so that I almost no longer suspend the machine -- anyway I'll have to do tests for a bug report concerning the video driver problem, which is a regression). In the wicd logs: [...] 2012/01/06 10:24:34 :: ifconfig eth0 up 2012/01/06 10:24:36 :: [..] 2012/01/06 10:24:36 :: attempting to set hostname with dhclient 2012/01/06 10:24:36 :: using dhcpcd or another supported client may work better 2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0 2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0 2012/01/06 10:24:37 :: ifconfig eth0 down 2012/01/06 10:24:37 :: ifconfig eth0 up [...] In this log, I don't understand when you unplug your cable. Could you please re-take it so that it is a bit clearer? It was done a few seconds before. In /var/log/syslog: Jan 6 10:24:31 xvii kernel: [26255.600180] e1000e: eth0 NIC Link is Down Jan 6 10:24:31 xvii netplugd[16325]: /etc/netplug/netplug eth0 out - pid 16325 Jan 6 10:24:32 xvii logger: /sbin/ifdown -v eth0 (the ifdown was done by netplug, as expected). As a workaround, one can leave the wired interface blank in the preferences. If you don't want wicd to mess with eth0 at all then yes, that's the way of doing it. But it would be nice to be able to see the status. Obviously, if you have that box unticked, wicd shouldn't attempt a connection on plug, nor a disconnection on unplug (unless the connection was started by itself). I can't remember if originally it didn't touch interfaces listed in /etc/network/interfaces -- but it would be nice to support that too. Don't forget things like: mapping eth0 script guessnet-ifupdown map default: eth0-dhcp map debug: true map timeout: 10 (i.e. with mapping instead of iface). However I'm quite busy releasing 1.7.1, so this feature might come with 1.7.2 or later :) OK, thanks. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged
Package: wicd Version: 1.6.2.2-3 Severity: important When I suspend my laptop or unplug the Ethernet cable, wicd deconfigures the wired (eth0) interface, even though I wasn't connected via wicd. I don't know whether wicd does that directly or whether this is done by dhclient (the logs show that dhclient is started at this time, and it is started by wicd, because if I stop the wicd daemon, this no longer happens). In any case, wicd is the culprit, because starting dhclient when I suspend my laptop or unplug the Ethernet cable makes no sense! This is an important problem, because at wake up or when I plug in the cable, the eth0 interface isn't reconfigured and my connection remains lost. Note: in manager-settings.conf, I have wired_connect_mode = 1, in order not to connect automatically. I don't use wicd for eth0 because it is too limited: depending on the environment (remote router), I sometimes need a static IP address and sometimes need to use DHCP (this is possible with ifup + guessnet, but not with wicd). -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages wicd depends on: ii adduser 3.111add and remove users and groups ii dbus1.2.16-2 simple interprocess messaging syst ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii dhcp3-client3.1.3-1 DHCP client ii ethtool 6+20090323-3 display or change Ethernet device ii iproute 20090324-1 networking and traffic control too ii iputils-ping3:20071127-2 Tools to test the reachability of ii lsb-base3.2-23 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ii psmisc 22.8-1 utilities that use the proc file s ii python 2.5.4-2 An interactive high-level object-o ii python-dbus 0.83.0-1 simple interprocess messaging syst ii python-glade2 2.16.0-1 GTK+ bindings: Glade support ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge ii python-support 1.0.4automated rebuilding support for P ii python-urwid0.9.8.4-1curses-based UI/widget library for ii wireless-tools 29-2 Tools for manipulating Linux Wirel ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (I Versions of packages wicd recommends: ii gksu 2.0.2-2+b1 graphical frontend to su ii python-notify 0.1.1-2+b1 Python bindings for libnotify ii sudo 1.7.2p1-1 Provide limited super user privile Versions of packages wicd suggests: ii pm-utils 1.2.6.1-1 utilities and scripts for power ma -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
