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 ca1528ce for ; Thu, 8 Mar 2018 16:53:01 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 4b424bce for ; Thu, 8 Mar 2018 16:53:01 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7a911684 for ; Thu, 8 Mar 2018 16:44:10 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 9edc1584 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Thu, 8 Mar 2018 16:44:10 +0000 (UTC) Received: by mail-ot0-f176.google.com with SMTP id r30so6070434otr.2 for ; Thu, 08 Mar 2018 09:02:39 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <85FE1433-439D-439C-A61E-B17754707077@toke.dk> References: <87efku1vza.fsf@toke.dk> <85FE1433-439D-439C-A61E-B17754707077@toke.dk> From: "Jason A. Donenfeld" Date: Thu, 8 Mar 2018 18:02:38 +0100 Message-ID: Subject: Re: Another roaming problem 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: , On Thu, Mar 8, 2018 at 5:59 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> and so I wonder if a simpler solution would also >>involve NAT -- namely, configuring "hair pin" NAT? > > What's that? It's the terrible vendor term for hitting the gateway through one of its IPs (say, the public one) and having it forward packets for you to another machine on the same LAN. The idea here, being, you'd get to keep using the same IP address for communicating, even when you're behind NAT in the private network. (This seems to work well for me at my house.) Wikipedia describes it in terms of the p2p discovery issue, which is slightly different, but still the same underlying concept: https://en.wikipedia.org/wiki/Hairpinning