From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: roaming and ddns dynamic ip
Date: Wed, 22 Nov 2017 09:49:33 -0600 [thread overview]
Message-ID: <D8DF2FC5-F5BF-474E-B774-C0FF4D993DB9@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAC6SzHJ_xHN5fCn2mQ=xrx2Uz6YbZLoHE6As0bwE1SmzprCn+g@mail.gmail.com>
On Nov 22, 2017, at 6:51 AM, d tbsky <tbskyd@gmail.com> wrote:
> 2017-11-22 19:59 GMT+08:00 Jason A. Donenfeld <Jason@zx2c4.com>:
>> Hello,
>>=20
>> This is not a bug. DNS resolution is not done by the WireGuard =
module,
>> but rather by the configuration tool. If you want to update an IP,
>> you'll need to devise a mechanism for this. One popular one is this
>> example script:
>> https://git.zx2c4.com/WireGuard/tree/contrib/examples/reresolve-dns ,
>> but many other possibilities exist too.
>>=20
>> Jason
>=20
> I don't think it's a bug. as you said, that's by design.although it
> means I need other tool to co-maintain the vpn connection.
Jason, question, if each endpoint had PersistentKeepalive enabled, does =
that update the endpoint addresses via your roaming code ? Or does =
actual tunnel data traffic need to occur to update roaming endpoints ?
If PersistentKeepalive updates roaming endpoints, then it would seem to =
be a very rare situation when both endpoints had an address change =
within the PersistentKeepalive window.
Lonnie
=20
next prev parent reply other threads:[~2017-11-22 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 10:53 d tbsky
2017-11-22 11:59 ` Jason A. Donenfeld
2017-11-22 12:51 ` d tbsky
2017-11-22 13:14 ` Jason A. Donenfeld
2017-11-22 15:49 ` Lonnie Abelbeck [this message]
2017-11-22 16:00 ` d tbsky
2017-11-22 16:39 ` Matthias Urlichs
2017-11-22 17:28 ` 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=D8DF2FC5-F5BF-474E-B774-C0FF4D993DB9@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.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).