Package: network-manager-openvpn Version: 1.2.4-1 Severity: important Tags: ipv6
Dear Maintainer, in a OpenVPN setup where everything is proven to work as expected using the `openvpn` command line client, the following happens when using NetworkManager to connect to the VPN instead: - first, the connection is established successfully - but then, no extra routes or DNS servers are set The extra routes (i.e. any routes not to 10.8.0.0) or DNS servers are not set whether the OpenVPN server pushes them down or whether they are set manually in the NM GUI. In the latter case, the settings for them are properly written into `/etc/NetworkManager/system-connections/<connection name>`, though. If routes and DNS servers are manually set after the VPN connection has been established by NM, everything works normally. This bug might be connected to #487378, even though that bug report does not mention DNS servers at all, nor the distinction between pushed routes/DNS servers and ones set through the NM GUI. Cheers, Jonathan -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager-openvpn depends on: ii adduser 3.115 ii libc6 2.23-2 ii libglib2.0-0 2.48.1-2 ii libnm0 1.2.2-2 ii network-manager 1.2.2-2 ii openvpn 2.3.11-2 network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information _______________________________________________ Pkg-utopia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
