AWS to begin charging for public IPv4 addresses

Post by 0cf8612b2e1e » Thu, Aug 03, 2023, 9:21 PM UTC

candiddevmike wrote: post #77

wongarsu wrote: post #51

This finally puts real pressure on software and services to work on IPv6 only. I wouldn't be surprised if within 1-2 release cycles lots of distributions suddenly update just fine with just IPv6, package mangers can download packages over IPv6, lots of APIs gain solid and well-tested IPv6 support, etc.

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

Post by lokar » Thu, Aug 03, 2023, 9:25 PM UTC

toast0 wrote: post #38

rblatz wrote: post #25

Earlier quoted context omitted.

At $45 a year per IP address you’d have to spend less than a man hour per address to even conceivably approach break even. And I normally would be worried if my company was focusing on break even initiatives instead of higher impact ones.

Depends how many IPs you're using. If you're using 10, who cares; if you're using 100, I dunno. If it's 1,000 or more, that's real money you probably shouldn't be pissing away. (OTOH, a lot of cloud spend is pissing away money, so what's another $45k/year)

Post by est31 » Thu, Aug 03, 2023, 9:34 PM UTC

blibble wrote: post #80

psanford wrote: post #64

Earlier quoted context omitted.

aws is many things but 'incompetent' is not one of them.

explain that page any other way

Post by p1mrx » Thu, Aug 03, 2023, 9:37 PM UTC

blibble wrote: post #89

xxpor wrote: post #82

Earlier quoted context omitted.

It's not really computationally expensive, it's memory expensive. You need per connection state.

it already has stateful firewall so that's: source ip, dest ip, protocol, source port, dest port, connection state (say 16 bytes total) doing NAT too is what, 3 more bytes per connection (8 bits for an offset into an IP table and 16 bits for the translated port)

Post by candiddevmike » Thu, Aug 03, 2023, 9:39 PM UTC

0cf8612b2e1e wrote: post #91

candiddevmike wrote: post #77

Earlier quoted context omitted.

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

Serious question, is there any enterprise gear made today which does not support IPv6? I have assumed that the natural hardware upgrade cycles made it so 99% of all active equipment could support the technology, even if it was not configured to do so.