wireguard windows socket binds to device

Andre Naujoks nautsch2 at gmail.com
Thu May 27 09:22:23 UTC 2021

Am 26.05.21 um 16:37 schrieb Jason A. Donenfeld:
> This might help:
> https://lists.zx2c4.com/pipermail/wireguard/2021-March/006442.html


Thanks for the answer.

The registry keys were not present, so I added them manually. That and 
the PostUp script seem to have done the trick.

For now, I see this as a viable workaround. Thank you for that.

I still see this as a bug though. I read the reasoning behind it in the 
other mail 

Maybe only use the IP_UNICAST_IF to the default route if AllowedIPs is and/or ::/0? For all other cases it seems unnecessary (errors 
in those cases would be configuration problems on the users side) and in 
some cases (i.e. mine, the non-default-route case) just wrong.

Thanks again and best Regards

More information about the WireGuard mailing list