From owner-freebsd-questions@freebsd.org Sun May 22 18:54:04 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D89DB459B8 for ; Sun, 22 May 2016 18:54:04 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: from box-fra-01.niklaas.eu (box-fra-01.niklaas.eu [IPv6:2a00:c98:2200:af07:6::1]) by mx1.freebsd.org (Postfix) with ESMTP id CE0BC1B86 for ; Sun, 22 May 2016 18:54:03 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: by box-fra-01.niklaas.eu (Postfix, from userid 1001) id 9708661FD7; Sun, 22 May 2016 20:54:00 +0200 (CEST) Date: Sun, 22 May 2016 20:54:00 +0200 From: Niklaas Baudet von Gersdorff To: freebsd-questions@freebsd.org Subject: Re: tinc and IPv6 routing, or: how to set up a local IPv6 Message-ID: <20160522185400.GB24569@box-fra-01.niklaas.eu> Mail-Followup-To: freebsd-questions@freebsd.org References: <20160519124446.GB2444@box-fra-01.niklaas.eu> <04e2cb6c-f8c3-7d30-dd53-ca18870c4598@seacom.mu> <20160520065857.GA59066@box-fra-01.niklaas.eu> <545832b8-d7df-9858-82c4-dfe9cc4c7023@seacom.mu> <20160520072052.GB59066@box-fra-01.niklaas.eu> <259f3563-b943-b75f-5d4b-92d3d39aa0ca@seacom.mu> <20160520090118.GA26491@box-fra-01.niklaas.eu> <573b2023-88f3-df1d-146f-c32ddfabf406@seacom.mu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <573b2023-88f3-df1d-146f-c32ddfabf406@seacom.mu> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 18:54:04 -0000 Mark Tinka [2016-05-20 17:33 +0200] : > On 20/May/16 11:01, Niklaas Baudet von Gersdorff wrote: > > > OK, thanks for the advice. I haven't grasped how IPv6 works > > completely yet. So, NAT66 is for prefix rewriting, right? > > NAT66 is the equivalent of NAT44. > > > Where would I need that? > > I'd say never. NAT66 is mostly being used by those are like NAT44. > > NAT44 is useful because IPv4 addresses are in short supply. IPv6 is > not in short supply, so NAT66 is not that useful, but that's just my > opinion. Okay, I get that. But I do not quite get how that was related to my question? > > Simple routing (as I tried to achieve) doesn't work here? > > Have you tried it without the firewall? Technically, I can't see > a reason why it's not working, despite it being ULA. I just disabled the firewall and tried it -- but without success. > Don't wait. Get your IPv6 going sooner rather than later. > > I'd advise to use GUA's instead, but for your internal purposes, ULA's > will work too. I guess, I'll send a similar inquiry to tinc's mailinglist. Maybe the issue is indeed related to tinc itself. Anyway, thanks a lot for your advice! Niklaas