Your message dated Tue, 18 Mar 2025 21:16:36 +1000
with message-id <[email protected]>
and subject line Re: network-manager-l2tp: trying access /usr/lib/ipsec/charon
which cannot be installed
has caused the Debian Bug report #1100104,
regarding network-manager-l2tp: trying access /usr/lib/ipsec/charon which
cannot be installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1100104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100104
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager-l2tp
Version: 1.20.20-1+b1
Severity: normal
Hello!
I was trying to connect to network over l2tp.
# apt install network-manager-l2tp-gnome
setup connection using L2TP and IPSEC in GNOME settings.
After trying to connect, this appears in the log:
NetworkManager[21788]: <info> [1741693089.1265] audit:
op="connection-activate" uuid="_redacted_" name="IceW>
nm-l2tp-service[26306]: nm-l2tp-service (version 1.20.20) starting...
nm-l2tp-service[26306]: /sbin/ipsec status > /dev/null 2>&1
nm-l2tp-service[26306]: /sbin/ipsec start --conf /run/nm-l2tp-_redacted_/"
ipsec.conf --debug
NetworkManager[26323]: IKE daemon '/usr/lib/ipsec/charon' not found
ipsec_starter[26323]: IKE daemon '/usr/lib/ipsec/charon' not found
NetworkManager[21788]: <warn> [1741693089.1915]
vpn[0x555942418f10,_redacted_,"_redacted_"]: failed to connect:>
strongswan-charon cannot be installed as it conflicts.
Thank you
David
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.17-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages network-manager-l2tp depends on:
ii libc6 2.41-4
ii libglib2.0-0t64 2.84.0-1
ii libnm0 1.52.0-4
ii libnspr4 2:4.36-1
ii libnss3 2:3.109-1
ii libssl3t64 3.4.1-1
ii network-manager 1.52.0-4
ii ppp 2.5.2-1+1
ii xl2tpd 1.3.18-1+b1
network-manager-l2tp recommends no packages.
network-manager-l2tp suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: network-manager-l2tp
Version: 1.20.20-2
Hi David,
On Tue, 11 Mar 2025 14:51:04 +0100 David Heidelberg <[email protected]> wrote:
> I managed to get the NM L2TP plugin working fetching the
> strongswan-charon manually and injecting the charon binary into
> /usr/lib/ipsec/ by hand.
>
> With latest strongswan with this workaround, IPSEC L2TP connection works
well.
There is a bit more info about the network-manager-l2tp and strongswan
dependency issues here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098710
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098714
With network-manager-l2tp 1.20.20-2, it now depends on stongswan-charon
instead of the stongswan meta package.
stongswan-charon-6.0.1-1 has a dependency fix and now depends on
strongswan-starter instead of strongswan-swanctl.
So I believe this issue has been fixed.
Cheers,
Doug
--- End Message ---
