IPv6 only in 2022

Pretty much. But your head end isp may or may not enable ipv6 which complicates things

You arent supposed to

You know how in SimCity you start in a plain green rectangle with a road coming in and one going out? How you have a rough idea in your head as to where the industrial area and the eventual down-town will end up?
Imagine that, but with a network. That is what I do on that front.

The first pair of switches goes in, then a firewall or two. Depending on demands, there may be a router and central switching setup in place now. This is where the “buzzing village”-achievement would pop up.

WHERE would I put that magical DNS?
“Just put a server” is like skipping past industry and directly going for the Space-Elevator. Possible, sure (at least with mods and god-mode), just does not result in a thought out system but an organically grown stain on the carpet.

1 Like

That’s all well and good if you’re starting over in modern times.

When you’ve got an existing 60 site network with architecture from 25 years ago, its a little trickier than that.

It would be nice if we could go IPv6-only.

As it stands now, if my mom calls me up and says the internet kinda works, I ask if she can access Facebook. If so, I ask if she can access Github.

Github is still IPv4-only, so if it fails to load, that means the DHCPv4 lease got FUBAR’d somehow (only happened twice, still not sure how it occurs), and the solution is to power cycle the modem.

The annoying thing is that for most webapps, the only thing holding them back is logging IP addresses in a VARCHAR(15) column. After that, it doesn’t matter what the internal network looks like, just give the nginx host an IPv6 address and edit the server block. And yet 80% of websites don’t support IPv6.

It’s a sad state of affairs.

1 Like

It seems that other people are finally getting interested in this

I need to re look into this, but moving and being at work really takes too much time off life. Anyone else got anything new on this matter?

Not possible today. There’s a lot of missing support structure that needs to be developed to adopt IPv6 even in the home lab.

Honestly, if the high end carriers used IPv6 for routing with the rest of us on segmented private IPv4 addresses behind NAT. Then we deal with the rich creamy IPv4 day-to-day, where the carriers dealt with the IPv6 interconnects. IPv6 is way overkill for address density.

Existing public IPv4 (that many companies and countries own) would still be viable, but they would be in a DMZ sort of arrangement where they were accessible through the IPv6 core net, but not really on it. Over time as the services mature, more people could move to the IPv6 universe.

Like fission (edit: meant fusion, typed fission. Leaving the error here to mock me forever), IPv6 is always ten years away.

If you want human readable, my suggestion (that I never had the time to do anything about) was Internet addresses based on the [location specific three words] technique (what3words /// The simplest way to talk about location). Where your location could be brought down to a single meter by stating three words.

For IP, you could register 4-5 plain text words as your network destination.

Contact me at: \\pear.shaped.karma.club

or shop now at: \\elegant.mens.fashion.design.shop

You get the idea.

I hope you mean fusion.

I feel like the part with the three words is going to be terrible when in a service desk situation where I have to tell the customer what website they need to open. And then having to NATO language the whole thing…

We should probably just move completely away from traceable internet to make it anonymous and safe for all. Where the packets only compare an api key with servers to know where to go.

1 Like


1 Like

It’s coming, then. It used to be 50 years. (I’m quoting a JET researcher I met in 1988.)

1 Like

So pretty much the endless race, always a half distance, of what it used to be, away.

Gives me more hope than the Soon™.

Unless we get a Tony Stark type then we can all have one in our chest.