Page 3 of 9
Re: IPv6 6RD testing
Posted: Mon Feb 03, 2014 8:32 pm
by Guest
also success with Tomato 7503.6 Toastman (Linksys E2000)
IPv6 service type=6rd Relay
6rd Routed Prefix= 2602:240::
6rd Prefix Length=32
static DNS=blank
6rd Tunnel Border Relay=184.23.144.1
6rd IPv4 mask length=0
Tunnel MTU=0
Tunnel TL=255
results= 9/10
http://test-ipv6.com/
bad test =Test if your ISP's DNS server uses IPv6 = bad (0.145s)
Re: IPv6 6RD testing
Posted: Mon Feb 03, 2014 10:05 pm
by Guest
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.
Sounds like the /28, only the /32, is getting advertised. It
is possible to give shorter IPv6 prefixes if you can omit the IPv4 prefixes (sinec those parts tend to be redundant), but ideally that would be combined with using an IPv6 /28 to give a /56 to each user as recommended by RfC. But a /60 would be fine too.
Re: IPv6 6RD testing
Posted: Mon Feb 03, 2014 10:09 pm
by Guest
Guest wrote: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.
Sounds like the /28, only the /32, is getting advertised. It
is possible to give shorter IPv6 prefixes if you can omit the IPv4 prefixes (sinec those parts tend to be redundant), but ideally that would be combined with using an IPv6 /28 to give a /56 to each user as recommended by RfC. But a /60 would be fine too.
Sorry, I meant to say "Sounds like only the /32, not the /28, is getting advertised" for the first sentence.
Re: IPv6 6RD testing
Posted: Wed Feb 05, 2014 4:32 pm
by Guest
Are there any Sonic IPv6 web hosts - just for testing?
ipv6.sonic.net = 127.0.0.1 ??
6rd using Tomato Shibby works fine.
Traceroute from outside into Sonic still seems not working.
core1.fmt2.he.net> traceroute ipv6 2602:240:ade4:7cc8::1 numeric
Target 2602:240:ade4:7cc8::1
Hop Start 1
Hop End 30
Hop Packet 1 Packet 2 Packet 3 Hostname
1 <1 ms <1 ms <1 ms 10ge1-1.core1.sjc2.he.net (2001:470:0:31::2)
2 11 ms 3 ms 2 ms 2610:18:16:6001::1
3 9 ms 10 ms 1 ms 2610:18:10d:c000::46
4 1 ms 1 ms 1 ms 0.xe-7-0-0.gw.pao1.sonic.net (2001:5a8:5:3::2)
5 1 ms 1 ms 1 ms 0.xe-6-1-0.gw2.200p-sf.sonic.net (2001:5a8:5:6::2)
6 * * * ?
7 * * * ?
8 * * * ?
Re: IPv6 6RD testing
Posted: Fri Feb 07, 2014 2:41 pm
by nsmill49
Guest wrote:Traceroute from outside into Sonic still seems not working.
Oddly, I get similar results to my Hurricane Electric 6in4 tunnel:
Code: Select all
Target 2001:470:1f05:448:c542:5807:54e0:634
Hop Start 1
Hop End 30
Hop Packet 1 Packet 2 Packet 3 Hostname
1 72 ms 18 ms <1 ms 10ge3-4.core3.fmt2.he.net (2001:470:0:2d::2)
2 4 ms 20 ms <1 ms 10ge1-3.core1.fmt2.he.net (2001:470:0:23b::2)
3 4 ms 4 ms 14 ms tserv1.fmt2.he.net (2001:470:0:45::2)
4 33 ms 42 ms 32 ms NKonaya-1-pt.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:448::2)
5 * * * ?
6 * * * ?
7 * * * ?
8 * * * ?
It appears that the HE looking glass can only see to the customer side IPv6 transport tunnel portal.
Here is my Sonic.net 6rd HE looking glass trace:
Code: Select all
Target 2602:240:ade4:7d9:8885:3491:cbf8:f5c0
Hop Start 1
Hop End 30
Hop Packet 1 Packet 2 Packet 3 Hostname
1 <1 ms <1 ms 13 ms 10ge11-1.core1.sjc2.he.net (2001:470:0:2f::2)
2 13 ms 25 ms 24 ms 2610:18:16:6001::1
3 13 ms 1 ms 1 ms 2610:18:10d:c000::46
4 8 ms 24 ms 24 ms 0.xe-7-0-0.gw.pao1.sonic.net (2001:5a8:5:3::2)
5 24 ms 25 ms 25 ms 0.xe-6-1-0.gw2.200p-sf.sonic.net (2001:5a8:5:6::2)
6 * * * ?
7 * * * ?
8 * * * ?
9 * * * ?
Re: IPv6 6RD testing
Posted: Mon Feb 10, 2014 11:21 am
by tomoc
In an effort to resolve the prefix length issues we are having, I will be working on our aggregation gear. Because of this, 6rd connectivity will be intermittently available throughout the day.
Re: IPv6 6RD testing
Posted: Tue Feb 11, 2014 6:00 pm
by tomoc
Thank you for your patience and valuable feedback. New equipment is in place for 6rd translation, so please feel free to test and report your findings.
6RD Prefix: 2602:240::/28
6RD Endpoint: 184.23.144.1
Enjoy!
Re: IPv6 6RD testing
Posted: Tue Feb 11, 2014 7:16 pm
by Guest
This is weird, still can't get it working with those settings tomoc. What's even weirder is that 6 replies above you someone used Tomato firmware and managed to get it working. Yet I'm using Tomato firmware and can't get it working.
Scored 0/10 on IPv6 test. My router did say it obtain an IPv6 address from WAN.
Re: IPv6 6RD testing
Posted: Tue Feb 11, 2014 10:30 pm
by polpo
Working here with the :28 prefix! Asus RT-N66U with Asus firmware.
Re: IPv6 6RD testing
Posted: Wed Feb 12, 2014 8:34 am
by Guest
polpo wrote:Working here with the :28 prefix! Asus RT-N66U with Asus firmware.
I tried both 28 and 32 prefix, not working for me at all. Was able to retrive IPv6 address but IPv6 test and IPv6 website all failed.
Just to clarify, does 6rd work on Sonic.net Legacy DSL?