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 ff4d0590 for ; Tue, 6 Mar 2018 21:48:10 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 1012f844 for ; Tue, 6 Mar 2018 21:48:10 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 724bd0f4 for ; Tue, 6 Mar 2018 21:39:19 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id a24f849a (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Tue, 6 Mar 2018 21:39:19 +0000 (UTC) Received: by mail-ot0-f181.google.com with SMTP id m22so158049otf.10 for ; Tue, 06 Mar 2018 13:57:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <871sgwna50.fsf@toke.dk> References: <871sgwna50.fsf@toke.dk> From: "Jason A. Donenfeld" Date: Tue, 6 Mar 2018 22:57:34 +0100 Message-ID: Subject: Re: Roaming between IPv4 and IPv6? To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= 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: , Hey Toke, For incoming packets, this would be strange behavior, since it's listening on v4 and v6. For outgoing packets, if wireguard thinks it should be sending to a v6 address, then that's what it will do. One way to fix this would be to re-resolve DNS from userspace, which is a bit ugly. Another way would be to simply store the last v4 address, and fall back to that if it can't establish a route for the v6 address. And yet another way -- if simplicity is desired -- would be to do nothing (the status quo), and not build legacy semantics into something new. Any opinions on this? Jason