IPv6 6RD testing

Advanced feature discussion, beta programs and unsupported "Labs" features.
84 posts Page 5 of 9
by rnovak » Wed Feb 26, 2014 10:08 pm
So I'm trying to get my Cradlepoint MBR1400 set up. I have Comcast and Sonic links coming into it, currently Comcast is disconnected just to be sane. Sonic connection is through the Comtrend router in bridge mode. Cradlepoint has latest firmware (5.0.0) for what it's worth.

IPv6 Settings: 6rd Tunnel
6rd Prefix: 2602:240::/28
IPv4 Border Router Address 184.23.144.1
IPv4 Common Prefix Mask: 0
IPv6 DNS servers are the Google ones (2001:4860:4860::8888 and 8844) although I've tried with blank too.
Delegated IPv6 Networks are blank.

Public IPv4 is 173.228.91.94/24 (static)
The router gets an IPv6 address of 2602:24a:de45:b5e0::1/60.

Am I missing anything obvious? Anything else I should try?

If I pop Sonic out and plug in Comcast with auto settings, it works, so my PC seems to be happy with IPv6.
by Guest » Thu Feb 27, 2014 8:04 pm
rnovak wrote:
So I'm trying to get my Cradlepoint MBR1400 set up. I have Comcast and Sonic links coming into it, currently Comcast is disconnected just to be sane. Sonic connection is through the Comtrend router in bridge mode. Cradlepoint has latest firmware (5.0.0) for what it's worth.

IPv6 Settings: 6rd Tunnel
6rd Prefix: 2602:240::/28
IPv4 Border Router Address 184.23.144.1
IPv4 Common Prefix Mask: 0
IPv6 DNS servers are the Google ones (2001:4860:4860::8888 and 8844) although I've tried with blank too.
Delegated IPv6 Networks are blank.

Public IPv4 is 173.228.91.94/24 (static)
The router gets an IPv6 address of 2602:24a:de45:b5e0::1/60.

Am I missing anything obvious? Anything else I should try?

If I pop Sonic out and plug in Comcast with auto settings, it works, so my PC seems to be happy with IPv6.

What exactly is not working? Your router settings seem to be correct.
by rnovak » Thu Feb 27, 2014 9:20 pm
Basically the IPv6 connectivity part from my client. I was able to ping stuff on ipv6 from the router itself (which I hadn't tried until tonight) :)

I got some help from a friend on troubleshooting, and we discovered that my IPv6 address from Comcast stuck around, and apparently that was causing the problem. Now that I've bounced the physical interface (my powershell was too old to do the cool stuff), it's working.

I apparently need to do some RA tuning if I want to run dual-WAN IPv6, so I'm going to get that friend's book on Practical IPv6 and see what I can learn.

But for now, it's okay and working. Router was fine, Windows not so much. :)
by Guest » Fri Feb 28, 2014 12:51 am
Depending on your chosen method to distribute addresses, you might have to use ipconfig /renew6 on Windows (which is analogous to ipconfig /renew for IPv4), if you're using DHCPv6.
by rnovak » Fri Feb 28, 2014 9:49 am
I tried /release6 and /renew6 but the 2601: IP addresses stuck.
by Guest » Fri Feb 28, 2014 8:29 pm
@tomoc @dane

In addition to my question about the ETA for Pace 4111n users, what about those with dynamic IPv4? Would that mean that their IPv6 prefix would also be equally dynamic? What about those using multiple public IPv4 addresses (both static and dynamic)?
by Guest » Sat Mar 01, 2014 12:07 pm
For anyone using a cisco isr, the following config works for me

Code: Select all

ipv6 general-prefix prefix_6rd_sonic 6rd Tunnel6

interface Vlan1
 ipv6 address prefix_6rd_sonic ::/64
 ipv6 enable

interface Tunnel6
 ipv6 unnumbered FastEthernet4
 ipv6 enable
 tunnel source FastEthernet4
 tunnel mode ipv6ip 6rd
 tunnel 6rd prefix 2602:240::/28
 tunnel 6rd br 184.23.144.1

ipv6 route 2602:240::/28 Tunnel6
ipv6 route ::/0 Tunnel6 2602:24B:8179:10::1
by tomoc » Mon Mar 03, 2014 10:58 am
Guest wrote:
@tomoc @dane

In addition to my question about the ETA for Pace 4111n users, what about those with dynamic IPv4? Would that mean that their IPv6 prefix would also be equally dynamic?

Your v6 prefix is tied directly to your v4 address, so if you need static v6, you need static v4.
What about those using multiple public IPv4 addresses (both static and dynamic)?

A /60 will be routed at every public IPv4 address, so multiple public v4 addresses means multiple 6rd prefixes. It should be stated that dynamic customers are only intended to use a single public IP address.
-Tomoc
Sonic NOC
by davidstrauss » Mon Mar 03, 2014 3:24 pm
What are the performance, bandwidth, and reliability of this versus the old 6in4 tunnels we've been using?
by kgc » Mon Mar 03, 2014 3:30 pm
David, once 6rd is completely supported and moves out of testing it will be engineered to be more reliable (all tunnels are handled by a single server whereas 6rd is handled by a cluster of systems) and likely a bit faster due to lower latency to the gateway. Bandwidth in both cases is limited by the CPE and circuit.
Kelsey Cummings
System Architect, Sonic.net, Inc.
84 posts Page 5 of 9

Who is online

In total there are 3 users online :: 0 registered, 0 hidden and 3 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 3 guests