Package: ifupdown Version: 0.6.8+nmu1 Severity: normal I use ifplugd, guessnet and custom interface names in /etc/network/interfaces to have my setup immediately right when I'm at home or at university. However, I noticed that dhclient (used for DHCP) generates /etc/resolvconf/run/interface/eth0, which seems correct so far. However, the dns-nameservers statements in /etc/network/interfaces are written to /etc/resolvconf/run/interface/eth0.inet and therefore I end up having resolvconf mixing up my current configuration and the last DHCP DNS configuration in /etc/resolv.conf
My setup in /etc/network/interfaces looks like this: auto lo iface lo inet loopback allow-hotplug wlan0 eth0 mapping eth0 script guessnet-ifupdown map default: dhcp iface wlan0 inet manual wpa-driver wext wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf iface default inet dhcp iface home inet static address 192.168.1.42 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 dns-search local.lan dns-nameservers 192.168.1.1 test peer address 192.168.1.1 mac 00:11:22:33:44 iface uni inet dhcp up /home/michael/Uni/VPN/wrapper.sh & down /home/michael/Uni/VPN/killwrapper.sh My temporary workaround is editing /etc/dhcp3/dhclient-enter-hooks.d/resolvconf to write its configuration to eth0.inet ($interface.inet) aswell. What's the clean solution, e.g. how can I have /etc/network/interfaces not cause the file to be named eth0.inet? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]