Transcript

False meme image that says “bad news ipv4 fans. linus torvalds has announced removing ipv4 support from the linux kernel after the maintainers of the network stack got into a fight over WHAT KIND OF HRT gives the best results. this incident will impact 5 billion people and will make 95% of all network equipment on Earth binnable.” with fake screenshots of the linux kernel mailing list a girl calling another one a slur from 4chan over HRT choices and Linus Torvalds saying he will drop IPv4 support and asking the maintainers to learn to shut the fuck up.

Source: https://rivals.space/@deuxnise/115032302416832519

  • MattTheProgrammer@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    17 minutes ago

    I’m ignorant enough that I didn’t realize this wasn’t actually happening until I read the comments. My networking knowledge is piss poor haha.

    • Korhaka@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      30 minutes ago

      I still don’t have an IPv6 address over 4G with Vodafone. I want to run a web server on my phone, isn’t this a normal use case? Nat444 makes that pretty difficult, just let me use IPv6!

      • purplemonkeymad@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        26 minutes ago

        Cabled from Vodafone is not much better, ip6 does auto configure from the router with a local address, so it at least supports it. but no routable ips yet.

  • lightnegative@lemmy.world
    link
    fedilink
    arrow-up
    22
    arrow-down
    4
    ·
    14 hours ago

    Ipv4 is simpler and therefore easier for my brain to comprehend.

    I deliberately disable IPv6 on all the devices on my home network because it’s really f**n annoying when some service tries to bind to localhost but picks up the IPv6 localhost instead of the IPv4 one

    • Trainguyrom@reddthat.com
      link
      fedilink
      English
      arrow-up
      46
      arrow-down
      2
      ·
      13 hours ago

      I’ve encountered way too many administrators and network admins who swear that “IPv6 does nothing but cause trouble” but the truth is, the trouble it’s causing is because you can’t half-implement IPv6. You either roll it out to the whole network or you don’t, and the longer you kick that can down the road the harder it’s going to be.

      Basically too many professionals who haven’t learned a new technology since 2005 and refuse to try new things keep holding the world back

      • Korhaka@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        22 minutes ago

        Can’t even attempt to learn it if my ISP won’t provide addresses though.

        Not been able to use it to even try, but doesn’t IPv6 not have subnets at all? No 192.168.1.1 on your local network with a different public facing 85.136.52.142 (and with NAT444 you also have ISP facing 10.183.23.6). So does your ISP provide you a range of IPv6 addresses?

      • anamethatisnt@sopuli.xyz
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        10 hours ago

        I think what those admins really mean to say is “We don’t need any of the benefits of IPv6, so IPv4 works just fine and making the large scale change is trouble.”, when you already got your DHCP, NAT, Firewall and stuff up and things do work as expected then you don’t really need NDP or SLAAC.

      • vithigar@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        9 hours ago

        I will happily enable and use it once doing so doesn’t break any of my connectivity.

        I’m not managing an enterprise network, it’s just my home, but my ISP doesn’t support IPv6 so that’s one extra layer of complexity right off the hop. On top of that internal services switch which previously required no manual configuration just seem to randomly not work.

        IPv6 is not going to see widespread adoption unless it can be implemented completely transparently for the end user, full stop.

      • irish_link@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        12 hours ago

        The issue for me is when I have it enabled and try to connect to a site that doesn’t support it fully (same thing / half assed) and the site doesn’t work properly. For home its my wife and kids that complain, when its the office then everyone complains. I get the blame for failed connections or things not working right when a fully compliant IPv6 site works just fine.

        Now I am not perfect so It could be me but I have read up and learned as much as possible. No expert but I did deploy DHCPv6 in a test environment. However there is no reason as of yet to deploy DHCPv6 locally since the address space is so wide. Just saying Its possible that the issue is me but from my understanding its like the U.S.A. switching to metric. Parts of us tried it but others didn’t and thus we failed as a giant group.

        I think there needs to be a big ass push and force everyone to switch as the same time. I know some of the old devices may not work however those devices have to be 20+ years by now.

      • splendoruranium@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        8 hours ago

        Basically too many professionals who haven’t learned a new technology since 2005 and refuse to try new things keep holding the world back

        If it ain’t broke…

        • Korhaka@sopuli.xyz
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          8 minutes ago

          Imagine arguing that ‘solutions’ like NAT444 isn’t broke as fuck

        • Trainguyrom@reddthat.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          I always bring it up when the network is experiencing problems that they wouldn’t have with IPv6. Running out of IPs in a given scope, increasing costs of public IPs, etc.

      • blackstrat@lemmy.fwgx.uk
        link
        fedilink
        arrow-up
        1
        arrow-down
        7
        ·
        9 hours ago

        “IPv4 is running out of IP addresses so therefore every local network needs to move to IPv6” is a full clown move.

        • Trainguyrom@reddthat.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          First of all, enterprises usually have at least one public IP (the one I work at right now has more public IPs than they have server VMs)

          Secondly enterprises have big enough and complex enough networks to see other benefits of IPv6. For example IPv4 has some problems when broadcast domains are too large, so your internal network sizes are artificially limited when following best practices. Without private networks you don’t have to worry about IP collisions between different private networks that you have to route between (comes up more than you’d think!) etc etc.

    • Johanno@feddit.org
      link
      fedilink
      arrow-up
      4
      ·
      9 hours ago

      In a local network there is no point in using ipv6.

      It is interesting when you run out of ip addresses for the amount of devices you have.

      So in the open Internet.

      Unless I am missing something.

      • jj4211@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 hours ago

        A couple of things that IPv6 does better for local networks is link local addressing (fe80::). and multicasting.

        In IPv4, they kind of hacked something out of 169.254, but if you have more than one NIC, it pretty much becomes useless.

        If you have a service designed explicitly never to be accessed over a router, then you can live in fe80:: a lot more easily than trying to do the same thing with 169.254.

  • JcbAzPx@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    15 hours ago

    Please, at least 85% of that network equipment hasn’t been updated in 30 years and they’re not about to start now.

          • Flipper@feddit.org
            link
            fedilink
            English
            arrow-up
            11
            ·
            10 hours ago

            There is the rule number one of the linux kernel: “We don’t break userspace.” Linux has refused fixes for buggy behavior in the past because of this rule. This would most certainly break userspace.

            Also the alt text of the original image states this is fake.

    • JasonDJ@lemmy.zip
      link
      fedilink
      arrow-up
      174
      arrow-down
      1
      ·
      1 day ago

      I’m glad that Linus clarified that it was High Resolution Timers. I was honestly thinking they were arguing about Hormone Replacement Therapy.

    • lmmarsano@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      13
      ·
      edit-2
      1 day ago

      Thanks for the alt text & transcript in OP. It’s missing here, though.

      Transcript

      From: Linus Torvalds <[email protected]>
      To: [email protected]
      Subject: [RFC] Remove IPv4 support from kernel, effective next merge window
      Date: Sat, 15 Aug 2025 10:42:00 -0700
      Message-ID: <[email protected]>

      Hey folks,

      After yet another deeply technical and entirely calm discussion about HRT (High-Resolution Timers) that somehow devolved into 200+ replies, personal insults, and at least one GIF of a raccoon, I have decided it’s time to take drastic measures.

      Effective next merge window, we will be removing IPv4 support from the kernel. This will both (a) resolve the maintainers’ scheduling disputes, and (b) force the world into the IPV6 utopia we were promised back in 1998.

      If you need IPv4 after this point, you can either:

      • run an ancient kernel from before the change (good luck with the bugs), or
      • rewrite your applications to use IPv6 and learn to love colons in your addresses.

      Yes, I realize this will break roughly *everything *.
      No, I don’t care. I have already switched all my machines to IPv6-only, except for the toaster, which unfortunately still insists on using a 192. 168. x. x address. The toaster will be replaced.

      If you disagree with this decision, I suggest you take it up with the HRT maintainers. But please keep it civil this time. (Or at least keep the raccoon GIFs under 1MB.)

      - Linus

      • thedruid@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        16 hours ago

        What a bunch of babies. They can’t work together so they make the world suffer.

        Got it

        Edit. I looked. It’s a joke. They got me. I’m leaving this to show my shame

        • Treczoks@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          37 minutes ago

          I noticed. But sometimes, LT can be a bit explosive, and we all know that devs can be bitches about their code. I would not put it past Linus that he actally threatens some fully nuclear option to bring some boneheads to reason.

    • AppleStrudel@reddthat.com
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      8
      ·
      1 day ago

      Well I’m not going to switch away my perfectly functional mesh routers that uses IPv4 as using IPv6 on a local net that I may sometimes need to type in manually is rather stupid. And that would also bin my routers, so I’m not doing that either.

      Oh well, I guess it’s been fun guys, no more Linux for me due to potential future security issues.

        • AppleStrudel@reddthat.com
          link
          fedilink
          English
          arrow-up
          8
          arrow-down
          2
          ·
          edit-2
          1 day ago

          No. But if this is true (which I do doubt completely, Linus can’t be this dumb to singlehandedly cripple his OS), this should also affect every intranet address.

          The current description of IPv6 intranet is just ridiculously dumb anyway. Should I want to ssh into a local device, I’ll have to type in for example fd9e:9aa0:c00f:1::a, with only the fd part being the same for all intranets rather than 192.168.1.10 with 192.168 generally always being the same.

          Edit: wait… Are you telling me to set DNS redirects on all my local devices? Yeah, that’ll work, but why the even…

          • lengau@midwest.social
            link
            fedilink
            arrow-up
            13
            ·
            23 hours ago

            I don’t think I’ve entered an IP address for a local device in years. Everything is accessible using <hostname>.local thanks to mDNS. Avahi has been doing this for… 20 years I think?

            • AppleStrudel@reddthat.com
              link
              fedilink
              English
              arrow-up
              3
              ·
              22 hours ago

              Cool. My mesh doesn’t have that though (I think?). But admittedly that’s a tangent. If IPv4 ever depreciates, I’ll have to toss my mesh anyway.

          • FauxLiving@lemmy.world
            link
            fedilink
            arrow-up
            9
            ·
            23 hours ago

            Pihole automatically adds clients that get an IP from its DHCP component. All my clients are server.local, client1.local, tv1.local, etc. So I can use their DNS name everywhere.

            Even if it don’t want to use pihole(why?), you can edit the SSH config and add addresses for each host so you can just type

            ssh server
            
          • anyhow2503@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            18 hours ago

            wait… Are you telling me to set DNS redirects on all my local devices? Yeah, that’ll work, but why the even…

            What do you mean by that? I’m pretty sure people are telling you to run a DNS server and set up entries for any clients you want to regularly connect to.

            with only the fd part being the same for all intranets

            Why?

            • AppleStrudel@reddthat.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              22 hours ago

              Yeah, I really have put too much time into replying to all these based solely on a hypothetical. But I did learn something from all these comments (technical something, not me being an idiot), so it’s all good.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        1
        ·
        22 hours ago

        Your ISP needs to setup IPv6 which isn’t trivial to do from scratch.

        What provider is it?

        • themadcodger@kbin.earth
          link
          fedilink
          arrow-up
          3
          ·
          22 hours ago

          Mine is Quantum Fiber, a sister of CenturyLink. CL has it, apparently QF doesn’t. Or at least not natively, rather 6rd. And then possibly not on the modem they installed? At any rate, I haven’t been able to find anything online.

          • Trainguyrom@reddthat.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            13 hours ago

            I’m on one of the regions of fiber that CenturyLink spun off to a private equity firm a few years ago. Zero IPv6 support here

  • Humorless4483@lemmy.world
    link
    fedilink
    arrow-up
    28
    arrow-down
    1
    ·
    22 hours ago

    My dream. IPv6 adoption would skyrocket to a degree unimaginable and those who don’t want to, will fall behind unless they move their asses and learn.