From: em12345 <em12345@web.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: remove peer endpoint
Date: Mon, 30 Dec 2019 12:50:44 +0100 [thread overview]
Message-ID: <54c26a82-4b7b-1bbd-4879-4c504392fc1a@web.de> (raw)
In-Reply-To: <CAHmME9pj1V5s3UzYx3BGmgD9ffuOepHM76k5OGU1f08Xr9j-oQ@mail.gmail.com>
Sorry, may be I was not clear enough. I didn't intend to ask for the
removal of the ability to set an endpoint, but for the ability to
configure a peer without knowing the endpoint at configuration time.
Because the endpoint is only known at a later point.
On 2019-12-30 11:58, Jason A. Donenfeld wrote:
> On Mon, Dec 30, 2019 at 11:13 AM em12345 <em12345@web.de> wrote:
>>
>> Hi,
>>
>> in my case the reason is not exactly being able to remove the endpoint,
>> but rather being able to setup a peer without endpoint, so that only the
>> endpoint needs to be setup later.
>>
>> Scenario:
>> All keys for interface and peer are configured via "wg" standard config
>> file, so that the interface can be brought up at boot time.
>>
>> But when having to use a to be resolved host name as endpoint, then the
>> boot process blocks for around a minute in case no network (incl. DNS)
>> is available. At least when running systemd reading
>> /etc/network/interfaces. I'm not using systemd builtin wg support.
>>
>> There is of course the possibility to bring up the wg-* interfaces later
>> altogether. But the easiest way for me was to use a local endpoint IP
>> (127.0.1.1) address, and then use up/down scripts triggered on LAN/WLAN
>> up/down, which then only resolve the endpoint host name and set via wg
>> the resolved IP of that.
>>
>> This way I'm also able to use several hostnames from different DynDNS
>> providers, in case one service provider is down, which wg as far as I
>> know doesn't currently support.
>> I.e:
>> 1.) resolve first host name
>> 2.) set endpoint IP on peer
>> 3.) ping into tunnel to see if it is working
>> 4.) if not working, then try next host name
>>
>>
>> Thanks,
>>
>> Emmanuel
>
> You've misunderstood the discussion. Nobody is discussing removing the
> ability to set an endpoint after the interface has been configured.
> This exists and works today and isn't going anywhere. Rather, this is
> a discussion about being able to unset an endpoint.
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-30 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 15:51 Devin Smith
2019-12-27 16:51 ` Lonnie Abelbeck
2019-12-27 18:28 ` Devin Smith
2019-12-28 20:53 ` em12345
2019-12-28 21:36 ` Jason A. Donenfeld
2019-12-30 9:37 ` Jason A. Donenfeld
2019-12-30 10:13 ` em12345
2019-12-30 10:58 ` Jason A. Donenfeld
2019-12-30 11:50 ` em12345 [this message]
2019-12-30 11:53 ` Jason A. Donenfeld
2020-01-08 0:48 ` Devin Smith
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=54c26a82-4b7b-1bbd-4879-4c504392fc1a@web.de \
--to=em12345@web.de \
--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 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).