Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Nicolas Prochazka <nicolas.prochazka@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: [ wireguard-devel] Purge old peer
Date: Wed, 1 Mar 2017 14:47:31 +0100	[thread overview]
Message-ID: <CADdae-jn7qKK=sg7QdP-UeepBrZyUswV4LkABCXsrpzexymk3g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

Hello,
we hare using wireguard with a lot of client, with a lot of dynamically
generated peer key.
So we have, server side, a lot of peers that are become obsoletes
At this time, we delete peer , based on latest handshake > delta time ,
with wg command.
Is the best thing to do ? is it possible to implement an auto purge of old
peer ?

Regards,
Nicolas Prochazka.

[-- Attachment #2: Type: text/html, Size: 439 bytes --]

             reply	other threads:[~2017-03-01 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 13:47 Nicolas Prochazka [this message]
2017-03-01 14:04 ` jens

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='CADdae-jn7qKK=sg7QdP-UeepBrZyUswV4LkABCXsrpzexymk3g@mail.gmail.com' \
    --to=nicolas.prochazka@gmail.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).