From: Sebastiano Barrera <sebastiano.barrera@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: On Windows: Wrong source IP address
Date: Mon, 16 Sep 2019 11:53:20 +0200 [thread overview]
Message-ID: <CAHo=znac+BQ594WTCGtrEm=G-Rc2O9AdvhBMYy3RGmr9eeUhjg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9p0ue59kxwD3BWGLmU3U-SmO2fxxhP7ubCsGts2GU-aZg@mail.gmail.com>
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!
-Sebastiano
Il giorno sab 14 set 2019 alle ore 19:11 Jason A. Donenfeld
<Jason@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.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-09-16 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 13:09 On Windows: Wrong source IP address Sebastiano Barrera
2019-09-14 16:51 ` Jason A. Donenfeld
2019-09-14 17:11 ` Jason A. Donenfeld
2019-09-16 9:53 ` Sebastiano Barrera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHo=znac+BQ594WTCGtrEm=G-Rc2O9AdvhBMYy3RGmr9eeUhjg@mail.gmail.com' \
--to=sebastiano.barrera@gmail.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).