US Cable Support → Time Warner Cable > [Internet] IPv6 just appeared on my connection

[Internet] IPv6 just appeared on my connection

So my inet went down, go to look in the router settings and there it was, an IPv6 IP. Sure enough, I can ping -6 google.com with it as well. Looks like TWC is rolling out IPv6.

BTW I am in the Los Angeles area with the Arris modem on their 50Mbit plan

Awe, it is no longer working. Can't even ping the gateway

And it is back up, well it was right before I left for the office.

IPv6 is a confusing mess. Does that mean I have to enable it on my Netgear router?

I'm showing a Teredo tunnel and can ping ipv6 / lookup ipv6 addresses, but I have to specify -6 in the ping command or the DNS lookup fails (which breaks most test websites). Probably a config issue on my end, but the actual ipv6 connectivity seems to work.

-- Rob
--
AT&T U-Hearse - RIP Unlimited Internet 1995-2011
Rethink Billable.

It gives AOLer's practicing being all l33t , a new topic to get all hard over.

Tracing route to www.google.com [2607:f8b0:4005:800::1011]
over a maximum of 30 hops:
 
  1     1 ms     8 ms     8 ms  Chihiro [2001:470:1f05:448::1]
  2    27 ms    33 ms    35 ms  NKonaya-1.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:448::1]
  3    39 ms    27 ms    24 ms  gige-g5-19.core1.fmt2.he.net [2001:470:0:45::1]
  4    37 ms    27 ms    38 ms  10gigabitethernet1-1.core1.sjc2.he.net [2001:470:0:31::2]
  5    36 ms    34 ms    34 ms  2001:4860:1:1:0:1b1b:0:9
  6    23 ms    27 ms    28 ms  2001:4860::1:0:7ea
  7    26 ms    24 ms    40 ms  2001:4860:0:1::691
  8    28 ms    29 ms    30 ms  nuq05s01-in-x11.1e100.net [2607:f8b0:4005:800::1011]
 
Trace complete.
 

Even so, the router must support it, and be configured for it.

My router is now pulling an IPv6 address, but it's only a /128 and so my LAN computers aren't getting anything. I need to poke a bit more...

2605:e000:7fc0:4a:7451:xxxx:yyyy:zzzz/128

/M

Where are you located? Is your router also setup for DHCPv6-PD?

Los Angeles

And yes, it's set for DHCPv6-PD.

/M

As I suspected, I just needed to reboot everything. DHCP-PD now gives me 2605:e000:1412:8xyz::/64 for my LAN.

traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2607:f8b0:4005:802::1014), 30 hops max, 80 byte packets
1 <snip my router> 0.354 ms 0.116 ms 0.277 ms
2 * * *
3 2605:e000:0:4::5:209 (2605:e000:0:4::5:209) 16.174 ms 16.888 ms 16.710 ms
4 2605:e000:0:4::5:b0 (2605:e000:0:4::5:b0) 18.513 ms 19.285 ms 19.092 ms
5 2605:e000:0:4::40 (2605:e000:0:4::40) 16.811 ms 16.635 ms 16.431 ms
6 2001:1998:0:8::86 (2001:1998:0:8::86) 18.249 ms 12.613 ms 17.348 ms
7 2001:1998::66:109:6:133 (2001:1998::66:109:6:133) 17.051 ms 2001:1998:0:4::56 (2001:1998:0:4::56) 15.687 ms 16.539 ms
8 2610:18:10d:8000::5 (2610:18:10d:8000::5) 84.097 ms 2610:18:10d:8000::45 (2610:18:10d:8000::45) 83.916 ms 2610:18:10d:8000::31 (2610:18:10d:8000::31) 82.677 ms
9 * * *
10 2610:18::2074 (2610:18::2074) 89.306 ms 89.060 ms 83.973 ms
11 2001:4860:1:1:0:b0c:0:1 (2001:4860:1:1:0:b0c:0:1) 86.508 ms 91.506 ms 92.299 ms
12 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 27.666 ms 21.980 ms 22.194 ms
13 2001:4860:0:1::693 (2001:4860:0:1::693) 22.551 ms 27.808 ms 28.568 ms
14 2607:f8b0:8000:2a::b (2607:f8b0:8000:2a::b) 68.521 ms 73.652 ms 2607:f8b0:8000:2a::5 (2607:f8b0:8000:2a::5) 75.388 ms

ping6 -c 10 ipv6.google.com
PING ipv6.google.com(nuq05s02-in-x14.1e100.net) 56 data bytes
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=1 ttl=51 time=19.5 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=2 ttl=51 time=19.4 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=3 ttl=51 time=19.9 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=4 ttl=51 time=19.5 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=5 ttl=51 time=19.5 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=6 ttl=51 time=19.6 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=7 ttl=51 time=19.3 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=8 ttl=51 time=19.9 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=9 ttl=51 time=19.9 ms
64 bytes from nuq05s02-in-x14.1e100.net: icmp_seq=10 ttl=51 time=19.6 ms

--- ipv6.google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 19.368/19.654/19.978/0.217 ms

The IPv4 google for reference:
ping -c 10 google.com
PING google.com (74.125.239.142) 56(84) bytes of data.
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=1 ttl=51 time=20.0 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=2 ttl=51 time=20.4 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=3 ttl=51 time=20.3 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=4 ttl=51 time=20.5 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=5 ttl=51 time=20.5 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=6 ttl=51 time=21.0 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=7 ttl=51 time=18.8 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=8 ttl=51 time=19.0 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=9 ttl=51 time=18.5 ms
64 bytes from nuq05s02-in-f14.1e100.net (74.125.239.142): icmp_seq=10 ttl=51 time=18.8 ms

--- google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 18.578/19.835/21.044/0.880 ms

/M

mtr -c60 --report{,-wide} ipv6.google.com
Start: Thu Aug  1 18:59:30 2013
HOST: localhost.localdomain                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2605:e000:1412:8<snip my router>        0.0%    60    0.4   0.4   0.4   0.5   0.0
  2.|-- ???                                    100.0    60    0.0   0.0   0.0   0.0   0.0
  3.|-- 2605:e000:0:4::5:209                    0.0%    60   10.9  10.2   7.9  23.8   2.8
  4.|-- 2605:e000:0:4::5:b0                     0.0%    60   10.8  11.5   7.5  17.6   1.6
  5.|-- 2605:e000:0:4::40                       0.0%    60   13.4  12.0   8.8  15.7   1.6
  6.|-- 2001:1998:0:8::82                       1.7%    60   14.5  12.6   9.1  20.0   2.1
  7.|-- 2001:1998::66:109:6:133                 0.0%    60    9.8  11.5   8.8  60.8   6.7
  8.|-- 2610:18:10d:8000::65                    0.0%    60   77.1  81.9  76.5 133.3  11.9
  9.|-- ???                                    100.0    60    0.0   0.0   0.0   0.0   0.0
 10.|-- 2610:18::2074                           0.0%    60   84.3  87.4  83.1 136.0   8.4
 11.|-- 2001:4860:1:1:0:b0c:0:1                 0.0%    60   90.2  91.0  82.8 148.5  12.0
 12.|-- 2001:4860::1:0:7ea                      0.0%    60   29.1  29.5  19.6  53.3   9.5
 13.|-- 2001:4860:0:1::693                      0.0%    60   20.5  22.7  20.0  42.1   3.9
 14.|-- nuq05s02-in-x11.1e100.net               0.0%    60   21.9  21.6  19.4  30.0   2.0
 
mtr -c60 --report{,-wide} google.com
Start: Thu Aug  1 19:01:33 2013
HOST: localhost.localdomain                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2605:e000:1412:8<snip my router>        0.0%    60    0.5   0.4   0.4   0.5   0.0
  2.|-- ???                                    100.0    60    0.0   0.0   0.0   0.0   0.0
  3.|-- 2605:e000:0:4::5:209                    0.0%    60    8.3   9.4   7.8  11.4   0.7
  4.|-- 2605:e000:0:4::5:b0                     0.0%    60   12.6  11.3   8.7  15.5   1.5
  5.|-- 2605:e000:0:4::40                       1.7%    60   12.9  12.5   9.4  25.4   2.5
  6.|-- 2001:1998:0:8::86                       3.3%    60   15.5  12.5   9.2  18.0   1.9
  7.|-- 2001:1998:0:4::56                       0.0%    60   10.5  12.4   8.8  70.6   8.0
  8.|-- 2610:18:10d:8000::61                    0.0%    60   77.2  79.1  76.9  91.9   3.0
  9.|-- ???                                    100.0    60    0.0   0.0   0.0   0.0   0.0
 10.|-- 2610:18::2074                           0.0%    60   84.5  88.7  83.4 113.1   6.7
 11.|-- 2001:4860:1:1:0:b0c:0:1                 0.0%    60   83.5  85.8  83.1 131.5   6.2
 12.|-- 2001:4860::1:0:7ea                      0.0%    60   21.8  22.6  19.5  36.6   2.7
 13.|-- 2001:4860:0:1::693                      0.0%    60   21.1  21.9  19.8  23.8   0.7
 14.|-- nuq05s02-in-x04.1e100.net               0.0%    60   22.9  21.6  19.5  34.2   2.1
 

mtr -c60 --report{,-wide} -4 google.com
Start: Thu Aug  1 19:04:54 2013
HOST: localhost.localdomain                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.10.254                          0.0%    60    0.2   0.2   0.2   0.4   0.0
  2.|-- cpe-172-248-208-1.socal.res.rr.com      0.0%    60   89.2  38.9  11.8 143.4  28.1
  3.|-- tge0-7-0-4.vnnzca24-cer02.socal.rr.com  0.0%    60    9.2   9.9   7.4  21.4   2.3
  4.|-- agg11.vnnycajz-ccr02.socal.rr.com       0.0%    60   14.0  11.4   7.5  19.4   2.2
  5.|-- agg29.tustcaft-ccr01.socal.rr.com       0.0%    60   13.3  13.7  10.7  22.1   2.1
  6.|-- ae-6-0.cr0.lax30.tbone.rr.com           0.0%    60   12.2  14.3  10.3  27.9   3.0
  7.|-- ae-1-0.pr0.lax10.tbone.rr.com           0.0%    60   10.2  13.2   9.6  58.4   7.0
  8.|-- 72.14.198.73                           78.3%    60   21.4  22.4  19.1  28.5   2.5
  9.|-- 216.239.46.40                           0.0%    60   19.1  25.2  17.9  94.7  14.6
 10.|-- 64.233.174.190                          0.0%    60   18.4  21.0  18.4  41.9   3.9
    |  `|-- 64.233.174.186
 11.|-- 64.233.174.205                          0.0%    60   20.2  20.7  18.0  29.8   2.5
    |  `|-- 64.233.174.207
 12.|-- 209.85.250.62                           0.0%    60   30.9  23.1  17.9  37.7   4.5
    |  `|-- 209.85.250.67
 13.|-- 66.249.95.31                            0.0%    60   22.4  21.0  18.4  33.5   2.9
 14.|-- nuq05s02-in-f7.1e100.net                0.0%    60   19.7  20.1  18.0  32.7   2.2
 

Curious why you're using ipv6.google.com when you can just use www.google.com?

Here is hoping that TWC will continue rolling out service in their other markets.

Anyone notice v6 active in other states?

Mainly old habit, but it also ensures that IPv6 is used (no chance of getting an A record by mistake).

/M

You might want to check out the Firefox add-on Sixornot.

Re: [Internet] IPv6 just appeared on my connection

Hrmm. So I see service is up and running in parts of California, Texas and I think New York. Anyone noticing service active anywhere else?

Unlike my compatriot in Elyria, I would love to see ipv6 hit the NE Ohio area. OTOH, my current firewall isn't capable (pfsense v2.0.x), but that is coming soon once 2.1 hits final...

How do you go about enabling it on a Netgear WNDR4300 router? Do you just choose automatic? Very confusing.

2.1 RC1 is very stable already. That aside, I'm in NEO and am not showing IPV6 on my modem.

Does anyone know how IPv6 addresses are delivered to TWC end users? Is it via DHCP6, SLAAC, 6rd Tunnel, 6to4 Tunnel, or Track Interface?

I'm using pfSense 2.1 beta with Biz Class service, no static addresses, and a Cisco DPC2100R2 modem. Currently am using a HE tunnel, but would drop it if TWC's IPv6 works good. I see a gateway address of "2002:c058:6301::" on the WAN interface if it set it up as DHCP6 or 6to4 tunnel. Not sure what that means since the address isn't complete.

'Native with DHCP-PD' is what I choose in my RT-N66U to get an IPv6 address.

Yes, 'Auto' should work fine. At least my D-Link DIR-825 likes it just fine

/M