It seems like the tunnel itself is not up or not coming up. Please confirm the status of the wireguard service on the Linode VPS side. To do that, login to your Linode VPS via SSH (PuTTY) and type in the following command.
systemctl status [email protected]
It should show you a large amount of information about the service but the most important bit is this line in green:
Active: active (exited) since Mon 2021-12-20 07:53:50 UTC; 3min 47s ago
If the status is instead "inactive" (dead) then the service itself isn't enabled or not coming up due to some error. In that case I'd recommend double checking the configuration part. If the status shows active then the following things left to check would be:
- Ping from one tunnel end to another
- If no ping is coming through, check for private/public key mismatch on the VPS side and the public key of the peer on the router side.
- If private/public keys are in order, double check the configuration on router side (endpoint host/allowed peer IP section)
In order to ping, while logged in to the VPS using PuTTY (via SSH), type in the following command: "ping 10.0.1.2". You should see an output similar to this:
[email protected]:/etc/wireguard# ping 10.0.1.2
PING 10.0.1.2 (10.0.1.2) 56(84) bytes of data.
64 bytes from 10.0.1.2: icmp_seq=1 ttl=64 time=80.8 ms
64 bytes from 10.0.1.2: icmp_seq=2 ttl=64 time=78.9 ms
64 bytes from 10.0.1.2: icmp_seq=3 ttl=64 time=78.2 ms
64 bytes from 10.0.1.2: icmp_seq=4 ttl=64 time=76.8 ms
--- 10.0.1.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 76.842/78.682/80.776/1.421 ms
If nothing comes through that means the tunnel itself hasn't been established.
Another issue could be the "Allowed IPs" of the peer as well as endpoint host/port. Make sure the "Allowed IPs" of the peer section is set to the VPS wireguard tunnel IP (10.0.1.1/32 according to the wiki article). Additionally, the "endpoint host" part should be the public IP address of your Linode VPS. Port, by default, is 51820.
Let me know more information when you've double-checked things and I'll try to assist you further regarding this issue. Additionally, if you could, please execute the following command via SSH on VPS (PuTTY) and paste it here:
The output should be similar to this:
[email protected]:/etc/wireguard# ifconfig wg0
wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420
inet 10.0.1.1 netmask 255.255.255.0 destination 10.0.1.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 17 bytes 2004 (1.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18 bytes 2212 (2.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
This part shouldn't have any private information but if for some reason it does, please sanitize it or send it to me via private message if you're not sure.