Author Topic: its a sad day in the land of the jacks (Read 5991 times)

applejacks · « **on:** May 24, 2004, 09:30:03 PM »

THE HORROR its been like this since sbc went on strike hehe the routers seem to have change and so has the route to xquake. never heard of these guys before but the border router before xquake is just total CRAP!!!
ahhh
my ping is been 60+- for the past 5days now

Art · « **Reply #1 on:** May 24, 2004, 09:57:15 PM »

Quick! , wanna play some 1v1 ? hehe

applejacks · « **Reply #2 on:** May 25, 2004, 08:43:06 AM »

bleh its still not getting any better. i dunno wtf is up with that router.
i ve heard there have been some routing probs in tx lately
i emailed that company but no replys so i telnetted to the router and tried to log in as:

FOR THE LOVE OF GOD FIX THIS ROUTER

well the above is a better way of saying what i said

hehehe

Hydro-cru · « **Reply #3 on:** May 25, 2004, 09:07:42 AM »

So my bribes to Allegiance Telecom,inc have paid off, muhahahahaha

spikeq2 · « **Reply #4 on:** May 25, 2004, 08:15:52 PM »

you knew the hamster running around inside his router would tire out eventually

Calvyn · « **Reply #5 on:** May 26, 2004, 06:48:24 AM »

Joo know it's probably a Cisco router...
Just get in there by exploiting the latest vuln, and reprogram it yourself..

Bad Monkey!

applejacks · « **Reply #6 on:** May 26, 2004, 07:53:32 AM »

hehe yea just set up acl to deny all and permit my ip/subnet only!!

Admin · « **Reply #7 on:** May 26, 2004, 11:54:43 AM »

Quote from: applejacks

THE HORROR its been like this since sbc went on strike hehe the routers seem to have change and so has the route to xquake. never heard of these guys before but the border router before xquake is just total CRAP!!!
ahhh
my ping is been 60+- for the past 5days now

I can assure you, that border router is not crap

It is our border router, we installed a new OC3 recently. I just logged into it, and the CPU, MEM and everything else is fine.

The problem with traceroutes is that they only show you one way, and do not display the latency of the packet coming back to you. So it may appear hop #12 is having problems, when actually the slow down is at #4!

Admin · « **Reply #8 on:** May 26, 2004, 12:01:55 PM »

Interesting.. the route back to you from that border router is through our sprintlink connection, not our algx connection:

core1.dal>ping 65.67.181.254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 65.67.181.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/38/40 ms
core1.dal>traceroute 65.67.181.254

Type escape sequence to abort.
Tracing the route to adsl-65-67-181-254.dsl.wcfltx.swbell.net (65.67.181.254)

1 fastethernet5-0-1-core2.dal.airmail.net (209.196.122.132) 0 msec 0 msec
fastethernet5-0-0-core2.dal.airmail.net (209.196.122.4) 4 msec
2 sl-gw34-fw-0-11.sprintlink.net (160.81.76.33) 4 msec 4 msec 4 msec
3 sl-bb22-fw-4-1.sprintlink.net (144.232.11.2) [AS 1239] 0 msec 4 msec 0 msec
4 sl-bb22-ana-8-1.sprintlink.net (144.232.9.249) [AS 1239] 32 msec 32 msec 36 msec
5 sl-bb21-ana-15-0.sprintlink.net (144.232.1.173) [AS 1239] 208 msec 72 msec 144 msec
6 sl-st20-la-13-0.sprintlink.net (144.232.20.67) [AS 1239] 32 msec 32 msec 32 msec
7 sl-sbcint-5-0.sprintlink.net (144.232.154.230) [AS 1239] 36 msec 32 msec 36 msec
8 bb1-p11-3.lsan03.pbi.net (151.164.191.242) [AS 7132] 32 msec 32 msec 32 msec
9 core1-p6-2.cranca.sbcglobal.net (151.164.241.214) [AS 7132] 36 msec 36 msec 32 msec
10 core2-p8-0.cranca.sbcglobal.net (151.164.241.226) [AS 7132] 32 msec 208 msec 212 msec
11 core1-p3-0.crrvca.sbcglobal.net (151.164.243.234) [AS 7132] 36 msec 40 msec 36 msec
12 core2-p11-0.crdltx.sbcglobal.net (151.164.243.222) [AS 7132] 36 msec 32 msec 32 msec
13 bb1-p11-1.dllstx.sbcglobal.net (151.164.240.89) [AS 7132] 36 msec 36 msec 32 msec
14 bb2-p15-0.dllstx.sbcglobal.net (151.164.243.150) [AS 7132] 32 msec 32 msec 36 msec
15 bb1-p1-0-0.wcfltx.sbcglobal.net (151.164.242.226) [AS 7132] 36 msec 36 msec 40 msec
16 dist1-vlan40.wcfltx.swbell.net (151.164.193.244) [AS 7132] 40 msec 40 msec 36 msec
17 adsl-65-67-181-254.dsl.wcfltx.swbell.net (65.67.181.254) [AS 7132] 44 msec 48 msec 48 msec

Admin · « **Reply #9 on:** May 26, 2004, 12:02:53 PM »

And here is from xquake itself:

mceder@arena$ traceroute 65.67.181.254
traceroute to 65.67.181.254 (65.67.181.254), 64 hops max, 40 byte packets
1 fe.49.ccb2.cidr.airmail.net (204.178.73.254) 0.938 ms 0.674 ms 1.043 ms
2 sl-gw34-fw-0-11.sprintlink.net (160.81.76.33) 1.993 ms 2.583 ms 2.303 ms
3 sl-bb22-fw-4-1.sprintlink.net (144.232.11.2) 5.274 ms 154.338 ms 3.554 ms
4 sl-bb22-ana-8-1.sprintlink.net (144.232.9.249) 25.717 ms 28.375 ms 25.793 ms
5 sl-bb21-ana-15-0.sprintlink.net (144.232.1.173) 26.322 ms 25.687 ms 25.900 ms
6 sl-st20-la-13-0.sprintlink.net (144.232.20.67) 28.975 ms 26.276 ms 26.529 ms
7 sl-sbcint-5-0.sprintlink.net (144.232.154.230) 35.489 ms 32.722 ms 32.551 ms
8 bb1-p14-3.lsan03.pbi.net (151.164.191.246) 33.113 ms 32.953 ms 32.693 ms
9 core1-p6-3.cranca.sbcglobal.net (151.164.241.218) 48.301 ms 184.266 ms 217.817 ms
10 core2-p8-0.cranca.sbcglobal.net (151.164.241.226) 33.390 ms 33.550 ms 33.663 ms
11 core1-p4-0.crrvca.sbcglobal.net (151.164.243.230) 37.913 ms 37.351 ms 37.759 ms
12 core2-p11-0.crdltx.sbcglobal.net (151.164.243.222) 33.378 ms 33.200 ms 34.241 ms
13 bb1-p14-3.dllstx.sbcglobal.net (151.164.240.97) 33.701 ms 33.635 ms 33.608 ms
14 bb2-p14-0.dllstx.sbcglobal.net (151.164.240.246) 33.314 ms 34.349 ms 33.618 ms
15 bb1-p1-0-0.wcfltx.sbcglobal.net (151.164.242.226) 38.938 ms 37.396 ms 38.393 ms
16 dist1-vlan30.wcfltx.swbell.net (151.164.193.228) 37.636 ms 37.600 ms 38.058 ms
17 adsl-65-67-181-254.dsl.wcfltx.swbell.net (65.67.181.254) 48.057 ms 52.876 ms 49.776 ms

applejacks · « **Reply #10 on:** May 26, 2004, 01:41:25 PM »

humm thats odd unless you take a different route out to me?
ive always ridden on the sprint route there before but around the same time sbc went on strike my ping doubled and i got on the aglx route
dunno but that one last router for me is just a pain!!!

it kinda feels like dial up my netgraph is still green but just spikes and what not..and more freezes and pauses

i think i need a new hampster!! hehe

applejacks · « **Reply #11 on:** May 26, 2004, 02:09:05 PM »

on the other hand why dont we just just hook up xquake to one of these and just give me a direct telepathic connection

http://news.com.com/Cisco%27s+%24500+million+router/2100-1033_3-5220313.html?tag=nefd.top

<<Hypno Bird>> · « **Reply #12 on:** May 26, 2004, 07:33:50 PM »

Excuse me while I cry. A 60 ping sounds pretty damn good to me

q2dude · « **Reply #13 on:** June 14, 2004, 04:53:50 AM »

Uhlouis, I would have thought the same thing at one time or another. The thing is though, if you're used to a certain ping and you're getting a ping that's 10 to 20+ ms higher than usual, for example.. you wouldn't like it. This is everyone I'd imagine ..

Really, anything below ..say 150 to 180 is good, IMO. But again, if you're not getting the ping you're used to..yeah, it sucks.

Author Topic: its a sad day in the land of the jacks (Read 5991 times)

El Box de Shoutamente