US Cable Support > Comcast HSI > Comcast deployed IPv6 yet?

Comcast deployed IPv6 yet?

We're very, very involved in working with the Internet community on IPv6 readiness. Here are a few samples for you from the upcoming NANOG meeting. (We're sponsoring NANOG in June in Philadelphia.)

»www.nanog.org/meetings/nanog46/a···=nanog46

»www.nanog.org/meetings/nanog46/a···=nanog46

»www.nanog.org/meetings/nanog46/a···=nanog46
--
JL
Comcast

JL, I realize Comcast is one of the cable leaders concerning IPv6 due to their massive base of installed equipment and shortage of private IP space for hosting, and hosting meetings on is great and all, but...

Is that a NO? Meaning Comcast is NOT currently using IPv6 for modem and box management, yet?

At least not that YOU know of?

Comcast is taking a phased approach to IPv6, check out the ppt from Comcast on this page:

»www.cybertelecom.org/dns/ipv6_transition.htm

It's from 2006 but it gives you a good idea of the approach they are taking. I believe Comcast's backbone has some IPv6 addresses in use with some of their peers and commerical customers so far. The use of IPV6 for CMs/eSTBs/eMTAs is going to require new code for at least one of the CMTS vendors so it may still be a little ways off.

reply to NSA_CIA

reply to NSA_CIA
I would suspect they might be using IPv6 for management ports. Right now that is one of the only places they could do it, that and backbone connections either inside their own network or peers to other networks. Actually since all their gear is interconnected I wouldn't be surprised if they are using private IP ranges such as the 10.x class A range. Yeah they're not "designed" to be routed but that doesn't mean they can't be.

It wouldn't take much effort to use private addressing for management access to their network connected devices. But then again it would only matter for devices that don't already have a public IPv4 address. For example, it wouldn't make much sense to use a public IP and a private IP on a modem when they can get to the public IP without any extra steps. A private IP would make sense for STB's and power supplies since they don't need a public IP.

If you think about it, they can't do much with the end user regarding IPv6 right now. Everything still requires an IPv4 address so at best they could provide you with both (which will be the first step in transitioning end users). But for the moment, you having an IPv6 address is likely not going to do you much good.

05/28/09 11:46:00 Slow traceroute 10.11.12.13
Trace 10.11.12.13 ...
192.168.0.1     RTT:   0ms TTL:170 (suzuka.aosake.net ok)
68.127.107.254  RTT:   9ms TTL:170 (adsl-68-127-107-254.dsl.pltn13.pacbell.net ok)
64.164.107.1    RTT:   9ms TTL:170 (No rDNS)
* * * failed
* * * failed
 

reply to JoelC707
Cable Modems have 2 IP addresses. The one they give to the customer could be an IPv4 address, while the "management" address could be an IPv6 address or a private IPv4 address. The modem's address doesn't really matter, since its only really used by Comcast anyway.

Cable modems have just one IP address, used to manage the modem. It is often a private address in the 10.x.x.x range.

One or more computers or routers connected to the modem have IP addresses assigned to them via DHCP. They must be public IP addresses, and at present they must be IPv4.

Yep, I'm being picky, but we see folks here who are confused onthis pint. It also leads them to think that the DHCP error messages in the modem log refer to the DHCP for their computer/router.

(Comcast does install cmobined modems/routers on some accounts. It's easiest to think of them as two seperate devices.)

reply to JoesphM
now if only there was a way to dump the MAC address from current memory without a full modem power cycle. would work wonders when supporting people with EMTAs if there was a "MAC Dump" button, put it where that useless standby usually goes.
--
[65 Arcanist]Filan(High Elf) Zone: Broadband Reports

reply to JoesphM
I read a post a few months ago on here about Comcast's IPv6 update.. and how they had a test bed ready for anyone who wanted to test something with it.. at the moment, can't seem to find it though...
--
...I don't have a 16mb speedy connection, I fly through the net at low altitudes!

reply to JoesphM
We can't forget that most routers, with the exception of certain business models such as the Cisco RVS4000 are not capable of IPv6 addresses.

I was referring to residental routers not having the capability of handling IPv6 addresses. If Comcast assigns customers with IPv6 addresses, ie gateway address, the router may not be able to use it.

With the number of IPv6 IP addresses available, why would we even need NAT routers? For the firewall? Not all NAT routers have a built-in firewall; and most router mfrs. will just start selling firewall appliances, without the NAT, when IPv6 really takes off.

In a world of IPv6, having NAT would be like having a buggy whip on your horseless carriage.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

When did we start talking about NAT? I'm talking about the product that routes data and supplies DHCP addresses to computers and networked appliances within a home enviornment, sometimes they come with wireless abilities.

How many of which don't provide NAT? Most people who use a router in a home environment need NAT because they share a single IPv4 IP address. If an ISP provided 12 IPv6 IP addresses with an Internet connection, all anyone would ever need is a switch, or hub.