• Scoopta@programming.dev
    link
    fedilink
    arrow-up
    47
    arrow-down
    2
    ·
    3 months ago

    Should probably fix that given we’ve been out of IPv4 for over a decade now and v6 is only becoming more widely deployed

    • renzev@lemmy.worldOP
      link
      fedilink
      arrow-up
      29
      arrow-down
      1
      ·
      3 months ago

      Agreed. Though I wonder if ipv6 will ever displace ipv4 in things like virtual networks (docker, vpn, etc.) where there’s no need for a bigger address space

      • Captain Janeway@lemmy.world
        link
        fedilink
        arrow-up
        29
        arrow-down
        1
        ·
        3 months ago

        I hope so. I don’t want to manage two different address spaces in my head. I prefer if one standard is just the standard.

      • Domi@lemmy.secnd.me
        link
        fedilink
        arrow-up
        29
        arrow-down
        1
        ·
        3 months ago

        Yes, because Docker becomes significantly more powerful once every container has a different publicly addressable IP.

        Altough IPv6 support in Docker is still lacking in some areas right now, so add that to the long list of IPv6 migration todos.

      • 30p87@feddit.de
        link
        fedilink
        arrow-up
        5
        ·
        3 months ago

        I wish everything would just default to a unix socket in /run, with only nginx managing http and stream reverse sockets.

        • verstra@programming.dev
          link
          fedilink
          arrow-up
          4
          ·
          3 months ago

          Wait, but if you have, for example an HTTP API and you listen on a unix socket in for incoming requests, this is quite a lot of overhead in parsing HTTP headers. It is not much, but also cannot be the recommended solution on how to do network applications.

          • WaterWaiver@aussie.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            Replacing a TCP socket with a UNIX socket doesn’t affect the amount of headers you have to parse.

    • PenisWenisGenius@lemmynsfw.com
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      3 months ago

      I use ipv6 when possible but it’s rarely possible. I’ve never had home internet that was ipv6 ready enough for my wan address when googling “what’s my ip” to be something besides an ipv4 number.

      Could I get ipv6 over otherwise non ipv6 compatible hardware using a vpn?

    • 0x0@programming.dev
      link
      fedilink
      arrow-up
      3
      arrow-down
      4
      ·
      3 months ago

      we’ve been out of IPv4 for over a decade now

      Really? Haven’t had trouble allocating new VPSs with IPv4 as of late…

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        7
        ·
        3 months ago

        You’re probably in a country that got a ton of allocations in the 90s. If you came from a country that was a little late to build out their infrastructure, or even tried to setup a new ISP in just about any country, you would have a much harder time.