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 65e96f67 for ; Sun, 6 May 2018 01:00:12 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id ef508ecf for ; Sun, 6 May 2018 01:00:12 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 84cabf95 for ; Sun, 6 May 2018 01:02:07 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 1a5aca55 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 6 May 2018 01:02:06 +0000 (UTC) Received: by mail-ot0-f172.google.com with SMTP id l13-v6so28414992otk.9 for ; Sat, 05 May 2018 18:02:22 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "Jason A. Donenfeld" Date: Sun, 6 May 2018 03:02:20 +0200 Message-ID: Subject: Re: Wireguard client not roaming To: Glen Bojsza 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: , Make sure the clock on the client is correct before connecting.