ELI5, why are IPv4 addresses so precious?
Having something that's addressable on the internet is trivial when you have a public IPv4 address.
161–170 of 480 posts
ELI5, why are IPv4 addresses so precious?
Having something that's addressable on the internet is trivial when you have a public IPv4 address.
Earlier quoted context omitted.
you've /never/ heard anyone call ipv6 long, confusing, and complicated? I've basically /only/ heard people say that. This is probably because the idealized world of "only network engineers" is leaky. Programmers, sysadmins, people trying to get their network printer to work, non-specialists have to interface with network addresses constantly. Saying they shouldn't is not a description of reality. Not everyone who nee…
I've almost never heard anyone in the general population use ip addresses, with the notable exception of gamers, but that's fading away too now that all major games come with friends, parties and deep linking support I don't really understand the use case for typing up addresses either, copy pasting is going to be more precise, and if one can't read 8 quartet of letters one shouldn't be near networking equipment eith…
It's human and behavior driven and addressing that is a matter of packaging, process, promotion, product, presentation... all those marketing ps.
can I buy one ipv4 for myself somehow. not lease or rent, buy ?
can I buy one ipv4 for myself somehow. not lease or rent, buy ?
I also don't think there are many places willing to announce your ultra specific route because it's not great for routing tables.
Earlier quoted context omitted.
I don't run IPv6 on my home network. I try it about once a year, enabling it at the router (it's already enabled on my laptop). And then random stuff just doesn't work. Various websites hang, various widgets just don't load, etc. Then I turn it off and everything gets better again. I'be been too lazy to diagnose why exactly it doesn't work, I just figure it's easier to run with it off. At some point a website I reall…
> And then random stuff just doesn't work. Various websites hang, various widgets just don't load, etc. Then I turn it off and everything gets better again. Before I switched ISPs a few weeks ago to one without IPv6, I was with an ISP with IPv6 (dual-stack) for about five years and had zero problems. In fact it worked 'too well' initially: when I was still IPv4-only I had put a bunch of Facebook domains in my iMac's…
Still unsure of the benefit of dual stack, but there are numerous costs.
Can we go back in time and hit the designers of IPv6 upside the head? The decision not to make IPv6 backwards compatible, the belief that a beautiful new standard could magically replace something already so widespread... "Naive" is an inadequate word. We are still futzing with the transition 3 decades later, with no end in sight. Grrr, grumble...
"Please just try to fit more than 4 billion numbers into 4 bytes" -- this is mathematically impossible.
"Just extend the address size" -- this is an entirely new protocol by the definition of IPv4, which uses fixed-size addresses.
The reason for the slow IPv6 adoption is that there was no financial or business pressure. While IPv4 is ubiquitous, nobody individually feels a need to migrate to IPv6.
E.g.: How many customers would you gain by supporting IPv6? Generally zero. That doesn't sell well internally when the network team is asking for a budget.
The IPv6 transition will be like a bankruptcy: very slowly, slowly, then all of a sudden.
The sudden bit will happen when IPv4 address will cost $1K to $10K annually. At that point, customers will be reaching those IPv4 endpoints via three layers of proxies or NAT gateways, and IPv6 will be noticeably faster, more reliable, and free.
Can we go back in time and hit the designers of IPv6 upside the head? The decision not to make IPv6 backwards compatible, the belief that a beautiful new standard could magically replace something already so widespread... "Naive" is an inadequate word. We are still futzing with the transition 3 decades later, with no end in sight. Grrr, grumble...
These arguments always boil down to these two: "Please just try to fit more than 4 billion numbers into 4 bytes" -- this is mathematically impossible. "Just extend the address size" -- this is an entirely new protocol by the definition of IPv4, which uses fixed-size addresses. The reason for the slow IPv6 adoption is that there was no financial or business pressure. While IPv4 is ubiquitous, nobody individually feels…
Take USB for example. The capabilities of USB 3.1, 3.0, 2.0 is impossible to achieve for USB 1.0. So is high-speed charging.
However, the end-user experience is generally pleasant, nitpicks around some of USB-IF's specific choices aside.
Earlier quoted context omitted.
EU have enough influence to do to IPV6 what it did to USB in iPhones.
It's harder to prove consumer harm with something as abstract as IP addresses, and there's a bunch of other pieces that make this much less unlikely, such as the fact that USBs already become obsolete and need to be replaced, so you're just shifting the replacement cycle.
Earlier quoted context omitted.
Only network engineers should see or care about IP addresses. The fact IPv6 addresses use colons is why people don't use IPv6 is the worst take I've ever heard.
I host a few video game servers for my friends and love the fact that I can say my easy to remember IPv4 address aloud whenever they forgot it. I have an IPv6 address but haven't bothered memorizing it or giving it out because it would just be more hassle.
game.latticeanimal.net. 3600 IN A 1.2.3.4