I have seen a Cisco router with 17 years of uptime in an internet exchange in Canada.
Who needs security patching or maintenance support anyway.
Who said it was connected to the internet?
Who said only internet-facing assets need to be patched?
Who said it was connected to a network?
What would be the point of a router not connected to any network?
I dunno. Development? Ask OP.
This comment thread is about an unpatched router (probably in production) at a Canadian Internet exchange
Developing for a 17 year old router
Not rebooting for security patches isn’t something to be proud of.
On the other hand, network partitioning and security that means you don’t have to reboot an internal device for security patches is something to be proud of.
On my site we have tons of archaic, unpatchable industrial devices.
It is if the reason is there are no security vulnerabilities to patch, which is highly unlikely. When you bought things they used to be fully functional and working for the rest of their life. Now we expect everything to be broken and require constant revisions, it’s terrible we expect all software to be of such a low quality that it’s ships with vulnerabilities.
There are ways to apply patches without rebooting but it requires super advanced understanding of the kernel, individual packages, and how they work. Rebooting is just the idiot’s catch-all solution. One of Red Hat’s biggest selling points is their live patched kernel. It takes a kernel hacker level of understanding to pull off live patching on your own.
Oracle Unbreakable Enterprise Linux patches the kernel live when you dnf update
I’m tired boss
I had a old ubuntu file server running on a PIII that ran for 2ish years. I thought that was impressive, but 6 is pretty awesome for non-enterprise grade hardware.
