Follow

Honestly the money involved in IP allocations and name allocations is totally digusting and really pisses me off

@sir hence why IPv6 movement needs to be faster/sooner

@linuxliaison @sir I did experiment with getting something that looked a lot like 6LoWPAN hacked on top of AX.25 but it was not very reliable even without the soundcard modem. I still believe it's a realistic option though and might revisit it one day.
@linuxliaison @sir context: AX.25 is kinda the amateur radio link layer
@linuxliaison @sir that is ok. I guess these are all pretty obscure standards.

@sir if it's rare, it's expensive.

With IP addresses, you can at least try to make sure they're abundant for a long period of time (I guess with IPv6 it will be at least several decades before we start running short).

OTOH, with human-meaningful catchy names, there will always be a limited supply, simply because there's only so many names that describe your project/restaurant/etc. well.

@Wolf480pl @sir I wish there was a similar system as with phone number. E.g.: when you call someone, the number is local to the country, but when you really want to reach someone abroad, you have to prefix.
I.e. two restaurants can have the same catchy name/number/identifier. But when I want to reach the 'other' restaurant, I have to prefix it with a country code of some sort.
Note that this not what the current DNS does: you always need to give the full name.

@BartG95
Actually, it's doable with DNS, to an extent. There's this `search` directive in resolv l.conf which allows you to specify DNS suffixes in which relative hostnames should be searched.

Eg if you have `search example.net` and you type `ping foo` it will try to resolve it as `foo.example.net.`. OTOH, if you type `ping foo.` (notoce the trailing dot), it will treat it as absolute name, and try to look for a `foo` TLD.

Now, if you put all suffixes you consider local in your `search`, it should in theory first try resolving names in those suffixes. But I haven't seen anyone put more than one suffix there.

I guess it would be more common if domains were organized more hierarchically, according to geographic or administrative location. But they are not, because people move around.
@sir

@Wolf480pl @sir @BartG95 in a time where domains described organisations and networks, rather than brands and topics, this actually was a good idea. recently i decided to do it myself; all my devices have <device>.wowana.me. hostnames, i have public dns set up for them, and i route to them with ipv6 addresses via vpn, currently
@Wolf480pl @BartG95 @sir so my point here is i can `search wowana.me.` and refer to my devices by their shortnames without any trouble

@Wolf480pl @sir

ip.sb/cidr/

18,446,744,073,709,551,616 /64 subnets in total available, lol

@eo
But each customer should get at least a /56, and the current pubkic pool is a /3, so it's really 2^53, and that's assuming optimal balancing of customers across ISPs... let's assume a factor of 256 for that, that leaves us with 2^45 customers, which is 32T, and we have ~8B people on the planet... ok that's still a lot of IPs.

But we don't really know that future brings. My pessimistic guess is we'll start running short in 50 years, my optimistic one is it will be enough forever.

@sir It's only going to get worse. There's more than a few third-party markets for address space.

Sign in to participate in the conversation
Mastodon

cmpwn.com is a private Mastodon instance for friends of SirCmpwn.