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
