Hacker News Reader

Comment by apaprocki | Hacker News Reader

Is anyone here actually using IPv6 with US cable modem providers (e.g. TWC)? Even though the device connected to the modem gets an IPv6 address, it is completely unclear as to a) what the assigned IPv6 block is or b) how to go about requesting one. It feels like they're in a limbo state of deployment where the edges work but they don't have the workflow/infrastructure set up to dole out address blocks to customers.

View on HN

I have Comcast cable service in Chicago. I have an SB6120 modem and an Airport Extreme base station. I didn't do anything special beyond plug it in.

The Airport Base has an IPv6 page that shows what the delegated /64 subnet is. All the devices on my network have autoconfigured themselves with addresses in that range. I appear to be able to manually set hosts to any address in that range as well and it seems to work fine. I do this on some of my server VMs because otherwise they generate a new random address every few days (privacy mode woo). The privacy addressing makes assigning a DNS name to said VM more difficult. I've had the same /64 delegated to me since June 2012.

I've heard that you can request a /60 prefix (16 subnets) if your router supports IPv6 Prefix Delegation (pretty sure the Apple one doesn't). I don't know exactly how you go about doing that though. I'd probably start with the HSI forums on dslreports.com

See, I have exactly the same setup (SB6xxx + AE) and on TWC in NYC it just doesn't work. The AE gets an IPv6 address from the modem, but TWC isn't assigning it a prefix, so all IPv6 devices behind the AE just sit there twiddling their digital thumbs.

TWC is definitely not as far along in their deployment. It might just take some more time. =\

Edit: If I recall correctly, when Comcast was doing their initial deployment they started with end nodes only (not delegating prefixes). Then moved to delegated /64s. Now are moving on to delegated /60s and more.

Some older AE/TC don't support DHCP-PD even if you update them with the latest firmware (that's really a shame IMHO). It might also just be your AE settings. Check that it is configured in router mode, with access mode set to native or automatic.

http://www.dslreports.com/forum/r27251137-IPv6-Time-Capsule-...

I'm in Schaumburg, and have had the same experience, but with a Linksys E3200 access point. Plugged into Motorola Comcast modem, and dual-stack came right up.

I am a TWC subscriber and as of December 2013 have IPv6 running perfectly fine in my home network. All my devices get IPv6 addresses and are able to connect to IPv6 test sites fine over IPv6. I'll note that I'm just using a /64 for my home network.

However, it took quite some time for that IPv6 connectivity to finally reach the small city in NH where I live. I'd first contacted TWC about 2.5 years ago asking about IPv6. I stayed in touch with people there over the years getting updates about where the deployment was at. There were issues with various internal equipment/software upgrades, etc. Finally I tried it out in December and found that it all worked and I had native IPv6.

Hopefully you may soon have the same experience.

A family friend with Comcast in the Seattle area has an IPv6 address that Google and other sites can see. That is, when they ask Google what their IP address is they only get their IPv6 address back as a response. This can only happen if end-to-end they're routing over IPv6, right?

DHCPv6-PD just works automatically with TWC (in Austin at least). You may need to upgrade your router.

(I am having some strange problems with Chrome reaching Google sites over IPv6, but I have no idea how to debug them.)

Reply on news.ycombinator.com