Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 May 2016 20:54:00 +0200
From:      Niklaas Baudet von Gersdorff <stdin@niklaas.eu>
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>
In-Reply-To: <573b2023-88f3-df1d-146f-c32ddfabf406@seacom.mu>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160522185400.GB24569>