From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id b7bcb1a7 for ; Mon, 10 Jul 2017 00:35:16 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 8aa4d49c for ; Mon, 10 Jul 2017 00:35:16 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id b7ad6f47 for ; Mon, 10 Jul 2017 00:48:50 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 9a850236 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Mon, 10 Jul 2017 00:48:50 +0000 (UTC) Received: by mail-wr0-f182.google.com with SMTP id k67so116892131wrc.2 for ; Sun, 09 Jul 2017 17:53:21 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170708142156.GB13268@tuxmachine.polynome.dn42> References: <1499116162.70598782@f401.i.mail.ru> <20170708142156.GB13268@tuxmachine.polynome.dn42> From: "Jason A. Donenfeld" Date: Mon, 10 Jul 2017 02:53:20 +0200 Message-ID: Subject: Re: Indefinite queuing for unconnected peers (Was: problem wireguard + ospf + unconnected tunnels) To: Baptiste Jonglez Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hey Baptiste, As alluded to in my other recent reply, WireGuard already does this actually. It tries the handshake a few times, and only after failing does it drop the queue. I suppose I could greatly reduce the clearing condition from dropping after 20 handshakes to dropping after 1 handshake, but I don't think it makes a difference anyway, because new packets should replace old packets in the queue. Jason