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
