[Resolvconf-devel] Bug#612351: resolvconf: move VPN interfaces to the end of interface-order
andrew at pimlott.net
Mon Feb 7 22:28:04 UTC 2011
Currently, tun* is ahead of eth* in /etc/resolvconf/interface-order. I
think that putting the VPN interfaces at the end may be a better
default. By "VPN interfaces" I mean the interfaces that are typically
used to reach VPNs or other special networks--probably tun* and tap*--as
opposed to the public internet, usually reached by eth*, etc.
I suggest this because, in typical use, most resolver requests are for
the public internet and can be handled by the "standard" resolver, which
is usually faster and more reliable than the resolver on the VPN
(typically running on a crappy VPN gateway and managed by an overworked,
underfunded, or incompetent corporate IT department). Also, in bug
460200, the VPN crashed without running "resolvconf -d", resulting
delays attempting to reach the VPN's nameservers. This is probably a
bug in vpnc, but bugs happen, and if the default is to use the standard
resolver first, the bug is not as painful.
Of course, this is just my use case, and you may have more information
about other use cases where this thange would break things. Just
offering it as an idea.
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages resolvconf depends on:
ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy
ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip
resolvconf recommends no packages.
resolvconf suggests no packages.
-- Configuration Files:
/etc/resolvconf/resolv.conf.d/base [Errno 2] No such file or directory: u'/etc/resolvconf/resolv.conf.d/base'
-- debconf information:
* resolvconf/link-tail-to-original: false
More information about the Resolvconf-devel