You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

GABarber Author

Level 1

27 points

Airport Extreme and Cox Internet IPv6 Problem

This is a notification to others as well as a question:

I have Cox Cable High Speed Internet at several locations using an Airport Extreme 3GB connected as a router to the Cox cable modem.

For more than a week we would regularly find in the morning that the outside connection to the internet DNS servers were lost. We called Cox several times, and they performed the usual reset of router and modem and things seem to work for a while. But the next day gone again.

They came out and replaced the hookups, I I had to buy a new cable modem and replaced a digital switch. Each time things seemed to work for a while.

I thought about replacing the Airport Extreme (as I read others had done in a similar situation to no avail).

After much frustration, I started to search for Airport Extreme and DNS and found similar tales.

After several unproductive calls with Cox Internet first tier support, I finally reached a tier who acknowledged that Cox was rolling out IPv6 and was having a problem with Airport Extreme Routers. They said Apple was working on it and gave me a number to call at apple router support. Unfortunalely the number they gave was no longer valid.

I persisted and eventually got to Apple support and indeed they knew of the problem and said Cox was working on it.. But there was a temporary fix - and that was to turn off iPv6 on the airport extreme (more precisely (internet > Internet Options > Configure Ipv6 : Link-Local Only).

For now this seemed to stop the overnight drop that seems to happen between 12:00 AM and 2:00 AM. From experience I dont think its really an IPV6 compaibility issue, but how the router responds to some sort of reset signal/test signal that the service does in the early morning.

So the question is - does anybody know for sure whats going on or who is really working on this. From my perspective both camps think its the other's problem. BTW - Ive read about others with Non Apple routers chasing something similar.

Posted on Mar 2, 2016 9:03 PM

483 replies

Apr 12, 2016 4:27 PM in response to keg55

I See no adjustment on the iPad?

the extreme is on local link only

Apr 12, 2016 4:29 PM in response to the_arje

What you are telling us is that Cox's DNS Servers are causing issues, while Cox continues to state on their website that Apple routers are not compatible with the new implementation of IPv6 service from Cox.

the_arje

Level 1

23 points

Apr 12, 2016 4:40 PM in response to Bob Timmons

Guess so. But for now, it's working. Seems like, upon more research, IPv6 and AEBs never really got along going back as early as firmware version 7.6.1

Apr 12, 2016 4:53 PM in response to the_arje

Not sure what research that you are referring to. Things have been fine with Comcast and Time Warner for a number of months. Can you find any reports of difficulty with IPv6 from users who are using those services?

I can find plenty of posts from Cox users. We see 3-4 per day on average.

In case you are interested, here is what the IPv6 setup looks like if you are on Comcast or Time Warner. It appears that you might be able to use the same setup with Cox and use the Google DNS servers, since Cox's are creating issues. A good friend, who is on Cox, tells me that the IPv6 setup that you see, along with the Google DNS servers, are working well for him.

http://mydeviceinfo.xfinity.com/download.php?file_id=35

I think you would agree that It would sure help if more ISPs would provide detail like this for their customers.

A big tip of the hat to Comcast on this one.

iJedie24

Level 1

16 points

Apr 12, 2016 4:50 PM in response to GABarber

Just wanted to give another update. I've been using Google DNS servers for almost a month now with no problems. There really is no downside to it. I say "set it and forget it". Maybe someday this will get fixed (I wouldn't bet on it) but for now, this works and works well. No reason not to do it. Full IPV6 compatibility and full speed.

Apr 12, 2016 4:52 PM in response to iJedie24

Same report from a good friend who is on Cox. See the message just above. Unfortunate that Cox is still telling users that Apple routers are incompatible.

keg55

Level 6

11,743 points

Apr 12, 2016 5:11 PM in response to the_arje

Thank you the_arje!

I'm trying the Google DNS servers (8.8.8.8, 8.8.4.4) now. I also just ran a test of IPv6 from test-ipv6.com and received a 10/10 score with the Google DNS servers. Prior to the change when I used Cox's DNS servers I got a 0/10 score. From what I was told by Cox Internet support, IPv6 has been in my area (Phoenix, AZ) since December 2015. I'll see if I make it through the night this way. If so, I'll stick with it and if Cox fixes their DNS servers, then I'll go back to theirs.

the_arje

Level 1

23 points

Apr 12, 2016 5:40 PM in response to keg55

@Bob Timmons. Not trying to get into a flame fight or anything like that 🙂

You're totally right. Not a peep out of TW or Comcast customers 🙂 Cause at least their DNS servers are working with AEBs in the mix at a user's home. So it's definitely something on Cox's end because if I can't use their DNS servers then they've got to fix something. BUUTTT, in regards to the research I found, it's here: http://arstechnica.com/apple/2013/02/airport-extreme-update-breaks-ipv6-tunnels- but-heres-how-to-fix-it/ Only suggests that Apple might have some of it's own apologizing to do.

Bottom line, it's working now for me, keg55, iJedie24, your friend and hopefully more and more people cause we're sharing the info.

CQ92651

Level 1

8 points

Apr 12, 2016 5:50 PM in response to GABarber

I'm also trying the Google DNS suggestion in Orange County CA. Too soon to tell, but worth a try. Thanks to all who provided this tip.

Apr 12, 2016 5:59 PM in response to the_arje

The article that you reference does not use the settings that Comcast and Time Warner recommend.

Please check this article. http://mydeviceinfo.xfinity.com/download.php?file_id=35

Are you using "Native" or "Tunnel"? "Native" is what is recommended by Comcast and Time Warner. I've gone about 6 months without a single hiccup with these settings. And, I'm not aware of a single post on this forum from a Comcast or Time Warner user who has posted to say that they are having IPv6 problems.

One will probably show up in a few minutes though.

Since the AirPort Extreme 802.11ac (and Time Capsule) were both designed about 4 years ago, that's not bad. The next generation of products will have many more IPv6 options, I am sure.

The point is that Apple Support has said that the issue is with Cox. While that might not be 100% accurate, it is a lot more accurate than the nonsense that Cox has been telling their customers.

the_arje

Level 1

23 points

Apr 12, 2016 6:18 PM in response to Bob Timmons

I don't think Bob Timmons likes me....oh well. At least my internet connection is working and let's hope CQ92651 finds success too.

@Bob, if you're on Comcast, why are you on this thread....nevermind....don't reply.

Apr 12, 2016 6:26 PM in response to the_arje

You did not read the previous messages, did you?.....nevermind.....don't reply.

jimpal

Level 2

228 points

Apr 12, 2016 6:39 PM in response to Bob Timmons

Bob Timmons wrote:

The article that you reference does not use the settings that Comcast and Time Warner recommend.

Please check this article. http://mydeviceinfo.xfinity.com/download.php?file_id=35

. . . . . . . The point is that Apple Support has said that the issue is with Cox. While that might not be 100% accurate, it is a lot more accurate than the nonsense that Cox has been telling their customers.

Agree. After three shutdowns/reboots with my Cox system last week, all has been working well ever since with 1pv6 set at Auto, and Cox's own DNS address. A good reason for this, I think, is that my four-month-old Time Capsule came with default settings exactly as specified in the Comcast instructions Bob Timmons provided above.

the_arje

Level 1

23 points

Apr 12, 2016 6:42 PM in response to Bob Timmons

Alright, I will take the high road here, Bob. I reread the previous messages, or at least the ones after my comment. And I think my problem with you is when you said "The article that you reference does not use the settings that Comcast and Time Warner recommend." This article doesn't because it comes way before it and was not meant to provide anyone here a solution. It's just a frame of reference for how Apple might be at fault too.

I put that article in there to illustrate how AEBs from as long ago as 2013 on 7.6.3 didn't play well with IPv6 - thus necessitating people to tunnel. Then you reposted the Xfinity article, which I had read the first time. Yes, the settings did help you. And yes, the settings would have helped me and they did.

This back and forth is useless and buries solutions waaaay to deep, so I will simply say I'm sorry if I offended you. And for anyone else on Cox who has an AEB and a problem with IPv6, make sure configuration is set to Automatic and that you're doing so "Native". Set the DNS to 8.8.8.8 and 8.8.4.4. Update the router and hopefully that works.

That's what I should have said and left it at that. I'm sorry, Bob.

Apr 12, 2016 6:50 PM in response to Bob Timmons

I am also a COX customer with an Airport Extreme router down here in San Diego. Been experiencing loss of WiFi internet connectivity for about 3 weeks now having to reboot Airport Extreme to fix. Oddly my wired computers do not experience any issues.

Just got off phone with Apple and they are aware of the issue and had me set the IPv6 setting on the Airport Extreme to "Link-local only". Also had me set my (2) Airport Express units I am using for a roaming network with the Airport Extreme in the same manner.

So far so good with no speed loss as others have indicated....actually I jut ran a test after updating IPv6 settings and since I last tested at Speedtest.net my download speed has doubled from 31 Mbps to 60 Mbps...upload remained the same at around 6 Mbps

If this does not fix the problem I will give the aformentioned Google public DNS a try.

On another note, I have probably installed 50+ Airport Extreme routers for COX customers (networking as eeked its way into my line of work of AV Integration) and have indeed received a few calls from them. Also received a call from one of my customers who has AT&T and had them update the Airport Etreme IPv6 settings and they said so far so good...hmmm

Airport Extreme and Cox Internet IPv6 Problem