From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Another roaming problem
Date: Thu, 8 Mar 2018 19:03:51 +0100 [thread overview]
Message-ID: <CAHmME9ojxMOoB5z4VJQbecTD+Y7VLK=K8=oTSDciofWLC6Q0fg@mail.gmail.com> (raw)
In-Reply-To: <7088098E-63F5-4ECB-A298-24444987482E@toke.dk>
On Thu, Mar 8, 2018 at 6:50 PM, Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke=
.dk> wrote:
> Well, I do generally setup routing in a somewhat unusual manner.
>
> I can try to capture some packet dumps tomorrow to poke into it a bit mor=
e. Anything in particular I should look for?
One thing to examine is when WireGuard calls
`socket_clear_peer_endpoint_src'. This makes wireguard forget the
source address that it should be using and fall back to the default.
You could add a pr_info(...) call in this function. I have an inkling
that I make calls to this function too zealously and in potentially
unneeded places, such as on handshake transmission retries.
I'm headed out of town super soon, so likely debugging this will have
to wait until I'm back, but do let me know what you find, and we'll
get this fixed up upon return.
next prev parent reply other threads:[~2018-03-08 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 14:29 Toke Høiland-Jørgensen
2018-03-08 14:49 ` Matthias Urlichs
2018-03-08 16:18 ` Jason A. Donenfeld
2018-03-08 16:59 ` Toke Høiland-Jørgensen
2018-03-08 17:02 ` Jason A. Donenfeld
2018-03-08 17:23 ` Toke Høiland-Jørgensen
2018-03-08 17:39 ` Jason A. Donenfeld
2018-03-08 17:50 ` Toke Høiland-Jørgensen
2018-03-08 18:03 ` Jason A. Donenfeld [this message]
2018-03-09 10:08 ` Toke Høiland-Jørgensen
2018-03-09 14:32 ` Toke Høiland-Jørgensen
2018-03-09 14:35 ` Jason A. Donenfeld
2018-03-09 14:42 ` Toke Høiland-Jørgensen
2018-03-09 14:39 ` Toke Høiland-Jørgensen
2018-03-09 14:41 ` Jason A. Donenfeld
2018-03-09 14:46 ` Toke Høiland-Jørgensen
2018-03-09 14:48 ` Jason A. Donenfeld
2018-03-09 14:53 ` Toke Høiland-Jørgensen
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='CAHmME9ojxMOoB5z4VJQbecTD+Y7VLK=K8=oTSDciofWLC6Q0fg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=toke@toke.dk \
--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).