Airport Extreme and Cox Internet IPv6 Problem

David K Oberlin Jr. the setting (Link-local only) will work just fine and solves the multiple reboots of the AEBS. But, it also turns OFF IPv6. The Google DNS servers fix turns IPv6 ON with the added benefit of eliminating the multiple reboots of the AEBS.

I find it interesting that both Cox and Apple support are telling folks to use the Link-local only setting. Maybe someone from both companies will see posts like this that show a better solution. And maybe.... just maybe.... Cox will realize they may need to take a look at their DNS servers and fix them.

keg55 wrote:

. . . I find it interesting that both Cox and Apple support are telling folks to use the Link-local only setting. Maybe someone from both companies will see posts like this that show a better solution. And maybe.... just maybe.... Cox will realize they may need to take a look at their DNS servers and fix them.

And I still find it interesting that after my multiple reboots a week ago, I am now online reliably here in Williamsburg, VA with my Time Capsule's default settings (1pv6 Auto, etc.), as I reported above.

Of course, the important thing is that an apparently reliable patch (Link-Local) is serving lots of people well, and your observation about Cox is certainly correct, but I wonder what is different about my setup that allows it to work without the patch? Could it be my modem? Seems like knowing that could be helpful to some who are still having problems.

jimpal wrote:

And I still find it interesting that after my multiple reboots a week ago, I am now online reliably here in Williamsburg, VA with my Time Capsule's default settings (1pv6 Auto, etc.), as I reported above.

That IS interesting that you haven't had to change any of your settings and I assume are able to use Cox's DNS servers (in your area) with Automatically set.

Maybe Cox fixed or didn't bork the DNS servers in your area. In my area, they don't work. These DNS servers - 68.105.28.11, 68.105.29.11 - don't work and if I use them I have to use the Link-local only setting to avoid rebooting my AEBS several times a day.

keg55 wrote:

jimpal wrote:

And I still find it interesting that after my multiple reboots a week ago, I am now online reliably here in Williamsburg, VA with my Time Capsule's default settings (1pv6 Auto, etc.), as I reported above.

That IS interesting that you haven't had to change any of your settings and I assume are able to use Cox's DNS servers (in your area) with Automatically set.

Maybe Cox fixed or didn't bork the DNS servers in your area. In my area, they don't work. These DNS servers - 68.105.28.11, 68.105.29.11 - don't work and if I use them I have to use the Link-local only setting to avoid rebooting my AEBS several times a day.

Yes, that is what is interesting. I am using the Cox DNS servers you listed. And, again, my Time Capsule setup is its default setup (including 1pv6 Auto), which is exactly as described in the Comcast directions provided by Timmons above.

As a reminder, I did lose internet and have to reboot three times here about a week ago, which is why I entered this discussion group, and learned that others were setting to Link-Local and changing servers to fix it. Since I thought Link-Local might slow down my service, I decided to try one more time to see if staying with 1pv6 Auto, and Cox's servers, would work. And it did. And has without failure for over a week since then. On the other hand, another poster from my area, Brad Purvis (see above), had to resort to the Link-Local setting to get reliable service.

Again, my Time Capsule (version 7.7.3) is only four months old. And I am using my own Arris WBM760 (not provided by Cox) in my setup. I have no idea if these are significant facts in this case.

So, my internet service continues to work reliably as described. Who knows why? I thought the info might be of interest to the discussion.

As I said before, I will report back if I have to eat these words and say I have begun having having problems and start the rebooting again.

Thanks for the additional information.

I have no idea why you can use those Cox DNS servers and I can't. But I'm not going to lose sleep over it! 🙂

I have an AEBS (same firmware as you), not a Time Capsule which is the AC model (tower) and less than 1 year old. I use an Arris SB6141 cable modem (not rented). Maybe my peripherals compared to yours is the culprit. I don't know, but I wouldn't think so. At least Cox Internet Support doesn't seem to think so after they suggested I use the Link-local only setting.

keg55 wrote:

. . . I have no idea why you can use those Cox DNS servers and I can't. But I'm not going to lose sleep over it! 🙂

. . .

Good idea. Me either.

The only conclusion I reach is that Cox had a problem here in Williamsburg, VA which affected me over a week ago, and they must have changed something which makes my system not vulnerable anymore. Yet, Brad Purvis (above) who is also located here still seems to be vulnerable to Cox's issues.

Thanks for the info! Changing IPv6 to Local link-only on my AEBS and Express units seems to have fixed things. Will pursue turning IPv6 back on using Goggle's DNS addresses (and not COX's) should I notice a speed issue or continued dropouts.

Changing DNS to Google did not work for me....Cox/San Diego. Changing Airport Extreme to "local link only" worked - speed very fast (300Mbps Down / 15Mbps UP) with Cox Premier Service - Cable Modem is Arris SB 6190.

Also, have same hardware as above as above with Comcast in another city - did not have to change to local link only and have had no issues - not sure if Comcast has rolled out IPv6 in that location.

Hi there. Just thought I'd weigh in from Orange County, CA. I'm a Cox customer running Airport Extreme. I tried the changing to the recommended Google DNS settings as well, but connection still keeps crashing a couple times per day. This morning I decided to try something different. Instead of rebooting both my Zoom 5345 modem and Aiport Extreme, I just rebooted the Extreme all by itself. The light on my modem was showing solid internet connectivity, so I figured why mess with that? After rebooting just the Extreme, my Internet came flying back. Testing on http://test-ipv6.com/ shows 10/10.

I know it will crash again, but I just thought I would share my observations here with those who are smarter than me. Can I assume that the issue is clearly with my Extreme settings since the signal seems to be getting to my modem just fine?

Had a very knowledgeable guy that specialized in modems and routers come by from Cox. He explained to me what was happening with the IP-V6 vs the IP-V4 issues. Cox has been trying to upgrade to V6 but is having difficulties. They are in the process of going back to just V4. He showed me how to set up the local link (2) settings by the way, and I haven't had any drops since. 5 days and going strong. Finally. Here's the run down.

1. Open System Preferences and go to Network, Click on Advanced and set Configure IPv6 to Link-local only.

2. Open AirPort Utility, (located in Utilities Folder) Click on AirPort Time Capsule, and open Edit.

Select Internet on top bar, then click on Internet Options, and ConfigureIPv6 to Link-local only.

3. Finally go back to System Prefs, and open Network again, and Renew DHCP Lease.

This is the part I think I missed before.

Hope this helps.

jstoneob wrote:

Had a very knowledgeable guy that specialized in modems and routers come by from Cox. He explained to me what was happening with the IP-V6 vs the IP-V4 issues. Cox has been trying to upgrade to V6 but is having difficulties. They are in the process of going back to just V4. . . .

Thanks for this info.

If the guy is right that Cox has reverted to 1pv4, then that explains why my system has worked right here in Williamsburg for over a week now, with all of the original settings: Cox DNS, ipv6 Auto (instead of Link-Local), etc., which have worked fine for previous months. While all the patches he recommends may work, this reinforces my decision to just stick with the original settings which have worked correctly for so long. Hopefully this will carry on until Cox gets their stuff together and executes 1pv6 properly.

Appreciate your offering this alternative info, in case any of us has future problems with Cox's execution. How typical of them to blame Apple for their problems.

Two weeks into Cox on-site and phone tech service; all lines & connections replaced from street through house. Just spoke both with Cox and Apple. Previously, fingers pointed in both directions; Apple Tech just told me that they are aware of the communication (firmware) problem between Cox/Airport Extreme, and that the 2 are working together to fix. No dates. For now, needing the higher speed, we switched back to automatic from local-only and will trial stability. At least I feel we have gotten to the heart of the issue and see 2 options: use the band-aid setting local-only for Airport and settle for stable slower speed; or leave Airport set to automatic, rebooting when needed. Either way, Apple said that we would get the usual software update alert or the Airport light would turn yellow from green. Hope this helps.

Your assumption is probably valid. I got tired of going to the room where the equipment is stored to reboot everything, especially late at night. I discovered that all you had to do was was make the base station think an update happened - like type over the name or uncheck/recheck a setting - and it would restart without unplugging, restoring the dropped Internet connection. It can be done from a comfy chair with the Airport Utility mobile app 🙂

BTW, over a week with no dropouts using link-local workaround and zero impact to Internet usage and speeds.

There is an issue with the apple DNS default flopping around with the cox DNS default. You'll have to disable the IPv6 through the airport and manually enter in the two IPv4 DNS sections with the DNS servers marked as ; 8.8.8.8 and 8.8.4.4

Thanks, I had the same problem with Cox with the internet connection dropping a few times a day but Airport was up. I had to restart it to get it connected again. Your recommendations have worked so far with network reconfiguration.. I replaced the Cox router and was headed to an Apple store to purchase a new Extreme until I read the post. Thanks again for taking the time to write this up for the rest of us.