Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
Valued Contributor II
•
RI has IPv6 :-)
Finally flipped the switch on my router. Didn't know it was enabled way back on 16th. I did find my eMTA had a much harder time pulling a IPv6 then my SB6141. This is the first time I am using native, instead of HE, but 5min to get a IPv6 with multiple DHCP errors? Makes me think Cox's IPv6 system is under-built and having troubles.
Anyone have issues in New England with a DPQ3212 and IPv6? Finally got it working, but I feel something is off.
AllenP
+4 more
Valued Contributor
•
I had it working for a short time (less than a day) here in Connecticut last week with dhcp. Then it stopped working and I was back to a 6to4 tunnel when I did an auto config ... no address from dhcp. Even when it was working, I was having problems with default IPv6 dns lookup. Had to go to Google's IPv6 dns servers for it to work. Chalked it up to Cox is still testing in my market ... no notice and not ready for prime time.
0
0
Tecknowhelp
Valued Contributor II
•
Yea, I tried a week or two ago and it didn't work, but I hadn't bypassed the router yet. I think some modems take longer to bridge the IPv6 address after boot maybe? And you have to reboot the router for it to use the DHCP-PD to get the new IPv6, the question is, do you have to reboot the modem too? IPv4 and IPv6 are similar, but just different enough to be a headache it seems.
Also, are you using a IPv6 firewall? Have you tried JUST using IPv6? Oh and yea, Cox DNS has always been bad, I didn't think IPv6, which has more overhead, would be better. 3rd party DNS FTW.
0
0