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?

  • BearOfaTime@lemm.ee
    53·
    3 months ago

    Why should I use IP6 in my small home network?

    Or in an SMB where there are less than 100 IP’s used on a daily basis?

    First I have to pay the cost of transition, along with the risk of things not working while I do this, and then the risk of something new being added and not working.

    There’s simply no value in these environments to switching, and a lot of risk.

    Now let’s look at Enterprise, where you have thousands of desktops, probably thousands of servers, extensive networking that already works (along with many, many devices that don’t support IP6, like printers, scanners, access control devices, surveillance hardware, etc, etc). Are you going to pay the tens of millions to transition, and assume the risk?

    IP6 is good for backbone right now. It will slowly transition into LAN for larger environments (think Enterprise when they setup new network segments, since they’re buying new hardware anyway. But only after extensive testing.

    But IP4 is just fine for small networks, and I don’t see any reason for IP6, ever, for home and SMB LAN.

    • chrisAEnglish
      8·
      3 months ago

      Why should I use IP6 in my small home network?

      • No NAT. Especially in a home network NAT can be a hassle.
      • A bit more anonymity through changing temporary adresses.
      • Some people don’t even have a real IPv4 address anymore in their home and only connect through CGNAT. That means that if you disable IPv6 on your computer you only use CGNAT.
      • The fact that EVERYONE needs to transition to IPv6 or it doesn’t make sense.

      Or in an SMB where there are less than 100 IP’s used on a daily basis?

      • No NAT. NAT is no firewall. If you can’t set up a firewall you are honetly not qualified to be a network admin.
      • Easier VPN S2S-VPN. I had a few instances where the internal IP ranges clashed.
      • All the other advancements of IPv6
      • The fact that EVERYONE needs to transition to IPv6 or it doesn’t make sense.

      First I have to pay the cost of transition, along with the risk of things not working while I do this, and then the risk of something new being added and not working.

      You can transition step by step. Dual Stack is a thing.

      IP6 is good for backbone right now. It will slowly transition into LAN for larger environments (think Enterprise when they setup new network segments, since they’re buying new hardware anyway. But only after extensive testing.

      That makes no sense to me. Every network in itself doesn’t need IPv6. The 10.0.0.0/8 range has 16 777 216 addresses. IPv6 only makes sense if everyone uses it. We bought ourselves time with NAT and CGNAT and splitting up older ranges but that won’t last forever and is costly.

      Everyone needs to transition otherwise services will need to keep their IPv4 forever. And if the services keep their IPv4 users don’t have an incentive. Maybe we should transition BEFORE there is time pressure. Now is the time to slowly start setting everything up with enough time to plan and test firewall rules and appliances and everything else.