3 ms·

This go-to argument for why we must all start using IPv6 doesn't fly, at least for me. We ran out of IPv4 some time ago, and yet, here we still are.

by ghusto 3y ago

orangeboats 3y ago
It depends on what you're doing. I am using IPv6 in my home network because I simply couldn't host anything on my CGNATed IPv4 connectivity. Working around this CGNAT either costed money and/or required people to install additional client on their machine to holepunch through the CGNAT, which wasn't ideal since all I wanted was to host a simple blog. Guess why people are being forced to move to CGNAT? Precisely because we have run out of addresses. The dismissal attitude of HN towards IPv6 ("we ran out of IPv4 and everything still works!") will always baffle me. Because things are _failing_ to work.
throw0101c 3y ago
> We ran out of IPv4 some time ago, and yet, here we still are. Yup. Spending money CG-NAT gear: > I work for a Native American tribe in the PNW. We scrambled to get the reservation reliable internet in the later part of 2019. We managed to cover most of the reservation with wi-max and wifi with a fiber back haul configuration. We are now slowly getting more stable and reliable fiber to the home(FttH) service installed to as many homes as we can, but it is slow process covering the mostly rural landscape doing all the work in house. > Our 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-2022-and-still-no-IPv6/m-p/854673/highlight/true#M35732 https://community.roku.com/t5/Features-settings-updates/It-s... * https://news.ycombinator.com/item?id=35047624 https://news.ycombinator.com/item?id=35047624 IPv4-only products and services is a problem right now.

This go-to argument for why we must all start using IPv6 doesn't fly, at least for me. We ran out of IPv4 some time ago, and yet, here we still are.

by ghusto 3y ago

This go-to argument for why we must all start using IPv6 doesn't fly, at least for me. We ran out of IPv4 some time ago, and yet, here we still are.

orangeboats 3y ago

It depends on what you're doing. I am using IPv6 in my home network because I simply couldn't host anything on my CGNATed IPv4 connectivity. Working around this CGNAT either costed money and/or required people to install additional client on their machine to holepunch through the CGNAT, which wasn't ideal since all I wanted was to host a simple blog. Guess why people are being forced to move to CGNAT? Precisely because we have run out of addresses. The dismissal attitude of HN towards IPv6 ("we ran out of IPv4 and everything still works!") will always baffle me. Because things are _failing_ to work.

throw0101c 3y ago

> We ran out of IPv4 some time ago, and yet, here we still are. Yup. Spending money CG-NAT gear: > I work for a Native American tribe in the PNW. We scrambled to get the reservation reliable internet in the later part of 2019. We managed to cover most of the reservation with wi-max and wifi with a fiber back haul configuration. We are now slowly getting more stable and reliable fiber to the home(FttH) service installed to as many homes as we can, but it is slow process covering the mostly rural landscape doing all the work in house. > Our 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-2022-and-still-no-IPv6/m-p/854673/highlight/true#M35732 https://community.roku.com/t5/Features-settings-updates/It-s... * https://news.ycombinator.com/item?id=35047624 https://news.ycombinator.com/item?id=35047624 IPv4-only products and services is a problem right now.