WireGuard not connecting to the Internet

Ul Tome picture Ul Tome · Apr 12, 2019 · Viewed 8.7k times · Source

WireGuard server seems not to be forwarding connection to the Internet.

I tried re-installing from scratch Wireguard on both my computer and my server, but the problem remained.

When I sudo wg-quick up wg0-client, I get:

[#] wg setconf wg0-client /dev/fd/63
[#] ip address add 10.200.200.2/32 dev wg0-client
[#] ip link set mtu 1420 up dev wg0-client
[#] resolvconf -a tun.wg0-client -m 0 -x
Too few arguments.
Too few arguments.
[#] wg set wg0-client fwmark 51820
[#] ip -4 route add 0.0.0.0/0 dev wg0-client table 51820
[#] ip -4 rule add not fwmark 51820 table 51820
[#] ip -4 rule add table main suppress_prefixlength 0

Here are my /etc/wireguard/wg0.conf (on my server)...

[Interface]
Address = 10.200.200.1/24
SaveConfig = true
PrivateKey = server_private_key
ListenPort = 51820

[Peer]
PublicKey = client_public_key
AllowedIPs = 10.200.200.2/32

... and my /etc/wireguard/wg0-client.conf (on my machine):

[Interface]
Address = 10.200.200.2/32
PrivateKey = client_private_key
DNS = 10.200.200.1

[Peer]
PublicKey = server_public_key
Endpoint = server_address:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 21

I guess the lines with -4 and Too few arguments may hold the key to the problem, but I know too little about this kind of things to figure it out myself. Of course I didn't forget to wg-quick up wg0 on my server.

Answer

Song Bi picture Song Bi · May 5, 2019

Too few arguments is just a warning, I met a same issue and the connection is okay. Someone is saying it's an issue of resolvconf in a resolvconf bug.

You are able to try again with scripts in wireguard scripts.