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 bb1bdfe4 for ; Wed, 20 Sep 2017 20:50:14 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 4be53175 for ; Wed, 20 Sep 2017 20:50:14 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 879e7adb for ; Wed, 20 Sep 2017 21:09:17 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 570f2fb0 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Wed, 20 Sep 2017 21:09:17 +0000 (UTC) Received: by mail-io0-f182.google.com with SMTP id v36so6698582ioi.1 for ; Wed, 20 Sep 2017 14:17:31 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "Jason A. Donenfeld" Date: Wed, 20 Sep 2017 23:17:30 +0200 Message-ID: Subject: Re: [wireguard-dev] Help about configuration To: nicolas prochazka 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: , Hi Nicolas, Great that fixed it. Sometimes WireGuard can be a good diagnostic for figuring out various network misconfigurations, because WireGuard's allowed-ips binding is very strict and explicit. By the way, you might want to change your private key to something new, since your first email contained these in plaintext. Jason