You are not logged in.
So I have a small WireGuard server set up. I works fine from multiple client devices including my laptops running Arch. The only odd issue I can't figure out is how to get NetworkManager to work with it. Whenever I start the WG VPN through NetworkManager, I can see one of "wg-crypt" kernel threads to fully hog one CPU core and according to "wg" output it keeps sending large blocks of data to the server. I can see something quite similar on the server side but according to "ip -s l", there is barely any traffic actually leaving both the server and the client. I can see some WG related traffic in Wireshark but the logged volume does not correspond to the values reported by "wg". With the link in this state I can't even ping the server from the client.
Sample server output:
[root@wg madcat]# wg
interface: wg0
public key: (hidden)
private key: (hidden)
listening port: 51115
peer: (hidden)
endpoint: 10.0.0.5:48444
allowed ips: 10.0.0.5/32, fd42:42:42::5/128
latest handshake: 2 minutes, 33 seconds ago
transfer: 5.13 MiB received, 9.45 GiB sent <<-- NOTICE THE VOLUME
[root@wg madcat]# ip -s l
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3c:c6:bd:4e brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
12021623 26832 0 0 0 0
TX: bytes packets errors dropped carrier collsns
8916640 25911 0 0 0 0
3: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/none
RX: bytes packets errors dropped overrun mcast
5380696 17152 197 0 0 0
TX: bytes packets errors dropped carrier collsns
10500097444 15722327 0 890155 0 0 If I use "wg-quick" on the client to create the connection, everything works perfectly fine.
Does anybody have any idea what could be happening here?
Offline