Now currently I’m not in the workforce, but in the past from my work experience, apprenticeship and temp roles, I’ve always seen ipv4 and not ipv6!

Hell, my ISP seems to exclusively use ipv4 (unless behind nats they’re using ipv6)

Do you think a lot of people stick with the earlier iteration because they have been so familiar with it for a long time?

When you look at a ipv6, it looks menacing with a long string of letters and numbers compared to the more simpler often.

I am aware the IP bucket has gone dry and they gotta bring in a new IP cow with a even bigger bucket, but what do you think? Do you yourself or your firm use ipv4 or 6?

  • Skull giver@popplesburger.hilciferous.nl
    0·
    1 month ago

    It fixes must about every gripe I have with IPv4. It closes the hidden security holes NAT introduces. It pretty much configures itself. It allows you to use multiple Xboxes or Playstations within the same network and play online without faffing about! You can also disable the firewall entirely and basically never get scanned because scanning 2^64 addresses to find one computer is infeasible for bots (though you shouldn’t).

    The addresses are longer, that’s for sure. But you shouldn’t be remembering those anyway. That’s why DNS exists! If you don’t have a local DNS server for some reason, just use mDNS, every device supports it out of the box. yourcomputersname.local will work in place of an IP address in just about everything since Windows Vista.

    IPv6 was severely underdeveloped when the Necromancy Address Translation kept IPv4 usable twenty years ago, but we’re beyond that now. We have been for a while, actually.

    Unfortunately, a lot of network people are the type that learned how networks worked in school forty years ago and decided that this is the way things are and they should never change again. That’s how you get things like “TLS 1.3 pretends to be a TLS 1.2 session resumption or half the internet will break” and “only port 80 and 443 are usable on the internet”. They even brought DHCP back when IPv6 works perfectly fine without it! At least Google did the right thing and refused to play ball with that malarkey in Android.

    The whole address reserve argument never helped much. Super expensive cloud providers are now charging extra for IPv4 addresses but if you’re using Amazon AWS you’re used to paying through the nose anyway. CGNAT is a much worse problem, with thousands or hundreds of thousands of people sharing the same IPv4 address and basically being forced to solve CAPTCHAs all day because one of their IP coinhabitors has a virus.

    As the comments here show, plenty of people can’t be bothered. That’s fine, legacy websites and devices can just use IPv4, that’s the beauty of it.