Router losing connection to Cable Modem

Wow!!  I have been having this problem for the past month and have not had the time to search the internet.  I am really glad that I am not alone.  I am a Cox customer (obviously) and am using the Motorola SB6183 and the Airport Time Capsule.  I am basically following the advise to set the IPV6 to LInk-Local and see what happens.  For me I am having to reset my router twice a day and I work from home, so it is really a disruption.

@georgeseifert

It appears from this end that you did correctly disable IPv6 as advised.  It is indeed a confirmed problem however it may not be the only problem you're experiencing.  You may wish to test without the router at this point to see if there is any change.

I just disabled IPv6 on my Time Capsule. Will this cause me any problems when trying to reach IPv6 web sites?

I just want to add in here...  Thanks to all of you who are dealing with this so diligently.  I live in Orange County CA and have been suffering with this for the past three weeks, give or take a week.  I finally had time to find this thread and have done the link local only on my Apple Time Capsule and on my three computers and iOS devices.  I will be checking back in and letting everyone know if it worked. 

Thanks again,

Well, I had to return to changing the IPv6 to local only. This is nuts. Still have to reboot several times a day because it "disconnects". If Cox can't find a solution, I may have to do away with them and go back to Centurylink. Why should Cox come up with a solution and not Apple? Cause it's only an issue with Cox, that's why. 

georgeseifert said:
Cause it's only an issue with Cox, that's why. 

Wrong. There are post on Centurylink, Comcast and even FIOS with IPv6 and Apple products. I can dig out the links if you want, but I doubt you would care. Do you really need IPv6? Why just disable it until you get a router that uses IPv6 standards?

I'm not sure if you're asking me a question or??? But I did change the settings to disable IPv6. I'm open to try what works. This entire network, sat on 2 other ISP's, which is why I made the comment. 

add me to the list. i just changed mine to IPv6 "tunneling," and it seems to work well, though i'm getting an IPv6 relay error message from my router.

I have changed my DNS settings to Google and have not had a problem with disconnects in over a week.  It was normal for me to lose my connection every 24hrs.  I still have IPv6 set to automatic and native with no noticeable issues with performance.

config - AirPort Time Machine and AirPort Extreme bridged. 

Below is a post from the apple forum.   Hope it helps.

Another update on the Cox IPv6 with Apple Airport Basestation (Extreme or Express) issue.  

Someone else on the Apple Support forum commented on contacting Apple regarding this issue. The support tech recommended changing the Airports DNS settings to go to Google Public DNS as opposed to Cox. This made sense to me. If the problem is with Cox's implementation of IPv6, switching servers could solve the issue. The DNS settings in your router basically tell the router which servers to connect you to. I have made these changes and have been using them for the last 36 hours without issue. As opposed to the previous temporary fix (switching IPv6 on the Airport to link only local), I view this as a more permanent fix. The previous temporary fix would leave you without any IPv6 support at all. Some also reported internet speed issues after this fix. I found my speeds okay during the day, but questionable during peek hours at night. So, the new fix will restore IPv6 functionality, reroute your internet connection through Googles servers and should restore or improve speed over the previous fix (I tested speeds a lot over the last 24 hours-some speed drop at night during peek hours-but that's really to be expected and it's not as bad as it was before-on a 100 Mbps connection, I was still getting 85). On to the fix, then.  

This was done using Airport Utility for iOS. Should be similar on Mac. Open Airport Utility app. Tap on your Airport basestation's icon. Tap "Edit" in the upper right hand corner of the screen. Tap "Internet Connection". DHCP should be highlighted in blue at the top of the screen. Under "DNS Server" you will see a primary and secondary set of numbers. These are the Cox DNS server numbers. Write these down. You'll need them should you ever decide to revert back. If you made the previous change to IPv6-link only local, you will not see any characters under "IPv6 DNS Server". If you did not make this change, Cox's DNS server numbers should be displayed here. Again, Write these down, so you may revert later. I haven't tested this, but, in theory, if you don't write these numbers down, you should be able to get them back by resetting the Airport to factory defaults with the hard reset button on the back of the unit. Okay. Now the changes. If you are using Google, you'll enter the following. There are other public DNS servers you can use like Level 3 and others. Do an internet search for it. For Google: tap in the field next to "Primary" under "DNS Server". Type in "8.8.8.8" (without the quotation marks). In the "Secondary" field, type "8.8.4.4" (again, without quotation marks). Go down to "IPv6 DNS Server" and type in the "Primary" field "2001:4860:4860::8888" (no quotation marks and notice the double colon between 4860 and 8888). Now go to the "Secondary" field and type "2001:4860:4860::8844" (no quotations and again notice the double colon). This switches you to Google servers (after the unit reboots). Tap "Done" in the upper right hand corner of the screen. If you had previously turned IPv6 off via "link only local"' we will need to fix that to restore IPv6 functionality via Google servers. If you did not make this change, tap "Done" at every screen you see and the unit will reboot and your changes will take effect. If you did make the link only local change, tap "Advanced", "IPv6", "Configure IPv6" and change this from "link-only local" to "Automatically". "IPv6 mode" should be "Native". "Share IPv6 Connection" should be on. "Block incoming IPv6" should be on. Keep tapping "Done" at every screen to save your changes and reboot. Once rebooted, you should be able to go back to the screen where the DNS settings are and see that they are now pointing to Googles servers. At this point, power off both the cable modem and AirPort for about two minutes. Power the modem back on first and let it boot. This could take a minute or two. Then power up the AirPort. Once everything is back up and running, go back into AirPort Utility. We are going to check that you have a functioning IPv6 connection. Tap on your AirPorts icon. Tap "Edit" in the upper right hand corner of the screen. Tap "Advanced" then "IPv6". You should see an IPv6 WAN address and an IPv6 Delegated Prefix assigned. Now open up Safari and go to www.test-IPv6.com. This site will test the state of your connections' IPv6 readiness. You should now have a working IPv6 connection. I would ask that some of you try this out and report back to the group as to whether it is working for you. For some, these changes may seem a bit intimidating. But, there's nothing here that can't be undone with a hard reset of the AirPort (the tiny button on the back that you have to press in with a paper clip for 10 seconds). This would completely reset the AirPort to factory defaults like it was when you first unboxed it when it was new. Best of luck everyone. Hope this helps.

I have experienced the same problem for about the same time-frame as this post has been running. Very frustrating and my wife can't understand why this hasn't been resolve. Whether it's Cox's fault or Apple's fault, I don't care. I just want my internet to work uninterrupted. I hope Cox and Apple can get this resolved soon as this post is over 6 months old. I also noticed that some folks have had problems with other routers other than Apple so it's obviously not just a Cox/Apple problem. I have tried the latest suggestion of going through Google. We'll see what happens!