wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: Devin Smith <devinrsmith@protonmail.com>
Cc: "WireGuard@lists.zx2c4.com" <WireGuard@lists.zx2c4.com>
Subject: Re: remove peer endpoint
Date: Fri, 27 Dec 2019 10:51:40 -0600	[thread overview]
Message-ID: <A02FDAAF-B405-4735-9DD1-95A7F6CE9B3F@lonnie.abelbeck.com> (raw)
In-Reply-To: <CtiLrRxfJF8VjxK15ZVRrI9eJBflmVjOBKiOTYAHVAmF7lVPMuQvg3luFb89M3FKdy2fvemWnkfXd-LRJ1MCGy0GC2TddQuX0-Wga9hBS_4=@protonmail.com>


> 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

  reply	other threads:[~2019-12-27 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 15:51 remove peer endpoint Devin Smith
2019-12-27 16:51 ` Lonnie Abelbeck [this message]
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
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=A02FDAAF-B405-4735-9DD1-95A7F6CE9B3F@lonnie.abelbeck.com \
    --to=lists@lonnie.abelbeck.com \
    --cc=WireGuard@lists.zx2c4.com \
    --cc=devinrsmith@protonmail.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).