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 eaa6e04d for ; Fri, 1 Jun 2018 20:59:15 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 3ddcd0a4 for ; Fri, 1 Jun 2018 20:59:14 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 9b1c44e4 for ; Fri, 1 Jun 2018 20:58:01 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id bfcd41a3 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Fri, 1 Jun 2018 20:58:00 +0000 (UTC) Received: by mail-ot0-f170.google.com with SMTP id t1-v6so30826593oth.8 for ; Fri, 01 Jun 2018 14:01:38 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "Jason A. Donenfeld" Date: Fri, 1 Jun 2018 23:01:37 +0200 Message-ID: Subject: Re: Wireguard on openwrt To: Steven Caskey 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 Steven, That's not really the kind of open ended problem that's easy to deal with on a mailing list. If you have particular logs that you think indicates a bug or interesting behavior, feel free to share. But I really think that for your case, you'll be better serviced by asking gently in the IRC channel: #wireguard on Freenode. Thanks, Jason