9 ms·
All it means is the free lunch is over and people have to start buying their IPs off of an informal market. Theoretically we could have transitioned to IPv6 in
by jandrese 7y ago
All it means is the free lunch is over and people have to start buying their IPs off of an informal market.
Theoretically we could have transitioned to IPv6 instead and avoided this hassle, but too many incumbents are dragging their feet on the whole IPv6 issue.
- tgvaughan 7y agoDo any of these incumbents stand to gain financially from IPv4 scarcity?
- snuxoll 7y agoYes, Residential ISP's can sell or lease their space to AWS, etc. for example and just start moving their customers over to CGNAT. Why bother upgrading your entire network, planning allocations, etc when you can just NAT everyone for cheap?
- freedomben 7y agoCan confirm this is happening. If you're lucky enough to have a choice in ISP, there are a few that won't CGNAT you. I pay a little extra for this ($10 a month) but it's worth it for me. Ask your ISP if that sounds interesting.
- flatiron 7y agoIs that really a feasible long term solution though? I require port forwarding and also work from home so require my service not get blocked due to some spammer on my block.
- wlesieutre 7y agoI’m sure your ISP would love to sell you a business connection for 3x the price
- wongarsu 7y agoThis honestly sounds like a perfect case for a business connection. Not only does it give you a static IP without NAT, possibly in an address block with other high paying (==reputable) people, it also bumps you up a lot in terms of customer service and service availability. Usually the first two questions in an outage are "how many customers are offline, and are any business connections impacted".
- nybble41 7y agoThat assumes the ISP is willing to run a business connection to a residential address. Not every ISP will, especially if you're just a home user with special requirements and not an actual business.
- freedomben 7y agoPerhaps not, but two years in and still going fine. Maybe once IPv6 is more widely adopted I won't need it anymore.
- Dylan16807 7y agoThat's such a ridiculous overcharge. Even a dollar a month would be well into overkill.
- freedomben 7y agoIt includes a static IP, but yeah I agree it's a bit steep. Other ISPs would make me buy a business line, which would cost a lot more than $10 extra.
- mfro 7y agohave you considered just using IPv6 instead of paying that charge?
- cooljacob204 7y agoI would be very, very upset if my ISP decided to throw me into a NAT. Fingers crossed they don't lol.
- mike_hock 7y agoAs long as you have a public IPv6 address, just use that.
- cbhl 7y agoI feel like I would mind NAT less if they gave all the devices IPv6, similar to how it works on some LTE networks. But IPv6 prefix delegation doesn't always work if you put your own router behind the ISP box...
- thu2111 7y agoI'm behind CGNAT for my home connection :( However, I also have native ipv6 to the home for as many devices as I want. It's easy to forget that carrier NAT is expensive for ISPs as NAT hardware needs a lot of fast RAM.
- wmf 7y agoNAT requires planning and expensive equipment; it's not obviously cheaper than IPv6.
- snuxoll 7y agoYes, but it doesn’t require upgrading all your routing hardware and the planning involved with adapting your physical network design to work with the hierarchical structure of IPv6 (we’ve had TCAM large enough to map every /24 of the v4 space for some time now, you can’t get away with that shit with v6 even if your hardware optimizes TCAM usage for routes up to /64’s). This is why many residential ISPs and business haven’t implemented IPv6 yet (well, the later enjoys the false sense of security NAT provides too).
- commandersaki 7y agoKind of. IPv6 addresses are for the most part worthless. They're only useful to shed load for CGNAT but that's only workable if you can configure the end user devices, hence why it's taken off with carriers.
- Agenttin 7y agoWhy, do you think? We're talking about computer people, not exactly Luddites. We all upgrade to new tech all the time, but IPv6 is more than 20 years old and adoption is still shit.
- ta58844874 7y agoIPv6 is a mess, over-engineered, non-intuitive, magic addresses etc. All they needed to do was expand the address space, but it looks like the kitchen sink got thrown in.
- ineedasername 7y agoWhat were the changes in IPv6, beyond just expanding the address space?
- jandrese 7y agoIP Fragmentation at routers was removed from the protocol for one. Another is that it changes the way you think about IP addresses, with endpoints getting a /64 instead of a single address like you did in IPv4. This allows users to change their IP address for every connection if they want, so if you want to apply policy to them you need to apply it to the entire subnet they are on. Granted, this also happens in IPv4 if you are doing NAT, so it's not really a change for most people. There are a few other changes to stuff like QoS to better reflect modern practice, but for the most part it's pretty similar. Also, the IP header lost its checksum, as it was basically never useful.
- dependenttypes 7y ago> IP Fragmentation at routers was removed from the protocol for one. Everyone that I talked to about this seemed to like the change.
- throw0101a 7y ago> Another is that it changes the way you think about IP addresses, with endpoints getting a /64 instead of a single address like you did in IPv4. End points get /128, it's just that subnets are now /64. That simply means that endpoints can auto-assign themselves a new /128 because--instead ofhaving only space for 2^8 hosts in the typical /24 subnet of IPv4--there is now space for 2^64 hosts, which makes it unlikely that collisions will occur.
- tialaramex 7y agoThey don't need an "informal market" when there's a perfectly good formal market. You can sell some of your IPv4 allocation to another LIR party which needs the addresses, the only case that you can't do through the formal mechanism is speculation. You can't buy a /16 and then sit on it hoping to sell it later when the prices are highest before a collapse. Good. One thing you don't see enough of yet is providers charging for the IPv4 address their customers probably don't need. Those have a real cost, and economics 101 tells us if something has a cost, even a small cost, and you surface that cost to your customers, suddenly they're a lot more interested in helping avoid that cost than they were when you just ate it as part of the service. Plastic carrier bags weren't free back when grocery stories didn't charge for them -- they just absorbed the financial cost and externalised the environmental cost. Charge for the bags and suddenly customers remember they already have a bag, they don't need a bag. Same with IPv4.
- dotancohen 7y agoAWS does charge for unused IPv4 addresses, but used addresses (i.e. attached to a running VM) are "free" (price included in service). Do other cloud providers (Azure, Google Cloud, Digital Ocean) do this?
- toast0 7y agoYeah, I've seen this at Digital Ocean, if you have a floating ip (can go to anything in the datacenter) and it's not attached, it has a price.
- goatinaboat 7y agoYep same on Azure
- Apofis 7y agoI'm seeing IPv6 popping up more and more lately, so I don't think it will be much longer.
- xnyan 7y agoCan I ask how old you are or how long you’ve been in the industry? I have been hearing about the impending coming up IPv6 since I was in school 15 years ago.
- jrockway 7y agoThings have changed a lot in 15 years. When you sign up with a major cable company like Spectrum and open up your browser and visit Google or Facebook, IPv6 is being used. I feel like the adoption problem is now firmly on "us". Last time I was setting up an internal network, I was afraid of the consequences of using IPv6 internally, so I just didn't. I imagine a lot of people are in the same boat, and they are the stragglers preventing us from turning off IPv4. The big players are ready. (I will say that jrock.us has worked over IPv6 for almost as long as Google, though. When you only have one computer on the network, IPv6 is not much work.)
- geofft 7y agoNot just incumbents. Have you seen a single startup that uses IPv6 for all their internal networking (running NAT on their internet uplink if needed)? If every single incumbent and every single newcomer is dragging their feet on IPv6, maybe, just maybe, the problem isn't every single engineer in the industry, the problem is IPv6. Theoretically we could have had a straightforward extension of IPv4 to a longer address length and the exact same design, but some architecture astronauts took over the IETF and they think it's more valuable to push their weird redesign of the internet than to actually solve IPv4 address exhaustion.
- jachee 7y agoThis sounds a lot like "These newfangled automobiles are scaring the horses!" The situation feels like chicken-and-egg to me. If I had the option to use IPv6 at home, I'd be on it 100%... as-is, there's little motivation to move off of v4 internally since I'd have to NAT/tunnel to get to the v6 internet over Fios. That said, most of my link-local intranet traffic is on the fe80:: network, because that's what avahi and mDNS prefer as answers.