IPv6 6RD testing

Advanced feature discussion, beta programs and unsupported "Labs" features.
84 posts Page 2 of 9
by Guest » Sat Feb 01, 2014 10:40 pm
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: 184.23.144.1

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.23.144.1
IPv4 Router Mask Length   0
Tunnel MTU                [   ]
Tunnel TTL                [255]

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.
by geogriffin » Sun Feb 02, 2014 8:33 am
my existing sonic 6in4 tunnel still works, but i'm having reachability problems with 6rd..

setup (i deleted my existing sonic 6in4 tunnel and ipv6 addresses before this test):

Code: Select all

$ ip addr add 2602:244:624c:44f0::1/60 dev eth0
$ ip tunnel add 6rd mode sit local 70.36.196.79 ttl 64
$ ip tunnel 6rd dev 6rd 6rd-prefix 2602:240::/28
$ ip addr add 2602:244:624c:44f0::1/60 dev 6rd
$ ip link set 6rd up
$ ip route add ::/0 via ::184.23.144.1 dev 6rd
$ ip link
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
...
26: 6rd: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN mode DEFAULT
    link/sit 70.36.196.79 brd 0.0.0.0
$ ip -6 addr
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2602:244:624c:44f0::1/60 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::221:85ff:fe4a:4833/64 scope link
       valid_lft forever preferred_lft forever
26: 6rd: <NOARP,UP,LOWER_UP> mtu 1480
    inet6 ::70.36.196.79/96 scope global
       valid_lft forever preferred_lft forever
    inet6 2602:244:624c:44f0::1/60 scope global
       valid_lft forever preferred_lft forever
$ ip tunnel
6rd: ipv6/ip  remote any  local 70.36.196.79  ttl 64  6rd-prefix 2602:240::/28



results:

Code: Select all

$ traceroute6 2607:f8b0:4005:800::1008
traceroute to 2607:f8b0:4005:800::1008 (2607:f8b0:4005:800::1008) from 2602:244:624c:44f0::1, 30 hops max, 16 byte packets
 1  * * *
 2  201.ge-5-1-1.gw.200p-sf.sonic.net (2001:5a8:5:d::1)  24.338 ms  24.698 ms  24.34 ms
 3  0.as0.gw2.200p-sf.sonic.net (2001:5a8:5:8::2)  24.295 ms  24.906 ms  25.523 ms
 4  0.xe-6-0-0.gw.pao1.sonic.net (2001:5a8:5:6::1)  24.762 ms  25.741 ms  24.79 ms
 5  2001:550:2:3a::9:1 (2001:550:2:3a::9:1)  25.937 ms  25.139 ms  25.755 ms
 6  2001:550:4::48 (2001:550:4::48)  26.525 ms  27.535 ms  26.726 ms
 7  2001:550:2:1f::46:2 (2001:550:2:1f::46:2)  25.535 ms  26.402 ms  26.025 ms
 8  2001:4860::1:0:7ea (2001:4860::1:0:7ea)  26.038 ms  27.011 ms  25.755 ms
 9  2001:4860:0:1::691 (2001:4860:0:1::691)  26.858 ms  29.084 ms  26.239 ms
10  2607:f8b0:8000:29::7 (2607:f8b0:8000:29::7)  25.587 ms  26.571 ms  25.796 ms


the traceroute terminated somewhere other than 2607:f8b0:4005:800::1008? never seen that before..

the packets at the end of the traceroute (you are seeing the packets twice; on both interfaces eth0 and 6rd):

Code: Select all

$ tcpdump -i any
...
00:13:53.948657 IP6 2602:244:624c:44f0::1.60167 > 2607:f8b0:4005:800::1008.traceroute: UDP, length 16
00:13:53.948727 IP 70.36.196.79 > 184.23.144.1: IP6 2602:244:624c:44f0::1.60167 > 2607:f8b0:4005:800::1008.traceroute: UDP, length 16
00:13:53.974195 IP 184.23.144.1 > 70.36.196.79: IP6 2607:f8b0:8000:29::7 > 2602:244:624c:44f0::1: ICMP6, destination unreachable, unreachable port, 2607:f8b0:4005:800::1008 udp port traceroute, length 72
00:13:53.974245 IP6 2607:f8b0:8000:29::7 > 2602:244:624c:44f0::1: ICMP6, destination unreachable, unreachable port, 2607:f8b0:4005:800::1008 udp port traceroute, length 72
by desertflyer » Mon Feb 03, 2014 1:15 pm
For anyone wanting to configure a Netgear DGND3700v2 (or possibly any other current Netgear router) I am having success with the following configuration.

Internet Connection Type: 6to4 Tunnel
Remote 6to4 Relay Router: Auto
LAN Setup: Use DHCP Server
IPv6 Filtering: Open
by tomoc » Mon Feb 03, 2014 1:28 pm
We are experiencing similar behavior, where 6rd traffic leaves the Sonic.net network, but fails when it comes to end-to-end connectivity. We are actively working to fix these issues, and I will post an update once I have some news. At this exact moment, we have our 6rd prefix configured for 2602:240::/32 and it is working fine for me. The disadvantage, is that this only allows customers a single /64 network for use. If anyone would like to try testing their configuration with a /32 prefix, I would love to know whether it is working for you or not.
-Tomoc
Sonic NOC
by geogriffin » Mon Feb 03, 2014 1:58 pm
tomoc wrote:
We are experiencing similar behavior, where 6rd traffic leaves the Sonic.net network, but fails when it comes to end-to-end connectivity. We are actively working to fix these issues, and I will post an update once I have some news. At this exact moment, we have our 6rd prefix configured for 2602:240::/32 and it is working fine for me. The disadvantage, is that this only allows customers a single /64 network for use. If anyone would like to try testing their configuration with a /32 prefix, I would love to know whether it is working for you or not.


/32 setup works for me!

Code: Select all

$ traceroute -6 -I -A --back google.com
traceroute to google.com (2607:f8b0:4005:802::1003), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  2001:550:4::48 (2001:550:4::48) [*] '-7'  44.876 ms  26.313 ms  26.900 ms
 7  2001:550:2:1f::46:2 (2001:550:2:1f::46:2) [*] '-6'  25.286 ms  26.078 ms  25.487 ms
 8  2001:4860::1:0:7ea (2001:4860::1:0:7ea) [AS15169] '-5'  30.953 ms  47.523 ms  30.647 ms
 9  2001:4860:0:1::693 (2001:4860:0:1::693) [AS15169] '-6'  25.564 ms  25.841 ms  26.197 ms
10  nuq05s02-in-x03.1e100.net (2607:f8b0:4005:802::1003) [AS15169/AS22577] '-7'  25.788 ms  25.554 ms  25.562 ms


btw, are we going to have control over reverse DNS in our networks like we do in the current 6in4 tunnel solution?
by tomoc » Mon Feb 03, 2014 2:25 pm
geogriffin wrote:
/32 setup works for me!

Code: Select all

$ traceroute -6 -I -A --back google.com
traceroute to google.com (2607:f8b0:4005:802::1003), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  2001:550:4::48 (2001:550:4::48) [*] '-7'  44.876 ms  26.313 ms  26.900 ms
 7  2001:550:2:1f::46:2 (2001:550:2:1f::46:2) [*] '-6'  25.286 ms  26.078 ms  25.487 ms
 8  2001:4860::1:0:7ea (2001:4860::1:0:7ea) [AS15169] '-5'  30.953 ms  47.523 ms  30.647 ms
 9  2001:4860:0:1::693 (2001:4860:0:1::693) [AS15169] '-6'  25.564 ms  25.841 ms  26.197 ms
10  nuq05s02-in-x03.1e100.net (2607:f8b0:4005:802::1003) [AS15169/AS22577] '-7'  25.788 ms  25.554 ms  25.562 ms


Good to know! I apologize for the instability, but in order to get this working I will be upgrading code on the aggregation boxes and switching around the prefix length throughout the day today, so expect some intermittent connectivity.


btw, are we going to have control over reverse DNS in our networks like we do in the current 6in4 tunnel solution?

At this moment we do not have a way to give you control over your own PTR records for these blocks, however in the future, static IP customers will be given control over their PTR records (however I'm not sure how that functionality will be delivered)
-Tomoc
Sonic NOC
by nsmill49 » Mon Feb 03, 2014 6:18 pm
tomoc wrote:
We are experiencing similar behavior, where 6rd traffic leaves the Sonic.net network, but fails when it comes to end-to-end connectivity ... At this exact moment, we have our 6rd prefix configured for 2602:240::/32 and it is working fine for me ... If anyone would like to try testing their configuration with a /32 prefix, I would love to know whether it is working for you or not.

Passing 10/10 at http://test-ipv6.com/.

Code: Select all

Tracing route to www.google.com [2607:f8b0:4000:801::1014]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2602:240:ade4:7d9::1
  2     *        *        *     Request timed out.
  3    33 ms    32 ms    32 ms  201.ge-5-1-1.gw.200p-sf.sonic.net [2001:5a8:5:d::1]
  4    32 ms    37 ms    32 ms  0.as0.gw2.200p-sf.sonic.net [2001:5a8:5:8::2]
  5    33 ms    32 ms    32 ms  0.xe-6-0-0.gw.pao1.sonic.net [2001:5a8:5:6::1]
  6     *        *       33 ms  2001:550:2:3a::9:1
  7    35 ms    35 ms    34 ms  2001:550:4::48
  8    33 ms    33 ms    33 ms  2001:550:2:1f::46:2
  9    33 ms    33 ms    36 ms  2001:4860::1:0:7ea
 10    34 ms    40 ms    34 ms  2001:4860::8:0:6117
 11    41 ms    42 ms    53 ms  2001:4860::8:0:2996
 12    76 ms    76 ms    75 ms  2001:4860::8:0:2c9d
 13   168 ms   200 ms   171 ms  2001:4860::1:0:dd7
 14    79 ms    76 ms    75 ms  2001:4860:0:1::48b
 15    75 ms    75 ms    75 ms  dfw06s17-in-x14.1e100.net [2607:f8b0:4000:801::1014]

Trace complete.


Oddity: I am being transported to Texas ("DFW") instead of Mt. View, California ("NUQ").
by nsmill49 » Mon Feb 03, 2014 6:25 pm
desertflyer wrote:
For anyone wanting to configure a Netgear DGND3700v2 (or possibly any other current Netgear router) I am having success with the following configuration.

Does "6to4" give you a Sonic.net IPv6 IP address? AFAIK, Sonic.net is using both "6in4", and "6rd", but I have seen no mention of "6to4".
by Guest » Mon Feb 03, 2014 6:48 pm
nsmill49 wrote:
desertflyer wrote:
For anyone wanting to configure a Netgear DGND3700v2 (or possibly any other current Netgear router) I am having success with the following configuration.

Does "6to4" give you a Sonic.net IPv6 IP address? AFAIK, Sonic.net is using both "6in4", and "6rd", but I have seen no mention of "6to4".

6rd is a modified version of 6to4, so it might be possible to trick a router into using 6rd by using 6to4.
by Guest » Mon Feb 03, 2014 7:13 pm
tomoc wrote:
If anyone would like to try testing their configuration with a /32 prefix, I would love to know whether it is working for you or not.

success with Linksys EA2700 browsing ipv6.cnn.com and ipv6.google.com

6rd tunnel= manual
prefix=2602:240::
prefix length=32
IPv4 mask length=0

c:\temp>tracert ipv6.google.com
Tracing route to ipv6.l.google.com [2607:f8b0:4010:801::1004]
over a maximum of 30 hops:
1 17 ms 8 ms 5 ms 2602:240:3201:7051:22aa:4bff:fe8f:71a0
2 * * * Request timed out.
3 20 ms 29 ms 29 ms 201.ge-5-1-1.gw.200p-sf.sonic.net [2001:5a8:5:d::1]
4 28 ms 28 ms 28 ms 0.as0.gw2.200p-sf.sonic.net [2001:5a8:5:8::2]
5 30 ms 28 ms 28 ms 0.xe-6-0-0.gw.pao1.sonic.net [2001:5a8:5:6::1]
6 * * 21 ms 2001:550:2:3a::9:1
7 27 ms 34 ms 23 ms 2001:550:4::48
8 23 ms 28 ms 29 ms 2001:550:2:1f::46:2
9 32 ms 28 ms 29 ms 2001:4860::1:0:21
10 31 ms 40 ms 29 ms 2001:4860:0:1::3d5
11 26 ms 28 ms 30 ms nuq04s19-in-x04.1e100.net [2607:f8b0:4010:801::1004]
Trace complete.

c:\temp>tracert ipv6.cnn.com
Tracing route to ipv6.cnn.com [2620:100:e000::8001]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 2602:240:3201:7051:22aa:4bff:fe8f:71a0
2 * * * Request timed out.
3 * 75 ms * 201.ge-5-1-1.gw.200p-sf.sonic.net [2001:5a8:5:d::1]
4 62 ms 65 ms 69 ms 0.as0.gw2.200p-sf.sonic.net [2001:5a8:5:8::2]
5 71 ms 69 ms 72 ms 0.xe-6-0-0.gw.pao1.sonic.net [2001:5a8:5:6::1]
6 * * * Request timed out.
7 83 ms 79 ms 81 ms 2001:550:4::48
8 73 ms 76 ms 79 ms te-3-3.car3.SanJose1.Level3.net [2001:1900:4:3::c9]
9 33 ms 38 ms 39 ms vl-70.edge2.SanJose1.Level3.net [2001:1900:1a:6::9]
10 59 ms * 32 ms vl-4061.edge6.LosAngeles1.Level3.net [2001:1900:4:1::66]
11 95 ms 99 ms 103 ms vl-4060.edge3.Dallas1.Level3.net [2001:1900:4:1::7e]
12 * * * Request timed out.
13 Destination host unreachable.
Trace complete.

c:\temp>ping -6 ipv6.cnn.com
Pinging ipv6.cnn.com [2620:100:e000::8001] with 32 bytes of data:
Reply from 2620:100:e000::8001: time=118ms
Reply from 2620:100:e000::8001: time=135ms
Reply from 2620:100:e000::8001: time=114ms
Reply from 2620:100:e000::8001: time=126ms

Ping statistics for 2620:100:e000::8001:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 135ms, Average = 123ms
84 posts Page 2 of 9

Who is online

In total there are 4 users online :: 0 registered, 0 hidden and 4 guests (based on users active over the past 5 minutes)
Most users ever online was 422 on Sat May 26, 2012 5:28 am

Users browsing this forum: No registered users and 4 guests