From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should I expect faster recovery after one side goes down
Date: Tue, 28 Nov 2017 00:44:13 -0600 [thread overview]
Message-ID: <20171128064413.GA9218@wolff.to> (raw)
In-Reply-To: <20171128061306.GA7842@wolff.to>
On Tue, Nov 28, 2017 at 00:13:06 -0600,
Bruno Wolff III <bruno@wolff.to> wrote:
>I do some source address rewriting and it may be that the initial
>addresses used for the encapsulating packets are different than the
>ones later.
When I'm on the local network, 192.168.6.1 gets used for the initial
source adddress and gets rewritten to 98.103.208.26 in order to make
the source consistent for the laptop whether or not it is on the
local network. (That way I don't need to allow connections from
192.168.6.1 somewhere else where it wouldn't be my router.) When this
happens the source port seems to normally get changed. Wireguard on the
laptop remembers the new source port and tries to keep using it after
the router is rebooted. But during the reboot the router forgets about
the port mapping so it ends up dropping the packets. It has no reason
to send packets on its own to the laptop (and wouldn't know where to
send them) so the port doesn't get corrected.
I think the correct fix is to know if I reboot the router for testing
something, I need to also restart wireguard to make sure it is sending
data to the expected port. This isn't going to be an issue in normal
operation.
next prev parent reply other threads:[~2017-11-28 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 9:49 Should I expect faster recovery after one side goes down Bruno Wolff III
2017-11-27 11:04 ` Jason A. Donenfeld
2017-11-27 13:49 ` Bruno Wolff III
2017-11-27 17:33 ` Bruno Wolff III
2017-11-27 17:36 ` Jason A. Donenfeld
2017-11-27 18:25 ` Bruno Wolff III
2017-11-28 6:13 ` Bruno Wolff III
2017-11-28 6:44 ` Bruno Wolff III [this message]
2017-11-28 8:42 ` Bruno Wolff III
2017-12-01 8:43 ` Baptiste Jonglez
2017-12-01 17:02 ` Bruno Wolff III
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=20171128064413.GA9218@wolff.to \
--to=bruno@wolff.to \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.