We’re getting ready to carve out a chunk of our residential network that will be delivered completely over IPv6. Unless I’m blind, I do not see any options for NAT64 (to let an IPv6 device reach an IPv4 device) or another workaround. We have IPv6 on our WAN already up and running, as well as internally, and want to try and hook up for first clients. Since IPv4 is very challenging to come by these days, we’d love to move to IPv6 for all of our new publics moving forward but obviously need to let them reach IPv4 as well.
If I remember right, there is no NAT64 available.
I could always be wrong but there is no CGN related capabilities on RouterOS yet.
In an IPv6-only-Network you don’t need to care about NAT64.
You can use NAT64 on clients and small routers just by using special DNS64-resolver-entries.
There some public DNS64/NAT64-Gateways.
http://ipv6.lt/nat64_en.php
http://www.trex.fi/2011/dns64.html
http://status.aaisp.net.uk/apost.cgi?incident=105
eg.
nameserver 2001:67c:2b0::4
nameserver 2001:67c:2b0::6
They are adding the missing AAAA-Records. It works with 99% of the (web)sites. For skype and some other problematic things you need 464xlat.
Using public/test-gateways is only a option for small sites. The better way would be to implement your own NAT64/DNS64-gateway.
Of course you could buy a cisco-device, but you can use also opensource-software to do that:
with linux: http://www.litech.org/tayga/
With that information you should be able to set up an NAT64-Gateway.
If the clients miss IPv4, you can spend them
https://github.com/toreanderson/clatd/
Regards,
Thomas
Does RouterBoard support NAT64 or IPV6 Stacking ??