Your message dated Fri, 10 Oct 2014 14:26:35 +0200
with message-id <[email protected]>
and subject line Re: dnssec-trigger: incorrect DNS servers are used when 
network-manager connects to VPN
has caused the Debian Bug report #760147,
regarding dnssec-trigger: incorrect DNS servers are used when network-manager 
connects to VPN
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
760147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760147
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.13~svn685-1
Severity: normal

Dear Maintainer,

when NetworkManager connects to a VPN, dnssec-trigger still uses the old DNS 
servers from the "outer"
(plain) network connection.
I can see the following in the system journal:

Sep 01 11:12:12 r-schnelltop logger[3766]: dnssec-trigger-hook(networkmanager) 
vpn0 vpn-up added global DNS 134.96.7.100 134.96.7.99 134.96.7.5

However, these are the DNS servers of wlan0. The VPN returned a different set 
of DNS servers.
Only after supplying the VPN-DNS-servers to dnssec-trigger-control, everything 
works as expected.

Kind regards
Ralf

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dnssec-trigger depends on:
ii  init-system-helpers  1.21
ii  libc6                2.19-9
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0         2.40.0-4
ii  libgtk2.0-0          2.24.24-1
ii  libldns1             1.6.17-5
ii  libssl1.0.0          1.0.1i-2
ii  python               2.7.8-1
ii  unbound              1.4.22-2

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- Configuration Files:
/etc/dnssec-trigger/dnssec-trigger.conf changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi,

> I did a debugging session with Pavel. It turns out this is a duplicate
> of <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757320>, the
> shell-based hook does not do the VPN thing right - but if I call the
> dnssec-trigger-script manually, the correct servers are set for unbound.

The other bug got fixed, and now VPNs work fine. Thanks a lot!

Kind regards
Ralf

--- End Message ---

Reply via email to