Yesterday, Dane Jasper posted a notice in the Sonic.net forum that their 6rd service has begun:
»
forums.sonic.net/viewtop ··· 3&t=1877They have not updated the Pace 4111N firmware, but third party CPE is supposed to work.
I have played with IPv6 in my Asus RT-AC66U a bit, but am disappointed. It looks like I need to learn the OS CLI in that model. It is supposed to be capable of 6in4 and 6rd tunneling, but can't create the tunnels with Sonic.net data; works fine with Hurricane Electric 6in4, though. Using the HE data, the RT-AC66U shows the following:
IPv6 Connection Type: Tunnel 6in4
WAN IPv6 Address: 2001:470:1f04:448::2/64
WAN IPv6 Gateway: ::
LAN IPv6 Address: 2001:470:1f05:448::1/64
LAN IPv6 Link-Local Address: fe80::62a4:4cff:fedc:9198/64
LAN IPv6 Prefix: 2001:470:1f05:448::/64
DNS Address: 2001:470:20::2 2001:4860:4860::8888 2001:4860:4860::8844
IPv6 LAN Devices List
-------------------------------------------------------------------
Hostname MAC Address IPv6 Address
Miyuki d4:be:d9:3f:82:eb 2001:470:1f05:448:2515:228c:5914:561c
The corresponding IPv6 routing table looks, in part, like this:
IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:470:20::2/128 2001:470:20::2 UC 0 1 0 v6in4
2001:470:1f04:448::/64 :: U 256 0 0 v6in4
2001:470:1f05:448:2515:228c:5914:561c/128 2001:470:1f05:448:2515:228c:5914:561c UC 0 3 0 br0
2001:470:1f05:448::/64 :: U 256 0 0 br0
2001:4860:4860::8888/128 2001:4860:4860::8888 UC 0 2 0 v6in4
HE gives the border server and client edge server IPv6 addresses as:
2001:470:1f04:448::1/127
For the RT-AC66U, I entered 2001:470:1f04:448::2 in the "Client IPv6 Address" field, and "64" in the "IPv6 Prefix Length" field.
For the Sonic.net 6in4 tunnel, the border server and client edge server IPv6 addresses are:
2001:5a8:0:1::149e/127
I can enter 2001:5a8:0:1::149f in the "Client IPv6 Address" field, but am limited, by the router GUI, to "IPv6 Prefix Length" field values of from 3 to 64; any value outside of that range throws an error. But an "IPv6 Prefix Length" field value of 64 yields the following:
IPv6 Connection Type: Tunnel 6in4
WAN IPv6 Address: 2001:5a8:0:1::149f/64
WAN IPv6 Gateway: ::
LAN IPv6 Address: 2001:5a8:4:a4f0::1/60
LAN IPv6 Link-Local Address: fe80::62a4:4cff:fedc:9198/64
LAN IPv6 Prefix: 2001:5a8:4:a4f0::/60
DNS Address: 2001:470:20::2 2001:4860:4860::8888 2001:4860:4860::8844
IPv6 LAN Devices List
-------------------------------------------------------------------
Hostname MAC Address IPv6 Address
Miyuki d4:be:d9:3f:82:eb 2001:5a8:4:a4f0:bc1f:75da:6198:abd3
... with this IPv6 routing table:
IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:5a8:0:1::/64 :: U 256 0 0 v6in4
2001:5a8:4:a4f0::/60 :: U 256 0 0 br0
2001:4860:4860::8844/128 2001:4860:4860::8844 UC 0 4 0 v6in4
It appears that I need to learn how to access the RT-AC66U CLI so I can modify the server/client data to reflect the 2001:5a8:0:1::149e/127.
For the Sonic.net 6rd tunnel I used the data from Dane's post, thus:
Asus 6rd configuration.
But the IPv6 LAN settings don't look right. I changed the "IPv4 Router Mask Length" field value to, "0"; which gives a "LAN Prefix Length" of "60". But still have some problems with a working tunnel:
IPv6 Connection Type: Tunnel 6rd
WAN IPv6 Address: 2602:24a:de40:7d90::/52
WAN IPv6 Gateway: ::208.201.234.221
LAN IPv6 Address: 2602:24a:de40:7d90::1/60
LAN IPv6 Link-Local Address: fe80::62a4:4cff:fedc:9198/64
LAN IPv6 Prefix: 2602:24a:de40:7d90::/60
DNS Address: 2001:470:20::2 2001:4860:4860::8888 2001:4860:4860::8844
IPv6 LAN Devices List
-------------------------------------------------------------------
Hostname MAC Address IPv6 Address
With this routing table:
IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::/96 :: U 256 1 0 6rd
2602:24a:de40:7d90::/60 :: U 256 0 0 br0
2602:240::/28 :: U 256 0 0 6rd
Since I can get the HE tunnel to work, I suspect some kind of configuration limitation with the Asus RT-AC66U Firmware Version:3.0.0.4.374_2239, which is the (as of this evening) latest, non-Beta release.