L2TP/IPSec VPN fails on Garuda but works on Pop!_OS/Kubuntu (same hardware)

Issues & Assistance
1

Problem: L2TP/IPSec VPN fails on Garuda Linux

Environment:

  • Hardware: [Ihr Laptop-Modell]
  • Garuda Version: [garuda-inxi output]
  • Kernel: 6.12.39-1-lts (tested both zen and lts)
  • strongSwan: 5.9.13 (downgraded from 6.0.1)
  • NetworkManager-L2TP: 1.20.16 (downgraded from 1.20.20)

What works:

  • :white_check_mark: Same hardware + Pop!_OS: VPN works perfectly
  • :white_check_mark: Same hardware + Kubuntu: VPN works perfectly
  • :white_check_mark: Same VPN server (Synology DS218)

What fails:

  • :cross_mark: Garuda Linux: “Zeitüberschreitung wurde erreicht”

Logs: [Ihre charon/strongSwan-Logs einfügen]

Tests performed:

  • Kernel downgrade (zen → lts)
  • strongSwan downgrade (6.0.1 → 5.9.13)
  • NetworkManager-L2TP downgrade (1.20.20 → 1.20.16)
  • PSK format troubleshooting
  • Manual strongSwan configuration

Conclusion: Garuda-specific issue, not version-related

CRITICAL: Fresh Garuda installation reproduces bug

Test Setup:

  • :white_check_mark: Fresh Garuda Linux (Live USB, untouched)
  • :white_check_mark: Same hardware that works with Pop!_OS/Kubuntu
  • :white_check_mark: Same VPN server (Synology DS218)

Results:

  • :cross_mark: Fresh Garuda: “dbus: failure” (11:14:09)
  • :white_check_mark: Pop!_OS (same hardware): VPN works
  • :white_check_mark: Kubuntu (same hardware): VPN works

Conclusion:
Systemic Garuda Linux bug, NOT user configuration issue.
No downgrades (strongSwan/NetworkManager-L2TP) can fix this.

2

Well.. perhaps you should post your garuda-inxi…without very less helpful.
And your description is also not very helpful. !! It looks like AI script !! and useful info i don’t
read.

  • this is not a downgrade, this is “only” a different kernel and you have then different dependence with hardware modules.
  • sorry.. Garuda linux is not ubuntu or pop! os

Do you have the right settings to use this ? Only install and all is running, well, can not work.

as info to read:
Pls next time use your private search to find a solution, too.
AI can mostly not help for solutions (current) for arch linux (my mind)
To understand how it is function ok..but more → sorry no (my mind)

6 Likes
3

Please post your Garuda-inxi. You have no idea how much this helps us to narrow it down

2 Likes
4

image
image936×373 68.2 KB

Obviously the bracketed remarks were meant as placeholders–you were supposed to put the actual content here. Even the chat bot that wrote your issue summary for you knew the garuda-inxi output was supposed to be included. :face_with_hand_over_mouth:

This conclusion is most likely false. You did not even test on any equivalent system, for example Arch Linux or an Arch-based distro, only a couple Ubuntu-based distros.

A more likely explanation than “something is wrong with Garuda Linux” is that you have not configured the application correctly.

Note that configuring this software on Arch Linux is well-documented: strongSwan - ArchWiki. You have not included any details about how you have configured the software, so how can anyone help you identify the issue?

6 Likes
6

nmcli connection up “VPN_DS218”
Fehler: Aktivierung der Verbindung ist gescheitert: Unbekannte Ursache
(Translated:
Error: Activation of the connection failed: Unknown cause)
Hint: use ‘journalctl -xe NM_CONNECTION=1b2e028c-33d3-4b6e-aa8e-f928e73c0015 + NM_DEVICE=wlp112s0’ to get more details.

And here the output:

Jul 25 21:27:26 XUL17L17 NetworkManager[1002]: <info>  [1753471646.8461] vpn[0x56304bc28410,1b2e028c-33d3-4b6e-aa8e-f928e73c0015,"VPN_DS218"]: starting l2tp
Jul 25 21:27:46 XUL17L17 NetworkManager[1002]: <warn>  [1753471666.4786] vpn[0x56304bc28410,1b2e028c-33d3-4b6e-aa8e-f928e73c0015,"VPN_DS218"]: dbus: failure: connect-failed (1)
Jul 25 21:27:46 XUL17L17 NetworkManager[1002]: <warn>  [1753471666.4787] vpn[0x56304bc28410,1b2e028c-33d3-4b6e-aa8e-f928e73c0015,"VPN_DS218"]: dbus: failure: connect-failed (1)

Let me know which additional infomation I should provide.

7

You should resolve this before you try working on the VPN, or anything else. It is possible this is caused by downgrading packages. Run garuda-update and reboot afterward to resolve the partially upgraded state.

A lot of your systemd services are failing, including some network-related services. You should investigate this issue before trying to get another network-related service working; it is likely there is an underlying issue with how your system is configured.

You should provide details regarding how you configured the VPN service. So far we don’t know anything except you downgraded some packages and it didn’t help.

6 Likes
9

But how did you configure it? I don’t think it works out of the box, it looks like you need to set it up. :backhand_index_pointing_down:

6 Likes
10

I use OpenVPN every work day to connect t my works server, I had to manually add all my pem files. I will assume you have to do the same.

11

Sorry… know ..a little bit confused i am.
First, I see a garuda-inxi from a schenker laptop

then i see a garuda-inxi from a desktop

Of course on both systems there is no prob to install garuda-linux + working l2tp/ipsec but..
current you need one running system without issues.
Post now again the current garuda-inxi and pls make a decission for Laptop or desktop.

as info:
with your schenker laptop you run in trouble with space. Only installed and you use 88,1 % current, on a btrfs filesystem + snapshot, you must often take a look of this.

your gigabyte have a out of date bios
current exist F21
https://www.gigabyte.com/Motherboard/B760M-GAMING-X-AX-DDR4/support#support-dl-bios-pid9332
Yes. that`s not solved your issue but important

3 Likes
12

Thanks for your kind support.

Just a few last comments.
BluishHumility asked me to upgrade my system and resolve the issues with my nfs connections. That is all of minor importance.
To get rid of those settings, I have tried to test the VPN with a new and clean installation (accidentally on another computer). That did not change anything.

I read the " Openswan L2TP/IPsec VPN client setup - ArchWiki".
It seems to be outdated and does not work for me. BTW, two parallel approaches are described. The first one (networkmanager) did not work for me.
Trying to set up a container is not worthwhile and is a cumbersome method for me (wasted another 2-3 h).

Research on the Internet indicates that this has been a problem for ages.

Sorry, I have given up or decided to spend my time more wisely.

13

Why not? What did you do? What were the results? There is no information here.

Why not? What did you do? What were the results? There is no information here either.

What research? Where are the links? What did you learn? What is the problem? Again, there is no information here.

By opening a support thread here, you are asking the community to help you figure out how to get this working. But you haven’t provided any information about how you have set anything up yet. How is anyone supposed to be able to see what went wrong?

Sounds good, me too.

6 Likes