Confirmed, just setting up new Xubuntu virtual machine 17.10 - after all
updates.
Architecture: amd64
network-manager-openvpn and network-manager-openvpn-gnome both Version:
1.2.10-0ubuntu2
I originally started with a config downloaded from pfSense. As usual, openvpn
from command line is
FWIW on my laptop (16.10) DNS queries are working as I wish it (ie
"correctly"). With VPN disconnected all queries are going to the home router
(192.168.33.1), queries for eg amachine.csl are sent there and come back
NXDOMAIN.
With VPN connected, queries on .csl are going to the remote VPN
Looks like finding out what DNS server is *asked* about a query (add
log-queries to dnsmasq.conf) is going to require another reboot : if I
restart NetworkManager then the VPN connection will also restart ..
circular reference to this bug again. I can't afford to keep doing this
during a work
Re "if you are using a VPN service for privacy purposes" - I have a contrary
use case. I want to use my home router as much as possible, and the VPN
(which may be my office network, or more critically a client's network) *only*
for traffic required to go there.
My understanding was that this
On 16.10 - Confirmed that after reboot, my VPN-pushed DNS comes back, on
second connection it is missing. I've logged a fresh Bug #1644098
pertaining ONLY to this issue. (Please don't pollute it with "DNS
doesn't work at all" comments!)
--
You received this bug notification because you are a
Finally see Bug #120 particularly the later (November 2016)
comments
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1644098
Title:
Network Manager + OpenVPN does not
/etc/NetworkManager/NetworkManager.conf contains:
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=false
(There are various posts floating around to the effect that
'dns=dnsmasq' should be commented out. However this is how the Ubuntu
install set it so assuming that either
Remote VPN is pfSense 2.3.2
>From syslog, expurgated (but not tampered with, no real secrets here):
:: Here's the WiFi coming up (showing local LAN) ::
Nov 23 19:06:41 rukbat dhclient[2169]: DHCPACK of 192.168.33.117 from
192.168.33.1
Nov 23 19:06:41 rukbat NetworkManager[1216]:
Public bug reported:
Scenario:
Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I
only have the one computer to test with, the 16.10 is definitely relevant (I
did not have this problem on 16.04) but I can't tell if the upgrade is part of
it, (the upgrade may or may
This might be my a-ha moment from comment # 64 "after upgrading to
16.10, yes it is even worse, the first VPN connection works as it
should, but after disconnect/connect, DNS from VPN isn't propagated"
I came to this bug because suddenly my VPN connection wasn't working
when I *swear* it was
10 matches
Mail list logo
