News for hackers. Stuff that matters.

A comment on iOS Supporting IPv6-Only Networks. Parent comment

Re:iOS Supporting IPv6-Only Networks by djrogers on Thursday May 05, 2016 @11:09AM (#11636752)
> This is called DNS64/NAT64 and has some small performance penalty.

While there may be some implementations that have a small performance penalty, certainly not all of them do. The NAT can be done in FPGA or ASIC, and there's not any difficult work being done to translate the DNS response.

* I've been installing NAT64 networks for several years

[ Parent | on HN ]
Re:iOS Supporting IPv6-Only Networks by X-Istence on Thursday May 05, 2016 @12:24PM (#11637480)
The performance penalty is that now my packets travel:

Phone -> T-Mobile -> NAT -> T-Mobile -> Internet -> My hosting provider

Whereas with IPv6:

Phone -> T-Mobile -> Internet -> My hosting provider

That NAT is an extra step, and will add a small amount of latency.

[ Parent | on HN ]
Re:iOS Supporting IPv6-Only Networks by Dylan16807 on Thursday May 05, 2016 @12:58PM (#11637795)
The NAT, if set up right, would not cause the packets to take a different route.

Changing the packet format requires nanoseconds, no more than normal packet processing.

It's possible to set up anything wrong, but there's nothing about this technology that would introduce latency when done correctly.

[ Parent | on HN ]
Re:iOS Supporting IPv6-Only Networks by djrogers on Thursday May 05, 2016 @03:25PM (#11639009)
That NAT in many cases happens on the same edge router that'd be dropping your packets off on the internet anyway, so it doesn't have to add an extra hop.
[ Parent | on HN ]