From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Devin Smith <devinrsmith@protonmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: remove peer endpoint
Date: Sat, 28 Dec 2019 22:36:10 +0100 [thread overview]
Message-ID: <CAHmME9q1s8Ze40Uzi9+9PM8h=iWAs7_U=Zh2+5O8GjAjQKFeag@mail.gmail.com> (raw)
In-Reply-To: <bWad1d4zSz8UESfEBgTLTfDZQbC9-fLXfJF2R3GoONB9PuL3WjNnYrnFQOYmt-gQa9sLLMDJJ8p6zY8XEUlXxxudvzNC5OUjuG75yjbBMIY=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1323 bytes --]
I'm interested to learn, why would you want such a thing? The endpoint
field is only ever a "hint" anyway, due to the roaming.
On Sat, Dec 28, 2019, 13:12 Devin Smith <devinrsmith@protonmail.com> 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
>
[-- Attachment #1.2: Type: text/html, Size: 2099 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-28 21:36 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 [this message]
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='CAHmME9q1s8Ze40Uzi9+9PM8h=iWAs7_U=Zh2+5O8GjAjQKFeag@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=devinrsmith@protonmail.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).