wireguard windows socket binds to device

Andre Naujoks nautsch2 at gmail.com
Tue May 25 10:34:35 UTC 2021

Hi all.

I am currently trying to create a wireguard tunnel over another VPN 
under windows.

The setup would be a wirguard tunnel through an openvpn connection.

However the wireguard implementation on windows forcibly binds itself to 
the network device with the default route (which is fortunately visible 
in the wireguard log).
The wireguard peer however resides inside the other VPN and is thus not 
reached by the windows client.

Is there a reason why the routing of the host machine is forcibly 
bypassed by binding to a specific network device or is this simply a bug 
in the windows implementation?

Best regards and thanks in advance

More information about the WireGuard mailing list