GABarber

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

Close

Q: Airport Extreme and Cox Internet IPv6 Problem

  • All replies
  • Helpful answers

first Previous Page 21 of 32 last Next
  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 8:35 AM in response to YatBob
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 8:35 AM in response to YatBob

    So YatBob, just to be clear.

     

    Before running the ping6 and traceroute6 tests you where failing the IPv6 tests on the test sites but after running ping6 and traceroute6 you were passing the IPv6 test on the test site?

     

    If that is correct that is an interesting result.

     

    Both the ping6 and traceroute6 test I had you run queried the ipv6.google.com domain name. Before the tests could run they needed to be able to resolve the ipv6.google.com domain name to its IPv6 address. This shows that the Cox DNS server(s) is resolving the IPv6 address.

     

    What I find particularly interesting though is that after running the ping6 and traceroute6 tests your were also passing the IPv6 tests on the test sites again. So I'm wondering if the Cox DNS server(s) are having some temporary problem that ping6 and traceroute6 tests is temporarily fixing.

  • by starhopper,

    starhopper starhopper Jun 5, 2016 8:36 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Jun 5, 2016 8:36 AM in response to Gino_Cerullo

    Got a 7/10 on that other link you suggested - here are the results

    Test with IPv4 DNS record  

    ok (0.220s) using ipv4

     

    Test with IPv6 DNS record  

    ok (2.219s) using ipv6 Teredo

     

    Test with Dual Stack DNS record  

    ok (0.260s) using ipv4

     

    Test for Dual Stack DNS and large packet  

    ok (0.154s) using ipv4

     

    Test IPv4 without DNS  

    ok (0.173s) using ipv4

     

    Test IPv6 without DNS  

    ok (2.159s) using ipv6 Teredo

     

    Test IPv6 large packet  

    ok (2.446s) using ipv6 Teredo

     

    Test if your ISP's DNS server uses IPv6  

    ok (0.335s) using ipv4

     

    Find IPv4 Service Provider  

    ok (0.380s) using ipv4 ASN 22773

     

    Find IPv6 Service Provider  

    ok (2.236s) using ipv6 Teredo

  • by sunjon,

    sunjon sunjon Jun 5, 2016 8:48 AM in response to starhopper
    Level 1 (9 points)
    Notebooks
    Jun 5, 2016 8:48 AM in response to starhopper

    Starhopper,  when you reset your AE router to Automatic IPv6, did you also reset it to Native IPv6 mode?  Teredo appears to be an option for tunneling IPv6 through IPv4 connection.

     

    Screen Shot 2016-06-05 at 11.33.08 AM.png

  • by YatBob,

    YatBob YatBob Jun 5, 2016 8:41 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Jun 5, 2016 8:41 AM in response to Gino_Cerullo

    That is correct I was failing the ipv6 test and after running the ping  and trace route test I passed the ipv6 test without any resets. When I fail the test later on today I will run the terminal tests separately and see which one restores the ipv6 test passing

  • by starhopper,

    starhopper starhopper Jun 5, 2016 8:42 AM in response to sunjon
    Level 1 (9 points)
    Jun 5, 2016 8:42 AM in response to sunjon

    Yes - it's set to automatic IPv6 mode, and Native IPv6 mode.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 8:43 AM in response to starhopper
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 8:43 AM in response to starhopper

    Sorry star hopper, I missed something in your post above. You wrote, ""Type" of ipv6 server is "Toredo" if that means anything to you." If that is correct then your IPv6 setting are not correct.

     

    Screen Shot 2016-06-05 at 11.37.28 AM.png

     

    Make sure the settings on your AirPort router are set correctly.


    IPv6_setting.jpg

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 8:48 AM in response to starhopper
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 8:48 AM in response to starhopper

    starhopper, also,

     

    IPv6_setting3.jpg

  • by starhopper,

    starhopper starhopper Jun 5, 2016 8:50 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Jun 5, 2016 8:50 AM in response to Gino_Cerullo

    Wow - thanks.  I just found that "Share IPv6 Connection" button was in the off position!  I turned it "on", did a reset, and now I'm scoring 18/20 and no longer getting that "Toredo" type!

     

    PS - I don't want to "block incoming IPv6 connections" do I?  I have that option deselected

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 8:52 AM in response to starhopper
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 8:52 AM in response to starhopper

    starhopper, that's better but let's see if we can get it to 19/20. You will always fail the Hostname test, that is normal. What is the other test that is failing?

  • by starhopper,

    starhopper starhopper Jun 5, 2016 8:57 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Jun 5, 2016 8:57 AM in response to Gino_Cerullo

    Not failing any other test. That being said, when I do the test using Microsoft "Edge" as my browser, I get the 18/20.  BUT, when I use "Chrome" or "FIREFOX" browser, I get 19/20

  • by OCRamón,

    OCRamón OCRamón Jun 5, 2016 8:59 AM in response to YatBob
    Level 1 (4 points)
    Jun 5, 2016 8:59 AM in response to YatBob

    FWIW, my test results (when ipv6 is working) look similar to yours.

     

    ping6 -c 10 ipv6.google.com

    PING6(56=40+8+8 bytes) 2600:8802:4100:d9:954b:1cd6:4db:9ff6 --> 2607:f8b0:4000:801::200e

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=0 hlim=56 time=48.217 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=1 hlim=56 time=47.288 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=2 hlim=56 time=47.600 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=3 hlim=56 time=48.678 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=4 hlim=56 time=48.288 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=5 hlim=56 time=48.400 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=6 hlim=56 time=48.383 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=7 hlim=56 time=48.032 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=8 hlim=56 time=48.395 ms

    16 bytes from 2607:f8b0:4000:801::200e, icmp_seq=9 hlim=56 time=49.544 ms

     

    --- ipv6.l.google.com ping6 statistics ---

    10 packets transmitted, 10 packets received, 0.0% packet loss

    round-trip min/avg/max/std-dev = 47.288/48.282/49.544/0.575 ms

     

    traceroute6 ipv6.google.com

    traceroute6 to ipv6.l.google.com (2607:f8b0:4000:801::200e) from 2600:8802:4100:d9:954b:1cd6:4db:9ff6, 64 hops max, 12 byte packets

    1  2600:8802:4100:d9:8a1f:a1ff:fe2a:5d51  1.083 ms  1.082 ms  1.338 ms

    2  2600:8802:41ff:ffff::1111  11.068 ms  10.240 ms  7.806 ms

    3  2001:578:400:fff0:5000::70  10.650 ms  11.795 ms  10.342 ms

    4  2001:578:400:fff0::2c  10.396 ms  8.923 ms  10.449 ms

    5  2001:578:1::172:17:249:33  20.998 ms  11.252 ms  15.963 ms

    6  2001:4860:1:1:0:58f5::  11.622 ms  12.239 ms  11.762 ms

    7  2001:4860::1:0:c432  11.567 ms  13.619 ms  14.372 ms

    8  2001:4860::8:0:7a1a  11.630 ms  11.462 ms  11.739 ms

    9  2001:4860::8:0:2c9d  45.853 ms  47.468 ms

        2001:4860::8:0:64bf  48.505 ms

    10  2001:4860::1:0:bf0c  48.998 ms  48.718 ms  48.460 ms

    11  2001:4860:0:1::15d9  51.120 ms  47.112 ms  49.813 ms

    12  dfw25s08-in-x0e.1e100.net  47.440 ms  47.832 ms  47.212 ms

     

    My ping times seem quite long compared to ipv4 (I'm in OC, CA), and traceroute6 took several minutes to run.  I will try this again after the next ipv6 failure.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 9:00 AM in response to starhopper
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 9:00 AM in response to starhopper

    starhopper, gotcha, good enough. We'll chock it up to Edge still needing work.

     

    If you don't mind running those IPv6 tests once a day over the next few days to see if the IPv6 connectivity stays up that will help the Cox engineer.

     

    If it goes down, before re-starting the router or modem, if you wouldn't mind running the ping6 and traceroute6 tests I posted earlier and posting the results that would help also. I don't know how to run them on Windows so you may need to look that up.

  • by starhopper,

    starhopper starhopper Jun 5, 2016 9:02 AM in response to Gino_Cerullo
    Level 1 (9 points)
    Jun 5, 2016 9:02 AM in response to Gino_Cerullo

    Will do!  But, as I said in an earlier post - haven't had to do a reset since the 7.7.7 upgrade (knock on wood!)

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 9:03 AM in response to OCRamón
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 9:03 AM in response to OCRamón

    OCRamón, if your IPv6 connectivity goes down, i.e., fails the tests on the IPv6 test pages, http://ipv6-test.com/ and/or http://test-ipv6.com/ can you run the ping6 and traceroute6 tests again before re-starting your router and/or modem and paste up the results.

  • by Gino_Cerullo,

    Gino_Cerullo Gino_Cerullo Jun 5, 2016 9:06 AM in response to starhopper
    Level 3 (567 points)
    Apple TV
    Jun 5, 2016 9:06 AM in response to starhopper

    starhopper, that was before when your connection was running through a Teredo tunnel. Let's see if it still stays up. Hopefully it will.

first Previous Page 21 of 32 last Next