Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: em12345 <em12345@web.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multiple Endpoints
Date: Sun, 15 Jan 2017 11:01:19 +0100	[thread overview]
Message-ID: <CAHmME9rBgpNVFypk68SLNLiDqrjTp2Aq+FaVNd3o+Dd8FCjTWQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pSJ3gsAUdNhk_Lt-QzOf6+eS=cay_Chq8YpdcaZJbCsA@mail.gmail.com>

Hey Em,

Circling back to this thread, indeed Baptiste was right. While the
existing situation will likely work fine with NAT, it won't work as
nicely with a strict stateful firewall, when the server IP is dynamic
and changing. So, there's some headway to be made with Baptiste's
multi-endpoint idea. But in the interim, it seems likely the best
mechanism to use would be some userspace solution to check
periodically if the dynamic IP has changed, and to update the
wireguard device accordingly. Hopefully I'll implement some kind of
userspace notification logic so this can be more fine grained than a
cronjob. I'll let you know how this progresses.

Jason

  parent reply	other threads:[~2017-01-15  9:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 14:43 em12345
2017-01-07 15:23 ` Jason A. Donenfeld
2017-01-07 16:45   ` em12345
2017-01-08 14:12     ` Baptiste Jonglez
2017-01-08 14:39       ` Jörg Thalheim
2017-01-08 21:22         ` Baptiste Jonglez
2017-01-08 22:19         ` Jason A. Donenfeld
2017-01-08 22:18       ` Jason A. Donenfeld
2017-01-08 22:57         ` Baptiste Jonglez
2017-01-08 23:00           ` Jason A. Donenfeld
2017-01-09 11:35             ` Varying source address and stateful firewalls (Was: Multiple Endpoints) Baptiste Jonglez
2017-01-10  4:32               ` Jason A. Donenfeld
2017-01-15 10:01             ` Jason A. Donenfeld [this message]
2017-01-08 22:14     ` Multiple Endpoints Jason A. Donenfeld

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=CAHmME9rBgpNVFypk68SLNLiDqrjTp2Aq+FaVNd3o+Dd8FCjTWQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=em12345@web.de \
    --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).