Router installation

Post by **Edge100x** » Mon Apr 26, 2004 10:13 pm

acuraCLS wrote:you cant say that the pings are not sexy

more custom routes!

They're a little high sometimes right now, also, because incoming traffic isn't using our AT&T or Level3 connections (which adds a couple of hops sometimes, and maybe a few ms to the pings). This is because the RADB wasn't updated with our information, so AT&T and Level3 were ignoring our route announcements. We have had the RADB updated now, so that particular issue should disappear overnight.

StrawDragon · Post by **StrawDragon** » Tue Apr 27, 2004 1:39 pm

Edge100x wrote:
acuraCLS wrote:you cant say that the pings are not sexy

more custom routes!
They're a little high sometimes right now, also, because incoming traffic isn't using our AT&T or Level3 connections (which adds a couple of hops sometimes, and maybe a few ms to the pings). This is because the RADB wasn't updated with our information, so AT&T and Level3 were ignoring our route announcements. We have had the RADB updated now, so that particular issue should disappear overnight.

Nice... Last night was terrible... Maybe the router was overloaded, but the website was downloading at 20KB/s... Instead of my usual 400KB/s

Post by **Edge100x** » Tue Apr 27, 2004 6:47 pm

We have been needing to rate limit the hosted websites in order to put less stress on the router =\

StrawDragon · Post by **StrawDragon** » Tue Apr 27, 2004 9:15 pm

Ouch... But 20KB/s is rather poor

I can download that fast from the game server if I increased my maxinternetrate

Serving maps at 20KB is rather bad

Taken people about 10 minutes to download a small 12MB map

Post by **Edge100x** » Tue Apr 27, 2004 9:21 pm

We didn't rate limit individual sites, just the overall usage. I capped it at to the equivalent of two T1's when it is normally allowed to use up to 10mbps.

I've removed the temporary cap now.

Hussie · Post by **Hussie** » Wed Apr 28, 2004 7:38 am

i live in OC and am still hosed by this issue and i still see vario in my7 tracert i have emailed you two tracerts 1 to a seattle server and 1 to an oc server i have problems w/ both

Post by **Edge100x** » Wed Apr 28, 2004 7:40 am

I'm not seeing any unhandled messages in our account. That means that if you did send it to us, we replied, and are waiting on another response from you.

Hussie · Post by **Hussie** » Wed Apr 28, 2004 7:50 am

i just resent the email

Hussie · Post by **Hussie** » Wed Apr 28, 2004 8:45 am

you email did not work

Hussie · Post by **Hussie** » Wed Apr 28, 2004 9:46 am

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : oc.cox.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-0D-61-30-D1-7E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 68.4.10.217
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 68.4.10.1
DHCP Server . . . . . . . . . . . : 172.19.89.19
DNS Servers . . . . . . . . . . . : 68.4.16.25
68.2.16.30
68.6.16.30
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Wednesday, April 28, 2004 10:14:49 A
M
Lease Expires . . . . . . . . . . : Thursday, April 29, 2004 10:14:49 AM

C:\Documents and Settings\Owner>tracert 66.150.165.145

Tracing route to client.internap.seattle.nuclearfallout.net [66.150.165.145]
over a maximum of 30 hops:

1 30 ms * * ip68-4-10-1.oc.oc.cox.net [68.4.10.1]
2 12 ms * 75 ms ip68-4-14-153.oc.oc.cox.net [68.4.14.153]
3 14 ms * * 68.4.15.109
4 104 ms 17 ms * rsmtdsrc02-gew0304.rd.oc.cox.net [68.4.15.241]
5 * 20 ms * rsmtbbrc02-pos0101.rd.oc.cox.net [68.1.0.188]
6 * 105 ms 39 ms lvxxbbrc01-pos0102.rd.lv.cox.net [68.1.0.86]
7 40 ms 45 ms 41 ms paltbbrj01-pos010000.r2.pt.cox.net [68.1.0.95]
8 * 818 ms 38 ms f0.pao1.verio.net [198.32.176.14]
9 57 ms * * p16-0-1-1.r21.plalca01.us.bb.verio.net [129.250.
3.84]
10 * 99 ms 65 ms p16-0-1-1.r20.sttlwa01.us.bb.verio.net [129.250.
5.82]
11 82 ms * 85 ms ge-0-1-0.a12.sttlwa01.us.ra.verio.net [129.250.2
8.20]
12 58 ms 57 ms 55 ms p1-0-0-2.a12.sttlwa01.us.ce.verio.net [198.104.2
03.74]
13 * 71 ms 52 ms border5.ge2-1-bbnet2.sef.pnap.net [63.251.160.74
]
14 55 ms 52 ms 57 ms client.internap.seattle.nuclearfallout.net [66.1
50.165.145]

Trace complete.

PING to same:
C:\Documents and Settings\Owner>ping 66.150.165.145 -n 30

Pinging 66.150.165.145 with 32 bytes of data:

Reply from 66.150.165.145: bytes=32 time=58ms TTL=114
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Reply from 66.150.165.145: bytes=32 time=59ms TTL=114
Reply from 66.150.165.145: bytes=32 time=56ms TTL=114
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Request timed out.
Request timed out.
Reply from 66.150.165.145: bytes=32 time=50ms TTL=114
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Reply from 66.150.165.145: bytes=32 time=50ms TTL=114
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=51ms TTL=114
Reply from 66.150.165.145: bytes=32 time=50ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=50ms TTL=114
Reply from 66.150.165.145: bytes=32 time=52ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=51ms TTL=114
Reply from 66.150.165.145: bytes=32 time=54ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=51ms TTL=114
Reply from 66.150.165.145: bytes=32 time=52ms TTL=114
Request timed out.
Reply from 66.150.165.145: bytes=32 time=52ms TTL=114
Reply from 66.150.165.145: bytes=32 time=51ms TTL=114
Request timed out.
Request timed out.

Ping statistics for 66.150.165.145:
Packets: Sent = 30, Received = 20, Lost = 10 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 59ms, Average = 52ms

now to OC server:

C:\Documents and Settings\Owner>tracert occlan.nuclearfallout.net

Tracing route to occlan.nuclearfallout.net [64.94.100.34]
over a maximum of 30 hops:

1 * 14 ms 79 ms ip68-4-10-1.oc.oc.cox.net [68.4.10.1]
2 15 ms * 16 ms ip68-4-14-153.oc.oc.cox.net [68.4.14.153]
3 19 ms * * 68.4.15.109
4 14 ms * 13 ms rsmtdsrc02-gew0304.rd.oc.cox.net [68.4.15.241]
5 14 ms * * rsmtbbrc02-pos0101.rd.oc.cox.net [68.1.0.188]
6 20 ms 15 ms * rsmtbbrc01-pos0100.rd.oc.cox.net [68.1.0.182]
7 15 ms * 12 ms so-4-0.hsa2.Tustin1.Level3.net [65.59.168.1]
8 * 15 ms 16 ms so-7-0-0.mpls2.Tustin1.Level3.net [4.68.114.21]

9 15 ms * 23 ms so-0-1-0.bbr1.LosAngeles1.Level3.net [64.159.1.1
25]
10 16 ms * * so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9.
214]
11 20 ms * 17 ms uunet-level3-oc48.LosAngeles1.Level3.net [209.0.
227.38]
12 16 ms * * 0.so-1-0-0.XL2.LAX7.ALTER.NET [152.63.112.154]
13 * 23 ms * 0.so-4-0-0.CL2.LAX15.ALTER.NET [152.63.116.106]

14 15 ms * * POS7-0.GW2.LAX15.ALTER.NET [152.63.117.85]
15 16 ms * 16 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
16 * 16 ms 17 ms border1.ge3-1-bbnet1.ext1.lax.pnap.net [216.52.2
55.22]
17 * 25 ms * nuclearfallout-11.border1.ext1.lax.pnap.net [216
.52.220.214]
18 18 ms 14 ms * client.la.losangeles.nuclearfallout.net [64.94.1
00.34]
19 * * * Request timed out.
20 16 ms * 13 ms client.la.losangeles.nuclearfallout.net [64.94.1
00.34]
Trace complete.

And PINGfor OC server:
C:\Documents and Settings\Owner>ping occlan.nuclearfallout.net -n 30

Pinging occlan.nuclearfallout.net [64.94.100.34] with 32 bytes of data:

Reply from 64.94.100.34: bytes=32 time=25ms TTL=111
Reply from 64.94.100.34: bytes=32 time=17ms TTL=111
Reply from 64.94.100.34: bytes=32 time=20ms TTL=111
Reply from 64.94.100.34: bytes=32 time=16ms TTL=111
Reply from 64.94.100.34: bytes=32 time=17ms TTL=111
Reply from 64.94.100.34: bytes=32 time=21ms TTL=111
Reply from 64.94.100.34: bytes=32 time=25ms TTL=111
Reply from 64.94.100.34: bytes=32 time=19ms TTL=111
Reply from 64.94.100.34: bytes=32 time=21ms TTL=111
Reply from 64.94.100.34: bytes=32 time=28ms TTL=111
Request timed out.
Reply from 64.94.100.34: bytes=32 time=20ms TTL=111
Reply from 64.94.100.34: bytes=32 time=22ms TTL=111
Request timed out.
Reply from 64.94.100.34: bytes=32 time=14ms TTL=111
Request timed out.
Reply from 64.94.100.34: bytes=32 time=17ms TTL=111
Reply from 64.94.100.34: bytes=32 time=16ms TTL=111
Reply from 64.94.100.34: bytes=32 time=14ms TTL=111
Reply from 64.94.100.34: bytes=32 time=27ms TTL=111
Request timed out.
Request timed out.
Reply from 64.94.100.34: bytes=32 time=16ms TTL=111
Reply from 64.94.100.34: bytes=32 time=18ms TTL=111
Request timed out.
Reply from 64.94.100.34: bytes=32 time=18ms TTL=111
Request timed out.
Request timed out.
Reply from 64.94.100.34: bytes=32 time=18ms TTL=111
Request timed out.

Ping statistics for 64.94.100.34:
Packets: Sent = 30, Received = 21, Lost = 9 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 28ms, Average = 19ms

This is bad but it gets insanely worse if both my roommate and I try playing. we are using a Linksys router. I used this router previously In LA and experienced no problems.
This problem is so bad that we both quit playing last night.

Nick|NFo · Post by **Nick|NFo** » Wed Apr 28, 2004 10:25 am

the problem isnt lying with us, its your broadband provider. If you read your tracert, you are timing out on the COX network, especially your first hop.

1 30 ms * * ip68-4-10-1.oc.oc.cox.net [68.4.10.1]
2 12 ms * 75 ms ip68-4-14-153.oc.oc.cox.net [68.4.14.153]
3 14 ms * * 68.4.15.109

that is really bad news, and needs to be fixed by COX.

that first hop is from your modem to the gateway, should be under 10ms, once thats fixed, everything else will be better.

I know that Irvine COX is impacted immensely, if you live in that area. Their network is saturated and tried to provide more bandwidth then they could, and it doesnt help when everyone has COX, since they cant get dsl in that area of town depending on people.

To call COX Customer Care: 1-949-240-1212

StrawDragon · Post by **StrawDragon** » Wed Apr 28, 2004 1:21 pm

acuraCLS wrote:the problem isnt lying with us, its your broadband provider. If you read your tracert, you are timing out on the COX network, especially your first hop.

1 30 ms * * ip68-4-10-1.oc.oc.cox.net [68.4.10.1]
2 12 ms * 75 ms ip68-4-14-153.oc.oc.cox.net [68.4.14.153]
3 14 ms * * 68.4.15.109

that is really bad news, and needs to be fixed by COX.

that first hop is from your modem to the gateway, should be under 10ms, once thats fixed, everything else will be better.

I know that Irvine COX is impacted immensely, if you live in that area. Their network is saturated and tried to provide more bandwidth then they could, and it doesnt help when everyone has COX, since they cant get dsl in that area of town depending on people.

To call COX Customer Care: 1-949-240-1212

WOW, That tracert does suck... But I am glad I have comcast.. Its much better then COX!

Maybe you can get that?

Nick|NFo · Post by **Nick|NFo** » Wed Apr 28, 2004 1:51 pm

generally you are restricted to the cable provider in your area, which happens to be COX for him.

theres always alternatives, like DSL if its available. however, COX does the phone service as well, so at times like Irvine, you are restricted to COX, big monopoly in Irvine

always look at other companies, see if they can hook up off COX phone lines, like speakeasy.

Post by **Edge100x** » Wed Apr 28, 2004 2:20 pm

This is a serious packet loss problem starting at the first hop.

Packet loss is something that the cable company will fix. It's not something nebulous like 10 milliseconds of lag in an online game -- packetloss affects everything on your connection at the same time, and with the amount of loss he's getting, it will be hurting everything he does.

Definitely call Cox about that ASAP. It's probably easily fixed, something like a weak signal or noisy connection.

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

acuraCLS wrote:generally you are restricted to the cable provider in your area, which happens to be COX for him.

theres always alternatives, like DSL if its available. however, COX does the phone service as well, so at times like Irvine, you are restricted to COX, big monopoly in Irvine

always look at other companies, see if they can hook up off COX phone lines, like speakeasy.

Yes I am aware of that, but some areas offer more then one service

Such as I can get Adelphia or Comcast... But I prefer Comcast...

I dont live in Irvine, so I dont know what else is available... I was just giving him a suggestion