For several months, I experienced problems with my WRT54G Linksys router. This surprised me because I've had a long-term love affair with this router. It is one of very few pieces of hardware that I have actually recommended to friends/family, and most reviews agree (although it did take some hits after Cisco took over). The main symptom was that it would stop giving out IP addresses to DHCP requests after it had been online for some arbitrary amount of time. Generally speaking, we would reset it in the morning and be fine as long as no new devices wanted to connect throughout the day.
Of course, it's a little embarrassing and frustrating to have such lackluster performance. Here are a few of the assumptions and why there were all eventually ruled out:
- It was initially on a business Internet connection that could have been targeted by automated hack attempts since I previously hosted a few web sites at the external IP address. The router is a consumer router, so it seemed reasonable that it might not be able to handle a hack attempt. This was ruled out when we transitioned to a different Internet provider with no improvement.
- At various points in time, I have used some peer-to-peer networks. I know for certain that I have seen routers choke when there are too many inbound requests... This was ruled out after months of avoiding peer-to-peer networks.
- The router might have been going out. However, the router was replaced with another of the same model number without resolving the issue.
- It could have been overuse of the Internet connection, but the symptoms arise after a period of time -- not after a period of time of active use. This suggests that it results from an automated process -- either an external attack or an internal attempt to communicate outwards (more likely given #1).
A couple weeks ago, my desktop hard drive went out. I decided to switch my host OS from Kubuntu to Windows 7 (I use VMWare Player). The router problems have mostly gone away. It is hardly conclusive, but there are definitely some strong indications that the Linux desktop (or some problem with it) was part of the problem.
Nevermind... Two weeks later, the problems started up again -- so Ubuntu might be off the hook as the primary cause. I have further suspicions about the source of the problem, but nothing has been confirmed yet.