Live data from Hacker News

How bad is IPv4 address exhaustion?

blog.apnic.net

71–80 of 94 posts

Re: How bad is IPv4 address exhaustion?

#71
post #69

Earlier quoted context omitted.

Here, the linux routers are way ahead of you. Odhcpd used to handle ipv6 delegations for normal users can coordinate with dnsmasq (often used for ipv4 assignments and dns proxying) or unbound - to assign nice local names. Three trouble begins at internet scale where mDNS just does not work due to collisions. And ISPs do not want to give you free domain names and especially free dynamic subdomain delegation.

I use Pfsense which communicates DHCPv6 leases to Dnsmasq/Unbound fairly easily. >And ISPs do not want to give you free domain names and especially free dynamic subdomain delegation. Probably not but for internal resolution a .local or similar TLD is sufficient.

Yes. The thing is, this would be super easy for the ISPs as they already have to maintain reverse DNS for dynamic IPv4 most of the time, so modifying it to also allow delegating to an authenticated DNS secret should be trivial. Eslecially now that ISPs are so fond of giving you big routers.

Re: How bad is IPv4 address exhaustion?

#72
post #46
post #22

Hypothesis: Mass adoption of IPv6 is blocked by the ugliness/inconvenience of the IPv6 address format, hence "end-users" (developers) don't like adopting IPv6. As long as this UX issue does not get solved, IPv6 adoption is only going to happen on an individual level when any given business' significant income stream is at immediate risk of being disrupted. Depending on how many of these individually affected business…

At home, I get IPv6, but I get assigned a different network every 24 hours, so it not that useful to, say, access my home server remotely. It works smoothly, though. At work, we had some problems with Windows' Network Location Awareness where a domain controller thought it was on a public/non-trusted network unless IPv6 was turned off in the network settings. So we actually had at least a little pressure not to enabl…

Funny, this is ISP complicating your and their life only so they can price gouge you.

Re: How bad is IPv4 address exhaustion?

#74
post #41
post #21

Earlier quoted context omitted.

Can you elaborate? IPv6's share of traffic has been increasing at about 0.5% per month for the past year. If IPv4 has 80% and IPv6 20% this month, next month it'll be 79.5 vs 20.5. So in your opinion... what? The change will stop? When? Why?

Sure, I am a RIPE member and am leasing out IPv4 (and IPv6) address space, ASN registrations, etc. Everyone is able to sign up with RIPE and get a /22, thats around 1000 IP addresses. For years the RIRs want to tell us that IP addresses run out but I am still able, today, to pay some bucks and get IPv4 addresses without issues. The issue was that exactly those RIRs handed out IPv4 addresses years ago like there is no…

1) Not everyone can sign up with RIPE. We have tried multiple times and been rejected despite being connected to backbone and having peering agreements and AS number.

2) Why track IP addresses instead of mandating DKIM? Gmail eats valid IPv6 sourced mail with good DKIM keys no problem.

3) Same can be said about IPv4 routes. Remember nobody really uses IP directly to route nowadays...

Re: How bad is IPv4 address exhaustion?

#75
post #68

Earlier quoted context omitted.

"Sir, please type this into your browser to get to the router web interface: 2001:0db8:85a3:0000:0000:8a2e:0370:7334. I repeat 2001:0db8:85a3:0000:0000:8a2e:0370:7334." "Server IP address could not be found." 5 minutes later... "Now could you please tell me the IPs of all connected devices?" Customer hangs up and cancels his subscription.

Wasn't a similar problem solved by services like URL shorteners? I had to work occasional technical service for products where I was one of the embedded engineers and I leaned heavily on bit.ly at the time to get URLs back and forth from customers and it worked exceedingly well. So, with that in mind, what would be the major drawbacks to IPv6 address shorteners? You'll always have a certain class of issues such as tr…

Problem with URL shorteners is ones that use characters, especially of varying cases. Relaying letters across a telephone sucks, I often resort to NATO codes, and now you'll have to distinguish capitalization.

Re: How bad is IPv4 address exhaustion?

#76
post #12
post #7

My ISP doesn't support IPv6 and it's been complicated to get IPv6 running properly at my hosting providers too. My hosting provider uses DHCP to propagate routing information, and I had a lot of issue with it going down, thus losing IPv6 connectivity. In the end I just disabled IPv6 on all the node I manage, it has no benefit except increased complexity. The problem is the lack of insensitive to do the conversion.

This sounds more like poor DHCP configuration on your side? DHCP going down doesn't remove anything unless your client decides to time out it's current address configuration - of which there's no incentive to do on a server. Moreover if routing was being propagated by DHCP, why was that not the case for IPv4 as well which would presumably be using it ?

That's what I thought too, I really tried a lot of configuration client side, on different OS (linux, bsd...), but none was working reliably, even the provider preconfigured linux image. It might be client that are all broken or something else, to be honest I didn't investigate it further, as I don't need IPv6, I just wanted to be "ready" for the future.

Re: How bad is IPv4 address exhaustion?

#77
post #68

Earlier quoted context omitted.

Wasn't a similar problem solved by services like URL shorteners? I had to work occasional technical service for products where I was one of the embedded engineers and I leaned heavily on bit.ly at the time to get URLs back and forth from customers and it worked exceedingly well. So, with that in mind, what would be the major drawbacks to IPv6 address shorteners? You'll always have a certain class of issues such as tr…

Problem with URL shorteners is ones that use characters, especially of varying cases. Relaying letters across a telephone sucks, I often resort to NATO codes, and now you'll have to distinguish capitalization.

Yeah, actually I guess that I was spoiled in that regard. I worked for an RF company when I had that experience and, also having a military background myself, the NATO phonetics were used naturally when communicating with our customers.

Re: How bad is IPv4 address exhaustion?

#78
post #5

I don't see an answer to 'how bad' in the article. I thought I'll get some recent numbers but instead i got... some generic text that was valid even 3 years ago?

This seems to answer the question: https://ipv4.potaroo.net/ The first diagram shows that IPv4 will be quite tight around 2020.

Those graphs are misleading, because APNIC (2011) and RIPE (2012) hit the wall so long ago that they've scrolled out of view.

Re: How bad is IPv4 address exhaustion?

#79
post #52

> The ultimate solution to IPv4 exhaustion is, of course, the complete transition of the Internet to IPv6, however, this will take time and until then there will be (by definition) networks and sites which only support IPv4. Off-topic: I've always wondered why English speakers (or perhaps just Americans?) use "by definition" arguments so much (also just saying that things are by definition so and so). People never se…

This usage seems pretty reasonable. He's saying "Before everything supports IPv6, there will (by definition) be things that only support IPv4."

He's defining a particular scenario, and then using a tautology to clarify that scenario.

Re: How bad is IPv4 address exhaustion?

#80
post #30
post #23

Earlier quoted context omitted.

Offtopic tangential forum rant: There has been an answer to your question in this thread for 14 minutes. However only users with showdead on can see it, because Arc has erroneously flagged it as evil. Screenshot/proof of what I currently see: https://i.imgur.com/Y7iM30E.png HN does get spam, but the text and links don't look like the currently-buried comment does. I can't see it being /that/ hard to train an RNN, wha…

Don't you have enough karma to vouch/favorite that comment? I just did. Usually there's a reason why the comment is automatically flagged so don't agree with your assessment.

I did immediately. It stayed dead!!, which is what prompted the rant.
Post reply on HN