You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell, everything works, but the following warning appears in the log:
-- Journal begins at Tue 2023-05-02 07:43:22 CEST, ends at Tue 2023-05-23 08:37:27 CEST. --
May 23 08:36:53 lab systemd[1]: Finished WireGuard Network Namespace (bandura2).
May 23 08:36:53 lab wg-netns[123795]: > ip netns exec dn42 /bin/sh -c ip addr add dev bandura2 fe80::2924/128 peer fe80::2923/128
May 23 08:36:53 lab wg-netns[123795]: > ip -n dn42 link set dev bandura2 mtu 1420 up
May 23 08:36:53 lab wg-netns[123795]: > ip link set bandura2 netns dn42
May 23 08:36:53 lab wg-netns[123795]: > wg set bandura2 peer bgSz1aqV9otL3uUiyBqdA7kdw3aE+itwoH4xjINi+0U= preshared-key /dev/stdin persistent-keepalive 0 endpoint p2>
May 23 08:36:53 lab wg-netns[123795]: > wg set bandura2 private-key /dev/stdin
May 23 08:36:53 lab wg-netns[123795]: > wg set bandura2 fwmark 0
May 23 08:36:53 lab wg-netns[123795]: > wg set bandura2 listen-port 0
May 23 08:36:53 lab wg-netns[123795]: > ip link add bandura2 type wireguard
May 23 08:36:53 lab systemd[1]: Starting WireGuard Network Namespace (bandura2)...
May 23 08:36:53 lab systemd[123795]: ConfigurationDirectory 'wireguard' already exists but the mode is different. (File system: 750 ConfigurationDirectoryMode: 755)
May 23 08:36:53 lab systemd[1]: Stopped WireGuard Network Namespace (bandura2).
May 23 08:36:53 lab systemd[1]: wg-netns@bandura2.service: Succeeded.
May 23 08:36:53 lab wg-netns[123791]: > ip -n dn42 link delete bandura2
May 23 08:36:53 lab wg-netns[123791]: > ip -n dn42 link set bandura2 down
May 23 08:36:53 lab wg-netns[123791]: > ip -n dn42 link show bandura2
May 23 08:36:52 lab systemd[123791]: ConfigurationDirectory 'wireguard' already exists but the mode is different. (File system: 750 ConfigurationDirectoryMode: 755)
May 23 08:36:52 lab systemd[1]: Stopping WireGuard Network Namespace (bandura2)...
May 23 08:36:40 lab systemd[1]: Finished WireGuard Network Namespace (bandura2).
May 23 08:36:40 lab wg-netns[123746]: > ip netns exec dn42 /bin/sh -c ip addr add dev bandura2 fe80::2924/128 peer fe80::2923/128
May 23 08:36:40 lab wg-netns[123746]: > ip -n dn42 link set dev bandura2 mtu 1420 up
May 23 08:36:40 lab wg-netns[123746]: > ip link set bandura2 netns dn42
May 23 08:36:40 lab wg-netns[123746]: > wg set bandura2 peer bgSz1aqV9otL3uUiyBqdA7kdw3aE+itwoH4xjINi+0U= preshared-key /dev/stdin persistent-keepalive 0 endpoint p2>
May 23 08:36:40 lab wg-netns[123746]: > wg set bandura2 private-key /dev/stdin
May 23 08:36:40 lab wg-netns[123746]: > wg set bandura2 fwmark 0
May 23 08:36:40 lab wg-netns[123746]: > wg set bandura2 listen-port 0
The text was updated successfully, but these errors were encountered:
marek22k
added a commit
to marek22k/wg-netns
that referenced
this issue
May 23, 2023
dadevel
changed the title
Systemd unit: ConfigurationDirectory 'wireguard' already exists but the mode is different. (File system: 750 ConfigurationDirectoryMode: 755)
Systemd unit ConfigurationDirectoryMode differs
May 25, 2023
As far as I can tell, everything works, but the following warning appears in the log:
The text was updated successfully, but these errors were encountered: