• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Tayga config issues

Started by collum, July 12, 2012, 07:41:17 PM

Previous topic - Next topic

collum

ok.. i've tried a number of different configs. but can't seem to get it to work.. I'm hoping there are some tayga users out there who mind lend a hand


(all numbers changed to protect the innocent ... )

have a router to the internet

     65.113.x.100               (ISP)
     2001:428:5000:x::2      (ISP)
         router
     65.114.x.201   (publicly routeable)
     2001:428:5003:d::1 /64
            |
            |
     65.114.x.204    (publicly routeable)
     2001:428:5003:d::3 /64      (publicly routeable)
           eth0.6
        linux, running totd, tayga, radvd, dhcpv6
          eth1.62
     2001:428:5003:e::3 /64    (publicly routeable)
     192.168.11.9    (private)
             |
             |
    ipv6 only network, all nodes having publicly routable ipv6 addresses, with no ipv4 address on the interface


i'm assuming i'll be using the  2001:428:5003:e::  /64 network to farm out the addresses,
using the prefix   2001:428:5003:e:eeee::/96

so the totd file would look like

forwarder 4.2.2.2 port 53
prefix 2001:428:5003:e:eeee::
port 53



my tayga file

tun-device nat64
ipv4-addr 192.168.11.200
ipv6-addr 2001:428:5003:e:aaaa::1
prefix 2001:428:5003:e:eeee::/96
dynamic-pool 192.168.11.0/24
data-dir /var/spool/tayga



my iptables setup would be

iptables -F
iptables -t nat -A POSTROUTING -o eth0.6 -j MASQUERADE
iptables -A FORWARD -i eth0.6 -o nat64  -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i nat64 -o eth0.6 -j ACCEPT



to start up tayga is

tayga --mktun                             
ip link set nat64 up
ip addr add 65.114.x.204 dev nat64           
ip addr add  2001:428:5003:d::1 dev nat64         
ip route add 192.168.11.0/24 dev nat64     
ip route add 2001:428:5003:e:eeee::/96 dev nat64
tayga -d


i'm sure i'm messing something up in the configs above.

thanks if anyone can help

collum

yes!! i was doing something wrong.. i was using the same ipv4 pool as the inside private network (192.168.11.x)
i changed that to 192.168.12.x and all is working!!!!

   jim