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

Re: [Internet] IPv6 just appeared on my connection

I haven't looked into it too deeply yet, but from the outside I can ping the /128 assigned to the router just fine but anything in the /64 fails.

/M

so someone please explain how do I configure ipv6 no one wants to give me instructions.

I have the RT-n66u configured as native dhcp for ipv6. Thanks!

I have the AC66U. From the menu screen I see no configurable parameters when "Native with DHCP-PD" is selected. I assume the router will make a request from the ISP DHCP-PD server; but I can't prove it one way, or another.

Update: I had to reboot my router due to config changes on it. When it came back, no more IPv6. Could TWC have disabled their DHCPv6 server here, or is there something else going on?

Try shutting down your router and unplugging modem. Plug modem back in, allow it to fully boot and then start up your router and see if you get your IPv6 back.
--
Do you remember when House began?

My service went out yesterday. When it came back I noticed IPv6 came back on my connection.

So it's been a few days since IPv6 came back permanently on my connection. I've noticed a few things:

•The AirPort Extreme seems to request and receive a /64. There seems to be no way to get a bigger block. I will probably get a router I can flash with DD-WRT or some other firmware when the APE finally dies so I can look into fixing that.
•Safari on my MacBook Pro always uses IPv4 when both options are available. It looks like it's because latency on IPv6 is consistently higher than on IPv4. Not sure if this will be something that gets fixed over time as TWC adds more IPv6 peering.
•Speaking of peering, it seems that any IPv6 traffic to AWS always goes through Seattle, at least to go to their Oregon datacenter. Is this normal?



traceroute to newsrdr.us (2620:108:700f::36d5:ba8e) from 2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, 30 hops max, 24 byte packets
 1  2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (2605:e000:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx)  0.414 ms  0.286 ms  0.234 ms
 2  2605:e000:40c:46::1 (2605:e000:40c:46::1)  10.401 ms  5.602 ms  6.721 ms
 3  2605:e000:0:4::2:311 (2605:e000:0:4::2:311)  6.399 ms  6.211 ms  7.374 ms
 4  2605:e000:0:4::2:b2 (2605:e000:0:4::2:b2)  11.642 ms  9.579 ms  15.914 ms
 5  2605:e000:0:4::24 (2605:e000:0:4::24)  14.268 ms  12.071 ms  11.808 ms
 6  2001:1998:0:8::86 (2001:1998:0:8::86)  14.646 ms  12.063 ms  11.822 ms
 7  ae-0-0.pr0.lax00.tbone.rr.com (2001:1998::66:109:6:135)  9.889 ms  11.185 ms  10.977 ms
 8  2001:1998:0:8::1e6 (2001:1998:0:8::1e6)  13.208 ms  11.851 ms  9.899 ms
 9  vl-80.edge6.LosAngeles1.Level3.net (2001:1900:12:3::b)  10.085 ms  17.595 ms  10.18 ms
10  vl-4061.edge2.SanJose1.Level3.net (2001:1900:4:1::65)  20.676 ms  21.805 ms  19.561 ms
11  vl-4040.car1.Seattle1.Level3.net (2001:1900:4:1::49)  39.372 ms  38.411 ms  38.168 ms
12  vl-52.edge2.Seattle1.Level3.net (2001:1900:1b:2::b)  37.871 ms  37.726 ms  37.57 ms
13  AMAZON-CORP.edge2.Seattle1.Level3.net (2001:1900:2100::1d5a)  40.091 ms  37.692 ms  37.779 ms
14  * * *
15  2620:108:7000::10 (2620:108:7000::10)  52.354 ms  49.708 ms  74.497 ms
16  2620:108:7000::11 (2620:108:7000::11)  49.636 ms  50.716 ms  49.066 ms
17  2620:108:7000::2 (2620:108:7000::2)  50.374 ms  71.05 ms  53.873 ms
18  *^C
 

Goog for both v4 and v6 servers.

/M

Hmm. Might be within the margin of error. It's possible the router has something to do with it, but we won't know without additional data.

Still confused. I have the Netgear WNDR4300. How do I activate it on my router?

In settings set ipv6 to auto config then power off router and then modem then turn modem on and wait til it is completely on the turn on wndr4300 it worked for me I have the same router.

Tried it out tonight and I finally got a native IPv6 address! Requested a /64 prefix and that worked too. Awesome!

Surprisingly I got better speed results over IPv6 than IPv4:

Well, I'm back on the he.net tunnel. The TWC IPv6 keeps making me manually renew the DHCPv6 lease every couple of hours, which I thought I had read someone else mention having a problem with, but I don't see it in this thread.

Also, for those interested, I was not able to request a /60 or /56. Only a /64.

I can request a /60 using pfSense and it will assign me 4 ipv6 addresses for my 4 LAN networks. Only thing is, testing IPv6 always fails saying no IPv6 address. When I request a /64 for just my main LAN, everything works perfectly and I get a 10/10 from test-ipv6.com. So something is not right with anything bigger than a /64
--
Do you remember when House began?