Hacker News new | past | comments | ask | show | jobs | submit login

I don't pay the NAT tax.

I just use public IP addresses.

It's fine, it works. Worked for EC2-Classic, works today.




You now get charged for ipv4 addresses as well. Less than nat, yes, but now ipv4 addresses are no longer free either.


So upgrade to IPv6.


Except that way many many AWS services can't do ipv6.


And since AWS/Amazon gets more money by not supporting IPv6 everywhere, why would they enable it?


and if you want to connect to anything ipv4-only like, say GitHub, then what?


How is GitHub still IPv4 only? Ridiculous.



Tbh this site is pretty misleading. Fastly and Cloudflare support ipv6 pretty well in their productы, it’s just that their marketing team apparently don’t care


> Tbh this site is pretty misleading

The website is pretty explicit about that it's testing if a domain/website is available over IPv6 vs IPv4. Clicking on a website also sends you to https://ipv6.fail/domain/cloudflare.net/ where it's even more explicit what they're testing against. Wouldn't call it misleading exactly.


They're not the only ones either. OpenAI also doesn't have ipv6 APIs, and neither does Stripe, many many others....


Or, y'know.... 89% of AWS own services: https://awsipv6.neveragain.de/


Use a nat64 gateway (a list is at https://nat64.xyz).


Just bolting on thing after thing to make it sort of work, maybe, sometimes.

I'll be sticking with ipv4.


IPv6 NAT is "bolting on thing after thing" but IPv4 NAT is good architecture :P


You do realize you also need dns64 for this to work right? So in fact your proposed architecture is strictly worse


It doesn't take much effort to setup DNS64 though.

Source: I have used NAT64 myself before.


Not something i would use in prod and also needs dns64




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: