please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853956
Title:
34 wireguard peers result in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853956
Title:
34
It turns out the fix for this issue was backported to systemd v240:
https://github.com/systemd/systemd-stable/pull/37
I performed a release upgrade on one of our affected servers, bringing
it up from ubuntu 18.04 to ubuntu 19.04 (which uses systemd v240), and I
can confirm that the peers are bein
I think the underlying problem is improper fragmentation of netlink
messages sent to the WireGuard device by systemd v237 in the
set_wireguard_interface function:
https://github.com/systemd/systemd/blob/v237/src/network/netdev/wireguard.c#L107
Appending netlink message data can fail if the messag
I now believe the dmesg complaint in my last comment to be a separate
issue. A fix for it was backported to systemd v238 in this commit:
https://github.com/systemd/systemd-
stable/commit/7db3fe08c5eb83584f3a3d356876b4acaa797585#diff-
f29d1bfc98e548dc0eb497c3d17cbefa
It was not backported to syste
On two systems with 33 peers I noticed that this shows up in dmesg after
a reboot:
netlink: 'systemd-network': attribute type 5 has an invalid length.
These lines also show up whenever I run `sudo systemctl restart systemd-
networkd` now. They didn't show up before the reboot.
This suggests that
