[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

2016-07-12 Thread Douglas Kosovic
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

[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

2017-03-13 Thread Douglas Kosovic
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

[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

2017-06-14 Thread Douglas Kosovic
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

[Touch-packages] [Bug 1692066] Re: [Request] Libreswan plugin for Network Manager

2017-10-27 Thread Douglas Kosovic
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) :

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-19 Thread Douglas Kosovic
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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-20 Thread Douglas Kosovic
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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
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

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
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"

[Touch-packages] [Bug 1970068] Re: L2TP+IPSec not working after upgrade to 22.04 LTS

2022-04-24 Thread Douglas Kosovic
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