Starting this thread to share information with interested customers on the status of Cox's IPv6 rollout to DOCSIS 3.0 Gateways (also known as "eRouters" or "WiFi modems").
As of 3/3/2016, all markets have IPv6 CPE access for customers with standalone cable modems or EMTAs as detailed in https://www.dslreports.com/forum/r30294430-AZ-Quarterly-COX-IPv6-Check-Sept-2015. The next phase of the rollout is to enable dual-stack IPv4/IPv6 on the home network of Cox-supplied D3.0 Gateways. Enablement will be non-service-impacting to customers, as Cox will not be proactively rebooting devices to make the changes take effect. Instead, once dual-stack is made available in a market, any subsequent reboot to the device (either self-generated, or due to firmware upgrade, plant mtc, or any other reason) will result in the device coming back online in dual-stack mode.
"Dual-stack", for the record, means that the router will have all of the following simultaneously:
Public IPv4 WAN address
Private IPv4 LAN address subnet (typically 192.168.x.x, NAT'd to the WAN address)
Public IPv6 WAN address
Public IPv6 LAN address prefix (varies by customer & market; no NAT required - native IPv6 routing)
This will be accomplished in a few phases.
Macon, GA: Cisco, Netgear, and Arris gateways are already dual-stacked. Ubee gateways will be enabled on or about 3/15/2016.
Omaha, NE: Ubee gateways are already dual-stacked. All other Cox-supplied gateways will be enabled on or about 4/12/2016.
San Diego and Santa Barbara, CA: All Cox-supplied gateways will be enabled on or about 3/29/2016.
Northern VA, Florida, Arizona, Louisiana, and Oklahoma: All Cox-supplied gateways will be enabled on or about 4/12/2016.
Kansas, Arkansas, Nevada, Rhode Island, Connecticut, Ohio, Orange County CA, Hampton Roads and Roanoke VA: All Cox-supplied gateways will be enabled on or about 4/26/2016.
↧