WRT54G v4 - internet very slow during morning

[musicman2059]

My WRT54G has been working perfectly for the last 6 months, but two week ago it decided it wanted to start acting up.

During the morning hours, usually for at least one hour between 9AM and 1PM, my internet decides it wants to act super duper slow. Web pages, including google, seme to take at least 5 minutes to load. I can still somehow connect to other services such at AIM and IRC, but any attempt to try to play a game at this time would be, of course, futile. (And I have problems with my games lagging out every 5-10 minutes for a bit before and after this happens)

Usually when this happens, though, I can ping fine in most cases.

This was a bit from my router pinging google during the last time this happened:

64 bytes from 216.239.57.104: icmp_seq=807 ttl=243 time=37.6 ms
64 bytes from 216.239.57.104: icmp_seq=808 ttl=243 time=37.5 ms
64 bytes from 216.239.57.104: icmp_seq=809 ttl=243 time=42.4 ms
64 bytes from 216.239.57.104: icmp_seq=810 ttl=243 time=38.8 ms
64 bytes from 216.239.57.104: icmp_seq=811 ttl=243 time=37.9 ms
64 bytes from 216.239.57.104: icmp_seq=812 ttl=243 time=37.9 ms
64 bytes from 216.239.57.104: icmp_seq=813 ttl=243 time=37.7 ms
64 bytes from 216.239.57.104: icmp_seq=814 ttl=243 time=37.5 ms
64 bytes from 216.239.57.104: icmp_seq=815 ttl=243 time=45.1 ms
64 bytes from 216.239.57.104: icmp_seq=816 ttl=243 time=37.7 ms
64 bytes from 216.239.57.104: icmp_seq=817 ttl=243 time=37.9 ms
64 bytes from 216.239.57.104: icmp_seq=818 ttl=243 time=58.6 ms
64 bytes from 216.239.57.104: icmp_seq=819 ttl=243 time=37.9 ms
64 bytes from 216.239.57.104: icmp_seq=820 ttl=243 time=38.0 ms
64 bytes from 216.239.57.104: icmp_seq=821 ttl=243 time=38.6 ms
64 bytes from 216.239.57.104: icmp_seq=822 ttl=243 time=37.8 ms
64 bytes from 216.239.57.104: icmp_seq=823 ttl=243 time=38.3 ms

And from my computer... (Note that this is from just now, so it's not really having any problems. Usually when this happens I get an occasional timeout, a few good pings, and then a string of 4 or 5 timeouts together)

Pinging google.ca [216.239.59.104] with 32 bytes of data:



Request timed out.

Reply from 216.239.59.104: bytes=32 time=201ms TTL=235

Reply from 216.239.59.104: bytes=32 time=202ms TTL=235

Reply from 216.239.59.104: bytes=32 time=200ms TTL=235

Reply from 216.239.59.104: bytes=32 time=201ms TTL=235

Reply from 216.239.59.104: bytes=32 time=203ms TTL=235

Reply from 216.239.59.104: bytes=32 time=202ms TTL=235

Reply from 216.239.59.104: bytes=32 time=203ms TTL=235

Reply from 216.239.59.104: bytes=32 time=202ms TTL=235

Reply from 216.239.59.104: bytes=32 time=202ms TTL=235



Ping statistics for 216.239.59.104:

Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),

Approximate round trip times in milli-seconds:

Minimum = 200ms, Maximum = 203ms, Average = 201ms

Any suggestions? I talked to linksys and the first person I tried talking to suggested to lower my MTU to 1300 from 1500. It didn't solve anything so I talked to another represenative and they said to reset it, but I wanna see if there's anything else I can do before having to go through that.

EDIT: I should also note too that this is happening on both wireless and wired connections.

[musicman2059]

(DP)

Okay, it just happened again and I was able to get what ping looked like from my computer when this happens:

Reply from 216.239.57.104: bytes=32 time=35ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=35ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=36ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.57.104: bytes=32 time=40ms TTL=242
Reply from 216.239.57.104: bytes=32 time=34ms TTL=242
Reply from 216.239.57.104: bytes=32 time=41ms TTL=242
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Request timed out.
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Request timed out.
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Reply from 216.239.57.104: bytes=32 time=39ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Reply from 216.239.57.104: bytes=32 time=38ms TTL=242
Reply from 216.239.57.104: bytes=32 time=37ms TTL=242
Reply from 216.239.57.104: bytes=32 time=35ms TTL=242
Reply from 216.239.57.104: bytes=32 time=35ms TTL=242

It seems to be happening more frequently now. I tried restoring my router's defaults and recofiguring it but that didn't work either.

[qwerty on my forehead]

i have that same problem wrt54g . but i used the optimizer and it got better . i think it may be the isp because ive tried evry setting and knob . the optimizer helps . calll your isp and ask them to check out your status . my isp usually finds something wrong . too bad they dont run cable out here in the stix

[YeOldeStonecat]

Which version wrt54g?
Guessing you're on cable?
Do you run any P2P file downloading programs?

[qwerty on my forehead]

i have v.5 and i use a p2p ( ares ) and im on wi fi

[musicman2059]

I tried the optimizer and it worked great for a while, but the next day it just went back to being the same old stuff.

Which version wrt54g?
Guessing you're on cable?
Do you run any P2P file downloading programs?

v4, DSL, and no.