From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: wireguard@lists.zx2c4.com
Subject: Re: Should I expect faster recovery after one side goes down
Date: Fri, 1 Dec 2017 09:43:19 +0100 [thread overview]
Message-ID: <20171201084319.GA30956@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <20171128084237.GA12292@wolff.to>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Hi,
On 28-11-17, Bruno Wolff III wrote:
> On Tue, Nov 28, 2017 at 00:44:13 -0600,
> Bruno Wolff III <bruno@wolff.to> wrote:
> >
> >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.
It sounds like one of these situations where persistent keepalives would
be useful, doesn't it?
This way the laptop would create a new binding in your firewall.
> I found a way to make it work more automatically. The reason the port was
> getting reassigned was because the original connection packet was being
> tracked and was conflicting with the source nat mapping even though in
> reallity the connection was the same. By putting in CT --notrack rules I was
> able to block that traking and without the conflict the port doesn't get
> remapped. I don't need tracking or the original connection for my firewall
> rules so this should be OK. On testing it seems to work as expected. Now
> when I reboot my router, my laptop reconnects and the wireguard tunnel works
> without having to restart it.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-01 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 9:49 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
2017-11-28 8:42 ` Bruno Wolff III
2017-12-01 8:43 ` Baptiste Jonglez [this message]
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=20171201084319.GA30956@tuxmachine.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--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).