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 eb85fd2e for ; Sun, 22 Jan 2017 23:18:41 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 8ad4ec6a for ; Sun, 22 Jan 2017 23:18:41 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 67b377b0 for ; Sun, 22 Jan 2017 23:18:40 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 99e7c19f (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 22 Jan 2017 23:18:39 +0000 (UTC) Received: by mail-ot0-f172.google.com with SMTP id 73so91595028otj.0 for ; Sun, 22 Jan 2017 15:29:59 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1CF3351B-5760-45D6-9D54-4D0A4FC92036@danrl.com> <9157BE7F-FAC4-4826-8493-E29F1C3D75AB@danrl.com> From: "Jason A. Donenfeld" Date: Mon, 23 Jan 2017 00:29:57 +0100 Message-ID: Subject: Re: Built-in Roaming is limited due to a design fault adding STUN and TURN support would be good and make wire-guard connections more durable. To: Peter Dolding 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, You raise interesting points. Symmetric NAT hole punching requires lots of notification hooks to implement. Seeing as these types of hooks and expanded userspace API are already something useful for other things people have been talking about, I expect to expand the userspace API. I imagine on top of those expansions, you'll be able to implement performant STUN punching or TURN relaying. I thought I had made these points clear much earlier, and asked whether you'd be willing to implement some code. In short, if you're interesting in writing code, you'll have what you want, and you'll have a partner in me writing APIs for the kernel side of things. However, if it's going to be more extremely long rambling emails, which are borderline offensive at times, that's not really going to work. It's now gotten to the point where people have been writing to me, "hey you have a great mailing list and project, and now this guy is really burdensome to read, what's the deal?" And indeed, a simple google search reveals a history of odd trolling. Therefore, I ask you to keep subsequent replies on this thread short and efficient. If you'd like to write some interesting network code, let's do it. Otherwise, at the very least I certainly do thank you for your suggestion. You've made more clear in my mind exactly what the challenges of symmetric NAT are. I'm quite confident we'll get to the point where these network concerns can be addressed, and where wireguard has the right notification mechanisms to enable this to happen. Regards, Jason