Earlier quoted context omitted.
> WThe nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. No issues? So, how are people supposed to be able to access your machine then?
Via the mentioned public IPv6 address
AWS adds an extra 5.5M IPv4 addresses
91–100 of 283 posts
Re: AWS adds an extra 5.5M IPv4 addresses
#92Earlier quoted context omitted.
The funny thing is social media and streaming is already there: facebook.com has IPv6 address 2a03:2880:f119:8083:face:b00c:0:25de instagram.com has IPv6 address 2406:da00:ff00::23ae:4dc1 snapchat.com has IPv6 address 2001:4860:4802:36::15 netflix.com has IPv6 address 2600:1f14:62a:de82:822d:a423:9e4c:da8d youtube.com has IPv6 address 2404:6800:4006:810::200e The holdouts are somewhere else. Imagine if cloudflare and…
We do default IPv6 on. https://blog.cloudflare.com/always-on-ipv6/ And the chart in that blog shows the dent we made.
This guide doesn't even mention AAAA records: https://www.cloudflare.com/learning/dns/dns-records/
API examples are ipv4 unless the option takes ipv6 only: https://api.cloudflare.com/#dns-records-for-a-zone-update-dn...
Your terraform examples use ipv4 only: https://registry.terraform.io/providers/cloudflare/cloudflar... https://registry.terraform.io/providers/cloudflare/cloudflar...
And many others.
In other words, I expect steering people to do ipv6, then maybe ipv4 as well rather than the opposite would give the internet as a whole another big jump in ipv6 usage.
Re: AWS adds an extra 5.5M IPv4 addresses
#93Re: AWS adds an extra 5.5M IPv4 addresses
#94Earlier quoted context omitted.
The funny thing is social media and streaming is already there: facebook.com has IPv6 address 2a03:2880:f119:8083:face:b00c:0:25de instagram.com has IPv6 address 2406:da00:ff00::23ae:4dc1 snapchat.com has IPv6 address 2001:4860:4802:36::15 netflix.com has IPv6 address 2600:1f14:62a:de82:822d:a423:9e4c:da8d youtube.com has IPv6 address 2404:6800:4006:810::200e The holdouts are somewhere else. Imagine if cloudflare and…
We do default IPv6 on. https://blog.cloudflare.com/always-on-ipv6/ And the chart in that blog shows the dent we made.
Re: AWS adds an extra 5.5M IPv4 addresses
#95Last October, Amazon bought ~4 million addresses by bribing the corrupt technocrats of a radioamateur "non-profit" organization. Fuck Amazon, fuck those corrupt technocrats (like the ICANN/.org team who tried to sell the TLD). It's incredible what this kind of people can get away with. Previous discussion on HN: https://news.ycombinator.com/item?id=24753654
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
Reselling them to a for-profit company was definitely not what was intended by anyone and directly contradicts their mission as custodians. Those addresses were that of the global radioamateur community and no one else's.
That's why i made a comparison with .org. ORG TLD was created exclusively by and for non-profits, so it was a scandal when some execs conspired against the general public to resell it and induce more costs for everyone. Likewise, it's a scandal that when you need/want to build DIY radio Internet setup, your addresses which were reserved for that usage don't exist anymore, as they have been appropriated by Amazon.
Please note that this story would be less of a scandal if the community had been consulted on how much of the IP range to sell (retaining some for legit usage), and/or if that money benefited the community and not some greedy capitalist execs, and/or if they had been reattributed through normal channels (RIPE and other RIRs) and not commercialized, none of which is true.
Re: AWS adds an extra 5.5M IPv4 addresses
#96Earlier quoted context omitted.
The funny thing is social media and streaming is already there: facebook.com has IPv6 address 2a03:2880:f119:8083:face:b00c:0:25de instagram.com has IPv6 address 2406:da00:ff00::23ae:4dc1 snapchat.com has IPv6 address 2001:4860:4802:36::15 netflix.com has IPv6 address 2600:1f14:62a:de82:822d:a423:9e4c:da8d youtube.com has IPv6 address 2404:6800:4006:810::200e The holdouts are somewhere else. Imagine if cloudflare and…
We do default IPv6 on. https://blog.cloudflare.com/always-on-ipv6/ And the chart in that blog shows the dent we made.
Let’s take any sort of CDN out of the equation for simplicity. Can I use Cloudflare DNS for the service, such that anyone using ipv6 will connect directly to my service, of course— but can CF do some magic ipv4->ipv6 translation/bridge sort of thing, so that someone on ipv4-only will also be able to connect to my ipv6-only service?
I’d imagine the answer is hopefully yes and perhaps this is trivial stuff these days, but anyway I’m thinking of setting up a blog and might go ipv6 only with it..
Re: AWS adds an extra 5.5M IPv4 addresses
#97Earlier quoted context omitted.
I guess there's a large pool of IP addresses used by residential ISPs that could be recycled relatively easily. When I lived in Ireland I only got a public IPv6, my IPv4 was behind CG-NAT. The nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. I could see ISPs making a quick buck by switching to CG-NAT on IPv4 so they can sell off their IPv4 blocks. Those IPs being recycled for…
> WThe nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. No issues? So, how are people supposed to be able to access your machine then?
Re: AWS adds an extra 5.5M IPv4 addresses
#98Earlier quoted context omitted.
I guess there's a large pool of IP addresses used by residential ISPs that could be recycled relatively easily. When I lived in Ireland I only got a public IPv6, my IPv4 was behind CG-NAT. The nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. I could see ISPs making a quick buck by switching to CG-NAT on IPv4 so they can sell off their IPv4 blocks. Those IPs being recycled for…
Problem with CGNAT is the costs involved in bookkeeping for law enforcement. Where an IPv4 solution for your clients only needs change-logging on IPbinding-to-client level, the CG-NAT requires you as an ISP to log every outgoing IPv4/port combination with timestamp to client mapping. Which requires A LOT more storage and much more expensive equipment. Going rate per IPv4 is up to $40 nowadays, selling of your v4 bloc…
If cgnat keeps scaling, these ip Limiters need to phase out.
Re: AWS adds an extra 5.5M IPv4 addresses
#99Earlier quoted context omitted.
I think the question is why not sell them openly instead sell them via backgate..
I assume Amazon came to them and offered the money and they accepted. I don't see anything shady about that. How do you sell something "openly"? Via an auction website? Is that standard procedure for everything these people sell?
That people sell food and houses is disconcerting in the physical world and creates real problems for real people where some can't afford to eat or have a roof over their head despite a global abundance of resources. That people do the same in the virtual world, with literal numbers, is beyond the scope of comprehension: pure madness.
Re: AWS adds an extra 5.5M IPv4 addresses
#100Last October, Amazon bought ~4 million addresses by bribing the corrupt technocrats of a radioamateur "non-profit" organization. Fuck Amazon, fuck those corrupt technocrats (like the ICANN/.org team who tried to sell the TLD). It's incredible what this kind of people can get away with. Previous discussion on HN: https://news.ycombinator.com/item?id=24753654
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.