Tayga as NAT64 only, not router

Bjørn Mork bjorn at mork.no
Tue Feb 28 15:39:42 CET 2012


Dick Visser <visser at terena.org> writes:

> Hi
> I am in the process of setting up an IPv6 only network, and finally
> gave up on Ecdysis because it kept crashing the VM that it ran on.
> Next candidate is Tayga, but I'm having some trouble getting things to
> work there as well.
>
> I have set-up a couple of things:
>
> VLAN20:  IPv6 only, 2001:610:148:b0b0::/64, gateway
> 2001:610:148:b0b0::1. Does DHCPv6+RA etc.
> VLAN6: IPv4 network, 192.87.38.0/24.
>
> I designated 2001:610:148:b0b0:ffff::/96 as our NAT64 prefix.
>
> I have a VM running Ubuntu 10.04, which has two interfaces, one in each VLAN.
>
> All the examples for Tayga seem to assume that the Tayga box itself
> acts as the router for IPv6 clients.
> In my set-up this is not the case, our Cisco does that.
>
> So stuff like "(replace with your router's IPv4 address)" does not
> make sense for my set-up.
> I suspect my set-up could actually be rather simple, but I can't wrap
> my head around it.

The Tayga box needs to be a router, but you only need to route the IPv6
and IPv4 NAT64 prefixes through it.  I.e.

on the Cisco router:
 add static routes for your NAT64 prefix and the IPv4 addresses you are
 going to translate it to, pointing to your Tayga box

on the Tayga box:
 add default IPv4 and IPv6 routes pointing to your router
 set up Tayga as if it was the only router in the network



Bjørn



More information about the ipv6-ops mailing list