IPv6

Advanced feature discussion, beta programs and unsupported "Labs" features.
23 posts Page 2 of 3
by ahava » Wed Dec 11, 2013 4:15 pm
If any Sonic Technical Support Gurus are listening: It's been two years and five days since gvdl posted the following issue to this forum, concerning the setup of ipv6 addressing:
Sonic only gives 2 ipv6 address when apparently 3 are needed:
  • WAN ipv6 Address=
    ipv6 default route=
    LAN ipv6 Address=

All I have is Transport:: 2001:<manyhexdigits>/127 & Network:: 2001:<manyhexdigits/60.
Does anybody have a guess how to translated these into the 4 time capsule fields?


Although these entries correspond with Apple's Time Capsule's Interface, unfortunately, gvdl did not reveal or offer a link to "the 2 ipv6 addresses" he mentioned and knows about. What do I need to do to drink the kool-ade?

Thing is, I don't have Time Capsule: I simply need to configure iPv6 settings correctly on a new Netgear Router SetUp Admin Login Screen. Why, the world and its devices are soon going to run out of IP addresses if the number of mobile continues to increase. Said addresses are virtually limitless when using IPv6. But in the IPv6 Setup Screen, the local Netgear configuration interface proposes settings options, but I am confused about how to to set them up, as was Support, who punted me over to this forum.

Could a network specialist suggest which settings to select to ensure a correct and solid configuration? FYI, I have an active Sonic DSL Elite Pro account using DHCP. ipv4 is working fire, but we have many wireless clients in a small home with daily IP address conflicts. I

I sincerely hope that the richer feature set of ipv6 will help alleviate our problems. Here are settings more or less as they appear on the routerlogin.com screen in Netgear's client.

  • Internet Connection Type: Options available:
    (a) Auto Detect (b) 6to4 Tunnel (c) Pass Through (d) Fixed (e) DHCP (f) PPPoE (g) Auto Config
    ipv6 Connection Type: No options here unless after it's been configured.
    WAN Now Reads: Router's IPv6 Address On WAN Not Available. (No choice but to leave as is.)
    Under LAN Setup, these Netgear Router settings specify how LAN IP Address Assignments are determined:
    Use DHCP Server
    Auto Config


I did try speaking with Customer Support at Sonic today, but they referred me to these forums. I felt basically blowed off when they stated that they are not simply not trained to help out with those types of questions. Maybe they should me: I think they named it call escalation in most CS centers. ipv6 was started as a project in the early 1990's and met FCC readiness deadlines to deploy ipv6 technologies around the world in 2002. It's already 11 years later, but the Sonic Support Staff member that I spoke with apologized that he could little more to help that send me to forums. I recommend that they be trained to deal with ipv6, and that whenever they do not something, rather than punting us over to forums that can take 2 years to get answered, make them go the extra mile to connect with a knowledgeable networking employee in your organization who's well-trained, knowledgeable and more than happy to help. It was honestly my first disappointment with a Sonic Support Agent since I first became a customer over 10 years ago.

So, can someone in the know please post the most appropriate configuration settings that would allow for the easy setup of "tunnels" using IPv6. Even better, gather relevant information and post it as a Knowledgebase Article that could be consulted by your staff as well as by your subscribers.

Thank you,
Paul (alias ahava)
by cdkeen » Thu Dec 12, 2013 4:09 pm
ahava wrote:ipv4 is working fire, but we have many wireless clients in a small home with daily IP address conflicts.
On a Netgear router the default settings are typically 192.168.1(or 0)/24 which provides for 254 usable IP addresses on the LAN. Unless your connected device count exceeds this limit, IP address conflicts are likely caused by a configuration setting on a LAN device.
ahava wrote:I did try speaking with Customer Support at Sonic today, but they referred me to these forums.
That is because [email protected] is not able to support modem and router devices that are not supplied by Sonic.net. For device specific configuration assistance with third party devices there are reference manuals provided by the manufacturer, usually included in the box with the device, but also available online (http://support.netgear.com/for_home/default.aspx) that contain detailed instructions for configuration.
ahava wrote:So, can someone in the know please post the most appropriate configuration settings that would allow for the easy setup of "tunnels" using IPv6.
To get setup login to the Sonic.net member tools and go to Labs > IPv6 Tunnels : https://members.sonic.net/connections/ipv6tunnel/
Click View/request Tunnel and you will be presented with configuration settings to input into your device.
ahava wrote:ipv6 was started as a project in the early 1990's and met FCC readiness deadlines to deploy ipv6 technologies around the world in 2002
dane wrote:I should also point out, we’ve been offering customers IPv6 tunnels since 2002, way before any other service providers. So, we’re not new to v6 by any means. (Notably, we were told by an Apple engineer & customer that the Apple Airport wouldn’t have had v6 support without our service: the engineer took it home to his Sonic.net connection to develop and test 6in4 tunnel support.)
By dane on Jun 28, 2012 - http://corp.sonic.net/status/2012/06/28 ... equipment/
I hope this information helps you get set up, thanks for choosing Sonic.net!
cdkeen - Sonic.net System Operations
by derek » Wed Jan 15, 2014 3:49 pm
ahava wrote:If any Sonic Technical Support Gurus are listening: It's been two years and five days since gvdl posted the following issue to this forum, concerning the setup of ipv6 addressing:
Sonic only gives 2 ipv6 address when apparently 3 are needed:
  • WAN ipv6 Address=
    ipv6 default route=
    LAN ipv6 Address=

All I have is Transport:: 2001:<manyhexdigits>/127 & Network:: 2001:<manyhexdigits/60.
Does anybody have a guess how to translated these into the 4 time capsule fields?


It's a shame gvdl didn't update his own thread, but he posted an update the next day at viewtopic.php?f=13&t=317.

Even better, gather relevant information and post it as a Knowledgebase Article that could be consulted by your staff as well as by your subscribers.


There's a list of these on the page cdkeen mentioned. "View Example Configuration" (includes gvdl's sample even) However, understand that it's going to be really hard for them to have exact "what do you put in each box" on devices they don't have access to. So when you get yours working, please update us and I hope that can get put into that list. :)
by Guest » Sun Jan 19, 2014 10:52 am
Hi,

Can anyone help me setting up 6rd on Tomato (custom firmware for router)? There are two options for 6rd: 6rd Relay and 6rd from DHCPv4 (Option 212).

It seems that I need Static DNS for both. For 6rd Relay I also need 6rd Tunnel Border Relay (IPv4 Address) and 6rd Routed Prefix.

By the way, dual stack IPv4/IPv6 is not availabe yet right?
by nsmill49 » Sat Feb 01, 2014 10:06 pm
Guest wrote:Hi,

Can anyone help me setting up 6rd on Tomato (custom firmware for router)? There are two options for 6rd: 6rd Relay and 6rd from DHCPv4 (Option 212).
I am not certain about the difference, but I am not using the DHCP option with an Asus RT-AC66U. I suppose "how" depends on what Tomato expects in the fields. AsusWRT expects 2602:240:: in the "Prefix" field, and 28 in the "Prefix Length" field. If Tomato allows/requires, it could be, 2602:240::/28. The border router would be, 184.23.144.1; with its Prefix Length apparently set to, 0.
by Guest » Sat Feb 01, 2014 10:37 pm
if the Tomato GUI does not accept prefix_length=28, the workaround is to manually set the value via telnet to the router
https://github.com/ReliefLabs/EasyTomato/issues/59

nvram set ipv6_6rd_prefix_length="28"
nvram commit
reboot
by nsmill49 » Sat Feb 01, 2014 10:39 pm
ahava wrote:Could a network specialist suggest which settings to select to ensure a correct and solid configuration? FYI, I have an active Sonic DSL Elite Pro account using DHCP. ipv4 is working fire, but we have many wireless clients in a small home with daily IP address conflicts. I

I sincerely hope that the richer feature set of ipv6 will help alleviate our problems. Here are settings more or less as they appear on the routerlogin.com screen in Netgear's client.

  • Internet Connection Type: Options available:
    (a) Auto Detect (b) 6to4 Tunnel (c) Pass Through (d) Fixed (e) DHCP (f) PPPoE (g) Auto Config
    ipv6 Connection Type: No options here unless after it's been configured.
    WAN Now Reads: Router's IPv6 Address On WAN Not Available. (No choice but to leave as is.)
    Under LAN Setup, these Netgear Router settings specify how LAN IP Address Assignments are determined:
    Use DHCP Server
    Auto Config

I tried a Netgear WNDR3700 last year. Sonic.net offers a 6in4 tunnel, and now a 6rd tunnel. I could not find either as listed options in the Netgear; needless to say, I returned it as unsuitable for my purpose.

I replaced it with an Asus RT-AC66U, which has options for 6to4, 6in4, and 6rd, among others. From the Hurricane Electric Tunnelbroker forums I have seen a screen shot of a D-Link DIR-655 (Rev B, or greater; Rev A hardware does not support IPv6) 6in4 configuration page.

The D-Link may be easier to configure with a Sonic.net 6in4 tunnel. It includes separate fields for the IPv6 endpoint pair. Sonic.net requires configuring the pair as a ::/127, but the pair does not align to a ::/64 boundary, as does a Hurricane Electric 6in4 tunnel.

The Asus router expects the local IPv6 endpoint, with a prefix length. However, the Asus router prefix length field only accepts a two-digit entry, and only values between 3 and 64 at that. This works well enough with Hurricane Electric, but for Sonic.net, you would need to specify an impossible 127 in the prefix length field.

In any case, I doubt if IPv6 can help with your wireless IP conflicts. A properly configured IPv4 LAN should not be having conflicts. That is a problem for another topic, though.

Also, Sonic.net support staff is only trained to support users with Sonic.net issue CPE. This is the same with every ISP. There is more CPE out there than any one person not specializing in CPE could possibly learn.
by vincepoy » Sun Feb 02, 2014 4:54 pm
I have a Netgear R7000 802.11AC Wireless router and currently, this is my results using the following config:

Internet Connection Type - Autodetect

Connection Type 6to4 Tunnel
Router's IPv6 Address On WAN
Not Available

LAN Setup
Router's IPv6 Address On LAN
2002:4b65:7bd7:0:c604:15ff:fe10:732c/64
IP Address Assignment
Use DHCP Server

Is the WAN not supposed to have a IPv6 Address?

Tracing route to google.com [2607:f8b0:4010:801::1001]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2002:4b65:7bd7:0:c604:15ff:fe10:732c
2 10 ms 10 ms 9 ms 2002:c058:6301::1
3 10 ms 10 ms 14 ms ge6-10.core1.sjc2.he.net [2001:470:0:1e1::1]
4 10 ms 10 ms 10 ms 2001:4860:1:1:0:1b1b:0:9
5 12 ms 11 ms 12 ms 2001:4860::1:0:21
6 53 ms 12 ms 11 ms 2001:4860:0:1::3d5
7 11 ms 11 ms 11 ms nuq04s19-in-x01.1e100.net [2607:f8b0:4010:801::1
001]

Trace complete.
by vincepoy » Sun Feb 02, 2014 5:27 pm
Anyone know how to configure this manually for 6to4 Tunnel:

Internet Connection Type
6to4 Tunnel

Remote 6to4 Relay Router
Auto works but what am I supposed to put in for the Static IP Address which is a ipv4 address

LAN Setup
Router's IPv6 Address On LAN
2002:4b65:7bd7:0:c604:15ff:fe10:732c/64
IP Address Assignment
either Use DHCP Server or Auto Config works

Use This Interface ID
What am I supposed to put here?
by nsmill49 » Mon Feb 03, 2014 11:15 am
vincepoy wrote:Anyone know how to configure this manually for 6to4 Tunnel:

Internet Connection Type
6to4 Tunnel
I may be out of my depth, here, but isn't "6to4" different from "6in4"? My Asus RT-AC66U shows the following:

Code: Select all

Basic Config
Connection type       [Tunnel 6to4]
IPv4 Anycast Relay    [192.88.99.1] 
Tunnel MTU            [   ]
Tunnel TTL            [255]
IPv6 LAN Setting
LAN IPv6 Address      No Field
LAN Prefix Length     [48]
LAN IPv6 Prefix       [2002:ade4:07d9::]
I am going to guess that the Netgear "Auto configures" using the same IPv4 Anycast Relay address as I show. Your LAN IPv6 address is assigned from the IANA "Special Use" block: 2002::/16. This is not a Sonic.net assigned IP address. But it looks like it works.

To use a Sonic.net assigned IPv6 address, you would need to go to the member tools:

https://members.sonic.net/connections/ipv6tunnel/

You would use the "View/Request Tunnel" button for a ::/60 block of IP addresses. Then you would configure your router for a "6in4" tunnel using the data for the assignrd IPv6 endpoints, the assigned IPv4 border relay, and the assigned ::/60 block.

The Asus RT-AC66U can configure from three tunnel options: "6to4", "6in4", and "6rd". When I looked at a Netgear WNDR3700, it only had "6to4". No "6in4", nor "6rd". No way to use it with either a Hurricane Electric, or Sonic.net "6in4" tunnel. So I am going to guess: You have a working IPv6 IP address, just not a Sonic.net assigned IPv6 address; and your Netgear probably doesn't have the ability to set up a "6in4" tunnel.

P.S. FWIW, Asus can't configure my Sonic.net "6in4" tunnel due to a limitation on the tunnel IPv6 address prefix length; but it works with a Hurricane Electric tunnel. My trace to you:

Code: Select all

Tracing route to 2002:4b65:7bd7:0:c604:15ff:fe10:732c over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  2001:470:1f05:448::1
  2    38 ms    37 ms    37 ms  NKonaya-1.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:448::1]
  3    32 ms    32 ms    40 ms  ge5-19.core1.fmt2.he.net [2001:470:0:45::1]
  4    33 ms    42 ms    33 ms  10ge8-2.core1.pao1.he.net [2001:470:0:30::2]
  5    32 ms    32 ms    33 ms  6to4.pao1.he.net [2001:470:0:13b::2]
  6    44 ms    43 ms    41 ms  2002:4b65:7bd7:0:c604:15ff:fe10:732c

Trace complete.
23 posts Page 2 of 3