From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: nicolas.prochazka@gmail.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 2b91825d for ; Wed, 1 Mar 2017 13:45:44 +0000 (UTC) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 29cc9a2e for ; Wed, 1 Mar 2017 13:45:44 +0000 (UTC) Received: by mail-lf0-f49.google.com with SMTP id a6so19646022lfa.0 for ; Wed, 01 Mar 2017 05:47:33 -0800 (PST) MIME-Version: 1.0 From: Nicolas Prochazka Date: Wed, 1 Mar 2017 14:47:31 +0100 Message-ID: Subject: [ wireguard-devel] Purge old peer To: WireGuard mailing list Content-Type: multipart/alternative; boundary=001a114b1a30e592b60549ab8d8f List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --001a114b1a30e592b60549ab8d8f Content-Type: text/plain; charset=UTF-8 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. --001a114b1a30e592b60549ab8d8f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 t= he best thing to do ? is it possible to implement an auto purge of old peer= ?

Regards,
Nicolas Prochazka.
--001a114b1a30e592b60549ab8d8f--