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 8b6009de for ; Sun, 15 Jan 2017 10:44:56 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id f40259f4 for ; Sun, 15 Jan 2017 10:44:56 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 2a464b4d for ; Sun, 15 Jan 2017 10:44:56 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 2fc96b1b (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 15 Jan 2017 10:44:56 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id u143so86415601oif.3 for ; Sun, 15 Jan 2017 02:55:17 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: "Jason A. Donenfeld" Date: Sun, 15 Jan 2017 11:55:16 +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: =?UTF-8?Q?Dan_L=C3=BCdtke?= Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list , Peter Dolding List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Jan 15, 2017 at 9:39 AM, Dan L=C3=BCdtke wrote: > Although I see the problem and ran into it myself, I would like to see a = solution outside the > wireguard code. Like the one Jason proposed or even a new approach. I am = afraid that > network layers problems (legacy IP and especially NAT) are about to uglif= y yet another > beautiful protocol. Yea -- worry not. I'm not going to add big cludges into core WireGuard. I would like to provide some useful facilities for people to do interesting composable solutions to disgusting networking problems. But I think this solution space is more in the realm of "API" than "protocol". I could also imagine people making "wireguard UDP proxy daemons" -- little programs that listen on 127.0.0.1:xxxxx and then forward packets to some dynamically learned MySQL-connected ASN1-parsed IP while doing things like "if multiple packets that start with a 0x1 and are 148 bytes long are sent in a row, the server has probably changed IPs and we should get STUNed again". Or, maybe this kind of proxy is objectionable and people would prefer to use netlink notification for connectivity events instead. Either way, there's plenty of room for building terrible things _on top of_, rather than inside of, wireguard. > My concerns expressed and all that said, I would love to see some code or= PoC. Code and pcaps are king :) :) As the Reverend Doctor Pastor says, PoC||GTFO. > Wireguards roaming feature tool care of the sites where even the ipv6 pre= fix changes from time to time. Or when your laptop or cellphone is moving around between IP addresses frequently.