(no subject)
My D-Link router didn't work with my Mac's wireless, and on top of that Ethernet ports started flooding the network with packets and generally misbehaving, so I ditched it and bought a Linksys router. This went against my years of experience telling me that Linksys products are crap.
Sure enough, it's 6 months later, and the thing developed a problem where it would freeze up a couple times an hour. And I mean really freeze up; even LAN traffic dies. Many times it revives itself somehow, but not always.
For lack of any other solutions, I decided to go third-party firmware. Mine is one of the newer Linksys routers that only has 2 MB of flash memory and runs VxWorks, but no matter; DD-WRT has a micro distribution designed for it.
Good news, I didn't brick my router. But this new firmware doesn't seem much more stable than the old one. In fact I'd say it's less stable, although I wonder if maybe it's a bug in the httpd serving the management pages. (The status pages have a 3 second auto-refresh, but after staring at it for a while the processor usage skyrockets and the router dies. Monitoring it over telnet instead, though, it has been up for a little while now.)
As a makeshift solution I set the Keep Alive option, which pings a site periodically and reboots the router if it can't reach it. That way I can at least have access during the day, even if it is interrupted.
Sure enough, it's 6 months later, and the thing developed a problem where it would freeze up a couple times an hour. And I mean really freeze up; even LAN traffic dies. Many times it revives itself somehow, but not always.
For lack of any other solutions, I decided to go third-party firmware. Mine is one of the newer Linksys routers that only has 2 MB of flash memory and runs VxWorks, but no matter; DD-WRT has a micro distribution designed for it.
Good news, I didn't brick my router. But this new firmware doesn't seem much more stable than the old one. In fact I'd say it's less stable, although I wonder if maybe it's a bug in the httpd serving the management pages. (The status pages have a 3 second auto-refresh, but after staring at it for a while the processor usage skyrockets and the router dies. Monitoring it over telnet instead, though, it has been up for a little while now.)
As a makeshift solution I set the Keep Alive option, which pings a site periodically and reboots the router if it can't reach it. That way I can at least have access during the day, even if it is interrupted.