[Solved] Wireguard handshake stuck after systemd 250 upgrade

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

[Solved] Wireguard handshake stuck after systemd 250 upgrade

Postby bnicolae » Sat Jan 08, 2022 7:12 pm

After upgrading to linux-aarch64-5.15.5, wireguard simply does not finish the handshake with the server and is stuck. It works just fine with the older version (linux-aarch64-5.15.1). Using an alternative kernel like linux-rpi-5.10.90 fails too.

The output of wg show looks like this:
$this->bbcode_second_pass_code('', 'peer: <redacted>
endpoint: <redacted>
allowed ips: <redacted>
// latest handshake: X seconds ago: this line is missing
transfer: 0 B received, Y KiB sent // no data received, which means server is not replying
')

Solved: Looks like the upgrade from systemd 249 to 250 is the culprit. More details here: https://github.com/systemd/systemd/issues/21964
Last edited by bnicolae on Sun Jan 09, 2022 3:24 am, edited 2 times in total.
bnicolae
 
Posts: 6
Joined: Thu May 13, 2021 1:21 am

Re: Wireguard handshake stuck on linux-aarch64 and linux-rpi

Postby graysky » Sat Jan 08, 2022 7:20 pm

The fact that it is affecting you under both kernels points to something in vanilla linux. Are you up to bisecting the kernel?
graysky
Developer
 
Posts: 1876
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Wireguard handshake stuck on linux-aarch64 and linux-rpi

Postby bnicolae » Sun Jan 09, 2022 3:20 am

After more analysis, I discoverd this is in fact a systemd issue, not a kernel issue. The breaking change was introduced in v250. More details here: https://github.com/systemd/systemd/issues/21964
bnicolae
 
Posts: 6
Joined: Thu May 13, 2021 1:21 am


Return to ARMv8

Who is online

Users browsing this forum: No registered users and 6 guests