Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I just updated my system, and in terms of ip v6 - with Comcast - everything seems to be working on http://ipv6test.google.com/ .

AirPrint printers come up much faster, and all of the printers on the network show up immediately like I originally expected them to. Before the update, only the printer that was connected to the access point I was connected to (main or extended) would show up.

AirPlay devices show up all at the same time and quickly rather than slowly populating the list.

My NAS seems like it's working just fine. I've never timed my connections, so I can't say it's faster, but initial connection/authentication does seem a bit faster. My Time Machine backup is going smoothly. (WD MyCloud EX2)

HomeKit seems unaffected, but I've never had a problem with HomeKit.
Would you mind sharing your ip6 settings on your AE.

Thanks
 
I hope it fixes an issue I was having when I used an airport extreme to extend the wireless network from my time capsule. Both A.C. versions, but the AE was causing conflicts and drops, so I had to stop using it. It's just sitting in a drawer, one month old and I can't return it...
 
I saw that, and I assumed one of the ports is needed to connect the router to the cable modem, so that leaves me with a single port, which for 199 dollars is totally inadequate.

Yeah, I don't like that either, but at least a switch can be connected. Having one port actually seems like something Apple would do, not Google.
 
Ran the update and got an error....lovely.
Nice,
I'm holding off, for this very reason - good luck :(

Yeah, I don't like that either, but at least a switch can be connected. Having one port actually seems like something Apple would do, not Google.
Yeah, which kind of flies in the face of having a simple device. I like the idea of having a lot of attennas.
 
Indeed it seems there's something wrong with the iOS Airport Utility app. At first it asked me for my Airport Time Capsule password (for the first time ever), then it didn't let me enter anyway although the password was in my keychain: it just sat there. I also tried to insert the password manually and to remove/reinstall the app, but still no luck.

Then I decided to update the firmware via El Capitan and everything went flawlessly. BUT I'm still unable to edit anything via the iOS app, even after a factory reset. Geez.

EDIT: in the end I managed to access my iOS Airport Utility profile. After removing and reinstalling the iOS app, I inserted the password manually asking to save it (although it was in my keychain already) and this did the trick.
 
Last edited:
Indeed it seems there's something wrong with the iOS Airport Utility app. At first it asked me for my Airport Time Capsule password (for the first time ever), then it didn't let me enter anyway although the password was in my keychain: it just sat there. I also tried to insert the password manually and to remove/reinstall the app, but still no luck.

Then I decided to update the firmware via El Capitan and everything went flawlessly. BUT I'm still unable to edit anything via the iOS app, even after a factory reset. Geez.

I had just the opposite experience.....nothing I did in the El Cap Airport Utility would get the updates to show up for my Extreme (ac version) or Express (newer version). I finally tried the iOS app on my phone and both showed up as needing updates and updated both that way.
 
I'm running Cox internet with SB6183 and Airport Time Capsule 802.11ac with IPv6 configured as "automatically"... test-ipv6.com reports 10/10 and ipv6-test.com reports 19/20.

I had switched mine from auto to local link only about 3 months ago. I wonder if I should switch back to auto after updating and see if my wifi network stays solid again.
 
I had switched mine from auto to local link only about 3 months ago. I wonder if I should switch back to auto after updating and see if my wifi network stays solid again.

Update to 7.7.7 on my AE (6G) + Cox + SB6190, and IPv6 is finally working for me with (seemingly) no stack/fallback traffic issues (I previously had the same problem as others with the IPv6 obfuscating all IPv4 traffic)...

Now, lets see if it stays stable... :eek:
 
I forgot about that, I wonder how it holds up against other routers and does it scan the packets to help deliver "targeted advertisements" ?

They claim not to according to their documentation (link below). They do collect all kinds of diagnostic info by default, but appear to offer an opt-out. The worst part in my opinion is there appears to be no way to manually control how the thing gets updated firmware. It just updates on its own whenever it wants. No thanks.

https://support.google.com/onhub/answer/6279845
 
I've known lots of people who think that they're real networking experts. Sacked a few of them.
The number of them that I would trust to change any configuration on a router, that you cannot change on an airport, I would trust on the fingers of one foot.
Yep, been there. But SNMP is not only about configuration, its also about monitoring for problems.
 
All this talk about IPv6 got me to play around with it to get it working. Now that I have done so, I'm not sure what the benefit is.

I thought one benefit would be getting away from having to implement NAT on my TC, to directly access certain Macs from outside my home network. But actually since the IPv6 addresses are dynamic, it doesn't solve that problem at all. So IPv6 just eliminated the solution (NAT) without eliminating the problem (dynamic PIs). (What I mean is that now with IPv6, the IP addresses of my individual devices are dynamic; before, only my router had a dynamic IP, which hardly ever changed. The IPv6 IP for a Mac changed during the short time while I was playing with this.)

At the end of the day, I only need one IP address, which the router has. The world is blind to everything else behind that IP. Even if my fridge, toaster, or whatever did want to access the internet, it could do so through that one IPv4 address.

I could turn it off for the clients, or turn it off completely, including the TC. So why bother with IPv6 at all?
 
Last edited:
  • Like
Reactions: tennisproha
After waiting almost three years for an update - whats the hurry to implement? The good news is that I haven't encountered ANY critical communication issues - so I am content to wait while other brave souls upgrade.
 
  • Like
Reactions: 2013.1
Updated this morning and got "firmware update failed" error message and no internet access. Couldn't see the Airport Extreme. Invited me to forget it. I declined. Unplugged AE and replugged in AE, connected to internet via iPhone hotspot to start troubleshooting, and happily the AE came back online saying it is updated to 7.7.7. All is well now but had a few choice curse words in the interim moments.
 
But actually since the IPv6 addresses are dynamic, it doesn't solve that problem at all. So IPv6 just eliminated the solution (NAT) without eliminating the problem (dynamic IPs).
If I understand correctly, then that's not an IPv6 problem per se. Your ISP "should" be issuing you a static prefix, which is then combined with each device's static MAC address to give each device a static IPv6 address. It sounds like in your case that isn't happening, but I don't have it all working correctly yet so can't say whether mine's any better! :)

I do at least have a static prefix in the documentation supplied by my ISP, but as noted in my earlier post the AirPort is plucking a different address out of thin air.
 
If I understand correctly, then that's not an IPv6 problem per se. Your ISP "should" be issuing you a static prefix, which is then combined with each device's static MAC address to give each device a static IPv6 address. It sounds like in your case that isn't happening, but I don't have it all working correctly yet so can't say whether mine's any better! :)

I do at least have a static prefix in the documentation supplied by my ISP, but as noted in my earlier post the AirPort is plucking a different address out of thin air.

Yeah, the IPv6 IP address for one of my Macs changed while I was playing with this. I discovered that because I configured ARD using the IPv6 address, and a little while later tried to connect again and was not unable to; the IPv6 IP address changed.
 
FWIW... Just finished updating 8 AP Express units, 3 AP Extremes, and 1 AP Time Capsule; The firmware upgrade took about 45 min for all twelve devices without any problems at all. I did one device at a time, not starting the next until the current device fully restarted. (Not sure if that was necessary.)
 
  • Like
Reactions: S.B.G
Indeed it seems there's something wrong with the iOS Airport Utility app. At first it asked me for my Airport Time Capsule password (for the first time ever), then it didn't let me enter anyway although the password was in my keychain: it just sat there. I also tried to insert the password manually and to remove/reinstall the app, but still no luck.

Then I decided to update the firmware via El Capitan and everything went flawlessly. BUT I'm still unable to edit anything via the iOS app, even after a factory reset. Geez.

EDIT: in the end I managed to access my iOS Airport Utility profile. After removing and reinstalling the iOS app, I inserted the password manually asking to save it (although it was in my keychain already) and this did the trick.
How did you get it to remember your password? I am running version 1.3.4 (134.22).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.