Long timeouts like that sound more like there's gear UPSTREAM at the ISP that has to timeout, not this equipment. Try this, instead of powering it off, physically DISCONNECT it from the cable modem. Wait that 3 minute period, reconnect it and see if the "problem" went away. I'm guessing it will.
That being the case there are other debug steps to consider.
Here's a thought, what other traffic was being routed through it? Is it an open wifi network? Might've been something else hammering a ton of traffic through the link and that tripped something on the ISP's side of things.
The WiFi segment is secured with WPA, and usually pretty light anyway. The bulk of my LAN traffic is on the wired side, including a gamer (sometimes 2). But the traffic wasn't unusually heavy when the router went funny.
I'm holding my breath, to see if the router (or whatever) goes awry again. This Linksys router is ~3 years old, and the previous router (Linksys) lasted for ~5 years before the radio front-end died.
There doesn't seem to be anything related to this problem in the release notes:
but methinks it's worth trying a firmware update anyway.
That's odd. You can connect to an SMTP server if you append a short message, but can't with a long message. The problem is that the initial SMTP connection is made *BEFORE* the message is sent. If it can't connect, it doesn't matter how long a message follows. Can you be more specific as to the error message?
weird. Look at the first setup page on the WRT54. What do you have for the MTU (maximum transfer unit)? For a cable modem, it should be
One possibility is that you have a sick router on the path between you and your SMTP server. Go unto:
and grab MTUROUTE.EXE v2.1. Run it and see if you can actually use
Same issue. Run MTUTROUTE pointing it to the web servers with problems. Compare with a web server that is close to your ISP and does not go through many other routers and spagetti.
It's possible. However, if there are any imparements involving SSL and encryption, you'll get a very different assortment of nasty error messages from the browser.
Weird 2.0. If it were an Max MTU problem, then it should show up on the downloads. However, that assumes that the downloads and the problem web sites go via the same router when leaving your ISP.
Smells like a buffer overflow problem in the router. Try the firmware update.
Yeah, it's weird. If you have another router, see if it does the same thing. That will at least determine if the router is at fault.
And when it does remove the ethernet cable from it first and wait the 3+ minutes. Or longer. You do want to rule out that it's not something being blocked upstream.
Hmm, here's another suggestion, change the hardware MAC address of the WAN port. It's buried in the setup pages on the router. This would, effectively, make the upstream network think a new device had been attached. This probably won't do anything. It's more likely any upstream filtering (or whatever) is tied to the IP address more than the MAC. If you change it make sure to change it back.
If the disconnecting doesn't work, then try powering down the DSL modem for that same delay. Couldn't hurt to rule it out.
It is not MTU; I've used MTU=1500 on the router and all PCs for years. And I only have one router in my LAN (I've stretched the 4-port LAN by using a hub to connect in 3 PCs that use the WAN sparingly).
Yeah, a buffer overflow fits. If it comes back, I may try to update the firmware, even though the firmware notes did not say anything about fixing this kind of problem.