All,
Wireguard Server
- Ubuntu 18.04 Server (fully up to date as of 11/20/2019)
- WireGuard is installed and working (wg0/192.168.220.1/24)
- IP Forwarding is enabled on in the VM
- IP Address: 10.0.0.4
Azure Virtual Network "Wireguard"
- Subnet = 10.0.0.0/24
- Dynamic Public IP
- IP Forwarding is Enabled on the Interface
- There is a custom route attached to the subnet withing azure, 192.168.220.0/24 > Gateway of 10.0.0.4
I am able to establish tunnels between the server and my clients (Pixel 2XL (192.168.220.3/24) and Windows 10 (192.168.220.4/24)).
From my clients I am able to ping the wireguard server's VPN interface (wg0), the server interface (eth0/10.0.0.4), as well as another VM on the same azure subnet (10.0.0.5).
From the Azure subnet I am able to ping my clients from the wireguard server. I am also able to ping my clients from other VM's on the same subnet.
When I try to ping 8.8.8.8 from either virtual server, it is successful When I try to ping 8.8.8.8 from either client, it is unsuccessful.
I suspect this has to do with the azure custom route table since I cannot traverse back to my clients from other devices on the azure subnet. but it looks setup correctly, and is assigned to the subnet.
Any help or suggestions is appreciated.