0

Update 2: I wrote a quick&dirty tutorial for Jool on Debian 11, since their website is very thorough, but also slightly confusing and the examples too complex for most cases.

I'm looking to go IPv6 native and need a NAT64 implementation on my Debian routers. Is tayga still the way to go, as it's in the user space and all? Is there no kernel equivalent to "iptables ... -j MASQ" for NAT64?

Also with tayga you need a lot of addresses:
Should I use 64:ff9b::/96 as the "prefix" as proposed by RFC 6052 or some public prefix from my site's range as suggested by litech?
Also it needs an "dynamic-pool" of IPv4 addresses, can I just use any RFC1918 addresses, and do I have to take care of routing those IPV4 addresses? And if so, how, if I have several internal IPv6 networks?
And finally it seems to require my "routers IPv4 address", but what if that's dynamic?

I'm slightly confused...

For the sake of discussion let's assume I'm using the IPv6 prefix 2001:db8:cafe:2000::/56 and the IPv4 prefix 172.20.20.0.0/16 for my home office and I have several spare prefixes available.

1 Answer 1

3

What you want is probably https://jool.mx. It's a kernel module that implements NAT64.

3
  • Looks promising, but it's only available in Debian testing and my routers run stable. So I'll try it, since testing is in freeze mode and it's about time to test it on production systems. But it may take a while till I get back to you...
    – OttoEisen
    Aug 7, 2021 at 22:02
  • @OttoEisen bullseye will be called stable in one week if it goes as planned: lists.debian.org/debian-devel-announce/2021/07/msg00003.html / wiki.debian.org/ReleasePartyBullseye
    – A.B
    Aug 8, 2021 at 0:42
  • Jool works as expected :-) 2 drawbacks: It seems that the kernel module is compiled during the installation, at least it says Building initial module for 5.10.0-8-amd64. This means that installation takes a really long time on my Celeron-VM. It also means that it installs a whole bunch of development tools, kernel-headers etc. Given that my router just used 1.7GB, even after the Debian 11 upgrade, the additional 312MB are not insignificant. Add to that the currently >70MB memory use by BIND and this whole *64 business turn out to be a real resource-hog.
    – OttoEisen
    Aug 9, 2021 at 12:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .