On Windows: Wrong source IP address

Sebastiano Barrera sebastiano.barrera at gmail.com
Mon Sep 16 11:53:20 CEST 2019

Hi Jason,

Thank you very much for your explanation! I'll look into it and study
the source code you linked, but I don't think I'll be able to
contribute any concrete work before the next week or so.  I'll be back
when I do!

Thanks again!

Il giorno sab 14 set 2019 alle ore 19:11 Jason A. Donenfeld
<Jason at zx2c4.com> ha scritto:
> To give more detail, a more ideal solution would be to specify the
> source address / source if index using WSASendMsg, and retrieve the
> incoming destination address / destination if index using WSARecvMsg,
> and implement sticky socket semantics. A linux implementation in C is
> here: https://git.zx2c4.com/WireGuard/tree/contrib/examples/sticky-sockets/sticky-sockets.c
> and in go is here:
> https://git.zx2c4.com/wireguard-go/tree/device/conn_linux.go . If you
> want to provide conn_windows.go that implements sticky sockets, that
> would probably solve 80% of the problem. The remaining part would be
> policy routing for the case when we don't have a sender if or when
> it's gone stale.

More information about the WireGuard mailing list