News for hackers. Stuff that matters.
Re:Support for IPv6 by throw0101a on Friday September 20, 2024 @07:53AM (#41601097)
> NAT registers in the microseconds for packet processing time, that isn’t even comparable to Internet path jitter.

NAT, at scale, can get expensive:

> Our [American Indian] tribal network started out IPv6, but soon learned we had to somehow support IPv4 only traffic. It took almost 11 months in order to get a small amount of IPv4 addresses allocated for this use. In fact there were only enough addresses to cover maybe 1% of population. So we were forced to create a very expensive proxy/translation server in order to support this traffic.

> We learned a very expensive lesson. 71% of the IPv4 traffic we were supporting was from ROKU devices. 9% coming from DishNetwork & DirectTV satellite tuners, 11% from HomeSecurity cameras and systems, and remaining 9% we replaced extremely outdated Point of Sale(POS) equipment. So we cut ROKU some slack three years ago by spending a little over $300k just to support their devices.

* https://community.roku.com/t5/Features-settings-updates/It-s...

* Discussion: https://news.ycombinator.com/item?id=35047624

Re:Support for IPv6 by commandersaki on Friday September 20, 2024 @07:22PM (#41606328)
Okay, but back to the original question, how does this affect latency or bandwidth?
Re:Support for IPv6 by throw0101a on Monday September 23, 2024 @09:11AM (#41625690)
> Okay, but back to the original question, how does this affect latency or bandwidth?

The CG-NAT gear takes time to process the request and has a finite bandwidth.

Re:Support for IPv6 by commandersaki on Wednesday September 25, 2024 @03:41AM (#41644762)
Does this present a latency or bandwidth bottleneck?