IPv4 address utilization is incredibly low. For example, consider 44.0.0.0/8 - it's sitting around almost entirely unallocated. UCSD Caida uses it for their network telescope (pretending to use it for amateur radio) and won't give it back. Just look at how dark it is: https://benjojo.co.uk/internet-2018.png (from https://blog.benjojo.co.uk/post/scan-ping-the-internet-hilbe... ) Discussion on r/amateurradio - https://…
The fact something looks "dark" on that plot doesn't tell you anything about how much of the space is allocated. The site linked by that many years old Reddit post says that in fact loads of this space is allocated, to specific people, in this case "Hams", I see alphanumeric designations which I seem to remember Hams call "handles" as well as geographic locations and some human names. Is the Amateur Radio "Ham" commu…
So Long Last /8 and Thanks For All the Allocations
91–100 of 201 posts
Re: So Long Last /8 and Thanks For All the Allocations
#92IPv4 address utilization is incredibly low. For example, consider 44.0.0.0/8 - it's sitting around almost entirely unallocated. UCSD Caida uses it for their network telescope (pretending to use it for amateur radio) and won't give it back. Just look at how dark it is: https://benjojo.co.uk/internet-2018.png (from https://blog.benjojo.co.uk/post/scan-ping-the-internet-hilbe... ) Discussion on r/amateurradio - https://…
If you said it was underutilized, you'd be correct.
But before we go after the hams, what about the absolutely massive address space held by the US DOD and related agencies? its literally 20x the size of the /8 held reserved for the ham community.
Re: So Long Last /8 and Thanks For All the Allocations
#93Earlier quoted context omitted.
Trouble is that NAT solved a huge chunk of the problem. The current setup is not quite painful enough for people to want to fix it. The good is the enemy of the great, as it were.
Also I do not need to have directly accesible stuff on my home network. I can use dropbox or buy cheap VPS if I want to keep my data in sync. One is security, NAT is nice for that a lot smaller attack surface. Second keeping your stuff always running at home is unreliable and annoying. Would be nice if I would not have to pay for VPS but $5 a month cheapest linode is more than enough for my hobby projects.
You also can walk everywhere instead of using machines to move around ... but why would you?
> One is security, NAT is nice for that a lot smaller attack surface.
No, it doesn't. It's a common myth, but NAT does not provide any security, it only hides insecurity.
> Second keeping your stuff always running at home is unreliable and annoying.
Complete non-sequitur?
Re: So Long Last /8 and Thanks For All the Allocations
#94Even in developed countries IPv6 is barely deployed (my UK ISP - BT - pretends that they rolled it out but half of the time my modem tells me IPv6 is not availabled until I force it to reconnect, and no sign of IPv6 on mobile networks). Was looking at whether it was more economical to buy a small address block vs rent it from a datacentre. A /24 address block seems to cost around $4,000 upfront but then you need to p…
> Even in developed countries IPv6 is barely deployed For reference, the list of currently leading and trailing countries by IPv6 adoption (from Akamai's August 2017 numbers): Belgium 46%, US 40%, India 36%, Greece 32%, Germany 25%, Switzerland 20%, Finland 20%, Brazil 19%, Canada 18%, Norway 16%, Japan 15% Portugal 13%, UK 12%, France 12%, Australia 8%, New Zealand 8%, Sweden 8%, Netherlands 7%, Mexico 5% Israel 3%,…
Once they go live, expect to see the UK climb significantly.
Re: So Long Last /8 and Thanks For All the Allocations
#95Earlier quoted context omitted.
Have you tried using a linux-based router? ISP-provided CPE is notoriously bad on average, especially in the IPv6 area.
It's a brand-new BT router so I would be surprised if that was the case. I suspect the non IPv6 connectivity rather come from which node I connect to on the network.
Re: So Long Last /8 and Thanks For All the Allocations
#96Earlier quoted context omitted.
Apple has an /8 but Microsoft does not? How did that happen?
Due to the efforts of a small number of people in Apple engineering (notably Erik Fair), Apple was a pretty major internet presence in the early 90’s. Though, oddly, the exec level pretty much didn’t know it existed. Remember eWorld? (Probably not.) How did Apple get a /8? “We asked.” ( https://www.quora.com/How-did-MIT-end-up-with-an-entire-clas... )
Not "just" asked for by Apple, but fairly close.
The relevant bit: 'we renumbered the entire company from "picked out of the air" IP Addresses to net 17, assigned to us upon request by the Internet Assigned Numbers Authority (IANA) (R.I.P., Jon Postel).'
https://www.quora.com/What-are-some-reasons-Apple-employees-...
Re: So Long Last /8 and Thanks For All the Allocations
#97Earlier quoted context omitted.
IMO retarded greedy ISPs issuing /64 prefixes to customers. Now you aren’t supposed to NAT but you can’t have multiple subnets either.
Not a network guy, but I thought IPv6 made subnetting mostly unnecessary? Certainly on an individual consumer level?
Re: So Long Last /8 and Thanks For All the Allocations
#98Re: So Long Last /8 and Thanks For All the Allocations
#99Can anyone offer an explanation why IPv6 still has not blanketed the world yet? I mean if client pings an IPv4 address, it should be automatically converted to an IPv6 version. So why isn't IPv4 instantly outdated?
Re: So Long Last /8 and Thanks For All the Allocations
#100Earlier quoted context omitted.
Why would IPv6 be a failure ? It sounds like you don't know what you're talking about
It's terrible from UX point of view. 1. 128 bit is likely an overkill. 64 bit would give more or less 2 billion addresses per every human for earth. Likely enough. 2. It's unreadable. Why the hell use hex? 3. It's been proposed in 1998. It became a standard last year. Not exactly quick adoption and it tells something. Yes, it will probably be deployed out of necessity, but it's weird nobody noticed that if something…
2. It allows you to see subnetting. It makes managing IPv6 so much easier than IPv4.
3. It became "Internet Standard" last year, because the working group decided that it was about time to combine all the RFCs with the errata corrected in a single RFC. Just a formality.
As for traction... blame humans. If there's something better to replace the old thing, but the improvements aren't dramatic enough (e.g. saving tons of money) and the old thing still works, then a huge portion of lazy people won't switch.