[Resolvconf-devel] Bug#626709: resolvconf: Add NetworkManager to interface-order

[Chris AtLee]

Package: resolvconf
Version: 1.48
Severity: normal

Something with NetworkManager or resolvconf changed recently so that
name servers retrieved from NetworkManager after connecting to a VPN
appear *after* the wlan0/eth0 name servers, making it impossible for me
to resolve VPN addresses. Adding NetworkManager* to interface-order
fixes this problem for me.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages resolvconf depends on:
ii  debconf [debconf-2.0]         1.5.39     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/interface-order changed:
lo.inet*
lo.dnsmasq
lo.pdnsd
lo.!(pdns|pdns-recursor)
lo
tun*
NetworkManager*
tap*
hso*
eth*
ath*
wlan*
ppp*
*


-- debconf information:
  resolvconf/downup-interfaces:
  resolvconf/link-tail-to-original: false
  resolvconf/linkify-resolvconf: true