Router installation

Shoe · Post by **Shoe** » Wed Apr 28, 2004 5:59 pm

(sigh)
got adelphia ~ just as bad....not much of a choice

Shoot self in right foot ~ choose adelphia
Shoot self in left foot ~ choose comcast

(sigh)

StrawDragon · Post by **StrawDragon** » Wed Apr 28, 2004 6:59 pm

Comcast is much better then adelphia.. Atleast in my section of CA

I rarely have an issue and my routing is always decent.. I ping to a buddys maine server under 80ms!

bOoya · Post by **bOoya** » Wed Apr 28, 2004 7:00 pm

i ping to an Atlanta NFo server at < 60ms

Post by **Edge100x** » Wed Apr 28, 2004 7:02 pm

Comcast uses the AT&T backbone which is very fast. Adelphia has isolated regional backbones that it interconnects with Verio and Level3 bandwidth. Verio has shown itself to be a very low-quality backbone and has led to our problems in LA.

aBstracT · Post by **aBstracT** » Wed Apr 28, 2004 7:07 pm

bOoya wrote:i ping to an Atlanta NFo server at < 60ms

Same here.

Hussie · Post by **Hussie** » Thu May 06, 2004 8:04 am

i really have no choice other than speakeasy and the price for what you get is not costeffective so i am calling Cox Cable every day till it is fixed but in the mean time... I remember edge saying he was routing around vario and i am still routed through them is this going to change at all?
BTW check this out--i am timing out like crazy today

Post by **Edge100x** » Thu May 06, 2004 10:58 am

On the Verio issue, make sure to email us a tracert so we can see if that's something that is affecting you. On the packet loss, since that is affecting your internet connection in general, make sure you escalate the issue when you call.

Hussie · Post by **Hussie** » Thu May 06, 2004 8:29 pm

rgr that

BigDaddy_az · Post by **BigDaddy_az** » Wed May 12, 2004 8:38 am

Hussie and I are roommates. Looks like part of the issue was I we had an SMC 7004VWBR router which, through trial and error, cannot handle the load needed to run to gaming comps. Stay away from that router if you are running a home network for gaming.

Now, regarding COX. They suck. We had them visit us a few times, had their engineers call us directly, talked to 2 managers/supervisors and the outcome was all the same.

You ping fine to various websites so the issue is not loss. Your tracert is fine (they looked at the one above) and it is not unusual to see a couple of timeouts in the path??

I think it is a maintenance issue with them, and they don't want to spend the money or time to fix it. We put in a new router and now we can play without lagging out or getting disconnected, but the ping for CS is awful in regards to our server. WE both have 100s, but like you said, I think the packet loss is factoring into that more than the fact that we are going through the verio network.

Anyhow, gaming is possible now, just at a crappy ping for our clans server.

Thanks for the tips and advice.

Peace,

[SU]BigDaddy

Post by **Edge100x** » Wed May 12, 2004 10:24 am

You might consider switching to our LA location if your other clan members are also in the southwest. We can control the routing much better in LA than we can in Seattle, and LA is also much closer to Phoenix than Seattle is.

Hussie · Post by **Hussie** » Sun May 16, 2004 5:54 pm

ok i had a buch of our seattle guys play on servers in LA and they had the same ping issues and they did tracerts the problems seemed to be in att route can you guys route around that too or just verio?
we are trying to get the best for everyone and right now the seattle one is suckin is this just us or are others experiencing problems too?

Post by **Edge100x** » Sun May 16, 2004 5:59 pm

I've never heard of problems with AT&T in LA. In fact, I am personally a Comcast customer in Seattle and I have no problems at all with our LA servers. I would need to see their tracert's to be able to diagnose that.

StrawDragon · Post by **StrawDragon** » Sun May 16, 2004 6:07 pm

I am wondering if he is having the timeout problem on a route between ATT and InterNAP...

I have had that problem since we switched to InterNAP, but it doesnt effect performance from what I can tell.

Post by **Edge100x** » Sun May 16, 2004 6:13 pm

If a hop entirely times out (three *'s in the trace for that hop), then it's most likely the case that the router is configured to not respond to that type of query. If this applies to them, then you're right that there is nothing to worry about. My trace to InterNAP LA looks like this and I do perfectly fine:

Code: Select all

C:\WINDOWS>tr www

NFO win32 trace tool v1.01, copyright (c)2004 Nuclearfallout Enterprises, Inc.

Tracing route to www [66.150.188.20]
with up to 30 hops:

 1   *        *        *       Request timed out.
 2   9.4 ms   8.0 ms   9.1 ms  12.244.20.241
 3   9.5 ms   8.9 ms   9.6 ms  12.244.0.13
 4  23.9 ms  24.0 ms   9.7 ms  12.244.72.18
 5  10.1 ms  11.2 ms  10.7 ms  tbr1-p012402.st6wa.ip.att.net [12.122.5.174]
 6  25.3 ms  28.1 ms  24.1 ms  tbr2-cl1.sffca.ip.att.net [12.122.12.113]
 7  33.9 ms  33.3 ms  33.6 ms  tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
 8  33.2 ms  33.1 ms  33.6 ms  gar1-p341.lsnca.ip.att.net [12.123.199.177]
 9   *        *        *       Request timed out.
10  33.9 ms  33.4 ms  34.1 ms  border1.ge3-1-bbnet1.ext1.lax.pnap.net [216.52.255.22]
11  36.2 ms  36.1 ms  36.8 ms  nuclearfallout-11.border1.ext1.lax.pnap.net [216.52.220.210]
12  34.6 ms  35.6 ms  34.3 ms  www.nuclearfallout.net [66.150.188.20]

Trace complete.

C:\WINDOWS>

But if there are other issues than that, we need to look into them.

Hussie · Post by **Hussie** » Sun May 16, 2004 8:47 pm

here is Lameducks tracert from seattle to LA

Code: Select all

Tracing route to outlawnation.nuclearfallout.net [64.94.100.53] 
over a maximum of 30 hops: 

 1     *        *        *     Request timed out. 
 2     9 ms     8 ms     9 ms  12.244.20.161 
 3    15 ms    11 ms    21 ms  12.244.0.21 
 4    12 ms    11 ms    11 ms  12.118.106.5 
 5    17 ms    11 ms    12 ms  tbr1-p012402.st6wa.ip.att.net [12.122.5.174] 
 6    31 ms    33 ms    29 ms  tbr2-cl1.sffca.ip.att.net [12.122.12.113] 
 7    37 ms    35 ms    37 ms  tbr1-cl3.la2ca.ip.att.net [12.122.10.26] 
 8    37 ms    35 ms    39 ms  gar1-p340.lsnca.ip.att.net [12.123.199.225] 
 9     *        *        *     Request timed out. 
10    35 ms    39 ms    37 ms  border1.ge3-1-bbnet1.ext1.lax.pnap.net [216.52.255.22] 
11    42 ms    44 ms    38 ms  nuclearfallout-11.border1.ext1.lax.pnap.net [216.52.220.210] 
12    37 ms    37 ms    44 ms  client.la.losangeles.nuclearfallout.net [64.94.100.53] 

Trace complete.

He knows the first one is his problem but that 9th one is not and that seems to be where his trouble is comming from.