Hi Yves-Alexis,
> Sorry for breaking your use case, I didn't really check the reverse
> dependencies of the strongswan metapackage (to be honest that
> metapackage was mostly intended for end-users, not packagers).
No worries.
Currently network-manager-l2tp package has the following dependency:
Hi Jongmin,
Thanks for the bug report.
> Although I do not have full context of this package, I suggest fixing the
> issue by trying one of these:
>
> 1. Explicitly depends on "strongswan-starter" instead of "strongswan"
> 2. Switch to use "strongswan-swanctl" (although I am not entirely know
Package: network-manager-l2tp
Severity: fixed
Hi Phil,
On 12/25/24 17:18, Phil Wyett wrote:
> I started a review when the package appeared for a short time on Debian
> Mentors. A review of licenses, show below. Possible false positives.
I was only intending to keep my upload on Debian Mentors f
Hi Rémi,
> since upgrading to 1.20.12-1, I cannot connect to my ipsec/l2tp vpn anymore.
>
> I tried many things, but the only thing that works is disabling mppe, or
> downgrading to 1.20.10-1
>
> Here are the debug log for 1.20.12-1:
> ...
>
> And here is the log with 1.20.10-1:
...
> I still
> If I do an update from a previously installed version using the following
> command:
>
> sudo debi -u network-manager-l2tp_1.20.10-1_amd64.changes
I meant upgrade, not update.
> I get the following error when trying to establish a L2TP VPN
> connection:
>
> ... starting: failure to start V
Hi Michael,
> For consistencies sake, please consider applying the attached patch,
> which moves the helper binaries to /usr/libexec.
There was a new upstream version, so I updated to the newest version and
incorporated the patch.
If I do an update from a previously installed version using the
Yeah, basically the same as bug #619557, xl2tpd upstream still doesn't support
IPv6, so IPv6 support was never added to NetworkManager-l2tp.
NetworkManager-l2tp >= 1.20.0 can use kl2tpd from the Katalix go-l2tp package
for L2TP support:
https://github.com/katalix/go-l2tp
Katalix are the ones
Hi Mark,
> When attempting to enable a L2TP VPN connection via Network
> Manager if the connection fails then an error message is popped
> up briefly saying "Activation of network connection failed" but
> no diagnostics are made available indicating what the problem
> might be, either immediately
Hi Marcel ,
Actually you might be having an issue with your existing VPN network connection
still having ipv4.ignore-auto-routes enabled, see:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946#note_1350911
my previous suggestion of switching from strongswan to libreswa
Hi Marcel ,
I was about to close this still open bug (which was cloned from a bug that was
closed), but decided to check the forum link you posted first :
https://debianforum.de/forum/viewtopic.php?t=183809
and noticed you said there you were still having an issue with
network-manager-l2tp and
Hi smcv,
No worries, I'll was planning on working on it this weekend, with floods and my
father passing away last month, I hadn't so far gotten back to looking at it
yet.
Cheers,
Doug
-Original Message-
From: Simon McVittie
Sent: Thursday, 7 April 2022 7:17 PM
To: Debian Bug Trackin
Hi Michael,
> Is there anything to fix on the network-manager package side or can
> this issue be closed?
With the upgrade of the network-manager package to 1.36.4-1, the
VPN routing issue appears to have been resolved.
I just checked again now that I'm not able to reproduce the issue,
so this i
As mentioned to the upstream NetworkManager 1.36.2 VPN routing bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946
The routing issue when the "Use this connection only for resources on its
network" IPv4 setting is enabled, no longer appears to occur with
NetworkManag
I suspect this is the same as the following upstream NetworkManager 1.36.2
routing bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/946
I assume you have enabled the "Use this connection only for resources on
its network" checkbox in the VPN connection's IPv4 settings?
macOS already handles the missing space before M= with code that does similar
to the upstream ppp patch, 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 n
Package: ppp
Version: 2.4.8-1+1~exp1
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.
The following upstream patch handles the non-comp
Forgot to mention network-manager-l2tp-1.2.12-1 was uploaded to
mentors.debian.net :
https://mentors.debian.net/package/network-manager-l2tp
awaiting pre-approval for testing before it is uploaded to unstable.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package network-manager-l2tp
I'm the current upstream maintainer of Networkmanager-l2tp and the Debian
package maintainer of network-manager-l2tp. My Debian package sponsor s
Package: xl2tpd
Version: 1.3.11-1
Kernels 4.15 and 4.16 break xl2tpd, please see following upstream issue for
more details :
https://github.com/xelerance/xl2tpd/issues/147
The following commit/patch fixes the issue:
https://github.com/xelerance/xl2tpd/commit/9c2cd4933478a83075df5b10f24af75
Hi Michael,
I've uploaded to https://mentors.debian.net/package/network-manager-l2tp , hope
it looks okay. If so, I'll commit the changes to
https://github.com/nm-l2tp/debian
One minor difference, I just changed the order of two
override_dh_auto_configure lines in debian/rules to match netwo
Package: wnpp
Owner: Douglas Kosovic
Severity: wishlist
* Package name: network-manager-l2tp
Version : 1.2.4
Upstream Author : Douglas Kosovic
* URL : https://github.com/nm-l2tp/network-manager-l2tp
* License : GPL
Programming Lang: C
Description
21 matches
Mail list logo
