*** This bug is a duplicate of bug 994575 ***
https://bugs.launchpad.net/bugs/994575
Thomas thank, this appears to be working fine with resolvconf
1.69ubuntu1 on Trusty, so I'm marking it as a duplicate of the bug you
referenced.
** This bug has been marked a duplicate of bug 994575
Hi Alkis,
Do you still have this problem? Or was it fixed in resolvconf
1.67ubuntu2:
resolvconf (1.67ubuntu2) quantal; urgency=low
[...]
* Update ppp hooks to also exit when passed
/org/freedesktop/NetworkManager/PPP/* (LP: #994575)
--
You received this bug notification because you
Hi Thomas,
sorry, I'm only using LTS releases so I'm still on 12.04 here:
$ dpkg-query -W resolvconf
resolvconf 1.63ubuntu16
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
If you have a chance to test a more recent resolvconf release, please
report back with your findings.
** Changed in: network-manager-pptp (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
We don't need VNC access.
So what I can think of here; it that I still don't know what kind of VPN
you used. Was it vpnc, openvpn, openconnect or pptp? This is important
because the behavior may change radically from one to the other.
What I tried was VPNC, seemed to work properly. I'll re-test
Could you also start the vpn plugin you use in debug mode
and send me the logs via email?
I've mail you the output of:
$ sudo /usr/lib/NetworkManager/nm-pptp-service --debug
(it's a pptp connection)
But, there was one try today were I couldn't reproduce the problem
anymore:
1. As I said,
Thanks.
Can you confirm exactly which DNS servers are the bad ones? I thought it was:
nameserver 150.140.1.4
nameserver 150.140.1.25
But those don't appear in NetworkManager's interface file for
resolvconf, which makes it look like it may be a bug directly in
n-m-pptp's way of getting DNS
Clearly a bug in either how n-m-pptp spawns the vpn process, or how it
goes out to update DNS. Regardless, then this may need to be reassigned
if pptp doesn't provide a way to avoid updating DNS directly.
** Package changed: network-manager (Ubuntu) = network-manager-pptp
(Ubuntu)
** Changed in:
So the VPN connection is set to addresses only?
Yes.
I can't reproduce this on my system (though dns=dnsmasq is enabled, of
course), with, or without a DNS being set, with the vpn configured as
addresses only.
I removed the standalone dnsmasq and I'm using the nm-spawned one now.
Same
So the VPN connection is set to addresses only?
Setting Confirmed/Medium, since this would indeed be a bug in that case.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
I can't reproduce this on my system (though dns=dnsmasq is enabled, of
course), with, or without a DNS being set, with the vpn configured as
addresses only. What I used was network-manager-vpnc.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Incomplete
--
You received this
11 matches
Mail list logo
