I concur with @tomasz-kontusz. This is a problem for users of network-
manager-sstp. Attaching a patch that I've tested with network-manager-
sstp
** Patch added: "missing nm-sstp-service-*, use nm-*-service-*"
The patch from #19 (which is now in Ubuntu) is not enough - there are
still problems with network-manager-sstp, which calls pptp with "nm-
sstp-service-*".
If there's no better workaround, can the userpeerdns and
000resolveconf scripts at least bail on all "nm-*-service-*"?
--
You received
The problem is still there on Ubuntu 18.04.4 LTS. The workaround from
comment #30 works for me.
$ apt show ppp
Package: ppp
Version: 2.4.7-2+4.1ubuntu5
Status: install ok installed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in
Ubuntu 18.04.4 LTS, same problem: DNS_PROBE_FINISHED_BAD_CONFIG after
disconnecting from MS VPN.
I can confirm that workaround by Marius Gedminas from comment #30 works as
expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp
The workaround I now use is to modify the cp -a command in /etc/ppp/ip-
up.d/usepeerdns to look like this:
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" || {
rm -f "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" "$REALRESOLVCONF.tmp"
exit 1
}
--
You received this bug
Unfortunately the fix doesn't work and Ubuntu 19.10 with ppp
2.4.7-2+4.1ubuntu4.1 is still affected. I've added a bunch of
logger -t usepeerdns -- doing stuff
commands to /etc/ppp/ip-up.d/usepeerdns and /etc/ppp/ip-
down.d/usepeerdns.
Here's what I see when /etc/resolv.conf is
Will this get backported to Bionic please? Or do we have to wait for the
20.4 LTS release?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a
I too have been facing this issue since a few releases, and still face
it on Ubuntu 19.10 (resolvconf not installed as it causes other issues):
# sudo rm /run/systemd/resolve/stub-resolv.conf.tmp
# sudo systemctl restart NetworkManager
# ls -la /etc/resolv.conf /run/systemd/resolve/
lrwxrwxrwx
Can confirm. Work-around is to turn off WiFi and re-enable it.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
This bug was fixed in the package ppp - 2.4.7-2+4.1ubuntu2
---
ppp (2.4.7-2+4.1ubuntu2) eoan; urgency=medium
* debian/extra/ip-up.d/usepeerdns: Added NetworkManager check, which
lets the script exit when NetworkManager is in use (LP: #1778946).
-- Till Kamppeter Fri, 08
Uploaded to Eoan.
If this needs to be SRUed, please adjust the bug description to follow
the template:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
Thanks!
** Changed in: ppp (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you
I've manually applied the patch proposed in comment #22 to my Ubuntu
18.10 desktop, and I can confirm that it fixes the issue for me. I
haven't seen any regression either, although my testing has been very
limited so far.
I've been experiencing this bug ever since Ubuntu 18.04 when
disconnecting
** Changed in: ppp (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a vpn/pptp connection
Status in
** Bug watch removed: GNOME Bug Tracker #785771
https://gitlab.gnome.org/785771
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a
** Also affects: ppp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363
Importance: Unknown
Status: Unknown
** Changed in: ppp (Ubuntu)
Importance: Undecided => Medium
** No longer affects: network-manager (Ubuntu)
** No longer affects: resolvconf (Ubuntu)
--
Attached is the debdiff with the proposed fix of comment #19 applied.
Someone with appropriate upload rights to Disco, please upload it.
I could not actually test it as I have no access to a Microsoft VPN,
I do not see any regression though. I can access Canonical's VPNs and
while having
As I see the comments here, the fix is to modify the file /etc/ppp/ip-
up.d/usepeerdns according to comments #17 and #19. /etc/ppp/ip-
up.d/usepeerdns is part of the ppp package, so the bug needs to be
fixed in the ppp package.
** Changed in: network-manager (Ubuntu)
Status:
Although this problem is easy to fix once you know what to do, I don't
know if it should be only "Medium" importance because the impact is
massive: no DNS is available. If you're not technically inclined enough
to know to go poking around /etc/resolv.conf if DNS breaks, you would
never be able to
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Comment 6 and 7 in the upstream GNOME NetworkManager-pptp bug report :
https://bugzilla.gnome.org/show_bug.cgi?id=785771#c6
are relevant to this bug (but not the 'cp -a' issue).
As mentioned, the following exit in /etc/ppp/ip-up.d/000resolvconf when
the interface is managed by NM, seems the
I wasn't able to redirect the stderr from the following line in /etc/ppp
/ip-up.d/usepeerdns (probably because of something pppd is doing) :
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
So I modified the cp.c source from the coreutils package and redirected
stderr to a
Sorry ignore comment #16 as the following line in /etc/ppp/ip-
up.d/usepeerdns will exit because of the '#!/bin/sh -e' shebang
line:
cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
So my original suggestion of replacing the following line:
cp -a "$REALRESOLVCONF"
I can confirm the issue is the following line in /etc/ppp/ip-
up.d/usepeerdns as previously mentioned :
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
The variable expansion of that line is :
cp -a /run/systemd/resolve/stub-resolv.conf
Correction the following line in /etc/ppp/ip-up.d/usepeerdns
probably should be changed from :
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
to:
cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
--
You
Sorry for the delay here.
Is this what you were interested in @cyphermox?
While VPN is up:
$ ls -lha /run/systemd/resolve/
total 16K
drwxr-xr-x 3 systemd-resolve systemd-resolve 140 Nov 28 12:29 .
drwxr-xr-x 20 rootroot460 Nov 28 12:28 ..
drwx-- 2 systemd-resolve
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ppp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
tagging as rls-cc-notfixing, while good to fix it impacts a non default
plugin and we don't think it's important enough to be actively tracked
by desktop
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Desktop
cp -a is supposed to preserve ownership. -a means "-dR --preserve=all".
Could someone look at what happens, by displaying more than just the
/run/systemd/resolve/stub-resolv.conf file? All files in
/run/systemd/resolve/ are relevant here.
This has more smells of being affected my UMASK and
Also confirming that installing resolvconf makes DNS work once the VPN
is disconnected.
--
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/1778946
Title:
No dns resolution after
Installing resolveconf fixed it for me, now DNS resolv works after PPTP
disconnects.
--
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/1778946
Title:
No dns resolution after
I spoke to stgraber a bit, he said that the resolvconf thing is probably
a red herring.
--
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/1778946
Title:
No dns resolution after
This upstream bug suggests that the problem can be resolved by installing
resolvconf:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363
I will test this, but I'm having problems with VPNs on this network atm.
** Bug watch added: Debian Bug tracker #378363
It would be a bug in "ppp" which provides that file then and worth
reporting to Debian because it's coming from there directly
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Tags added: rls-cc-incoming
--
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/1778946
Title:
No dns resolution after closing a vpn/pptp connection
Status in network-manager
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
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/1778946
Title:
No dns resolution after closing
** Also affects: ppp (Ubuntu)
Importance: Undecided
Status: New
--
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/1778946
Title:
No dns resolution after closing a
** Also affects: openvpn-systemd-resolved (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: openvpn-systemd-resolved (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
seems related to the file /etc/ppp/ip-up.d/usepeerdns on line 23-24
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
mv -f "$REALRESOLVCONF.tmp" "$REALRESOLVCONF"
the cp command doesn't preserve file ownership
--
You received this bug notification because you are a member
Before start pptp vpn:
$ ls -laF /run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 714 jun 30 18:26
/run/systemd/resolve/stub-resolv.conf
After start pptp vpn:
$ ls -laF /run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 714 jun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
41 matches
Mail list logo
