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 44800fe2 for ; Thu, 23 Feb 2017 17:31:54 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id e24af463 for ; Thu, 23 Feb 2017 17:31:54 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 48f342e3 for ; Thu, 23 Feb 2017 17:31:54 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 3cc4a31d (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Thu, 23 Feb 2017 17:31:54 +0000 (UTC) Received: by mail-ot0-f181.google.com with SMTP id w44so28650014otw.2 for ; Thu, 23 Feb 2017 09:33:00 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: "Jason A. Donenfeld" Date: Thu, 23 Feb 2017 18:32:59 +0100 Message-ID: Subject: Re: [ wireguard-dev ] dmesg when using ipv6 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: , Hello, For the second time today, please provide more debugging information than that. Full dmesg output, full configs, exactly what you're doing. Otherwise nobody can help you. Jason