From: em12345 <em12345@web.de>
To: wireguard@lists.zx2c4.com
Subject: Re: remove peer endpoint
Date: Sat, 28 Dec 2019 21:53:26 +0100 [thread overview]
Message-ID: <c58f53cd-5e9e-1008-97cc-ef160d35ce60@web.de> (raw)
In-Reply-To: <bWad1d4zSz8UESfEBgTLTfDZQbC9-fLXfJF2R3GoONB9PuL3WjNnYrnFQOYmt-gQa9sLLMDJJ8p6zY8XEUlXxxudvzNC5OUjuG75yjbBMIY=@protonmail.com>
Hi,
how about setting the peers endpoint to any local IP (127.0.99.1)?
I'm setting the peers endpoint initially to 127.0.1.1, and only later I
resolve the hostname of the endpoint and update to that IP.
Because in my case I need more control of the resolving process, than
standard "wg" supplies.
--
Emmanuel
On 2019-12-27 19:28, Devin Smith wrote:
> If I'm not mistaken, `wg set <interface> peer <base64> remove` removes the whole peer - I'm looking to remove just the peer's endpoint attribute [endpoint <ip>:<port>].
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, December 27, 2019 10:51 AM, Lonnie Abelbeck <lists@lonnie.abelbeck.com> wrote:
>
>>> On Dec 27, 2019, at 9:51 AM, Devin Smith devinrsmith@protonmail.com wrote:
>>> Is it possible to remove the endpoint of a peer via the `wg set` command? All of the other peer attributes (preshared-key, persistent-keepalive, allowed-ips) are removable in this fashion (and documented in the man page). I've tried `wg set <interface> peer <base64-public-key> endpoint 0` ...
>>
>> Yes, this works:
>>
>> -------------------
>>
>> wg set <interface> peer <base64-public-key> remove
>> --
>>
>> If you forget, "wg set --help" will remind you.
>>
>> Lonnie
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-28 20:53 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 [this message]
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
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=c58f53cd-5e9e-1008-97cc-ef160d35ce60@web.de \
--to=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).