[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
Suppose resolvconf were to be changed so that it omitted information from resolv.conf that appeared to be associated with a down interface. What if a resolvconf update happens when some interface happens temporarily to be down? Information gets omitted even though it should not be. What if a package (e.g., NetworkManager) doesn't name records like interface names? Etc. Keeping track of the networking subsystem is simply beyond the scope of resolvconf which is just a tiny bit of glue script. vpnc should not die abnormally. If it does and this can't be fixed then someone should write a vpnc watchdog which takes appropriate actions when vpnc dies abnormally. ** Changed in: resolvconf (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/262650 Title: resolvconf should not use dns info for interfaces that are down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/262650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
someone has to do a check, because there are times that the cleanup will not happen. if vpnc gets a kill -9, it can't cleanup and it would be difficult to argue that that is a bug with vpnc. there is a convention as you mention. if resolveconf enforced it, others would follow it. for that matter they already do seem to follow it. in the end you can point the fingers how ever you want, but this problem is easy to address in a general way in resolvconf and is hard to address (and impossible to address in general) at the interface side. this bug results in a really horrible user experience. it should be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/262650 Title: resolvconf should not use dns info for interfaces that are down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/262650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
One question is whether or not it is resolvconf's responsibility to
check upness of interfaces. Resolvconf is really just a registry.
Suppliers of nameserver information are responsible for updating the
information they have supplied. So the bug in this case is certainly
vpnc's.
Given that the bug exists and some maintainers are more responsive than
others, it's conceivable that a workaround could be implemented in
resolvconf.
But it would be a bit of a hack because resolvconf doesn't know for sure
what interfaces correspond to what records. Suppliers of nameserver
information run resolvconf -a $X for some value of X. By convention X
has the value ${INTERFACE}.${SUPPLIER} but not all suppliers follow
this convention. So resolvconf can't be sure what interface should be
checked. If a workaround were implemented it would have to be narrowly
focussed on the vpnc case.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/262650
Title:
resolvconf should not use dns info for interfaces that are down
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/262650/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
is there anyway to inspire action on this bug? it is still happening and it is super annoying! -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
Just seen this too. Also using vpnc - presumably it did not terminate correctly last time I shut down. -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
Ubuntu 8.10 resolvconf 1.42ubuntu2 network-manager 0.7~~svn20081018t105859-0ubuntu1 network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1 I'm experiencing exactly the same as described in #51339, i.e. my /etc/resolv.conf looks like this: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.0.1 ## wrong (from /etc/resolvconf/run/interface/eth1) nameserver 134.x.x.x ## correct search informatik.my-university.de After choosing the network connection via the network manager (wired via eth0), /etc/resolv.conf is being rewritten by resolvconf. It also includes the /etc/resolvconf/run/interface/eth1 even if this interface is down. Are there any intentions to adjust the behaviour of resolvconf as suggested by Benjamin Reed (the bug reporter)? -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
Benjamin's patch isn't in resolvconf trunk, I applied it locally and tested it with: vpnc + resolvconf + dnsmasq. The patch now has an ugly workaround to work with dnsmasq also and works with more interfaces. Although I think it would be better not to have vpnc die in the first place, so its resolvconf hooks fire, as they normally do. The patch may solve problems when something dies and /etc/resolvconf/run/interfaces/* files are still left (It probably happened to me with dnsmasq and it's lo.dnsmasq file), so maybe a pid should be associated with the interface files? If the pid doesn't exist anymore, we skip/delete the interface definition. And note the strange newline echoing in the script - without it, it glues item together, e.g: eth0tun0 instead of eth0 tune0 ** Attachment added: Additional adjustments in above patch http://launchpadlibrarian.net/18007430/list-records.patch_with_dnsmasq -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
** Attachment added: Only return interfaces that are up http://launchpadlibrarian.net/17156898/list-records.patch -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
