Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63149 - [wireguard-arch][networkmanager] can't activate Wireguard connection from NetworkManager

Attached to Project: Community Packages
Opened by nl6720 (nl6720) - Wednesday, 10 July 2019, 18:59 GMT
Last edited by Antonio Rojas (arojas) - Friday, 26 July 2019, 17:26 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
After upgrading to linux 5.2.arch2-1 & wireguard-arch 0.0.20190702-3, I can't activate Wireguard from NetworkManager

`nmcli connection up wg0`:

Error: Connection activation failed: The device could not be readied for configuration
Hint: use 'journalctl -xe NM_CONNECTION=35435c53-3c41-43f2-ab38-b4f81ef3596c + NM_DEVICE=wg0' to get more details.

Jul 10 18:41:57 NetworkManager[1029]: <info> [1562784117.5824] manager: (wg0): new WireGuard device (/org/freedesktop/NetworkManager/Devices/5)
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2214] device (wg0): state change: unmanaged -> unavailable (reason 'user-requested', sys-iface-state: 'external')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2223] device (wg0): state change: unavailable -> disconnected (reason 'user-requested', sys-iface-state: 'external')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2249] device (wg0): Activation: starting connection 'wg0' (35435c53-3c41-43f2-ab38-b4f81ef3596c)
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2291] device (wg0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2297] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2439] device (wg0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2481] device (wg0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2484] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2493] device (wg0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <warn> [1562784214.2498] device (wg0): Activation: failed for connection 'wg0'
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.2501] device (wg0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jul 10 18:43:34 NetworkManager[1029]: <info> [1562784214.3900] device (wg0): state change: disconnected -> unmanaged (reason 'user-requested', sys-iface-state: 'managed')

If I downgrade to linux 5.1.16.arch1-1 & wireguard-arch 0.0.20190702-2 it works again:
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any
linux 5.2.arch2-1
wireguard-arch 0.0.20190702-3
networkmanager 1.18.0-1

Steps to reproduce:
create a Wireguard connection /etc/NetworkManager/system-connections/wg0.nmconnection . ( https://blogs.gnome.org/thaller/2019/03/15/wireguard-in-networkmanager/ )
Load the connection: nmcli connection load /etc/NetworkManager/system-connections/wg0.nmconnection
Try to activate the connection: nmcli connection up wg0
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 26 July 2019, 17:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  networkmanager 1.18.2
Comment by Vianney le Clément (quartic) - Thursday, 18 July 2019, 10:37 GMT
I can confirm this issue with the following stable packages:
linux 5.2.1.arch1-1
wireguard-arch 0.0.20190702-4
networkmanager 1.18.0-1

Journal:
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5196] device (wg0): state change: unmanaged -> unavailable (reason 'user-requested', sys-iface-state: 'external')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5205] device (wg0): state change: unavailable -> disconnected (reason 'user-requested', sys-iface-state: 'external')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5210] device (wg0): Activation: starting connection 'wg0' (f087df82-8173-4508-8f8d-91d3331b402c)
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5211] audit: op="connection-activate" uuid="f087df82-8173-4508-8f8d-91d3331b402c" name="wg0" pid=2111 uid=1000 result="success"
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5213] device (wg0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5216] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5656] device (wg0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5761] device (wg0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5774] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <warn> [1563445648.5788] platform-linux: wireguard: set-device, message #0 was rejected: Invalid argument
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5789] device (wg0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <warn> [1563445648.5805] device (wg0): Activation: failed for connection 'wg0'
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.5814] device (wg0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jul 18 12:27:28 NetworkManager[538]: <info> [1563445648.7795] device (wg0): state change: disconnected -> unmanaged (reason 'user-requested', sys-iface-state: 'managed')

The interesting line here is:
<warn> platform-linux: wireguard: set-device, message #0 was rejected: Invalid argument
Comment by Vianney le Clément (quartic) - Thursday, 18 July 2019, 11:06 GMT Comment by Stefan Tatschner (rumpelsepp) - Tuesday, 23 July 2019, 15:42 GMT Comment by Weston Myers (weston) - Thursday, 25 July 2019, 18:37 GMT
That commit referenced by Stefan was released from upstream via 1.18.2, which is in the Extra repo as of 2019-07-25.

I was having the same issue/log lines that opened this task, and updating to 1.18.2-1 resolved the reported behavior for me.

Loading...