I think this is a duplicate of the following, although the xl2tpd errors
manifest slightly differently :
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1968336
But as others have confirmed, Ubuntu 22.05's xl2tpd-1.3.16-1 is
Nim's status change of no longer affects ppp I think was just a mistake
and rectified, but the rectification wasn't recorded in a new message.
This bug report no longer affects ppp >= 2.4.9, as it was fixed upstream
and is the reason the corresponding Debian bug was closed.
This SRU patch
** Bug watch added: Debian Bug tracker #968040
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968040
** Also affects: ppp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968040
Importance: Unknown
Status: Unknown
--
You received this bug notification because
macOS already handles the missing space before M=, extract from :
https://opensource.apple.com/source/ppp/ppp-862.120.2/Helpers/pppd/chap_ms.c.auto.html
//we'll allow the missing-space case from the server, even though
//it's non-conforming to spec!
dbglog("Rcvd
Public bug reported:
[Impact]
According to RFC2759, the format of PPP success packets is :
"S= M="
Recently Windows Server 2019 has started producing non-complaint PPP
success packets which have a space missing before the M= characters.
PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting
** Project changed: l2tp-ipsec-vpn => ubuntu
** Changed in: ubuntu
Status: New => Confirmed
** Package changed: ubuntu => network-manager-l2tp (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
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
I suggest you file a Debian Request for Package (RFP) for
network-manager-libreswan :
https://wiki.debian.org/RFP
Once the package is in Debian Sid, it will automatically make its way to
Ubuntu.
Or if you are able to provide a package, an Intent to Package (ITP) :
network-manager-l2tp 1.2.6-2 was accepted into Debian sid :
https://tracker.debian.org/pkg/network-manager-l2tp
The Debian package was automatically added to Ubuntu artful (17.10).
I've requested an Ubuntu backport of network-manager-l2tp from artful to
xenial (16.04) which includes
There is now a new PPA, network-manager-l2tp 1.2.4 for 17.04 (zesty), 16.10
(yakkety) and 16.04 (xenial) packages can be found here:
https://launchpad.net/~nm-l2tp/+archive/ubuntu/network-manager-l2tp
strongswan stable release updates for yakkety and xenial which fix the
aforementioned
I've posted a summary of current NetworkManager-l2tp known issues and
workarounds for Ubuntu and Debian here :
https://github.com/nm-l2tp/network-manager-l2tp/issues/12
I haven't created a new network-manager-l2tp PPA because because of the
strongSwan AppArmor name space issue involving
15 matches
Mail list logo
