21/09/2008, 06:57 PM
okay router keeps screwing up (I assume it is the router (I have done nothing wrong to comcast recently(and the router is really the only recent network thing wee have changed))).
so wireless draft n router...
DIR-655 to be exact
WPA with AES
that's about it. Nothing more nothing less. Haven't changed much
Anyway speed test results first
you can see where the general decrease begins to show up
on the log page of the router it keeps saying
"[info] UDP 6112 Blocked"
and when I ping any domains I generally get this
Please wait, resolving http://www.google.com....
Resolved to 209.85.171.103.
Response from 209.85.171.103 received in 65 milliseconds. TTL = 241
Response from 209.85.171.103 received in 67 milliseconds. TTL = 241
Response from 209.85.171.103 received in 81 milliseconds. TTL = 241
No response from host, retrying...
Response from 209.85.171.103 received in 66 milliseconds. TTL = 241
No response from host, retrying...
No response from host, retrying...
User stopped
Pings sent: 7
Pings received: 4
Pings lost: 3 (42% loss)
Shortest ping time (in milliseconds): 65
Longest ping time (in milliseconds): 81
Average ping time (in milliseconds): 69
Now I wonder if it is construction because they are tearing up the entire main road of town and may have hit a cable.
Or I wonder if since S4 league uses p2p they think I am using torrents and punishing my bandwith severely.
of course there is always the option that it could be the router but idk...
so anyone have any ideas?
so wireless draft n router...
DIR-655 to be exact
WPA with AES
that's about it. Nothing more nothing less. Haven't changed much
Anyway speed test results first
you can see where the general decrease begins to show up
speedtest Wrote:3/20/2008 3:58 AM GMTsee what I mean?98.202.106.3518577 kb/s1845 kb/s27 msSalt Lake City, UT~ 50 miClose
3/20/2008 4:00 AM GMT98.202.106.3515834 kb/s1835 kb/s53 msLos Angeles, CA~ 600 miOpen
3/20/2008 4:01 AM GMT98.202.106.3515590 kb/s1842 kb/s28 msSalt Lake City, UT~ 50 miOpen
5/1/2008 12:11 AM GMT98.202.106.3513404 kb/s1236 kb/s28 msSalt Lake City, UT~ 50 miOpen
9/21/2008 11:53 PM GMT98.202.106.351046 kb/s284 kb/s49 msSalt Lake City, UT~ 50 miOpen
9/22/2008 12:00 AM GMT98.202.106.35500 kb/s228 kb/s49 msSalt Lake City, UT~ 50 miOpen
9/22/2008 12:05 AM GMT98.202.106.35870 kb/s292 kb/s51 msSalt Lake City, UT~ 50 miOpen
9/22/2008 12:08 AM GMT98.202.106.35570 kb/s310 kb/s49 msSalt Lake City, UT~ 50 miOpen
9/22/2008 12:24 AM GMT98.202.106.35468 kb/s299 kb/s92 msSalt Lake City, UT~ 50 miOpen
9/22/2008 12:28 AM GMT98.202.106.351789 kb/s354 kb/s50 msSalt Lake City, UT~ 50 miOpen
9/22/2008 1:45 AM GMT98.202.106.35278 kb/s281 kb/s51 msSalt Lake City, UT~ 50 miOpen
on the log page of the router it keeps saying
"[info] UDP 6112 Blocked"
and when I ping any domains I generally get this
Please wait, resolving http://www.google.com....
Resolved to 209.85.171.103.
Response from 209.85.171.103 received in 65 milliseconds. TTL = 241
Response from 209.85.171.103 received in 67 milliseconds. TTL = 241
Response from 209.85.171.103 received in 81 milliseconds. TTL = 241
No response from host, retrying...
Response from 209.85.171.103 received in 66 milliseconds. TTL = 241
No response from host, retrying...
No response from host, retrying...
User stopped
Pings sent: 7
Pings received: 4
Pings lost: 3 (42% loss)
Shortest ping time (in milliseconds): 65
Longest ping time (in milliseconds): 81
Average ping time (in milliseconds): 69
Now I wonder if it is construction because they are tearing up the entire main road of town and may have hit a cable.
Or I wonder if since S4 league uses p2p they think I am using torrents and punishing my bandwith severely.
of course there is always the option that it could be the router but idk...
so anyone have any ideas?