This still happens in Xenial.
#7 has it right, if the IPv4 and IPv6 'use this connection only for
resources on its network' are different then the default DNS server is
dropped.
It is very easy to make this mistake and very hard to figure out that is
the problem!
--
You received this bug
For me, this seems to have been a case of VPN server misconfiguration going
unnoticed until the recent fixes. Just in case you're in a position where
somebody else is responsible for the server, or there's a different etiology,
checking
IPv6 [+] use this connection only for resources on its
I faced same issue.
My setup is:
IPv4 [+] use this connection only for resources on its network
IPv6 [-] use this connection only for resources on its network
I get `REFUSED` when I try to run `dig google.com.` and I see following
at /var/log/syslog:
May 12 21:54:45 localhost
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-openvpn (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm facing this problem too...
And one more... The `network-manager-openvpn` on Trusty is replacing the
default route of my Ubuntu Desktop to the VPN tunnel! This way, I am
unable to browse the Internet after stablishing the OpenVPN connection
through NetworkManager...
No idea about how to
Guys,
Please, ignore my latest message, I just enabled the option:
Edit VPN Connection 1 - IPv4 Settings - Routes... - [X] Use this
connection only for resources on this network.
Sorry about the buzz...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
One more comment: I had a leftover IPv6 config on the server, which
basically ment it was enabled but not really used. After disabling it
(commenting out all server-ipv6) everything works as it used to, just
without IPv6.
I've noticed now what I missed before, in syslog (again, parts removed):
2 more observations:
- After upgrading saucy to trusty: I have the same problem
- Downgrading network-manager-openvpn to saucy version (0.9.8.2-1ubuntu2) fixed
the problem.
It seems that the IPv6 patches somehow broke IPv4 for me, but I wasn't
able to figure out why...
--
You received this
