Me: grinning manically
Coworker: Why are you looking at me like that?
Me: Open up a terminal and type
ping 4.2.514 and hit enter.Coworker: ...what's the fourth number?
Me: grin widens Just hit enter.
Coworker: WTF!?
ping 4.2.514 and hit enter.@jschauma @ryanc @0xabad1dea Back in 2018 Dave Taht and a few other people tried to reclaim the "class E experimental" address range and most of multicast, which together are about 1/8 of the IPv4 address space.
https://landley.net/notes-2018.html#25-10-2018
The ipv6 stans FREAKED OUT because the only argument their terrible tech ever had was ipv4 exhaustion, largely due to poor initial allocation back in the 1980s (giving korea 64k total addresses, for example).
@landley @jschauma @ryanc @0xabad1dea I think #IPv6 would've gotten more acceptance if it was merely a 4x long #IPv4 annotation instead of doing hexadecimals.
@kkarhan @jschauma @ryanc @0xabad1dea Nope, ipv6 is fundamentally flawed because you can't persistently identify an internet access point in a useful way. That's why wikipedia blocked the entire IPv6 address range for anonymous edits. (May still do, haven't checked.)
You could instead have subdivided the port space without ANY protocol change, and done 1.2.3.4.[0-16] to give each NAT user their own 4096 public ports. 1.3.2.4.2 port 80 is a web server on host port 8192+80...
@kkarhan @jschauma @ryanc @0xabad1dea Ahem, [0-15].
As the saying goes: the two fundamental problems in computer science are cache invalidation, naming things, and off by one errors.
@kkarhan @jschauma @ryanc @0xabad1dea There's only about twice as many people on the planet as there are IPv4 addresses NOW. Increasing the address space by 16x would mean each person (including infants and the illiterate) could have 8 public devices online fulltime without sharing or dynamic provisioning.
Giving each grain of sand in the solar system its own subnet was unmanageable futurism BS to extend the address range to a star trek future with zillions of planets talking via instant FTL.
@pmevzek @landley @jschauma @ryanc @0xabad1dea still, a #64bit #AddressSpace would've been more than sufficient as we can see by the fact that /64 is the default #IPv6 allocation for basically any consumer connection.
A #128bit address space is quite inefficient given we ain't saturating even half of it.
#ZFS does have that problem, abeit #Sun engineers at the time expected #64bit to be as quickly deprecared as #16bin and #32bit.
@pmevzek @kkarhan @jschauma @ryanc @0xabad1dea Some friends in Tokyo talked to a hosting place at the top of a skyscraper in shinjiku to get 3U of rack space last week, and part of the negotiation was how many IPv4 addresses they should get for the servers. (They were offered up to 8 depending on what they wanted to pay.)
I asked: the japanese translated in their .en PDF as "publicly routable" meant ipv4. IPv6 isn't even used internally there (it's 192.168.x.x or something behind the firewall).
@landley @pmevzek @jschauma @ryanc @0xabad1dea And that is espechally baffling considering that #APNIC as #RIR ran out of #IPv4|s first.
Cuz people telling me "Oh, just use HEnet's Tunnelbroker"" never experienced the shitshow that is #Geoblocking and #GDPR-#Noncompliance with #Malvertising to slap their faces!
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] no, it's just absurd to skip #64bit... I'd not be pissed if #IPv6 was widely available. - I can't even get a /64 but my ISP is happy to give me /28 subnets of IPv4...
@landley @pmevzek @jschauma @ryanc @0xabad1dea @ripencc Tho scratch that.
Almost as if my objections at @BNetzA & @[email protected] / @[email protected] / #Bundeskartellamt were 100% justified, cuz noone likes #Vodafone!
@kkarhan @pmevzek @jschauma @ryanc @0xabad1dea @ripencc j-core.org is 5.8.71.57, and landley.net is 67.205.27.143. Neither had trouble getting or keeping an ipv4 address for many consecutive years. There's over a billion of them, even with IPv6 advocates keeping hundreds of millions of multicast and class e addresses out of use.
We haven't suddenly needed to quadruple the length of phone numbers or credit card numbers either. That's not how humans work.
@landley @pmevzek @jschauma @ryanc @0xabad1dea @ripencc mostly because addresses get reused (Dynamic IPs were always the norm for consumers!) and because big block allocations get sold off and deallocated.
The fact that the #US #DoD has multiple /8 blocks hoarded that ain't even publicly routed is the most extreme example: The have enough static IPv4's to assign every past and current servicemember and every military vehicle one and would still have enough to spare.
In fact they have enough static #IPv4's to give everyone in the USA one and would still have propably more to spare than the entire rest of #NATO & #ANZUS / #14Eyes' #MILINTEL have combined.
Instead we have a giant cottage industry that deals with the artificial scarcity of IPv4's like digital real estate brokers, collecting value-removing fees for every transfer they can make which is explicitly rewarding #GAFAMs like #Apple that got a /8 early on and are now propping up their corporate valuation because that address block alone is propably worth a billion if not more.
@kkarhan @landley @pmevzek @jschauma @ryanc @0xabad1dea @ripencc An IPv4 /8 block won't be worth a billion if everyone is using IPv6.
The moment that the bigger IPv6 shift begins, it'll start to snowball and reduce the need for IPv4. Lower demand means lower value. (Especially if the supply keeps increasing from all those ISP's that are selling their remaining IPv4 blocks.)
At least, that is what i suspect will happen.
@namedbird @kkarhan @pmevzek @jschauma @ryanc @0xabad1dea @ripencc The first presentation I saw about IPv6 was in 1998. IPv4 was ~15y old at that point. It's been about 30y since then.
I hear less about ipv6 now than in 2011. Passive consumers of data NATed behind firewalls don't really _have_ meaningful addresses, whether they see themselves as 10.x.x.x or something with colons is irrelevant. Public facing boxes don't have a hard time getting IPv4, https://www.lightwavenetworks.com/our-services/raspberry-pi-colocation/ is $7/month for 5.
We are introducing a new charge for public IPv4 addresses. Effective February 1, 2024 there will be a charge of $0.005 per IP per hour for all public IPv4 addresses, whether attached to a service or not (there is already a charge for public IPv4 addresses you allocate in your account but don’t attach to […]
@pmevzek @kkarhan @jschauma @ryanc @0xabad1dea @ripencc I said "over a billion". The address space is 4 times that. Why should I care about 30-year-old DOD hoarding or Class E and multicast still being locked up for no reason? (If YouTube, Netflix, and Spotify aren't using multicast nothing ever will. Release it to GenPop already.)
IPv6 believers have been warning for 30 years about a critical shortage of a resource currently available for less than $2 a month, and it's always "real soon now".
At the 2014 v6 World Congress in Paris, Facebook’s Paul Saab outlined how Facebook is well on the path toward moving to an IPv6-only internal network. He makes the point that why should you deal with the headache of maintaining a dual-stack (IPv4/IPv6)? Instead just move your internal network to be IPv6-only and then have […]
@pmevzek @landley I wish I had this luxury.
And I'm more often than not not the guy who gets to make that decision.