Threaded Mode | Linear Mode

Slushba132 · 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

speedtest Wrote:3/20/2008 3:58 AM GMT
	
98.202.106.35
	
18577 kb/s
	
1845 kb/s
	
27 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Close

3/20/2008 4:00 AM GMT
	
98.202.106.35
	
15834 kb/s
	
1835 kb/s
	
53 ms
	
Los Angeles, CA
	
~ 600 mi
	
Open

3/20/2008 4:01 AM GMT
	
98.202.106.35
	
15590 kb/s
	
1842 kb/s
	
28 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

5/1/2008 12:11 AM GMT
	
98.202.106.35
	
13404 kb/s
	
1236 kb/s
	
28 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/21/2008 11:53 PM GMT
	
98.202.106.35
	
1046 kb/s
	
284 kb/s
	
49 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 12:00 AM GMT
	
98.202.106.35
	
500 kb/s
	
228 kb/s
	
49 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 12:05 AM GMT
	
98.202.106.35
	
870 kb/s
	
292 kb/s
	
51 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 12:08 AM GMT
	
98.202.106.35
	
570 kb/s
	
310 kb/s
	
49 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 12:24 AM GMT
	
98.202.106.35
	
468 kb/s
	
299 kb/s
	
92 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 12:28 AM GMT
	
98.202.106.35
	
1789 kb/s
	
354 kb/s
	
50 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

9/22/2008 1:45 AM GMT
	
98.202.106.35
	
278 kb/s
	
281 kb/s
	
51 ms
	
Salt Lake City, UT
	
~ 50 mi
	
Open

see what I mean?

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?

Kaiser · 21/09/2008 07:00 PM

connect modem directly to pc. speedtest.
if connection is improved, trash the router
if connection still fails, go on a murderous rampage on your street for fudgeing up your internet (or call comcast and whine, your choice).

Slushba132 · 21/09/2008 07:10 PM

will do

S7* · 22/09/2008 01:59 AM

Kaiser Wrote:if connection still fails, go on a murderous rampage on your street for fudgeing up your internet (or call comcast and whine, your choice).

S7* · 22/09/2008 01:59 AM

Kaiser Wrote:if connection still fails, go on a murderous rampage on your street for fudgeing up your internet

LaneLander · 22/09/2008 06:29 AM

I have similar issues with my Netgear. I got rid of them by running smoothwall and slaving the Netgear as an AP. But then I had a hardware issue and needed to go backto the Netgear till I have replacement hardware. Works wonders.

Slushba132 · 23/09/2008 03:43 PM

I got it fixed...
Reflashed firmware...then unplugged everything and plugged it back in.
I'm back to 4000
but I'm still 1000 kb and I wonder why our connection isn't faster.

(5000kb was the most I ever got)
I wonder if the old modem slows us down

Threaded Mode \| Linear Mode Hey hey router, you're being kind of a bitch
Author	Message