• tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    98
    arrow-down
    2
    ·
    edit-2
    11 hours ago

    I mean, some of those EOLed nearly a decade ago.

    You can argue over what a reasonable EOL is, but all hardware is going to EOL at some point, and at that point, it isn’t going to keep getting updates.

    Throw enough money at a vendor, and I’m sure that you can get extended support contracts that will keep it going for however long people are willing to keep chucking money at a vendor – some businesses pay for support on truly ancient hardware – but this is a consumer broadband router. It’s unlikely to make a lot of sense to do so on this – the hardware isn’t worth much, nor is it going to be terribly expensive to replace, and especially if you’re using the wireless functionality, you probably want support for newer WiFi standards anyway that updated hardware will bring.

    I do think that there’s maybe a good argument that EOLing hardware should be handled in a better way. Like, maybe hardware should ship with an EOL sticker, so that someone can glance at hardware and see if it’s “expired”. Or maybe network hardware should have some sort of way of reporting EOL in response to a network query, so that someone can audit a network for EOLed hardware.

    But EOLing hardware is gonna happen.

    • shininghero@pawb.social
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      8 hours ago

      I think there should be a handoff procedure, or whatever you want to call it.

      As EOL approaches, work with whatever open router OS maker is available (currently OpenWRT) to make sure it’s supported, and configs migrate over nicely. Then drop one last update, designed to do a full OS replacement.

      Boom, handoff complete.

      • Brkdncr@lemmy.world
        cake
        link
        fedilink
        English
        arrow-up
        11
        ·
        8 hours ago

        I’d support a regulation that defines either an expiration date or commitment to open source at the time the hardware is sold.

    • db2@lemmy.world
      link
      fedilink
      English
      arrow-up
      50
      arrow-down
      2
      ·
      11 hours ago

      all hardware is going to EOL at some point, and at that point, it isn’t going to keep getting updates

      EOLing hardware should be handled in a better way

      Both of these are solved by one thing: open platforms. If I can flash OpenWRT on to an older router then it becomes useful again.

      • Rivalarrival@lemmy.today
        link
        fedilink
        English
        arrow-up
        27
        ·
        9 hours ago

        Bingo.

        Either support the device until the heat death of the universe, or provide consumers with the access to maintain it themselves.

      • thejml@lemm.ee
        link
        fedilink
        English
        arrow-up
        8
        ·
        edit-2
        9 hours ago

        Definitely don’t this in the past (Linksys WRT54G!) but let’s be honest, the kind of people running 10yo Dlink routers aren’t going to flash new firmware, let alone OpenWRT or even know to look for it. It would have to come that way from the factory. And even then I doubt most people even do regular updates, sadly.

      • BearOfaTime@lemm.ee
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        3
        ·
        11 hours ago

        Right?

        Something this old is going to be power inefficient compared to newer stuff, and simply not perform as well.

        I would know, I just booted up a 10 year old consumer router last night, because the current one died. It’ll be OK for a few days until I can get a replacement. Boy, is this thing slow.

        • metaStatic@kbin.earth
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          11 hours ago

          I have a netgear router that isn’t even that old and it doesn’t have gigabit ports.

          even though I was able to throw openwrt on there to mess around with it’s still e-waste

    • tabular@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      9 hours ago

      When the users are in control of the software running on their devices then “EOL” is dependent the user community’s willingness to work on it themselves.