nsmill49 wrote:dane wrote:
... members with their own CPE who have asked for IPv6/6RD capabilities can now give it a try. Here are the settings:
6RD prefix: 2602:240::/28
6RD Endpoint: 188.8.131.52
My Asus RT-AC66U has a field labeled, "IPv4 Router Mask Length" right below the field for the 6rd endpoint. The router defaults to a value of, "24". When that failed, I poked around the Internet, and came across a web page for configuring a Comcast 6rd tunnel. The instructions were to use a value of, "0", in that field. When I changed from "24" to "0", I could finally get something going; but I am still failing at http://test-ipv6.com/ with the following Asus configuratin:
Code: Select all
Connection type [Tunnel 6rd]
DHCP Option ( )Enable (*)Disable
IPv6 Prefix 2602:240::
IPv6 Prefix Length 28
IPv4 Border Router 184.108.40.206
IPv4 Router Mask Length 0
Tunnel MTU [ ]
Tunnel TTL 
In fact, I think dane should specify the mask length, which I assume is the "redundant part." It appears everyone will get a /60 because the addresses will be in the form [28-bit prefix of Sonic][IPv4 address in hex form]/60 (by design of 6rd), but that might not be so in the future because Sonic may not need the first few bits of the IPv4 address (the prefix specified), depending on what its IPv4 space looks like. In other words, if Sonic could find a way to uniquely specify IPv6 prefixes while omitting redundancies in the embedded IPv4, prefixes greater than /60 could possibly be assigned (theoretically it would be implemented using multiple 6rd servers, one for each IPv4 range).
The apparent BGP problems here are a reason why this is a test, after all.