GABarber
Level 1 (12 points)
Notebooks

Q: 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:07 PM

by babysus,Apple recommended
babysus babysus
Level 1 (12 points)
A:

GABarber,

 

I too had a similar problem.  Prior Cox Communications service in Phoenix AZ was terminated, and recently reinstated yesterday (Mar. 1st) afternoon.  After the technician left, the wi-fi failed to produce a valid connection, citing DNS error and no response from server.  We have a new CISCO modem, ethernet cable to a 2TB Air Port/Time Capsule.

 

After speaking with Tier 1 and then Tier 2 Cox support, there was adequate evidence for a valid signal through the modem, but the Air Port was not picking it up or broadcasting it (per Cox).  Checking my Air Port Utility apps on iMac and iPhone would demonstrate occasional Internet or Air Port signal, but never both together.  The modem and Air Port both would demonstrate appropriate green indicator lights, but to no avail to working wi-fi.

 

The only thing thus far that has worked is your solution listed above: Air Port Utility > Internet > Internet Options > Configure Ipv6 : Link-Local Only.

 

Thank you, GABarber.

Posted on Mar 2, 2016 10:08 PM

Close
GABarber

Q: Airport Extreme and Cox Internet IPv6 Problem

  • All replies
  • Helpful answers

first Previous Page 6 of 32 last Next

  • by dwmreg64,

    dwmreg64 dwmreg64 Apr 20, 2016 5:45 AM in response to GABarber
    Level 1 (38 points)
    Mac OS X
    Apr 20, 2016 5:45 AM in response to GABarber

    Has anyone considered replacing their Apple Airport equipment with something completely different? I'm seriously considering it since setting the link-only settings has not helped me at all. Consistently dropping, etc. I have an open ticket with Apple support and engineering is engaged. I'd assume we'll see a firmware update soon, but I need to do something now to fix my sanity and to be able to work productively.

     

    The problem is picking something to replace that I have now. A Time Capsule and an Airport Extreme.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 20, 2016 5:56 AM in response to dwmreg64
    Level 3 (567 points)
    Apple TV
    Apr 20, 2016 5:56 AM in response to dwmreg64

    dwmreg64, the problem with that is that you may be spending money to replace perfectly good Apple routers with another brand and not solving your problem. This problem appears to be isolated to Cox's implementation of IPv6. Apple's AirPort routers work perfectly fine with every other ISP's implementation of IPv6. If you visit the Cox forums at DSLReports.com you will find that people are having problems with other routers as well.

     

    Have you tried the remedy I posted that merely requires you to change the DNS settings to those of Google's Public DNS?

  • by dwmreg64,

    dwmreg64 dwmreg64 Apr 20, 2016 5:11 PM in response to Gino_Cerullo
    Level 1 (38 points)
    Mac OS X
    Apr 20, 2016 5:11 PM in response to Gino_Cerullo

    I'll try that on my Time Capsule connected to the cable modem, but the next question would be - what about devices like my Airport Extreme that I'm using to extend the network. Right now IPV6 on it is link-local only and the DNS is preset - to the TC's ip address. Probably leave the AE alone.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 20, 2016 5:25 PM in response to dwmreg64
    Level 3 (567 points)
    Apple TV
    Apr 20, 2016 5:25 PM in response to dwmreg64

    AirPort routers that are in bridged mode that are extending a wired or wireless Airport network should be set to Automatic and Native mode for IPv6 as well. That is so that they can continue to do their job of bridging and extending the network using the IPv6 protocol in addition to IPv4. If they are set to DHCP they will pull all the info they need from the main router so you do not need to add separate DNS settings to them. If they are setup using a Static IPv4 address then you will also need to add the DNS setting for both IPv4 and IPv6 as well.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 20, 2016 6:43 PM in response to dwmreg64
    Level 3 (567 points)
    Apple TV
    Apr 20, 2016 6:43 PM in response to dwmreg64

    One other thing!

     

    Screen Shot 2016-04-20 at 9.34.23 PM copy.png

  • by CQ92651,

    CQ92651 CQ92651 Apr 21, 2016 8:31 AM in response to GABarber
    Level 1 (4 points)
    Apr 21, 2016 8:31 AM 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.

     

    UPDATE: I took a break from this thread while waiting to see if the Google DNS switch solved my problems. (Gino Cerillo's illustrations would have made it even less stressful. If he is Level 1, I am Level -10.)  I have not had the problem since. I did notice it turned IPv6 back on and (subjectively) it feels like I regained the speed I had lost. Hopefully a happy ending until Cox gets its act together. (Experience has convinced me that blaming Cox is a safe bet.)

  • by YatBob,

    YatBob YatBob Apr 21, 2016 9:53 AM in response to CQ92651
    Level 1 (9 points)
    Apr 21, 2016 9:53 AM in response to CQ92651

    I am trying these settings now, one question on the bridged Airport is it necessary to enter the DNS and iPv6 Servers numbers on the bridged device, or does just entering them on the main router suffice

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 21, 2016 10:10 AM in response to YatBob
    Level 3 (567 points)
    Apple TV
    Apr 21, 2016 10:10 AM in response to YatBob

    It depends on how the bridged AirPort router is set up.

     

    If it is set up to Connect Using: DHCP it will get its settings, including DNS, from the main router. (Preferred method)

     

    If it is set up to Connect Using: Static then you need to configure everything manually including: static IPv4 address, subnet mask, router address and DNS server address(es) for both IPv4 and IPv6.

     

    Screen Shot 2016-04-21 at 1.04.00 PM.png

  • by YatBob,

    YatBob YatBob Apr 21, 2016 10:19 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Apr 21, 2016 10:19 AM in response to Gino_Cerullo

    I'm set up using DHCP

     

    Thanks for the quick response, will provide feedback in a few days

  • by dwmreg64,

    dwmreg64 dwmreg64 Apr 21, 2016 10:46 AM in response to Gino_Cerullo
    Level 1 (38 points)
    Mac OS X
    Apr 21, 2016 10:46 AM in response to Gino_Cerullo

    Actually I see that it doesn't populate and the fields are either blank or greyed out when the network is extended and set to DHCP.

     

    Either way I'm trying this to see if there is a difference using the tips supplied here.

     

    I will say this - I've been engaged with Apple support and through them engineering for a few weeks now.

     

    According to what I know there is known problem, but they don't have a work around for it that they offer.

     

    They teased me with some beta firmware, but as of now Apple just left me hanging with the problem and a promise of a firmware update - some day. No time frame for the release. If they need additional test information I'd supply them with what they ask for.

     

    I'm on Xfinity/Comcast so I don't know if the problem Cox subscribers are having even applies to me. I find it odd that since IPV6 is a standard how could Cox screw it up????

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 21, 2016 10:52 AM in response to dwmreg64
    Level 3 (567 points)
    Apple TV
    Apr 21, 2016 10:52 AM in response to dwmreg64

    When set up using DHCP, if the fields are blank it is because there is nothing needed in those fields. If they are greyed out that means that the field has been filled-in for you but you can over-ride it by filling them in with your own info.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 21, 2016 10:54 AM in response to CQ92651
    Level 3 (567 points)
    Apple TV
    Apr 21, 2016 10:54 AM in response to CQ92651

    CQ92651 wrote:

     

    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.

     

    UPDATE: I took a break from this thread while waiting to see if the Google DNS switch solved my problems. (Gino Cerillo's illustrations would have made it even less stressful. If he is Level 1, I am Level -10.)  I have not had the problem since. I did notice it turned IPv6 back on and (subjectively) it feels like I regained the speed I had lost. Hopefully a happy ending until Cox gets its act together. (Experience has convinced me that blaming Cox is a safe bet.)

    Thanks CQ92651!

     

    FYI, I'm only a Level 1 because I changed the Apple ID I use for posting in the forums. I earned a Level 4 with my previous Apple ID.

  • by bobandapple,

    bobandapple bobandapple Apr 21, 2016 11:16 AM in response to CQ92651
    Level 1 (4 points)
    Apr 21, 2016 11:16 AM in response to CQ92651

    Thanks for the info re your success with the Google DNS settings. I experienced the same (or similar) problems with Cox IPV6, etc. as the other posters, and it got so bad that I was unplugging & replugging my Apple Time Capsule 3-5 times per day. Then, finally, even THAT didn't work anymore. So I called Apple and was coached by an Apple Support Rep named Doug (not sure what level he was) to try the Link-Local setting. It worked... whew! Now the only weird thing that happens is that every day in the afternoon my Time Capsule goes from steady green (peace, love, etc.) to flashing yellow (fear, loathing, etc.). However, I notice no reduction in speed... the internet service feel the same... whew again. Then, sometime every evening around 6pm, it goes back to green again. This pattern has continued pretty reliably for the past week or so. Now, while I would love to find a way to make it stay steady green, I'm an old-school believer in the "If it ain't broke (even it looks kinda broke)... don't mess with it."

     

    I'll try the Google DNS move if this craps out again (I live in Orange County, too...same as CQ92651!). Thanks for all who contribute and share their woes.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Apr 21, 2016 11:39 AM in response to bobandapple
    Level 3 (567 points)
    Apple TV
    Apr 21, 2016 11:39 AM in response to bobandapple

    Be aware that setting the router to link-local is not fixing the problem it is merely making it go away. It is essentially disabling IPv6. That should not be your goal. Your goal should be to get a functioning IPv6 network.

     

    The transition to a functional IPv6 network is essential to the continuation of functional Internet. We ran out of IPv4 addresses a while ago, it is only because of the work-around the is NAT that we have been able to continue the way we have. Now, NAT is no longer sufficient to address the problem of the shortage of IPv4 addresses.

     

    Cox is the only major ISP that I am aware of in North America who is having difficulty with the transition to IPv6. They should have done more testing before enabling this for their customers. I'm sure they'll eventually figure it out though.

  • by CQ92651,

    CQ92651 CQ92651 Apr 21, 2016 11:42 AM in response to GABarber
    Level 1 (4 points)
    Apr 21, 2016 11:42 AM in response to GABarber

    I may be asking a question that's already been answered, but is there any current or potential downside to using the Google servers, now or even after Cox gets its act together?

first Previous Page 6 of 32 last Next