Please note that this tool is part of our Labs and our technical support department cannot provide assistance with it.
What is my current tunnel end point?
Your tunnel end point is the IPv4 IP address you would like us to provide tunnel service to, probably your public facing IP address.
What is my Master DNS Server IP?
This is not required and is optional. Rather than delegating RDNS lookups to the IP we've set our servers up to operate as hidden masters for the routed blocks. Our DNS servers will attempt to transfer the zone from the provided (IPv4) DNS server.
Tunnel Configuration Examples
Please note that these examples are provided for reference only.
Linux Net-Tools
ifconfig sit0 up ifconfig sit0 inet6 tunnel ::208.201.234.221 ifconfig sit1 up ifconfig sit1 inet6 add 2001:05a8:0000:0001:0000:0000:0000:186f/127 route -A inet6 add ::/0 dev sit1
Linux Route2
modprobe ipv6 ip tunnel add sixbone mode sit \ remote 208.201.234.221 local 209.204.142.42 ttl 255 ip link set sixbone up ip addr add 2001:05a8:0000:0001:0000:0000:0000:186f/127 dev sixbone ip route add ::/0 dev sixbone ip -f inet6 addr
OpenBSD
ifconfig gif0 tunnel 209.204.142.42 208.201.234.221 ifconfig gif0 inet6 alias \ 2001:05a8:0000:0001:0000:0000:0000:186f \ 2001:05a8:0000:0001:0000:0000:0000:186e prefixlen 127 route -n add -inet6 default 2001:05a8:0000:0001:0000:0000:0000:186e
OpenBSD startup example for /etc/hostname.gif0
tunnel 209.204.142.42 208.201.234.221 inet6 alias 2001:05a8:0000:0001:0000:0000:0000:186f 127 dest 2001:05a8:0000:0001:0000:0000:0000:186e ! route add -inet6 default ::1 ! route change -inet6 default -ifp gif0
FreeBSD
ifconfig gif0 create ifconfig gif0 tunnel 209.204.142.42 208.201.234.221 ifconfig gif0 inet6 2001:05a8:0000:0001:0000:0000:0000:186f/127 route -n add -inet6 default 2001:05a8:0000:0001:0000:0000:0000:186e ifconfig gif0 up
NetBSD
ifconfig gif0 tunnel 209.204.142.42 208.201.234.221 ifconfig gif0 inet6 \ 2001:05a8:0000:0001:0000:0000:0000:186f \ 2001:05a8:0000:0001:0000:0000:0000:186e prefixlen /127 route -n add -inet6 default 2001:05a8:0000:0001:0000:0000:0000:186e
Windows NT/2K/XP
ipv6 rtu ::/0 2/::208.201.234.221 pub ipv6 adu 2/2001:05a8:0000:0001:0000:0000:0000:186f
Windows 2008/Vista/7
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 208.201.234.221 209.204.142.42 netsh interface ipv6 add address IP6Tunnel 2001:05a8:0000:0001:0000:0000:0000:186f netsh interface ipv6 add route ::/0 IP6Tunnel 2001:05a8:0000:0001:0000:0000:0000:186e
Cisco
configure terminal interface tunnel1001 description Sonic.net IPv6 Tunnel no ip address ipv6 enable ipv6 address 2001:05a8:0000:0001:0000:0000:0000:186f/127 tunnel source 209.204.142.42 tunnel destination 208.201.234.221 tunnel mode ipv6ip ipv6 route ::/0 tunnel0 end write
Solaris
ifconfig ip.tun0 inet6 plumb ifconfig ip.tun0 inet6 tsrc 209.204.142.42 tdst 208.201.234.221 up ifconfig ip.tun0 inet6 addif \ 2001:05a8:0000:0001:0000:0000:0000:186f \ 2001:05a8:0000:0001:0000:0000:0000:186e up route add -inet6 default 2001:05a8:0000:0001:0000:0000:0000:186e
How do I setup IPv6 reverse DNS on my tunnel?
Though we do not have configuration examples for all DNS software, you will need to enable transfer and notify to mns.sonic.net 64.142.8.20 and dns-notify.sonic.net 64.142.100.92
Using bind, your zone config should look something like this (note that the leading 0 in zones should be dropped):
zone "4.e.5.4.0.0.0.8.a.5.0.1.0.0.2.ip6.arpa" { type master; file "master/2001:05a8:0004:5e4.db"; allow-transfer { 64.142.8.20; }; also-notify { 64.142.100.92; }; };
And the zone itself should look something like this:
$TTL 3h $ORIGIN 4.e.5.4.0.0.0.8.a.5.0.1.0.0.2.ip6.arpa. @ IN SOA kleio.microshaft.org kgc.mircoshaft.org.( 2010121602 ; Serial 10800 ; Refresh 3600 ; Retry 2419200 ; Expire 604800 ) ; Default TTL NS kleio.microshaft.org. 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR kleio.microshaft.org.
See Also
Fusion IPv6 Tool
2 comments
For a quick and dirty configuration on Ubuntu systems, "sudo apt install miredo" will install the miredo handler for the Teredo protocol, which seems to set itself up magically, and traceroutes show a path through Hurricane Electric.
To use any of the above more detailed methods, though, Sonic needs to provide us with the following
- Sonic's IPv4 tunnel endpoint (I'm assuming it's 208.201.234.221)
- IPv6 addresses for one or both tunnel endpoints (I'm assuming the 2001:05a8:0000:0001:0000:0000:0000:186f/127 shown above is just an example, and you need some way to get real addresses?)
- Some way to set DNS with your current IPv6 public address so you can get incoming connections to your web server or whatever.
A related problem is that for the local endpoint IPv4 address of the tunnels, I don't know if that needs to be a real 208.201.xxx.xxx public IPv4 address, or the 192.168.0.xxx NAT address that my router gives me.
Please sign in to leave a comment.