Skip to main content

IPv6 Tunnel Configuration

Customer Care Team
Updated

Sonic offers IPv6 support through 6-in-4 tunneling as a Labs feature for ADSL2+ and VDSL2 circuits, allowing users the ability to send IPv6 traffic over an existing IPv4 network. The following article will explain how to access the tool and provide example tunnel configurations to help you set that up on your equipment. 

If you have Sonic Fiber, you can now use native IPv6 instead. For more information, see our IPv6 article. 

 

Using the Fusion IPv6 Tool

The Fusion IPv6 Tool can be found in Member Tools (https://members.sonic.net/) under Labs > IPv6 Tunnels.

After selecting the IPv6 Tunnel tool from the Member Tools menu, you will be prompted to View/Request Tunnel.

The IPv6 Tunnel tool home page with the View/Request Tunnel button in the center.
 

IPv6 Tool Minimum Requirements

In order to use the Fusion IPv6 Tool successfully you must meet the following minimum requirements:

  • Have a Fusion ADSL2+ or VDSL2 circuit.
    • Note: the following tool is not compatible with services such as Sonic Fiber or Fusion IP Broadband (AT&T FTTN/FTTH).
  • A Sonic owned IPv4 IP address.
  • A dedicated and compatible networking device, such as a router, firewall, or computer that includes 6-in-4 protocol support.
     

What is my Current Tunnel Endpoint?

Your tunnel endpoint is the IPv4 IP address you would like us to provide tunnel service to, most likely your public-facing IPv4 Address.

"Your current tunnel endpoint is:" field located in the IPv6 Tunnels tool.
 

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 up our servers to operate as hidden masters for the routed blocks. Our DNS servers will attempt to transfer the zone from the provided (IPv4) DNS server.

"Master DNS Server IP (More Info):" field located in the IPv6 Tunnels tool.
 

Tunnel Configuration Examples

The following examples demonstrate how to configure the IPv6 tunnel on most popular operating systems and are sufficient to get a single host up on IPV6. 

Please note that the examples are provided for reference only. You will need to use your Tunnel Endpoint v4 Address and assigned v6 Transport block.

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

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 Sonic

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 { 184.23.168.134; };
        also-notify { 184.23.168.134; };
};

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.

 

IPv6 Tunneling Troubleshooting

Please keep in mind that this tool is part of our experimental Labs features, and our Technical Support team is unable to assist with configuring or troubleshooting IPv6 tunnels. You may find help from other users on our Forums. 

Related articles