this post was submitted on 20 Nov 2024
294 points (98.4% liked)

Technology

59495 readers
3092 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
top 34 comments
sorted by: hot top controversial new old
[–] irotsoma@lemmy.world 2 points 49 minutes ago* (last edited 44 minutes ago) (1 children)

I mean this is pretty standard in all industries regardless of whether it's a software flaw or a physical flaw in any other kind of product. What's the likelihood of a vacuum manufacturer replacing a part in a 15 year old product that had a 1 year warrantee even if it's a safety issue? Sure the delivery and installation is cheaper with software, but the engineering and development isn't, especially if the environment for building it has to be recreated.

[–] SplashJackson@lemmy.ca 1 points 5 minutes ago

I work for a manufacturer with part catalogues going back to 1921, and while the telegraph codes no longer work, you could absolutely still order up a given part, or request from us the engineering diagram for it to aid in fabricating a replacement. You can also request service manuals, wiring diagrams, etc. Don't all half-decent manufacturers do this?

[–] Steamymoomilk@sh.itjust.works 19 points 3 hours ago

There right you and i should just buy a new one

Of a diffrent brand

[–] Iheartcheese@lemmy.world 17 points 4 hours ago

Our shit sucks. Buy more lol

[–] psmgx@lemmy.world 27 points 6 hours ago (1 children)

Welp never buying anything D-Link ever again

[–] Imgonnatrythis@sh.itjust.works 48 points 7 hours ago

I agree. Buy a new router that isn't Dlink.

[–] anon_8675309@lemmy.world 5 points 4 hours ago

Why do they say they’re prohibited to provide support? That a bad translation?

[–] tal@lemmy.today 92 points 8 hours ago* (last edited 8 hours ago) (4 children)

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 8 points 5 hours ago (1 children)

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 6 points 4 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 39 points 7 hours ago (2 children)

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 21 points 6 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 6 points 6 hours ago* (last edited 6 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.

[–] YaksDC@sh.itjust.works 33 points 8 hours ago (1 children)

This is the correct reaction to old home equipment.

[–] BearOfaTime@lemm.ee 11 points 8 hours ago (2 children)

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.

[–] jabathekek@sopuli.xyz 3 points 6 hours ago

My cat likes how much heat they make too.

[–] metaStatic@kbin.earth 3 points 8 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 5 points 6 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.

[–] sunzu2@thebrainbin.org 25 points 8 hours ago

don't buy shit unless it runs openwrt or whatever

[–] sunbeam60@lemmy.one 4 points 5 hours ago

I moved to an OPNsense router a couple of years ago and I’ve never looked back. Hell is shitty consumer routers.

[–] andyortlieb@lemmy.sdf.org 5 points 6 hours ago* (last edited 6 hours ago)

Commodity hardware & open source software for the win.

When my Western Digital NAS was never going to get critical security patches, I was so freaking glad to find out that they just used software raid... I threw the HDDs in a Debian server and never looked back.

It's certainly nice to have things that are turn-key, but if you can find your way around any OS, just avoid proprietary everything.

[–] ch00f@lemmy.world 4 points 6 hours ago (1 children)
[–] pastermil@sh.itjust.works 3 points 3 hours ago

OpenWRT is. Not sure if it's supported on that hardware tho.

[–] skillissuer@discuss.tchncs.de 11 points 8 hours ago* (last edited 8 hours ago)

but does it run openwrt?

e: no it doesn't, only one model had half-baked image made and available for download from some sketchy forum post made in 2014

[–] Hobbes_Dent@lemmy.world 5 points 7 hours ago (1 children)
[–] Deebster@infosec.pub 6 points 6 hours ago

I watched and enjoyed that one yesterday, and he's bang on the money. People here are saying "well it's EoL" but that means it's got all the way through development and its full lifetime with such a prominent set of bugs.

I don't think I'll be buying D-Link if that's what supported means.

[–] Someonelol@lemmy.dbzer0.com 1 points 5 hours ago

Instead of trusting DLink with an off the shelf NAS, it might be easier to build your own with a Raspberry Pi running openmediavault hooked up to a couple of USB hard drives. It's worked well for me for over 6 years now with no issue and could cost way less.

[–] FutileRecipe@lemmy.world 4 points 7 hours ago

Same website (granted, different author, but), same inflammatory language, same vendor, referencing previous erroneous article...I'm not even gonna read this one. Just going to copy/paste my previous response from the previous post:

At a certain point it's the consumer's (and blog writer's) fault, and that's after EoL. Not patching a supported one and just getting rid of support, saying buy a newer one? Yeah, that's bad.

Continuing to not support an EoL model that you already don't support due to EoL (or even dropping support for an EoL model that no one expected you to support in the first place due to EoL)? Non-issue.