From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: news@lindenberg.one, Simon Rozman <simon@rozman.si>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Hyper-V 2019: unable to create wintun device: no interfaces found
Date: Sun, 25 Aug 2019 12:54:35 -0600 [thread overview]
Message-ID: <CAHmME9qf_kpT=u3JfLDh2fENq=z6P5cebYC5YRwTBF2P7NcGWg@mail.gmail.com> (raw)
In-Reply-To: <015d01d55b76$30373290$90a597b0$@lindenberg.one>
On Sun, Aug 25, 2019 at 12:52 PM <news@lindenberg.one> wrote:
> not the port. My external IP is dynamic. This is really standard for internet services in Germany offered to non-business users, or also business that prefer not the pay extra charges for the assignment of a static ip address. My IP address changes at least once a day (usually between 1 am and 2 am). Usually one uses a dyndns provider, and many routers support updating the ip address automatically. As I am running my external DNS with cloudflar, I am calling their API to update my external address.
> Now afaik Wireguard resolves the domain name of the server just once to an IP address and not regularly or whenever the connection breaks down or has been idle for some time.
> PersistentKeepAlive cannot address the issue, as the client is also not awake all the time in order to save energy. Looking at wg /? on windows I also don´t see any option that seems applicable..
Ahhh, the DNS re-resolution issue. On linux we have this nice script:
https://git.zx2c4.com/WireGuard/tree/contrib/examples/reresolve-dns
On windows, it should be pretty easy to do as well. You can actually
just use task scheduler to run `wg set wg0 peer ABCD...EF= endpoint
somewhere.on.dyndns:1234` every minute or whatever you feel is best.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-25 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 12:15 Joachim Lindenberg
2019-08-25 15:54 ` Jason A. Donenfeld
2019-08-25 17:23 ` AW: " Joachim Lindenberg
2019-08-25 18:35 ` Jason A. Donenfeld
2019-08-25 18:52 ` AW: " news
2019-08-25 18:54 ` Jason A. Donenfeld [this message]
2019-08-25 19:04 ` news
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='CAHmME9qf_kpT=u3JfLDh2fENq=z6P5cebYC5YRwTBF2P7NcGWg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=news@lindenberg.one \
--cc=simon@rozman.si \
--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).