Dear Maintainer,

I am experiencing a problem with establishing OpenVPN connections with Network
Manager, where the routing table is not set up correctly after the VPN tunnel
has been established. In previous stable version (Debian 8) this only occured
when using the KDE desktop but on upgrade to Debian version 9 it has started
happening when using Gnome 3 also - which still persists on update to testing.
Problem also exist on two other systems currently still on Debian 8 (KDE only),
and across two VPN providers.

Example of incorrect routing table:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         dsldevice.lan   0.0.0.0         UG    100    0        0 eth0
10.8.8.0        0.0.0.0         255.255.255.0   U     50     0        0 tun0
5a.42.caa1.ip4. dsldevice.lan   255.255.255.255 UGH   100    0        0 eth0
link-local      0.0.0.0         255.255.0.0     U     1000   0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 eth0
dsldevice.lan   0.0.0.0         255.255.255.255 UH    100    0        0 eth0

Note default route is eth0, should be tun0. Manual alteration of routing table
is a viable work-around for the problem. Data leakage and efficacy of work-
around confirmed using wireshark.

Yours Sincerely,
Chris Pryor

This issue is fixed upstream and should appear in the next releases of
BIND 9.10 and 9.11, as well as all 9.12 releases.

https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=cee0d603a3b142df744d94b18cf42f086cdb0ff7

Tony.

Drat, sorry, that message was supposed to be for bug #867570

Tony.