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.
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.
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.
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.
EoL of anything should mean open source code. You don’t want to open source your code? Then you must keep servicing your products and must keep your servers up
I can still use a 2003 AMD Opteron with the newest builds of Linux. It’s an open standard. As long as the hardware still physically works. The only reason these pieces of hardware are EOL is because they chose to lock them down.
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.
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.
I’d support a regulation that defines either an expiration date or commitment to open source at the time the hardware is sold.
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.
This is the correct reaction to old home equipment.
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.
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.
EoL of anything should mean open source code. You don’t want to open source your code? Then you must keep servicing your products and must keep your servers up
I can still use a 2003 AMD Opteron with the newest builds of Linux. It’s an open standard. As long as the hardware still physically works. The only reason these pieces of hardware are EOL is because they chose to lock them down.