Comcast XFINITY → Re: [IPv6] Comcast Pulls Back On IPv6 Rollout

This statement is on Comcast's IPv6 Information Center page this morning:

Statement Regarding NetGear CMD31T Devices
Thursday, March 29, 2012

Comcast is in the process of deploying IPv6 nationally, as noted on this site in great detail. We recently identified that the retail NetGear CMD31T device ships with and runs an uncertified version of firmware that exacerbates a critical IPv6-related defect. To ensure Comcast customers with these devices will continue to have uninterrupted Internet service, we have rolled back IPv6 temporarily in some parts of our network to give NetGear more time to address the issue. Comcast anticipates NetGear will soon address the issue for their retail devices, which we will test and deploy on an emergency basis.

This is on the device info page for that modem as well-

"The retail NetGear CMD31T device has a known IPv6-related software defect. This prevents the device from being provisioned on the Comcast network. NetGear is aware of this defect and is working with us to test a fix. If you have purchased this device and it does not appear to work on our network, please contact NetGear or the store where you purchased the device."

What Comcast and Netgear should have done was notify retail outlets that if any customer comes in to return or exchange, to tell them that the issue is only temporary with the modem. Now there are demands that Comcast and/or Netgear reimburse customers who jumped the gun and purchased new modems from other manufacturers.

Maybe.
But ComCast has no idea how long it will take Netgear to fix the problem, so what are those subs supposed to do in the meantime?
This is Netgear failing to deal with a known problem over several years, hardly ComCast's fault, yet it effects CC's business and upgrade schedule and their relationship with their customers.
One of the big advantages of renting a modem is that it would be on ComCast to replace the modem with a fully IPv6 modem (likely a different brand) When you choose to buy your own ALL the risks of poor design, manufacturing defects, or inadequate support fall on you and it becomes your responsiblity to persue claims against the manufacter.

CC can't hold up their upgrade process for long just because of NetGear or any other single manufacter failed to assure a quality product.
I don't believe CC knew how severe the problem would be, but it would be risk to interfere in the netgear customer relationship... posting "Don't buy their crap" anywhere would certainly get you sued, even if it proved correct.

The thing is, the statements from Comcast say that the Netgear issue "exacerbates a critical IPv6-related defect."

This sounds like there is also a problem on Comcast's side, with their IPv6 hardware and/or software, that the issue with Netgear's modem brought to light.

From a story I read, Comcast returned service to the affected customers within a day or so by rolling back the CMTS.

Yes, they backed out of the upgrade (problem avoided, not solved)
so at first glance, some will say "it comcast's fault"....but it 's only this model with a certain "uncertified firmware/software" on it that failed. a model with a known problem. and apparent the software it current ships with.

Based on my experience with my Motorola modems, Comcast replaces the shipped firmware with a compatibe version of its own, even when the shipped firmware is newer. I would think this same practice takes place with other brands as well like Netgear. I also would think that any changes would be tested internaly every step of the way well before it would be released into the public production network.

If you put 10 engineers in a room, and told them "Make it PERFECT"
we'd still be on sneakernet.

I'm sure they are thoroughly tested (to death if needed, but some minor idiosyncrasies* must be allowed to exist)
but some effects/defects don't show up until stress tested** which is the point of the limit rollout area wise, and system wise***

*Brandcentric "FEATURES"
** exposed to the billions (really!) of possible hardware/software/equipment/usage combinations possible when big iron touches small systems. ( I think will call it "Internet")
*** I believe they are still in the ~~direct connect to a limited group of modems phase (this modem was known to be noncompliant, but not known to be incompatible)

Latest status from the Multichannel News site:

Netgear Working On IPv6 Modem Update For Comcast
Users of Vendor's CMD31T Lost Connectivity After MSO's IPv6 Deployment
Multichannel News - March 29, 2012

"Netgear said it will provide Comcast a firmware update for one of its DOCSIS 3.0 cable modems to make the devices compatible with IPv6, after several hundred of the MSO's customers lost Internet connectivity last week when Comcast put the next-generation protocol into operation in several markets.

"Recently, some Comcast customers lost their Internet connection due to an IPv6-compatibility issue we have with the Netgear CMD31T high-speed cable modem," Netgear said in a statement Thursday. "We are providing a firmware upgrade to Comcast for certification to make these devices IPv6 capable."

Comcast on Wednesday said it was rolling back its IPv6 deployment in some markets because of the glitch in the Netgear cable modems. The issue affected fewer than 1,000 subscribers, according to a source close to Comcast.

Once Comcast has certified the upgrade, the MSO will push it out across their network.

"Resolving this issue for customers in a timely fashion is our number one priority and we are working closely with Comcast on the solution," Netgear said. "We apologize for any inconvenience we have caused our customers."

According to Comcast, the Netgear CMD31T device currently "runs an uncertified version of firmware that exacerbates a critical IPv6-related defect," which prevents the device from being provisioned on the Comcast network. The cable operator is in the process of deploying IPv6 nationally, in a "dual-stack" implementation in which both IPv6 and IPv4 are supported on the client.

Comcast provides an "IPv6-readiness" check at »test-ipv6.comcast.net for any Internet user to check for IPv6 compatibility problems."

It is not a problem with the network...

hi Jason We missed ya.

Mike, I changed routers, I sent the Netgear back and went with the Asus RT-N66U. Anyway, I am having trouble getting IPv6 to work, I can get an IPv6 address using Comcast's 6to4, but every IPv6 test fails, any ideas? I tried HE's 6in4 too, same story. Thanks!

When you are doing the tests, what errors pop up? »test-ipv6.com/ Is your computers recieving an IPv6 address from the router?

Your IPv4 address on the public Internet appears to be 67.180.42.98

Your IPv6 address on the public Internet appears to be 2001:0:4137:9e76:3492:635:bc4b:d59d
Your IPv6 service appears to be: Teredo

The World IPv6 Launch day is June 6th, 2012. Good news! Your current browser, on this computer and at this location, are expected to keep working after the Launch. [more info]

You appear to be able to browse the IPv4 Internet only. You will not be able to reach IPv6-only sites.

Your IPv6 connection appears to be using Teredo, a type of IPv4/IPv6 gateway; currently it connects only to direct IP's. Your browser will not be able to go to IPv6 sites by name. This means the current configuration is not useful for browsing IPv6 web sites. [more info]

Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access.
Your readiness scores
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
0/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

That's what I'm getting.

looks like its an issue with the router not being configured because I get the same results when the 6rd tunnel has the wrong numbers.

what operating system are you using because with a Vista machine I tested it says the browser perfers IPv4 over IPv6 whereas my 7 machines which run the same IE9 browser says the browser perfers IPv6 over IPv4.

Do your computers have an IPv6 address?

I'm running Windows 7 SP 1 on this computer. According to ipconfig, this pc has a IPv6 address-

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Blade Runner>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::4589:eeb8:8948:f6b2%13
IPv4 Address. . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

IPv4 shows as enabled, IPv6 is showing as not enabled. Thanks for the help by the way, I appreciate it!

try tunnel 6RD. I noticed that its an option on your router.

That didn't work either.

what i ment was reconfigure the router to use 6RD and the 6RD info supplied by HE. It's what I'm currently using without a problem. »www.tunnelbroker.net/for ··· c=1850.0

6rd doesn't have all those settings on mine, just to enable or disable the DHCP Option, a place for tunnel mtu and tunnel ttl, and ipv6 dns servers.

wierd because the service mockup shows theres options.
maybe try disabling the DHCP option?

That was it, D'OH, I feel dumb!

it happens to all of us sometimes lol so is it all working now?

6RD will not work unless your ISP has 6RD relays.

Really?, thats unusual because for example I use 6RD on Comcast with a hurricane electric tunnel and it works. Comcast turned off their own 6RD relays back in June.

Not sure how it's working. Maybe you'll want to run »test-ipv6.com/ again.

6RD encodes your public IPv4 address into a /32 subnet on IPv6. That won't work with static 6in4 tunnels as address blocks are already pre-defined for you.

10/10 IPv4
10/10 IPv6