Apple and IPv6 – Happy Eyeballs | Hacker News Reader

Apple and IPv6 – Happy Eyeballs

ietf.org

162 pointsjasonmp8540 comments

If you're wondering what Happy Eyeballs is: https://en.wikipedia.org/wiki/Happy_Eyeballs

I thought (before reading) it had something to do with the X11 xeyes program.

Apple has done amazing things for IPv6 on the client side; first defaulting to IPv6 for link-local traffic, and then being an early adopter of Happy Eyeballs and putting relatively good IPv6 support in their AirPorts.

Many brownie points!

Interesting, now I am not even sure how much credibility can be given to the networking engineers from Apple: we're in 2015 and I still need to manually tune the TCP stack of my mac to get decent download speeds!

What tuning parameters are you using and where are you making those changes?

net.inet.tcp.win_scale_factor=8 net.inet.tcp.autorcvbufmax=16777216 net.inet.tcp.autosndbufmax=16777216

Am I reading way too far into David's "CoreOS Networking Engineer" title?

Apple has had a CoreOS group for a very long time. Here's a post from 2008 that mentions it: http://lists.freebsd.org/pipermail/freebsd-jobs/2008-October...

Ah got it thanks for clearing that up.

It's had a Core OS group, not a CoreOS group.

They are interchangeable. It doesn't mean what you're implying.

Source: Former Apple employee who has been involved in multiple "which CoreOS?" conversations.

Exactly. It is Core OS, not CoreOS and it doesn't mean what they think it means. But's that's as much you're going to hear from someone that's actually from inside Apple.

Yep, core os technologies would be the way to read it.

Almost any technology low in Apple's stack is called 'Core ...'. A quick search at developer.apple.com yields Core Animation, Core Video, Core Text, Core Graphics, Core Image, Core Data, JavaScriptCore, WebCore, Core Audio, Core Bluetooth, Core Foundation, and Core Media Framework.

That convention started with Mac OS X, when they had to somehow unite the low-level technologies of classic Mac OS and NextStep.

previously they'd call their stuff OpenSomething... OpenDoc, OpenTransport etc.

It would be hard to be worse. If I turn on too much of IPV6 on OSX DNS takes forever (yes I did check the IPV6 config).

Can you file a radar for that with the specific things that are causing the slowdown? Radars are always appreciated.

Slow DNS with some configs that involve IPv6 is a known issue on OSX :(

I finally pulled IPv6 resolvers out of my config for this very reason. I was getting 4+ second lookups against both Comcast and Google v6 resolvers even though direct v6 sockets worked instantly; made worse because HSTS apparently makes Chrome put "establishing secure connection" in the status bar while resolving (maybe?), so I ended up down a rabbit hole of identifying reasons for phantom TLS stalls. Finally cut down to just v4 resolvers and it's a brand new computer.

Glad to know it's not just me.

That is pretty much what I saw. I was somewhat worried if it was the AT&T modem config or OSX, but nothing I tried fixed it (including explicitly setting DNS sources and so on).

Sure, pay me my consulting rate to run it down and fill out the forms.

Reply on news.ycombinator.com