WTH !!! .. AT&T sucks

[LA_MERC_T4rg3T]

Man, AT&T and Bayou are really screwing me over now.. When they switched to AT&T, we found one issue with our old router and replaced it. Then we found another issue that still has yet to be resolved but its on Bayou's end. Besides that, I started out at 15 hops from the server. NOW I'M 17 HOPS AWAY AND GOING THROUGH LOS ANGELAS?!?!?! The freaking server is 3-5 miles from my house.. WTH is going on ..

Sorry for the rant, it just ticks me off at times.

Look how stupid..

Tracert from my home to the LA_MERC game server



Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 8 ms 16 ms 30 ms 10.76.32.1
2 9 ms 9 ms 7 ms pos0-1-0.monrla-rtr1-jam.rr.com [24.162.64.6]
3 26 ms 27 ms 25 ms srp0-0.hstntxtid-rtr3.houston.rr.com [24.93.33.88]
4 29 ms 67 ms 27 ms son0-1-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.165]
5 54 ms 28 ms 29 ms pop1-hou-P0-1.atdn.net [66.185.133.145]
6 29 ms 28 ms 28 ms bb1-hou-P2-0.atdn.net [66.185.150.148]
7 31 ms 35 ms 34 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
8 32 ms 36 ms 49 ms pop1-dls-P0-0.atdn.net [66.185.133.81]
9 40 ms 56 ms 34 ms ATT.atdn.net [66.185.134.38]
10 33 ms 33 ms 39 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
11 74 ms 63 ms 65 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
12 64 ms 63 ms 65 ms tbr2-p012501.la2ca.ip.att.net [12.122.9.146]
13 83 ms 91 ms 82 ms tbr2-cl2.sl9mo.ip.att.net [12.122.10.13]
14 82 ms 84 ms 138 ms gbr6-p90.sl9mo.ip.att.net [12.122.11.126]
15 84 ms 81 ms 82 ms gar2-p370.sl9mo.ip.att.net [12.123.24.237]
16 109 ms 121 ms 99 ms 12.125.74.138
17 121 ms 100 ms 101 ms lamerc.bayou.com [209.209.214.5]

Trace complete.


Tracert to from my home to my server which also is uses AT&T



Tracing route to 209.142.136.39
over a maximum of 30 hops:

1 12 ms 8 ms 7 ms 10.76.32.1
2 17 ms 9 ms 7 ms pos0-1-0.monrla-rtr1-jam.rr.com [24.162.64.6]
3 52 ms 25 ms 27 ms srp0-0.hstntxtid-rtr3.houston.rr.com [24.93.33.88]
4 29 ms 26 ms 36 ms son0-1-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.165]
5 30 ms 49 ms 34 ms pop1-hou-P1-0.atdn.net [66.185.133.153]
6 25 ms 28 ms 30 ms bb1-hou-P2-0.atdn.net [66.185.150.148]
7 33 ms 35 ms 42 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
8 49 ms 31 ms 34 ms pop1-dls-P0-0.atdn.net [66.185.133.81]
9 33 ms 34 ms 31 ms ATT.atdn.net [66.185.134.38]
10 33 ms 47 ms 37 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
11 33 ms 35 ms 32 ms gbr6-p20.dlstx.ip.att.net [12.122.12.70]
12 35 ms 32 ms 36 ms gar2-p370.dlstx.ip.att.net [12.123.17.29]
13 37 ms 41 ms 40 ms 12.124.211.74
14 36 ms 40 ms 37 ms 209.142.136.39

Trace complete.


Tracert from my server to LA_MERC's game server which are both on AT&T


traceroute to 209.209.214.5 (209.209.214.5), 30 hops max, 40 byte packets
1 64.91.2.1 0.470 ms 0.369 ms 0.500 ms
2 12.124.211.73 6.074 ms 5.812 ms 5.661 ms
3 gbr5-p80.dlstx.ip.att.net (12.123.17.26) 5.754 ms 5.703 ms 5.743 ms
4 tbr1-p012401.dlstx.ip.att.net (12.122.12.65) 6.470 ms 6.367 ms 6.814 ms
5 tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 34.268 ms 34.267 ms 34.198 ms
6 tbr2-p012501.la2ca.ip.att.net (12.122.9.146) 32.778 ms 32.517 ms 32.624 ms
7 tbr2-cl2.sl9mo.ip.att.net (12.122.10.13) 72.778 ms 74.385 ms 73.467 ms
8 gbr5-p20.sl9mo.ip.att.net (12.122.11.122) 72.041 ms 90.669 ms 89.229 ms
9 gar2-p360.sl9mo.ip.att.net (12.123.24.233) 92.073 ms 90.148 ms 88.278 ms
10 12.125.74.138 129.478 ms 127.552 ms 125.621 ms
11 lamerc.bayou.com (209.209.214.5) 114.221 ms 114.311 ms 113.386 ms

[LA_MERC_YellowDog]

Im going back to cali.. to cali... to cali...HEHE

California... Thats wacked!

[LA_MERC_Heater]

I say we as a group go in and raise enough money for a year at a time and rent a better sever host like Cops,or Fa is on...get 50 or less pings on there sever..Or set up a perment sever like your backup..
I for one would be willing to donate for this cause..IMHO

[Apocalypse]

I as well

[LA_MERC_RiverRat]

I kinda have a good relationship with jerry at bayou and will mention this too him; but he will be out of town tomorrow so it will be Friday at the earliest that I can mention it to him....after all he values the advertisement we do for Bayou...

[roXet]

From my desk at work to the CS server


Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms cisco-gw.cp-tel.net [12.14.248.1]
2 14 ms 12 ms 12 ms 12.124.131.73
3 19 ms 19 ms 19 ms gbr1-p56.sl9mo.ip.att.net [12.123.198.33]
4 21 ms 20 ms 20 ms tbr1-p012502.sl9mo.ip.att.net [12.122.11.97]
5 20 ms 20 ms 19 ms gbr6-p100.sl9mo.ip.att.net [12.122.11.110]
6 19 ms 19 ms 19 ms gar2-p370.sl9mo.ip.att.net [12.123.24.237]
7 38 ms 38 ms 38 ms 12.125.74.138
8 38 ms 39 ms 38 ms lamerc.bayou.com [209.209.214.5]


A trace from here to the router in front of Toby's house


Tracing route to pos0-1-0.monrla-rtr1-jam.rr.com [24.162.64.6]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms cisco-gw.cp-tel.net [12.14.248.1]
2 12 ms 12 ms 12 ms 12.124.131.73
3 19 ms 19 ms 19 ms gbr2-p56.sl9mo.ip.att.net [12.123.198.37]
4 20 ms 20 ms 21 ms tbr2-p013602.sl9mo.ip.att.net [12.122.11.117]
5 27 ms 27 ms 27 ms tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
6 26 ms 26 ms 26 ms ggr2-p3120.cgcil.ip.att.net [12.123.6.69]
7 26 ms 26 ms 26 ms pop2-chi-P5-3.atdn.net [66.185.132.97]
8 26 ms 26 ms 26 ms bb1-chi-P1-0.atdn.net [66.185.148.64]
9 39 ms 39 ms 39 ms bb1-kcy-P7-0.atdn.net [66.185.152.125]
10 39 ms 40 ms 39 ms bb2-kcy-P1-0.atdn.net [66.185.152.127]
11 73 ms 73 ms 74 ms bb2-dls-P6-0.atdn.net [66.185.152.128]
12 68 ms 68 ms 68 ms bb1-dls-P2-0.atdn.net [66.185.153.28]
13 73 ms 77 ms 73 ms bb1-hou-P6-0.atdn.net [66.185.152.133]
14 79 ms 79 ms 78 ms pop1-hou-P3-0.atdn.net [66.185.150.149]
15 78 ms 78 ms 79 ms RR3-HOU.atdn.net [66.185.133.154]
16 75 ms 74 ms 75 ms pos15-0.hstntxtid-rtr3.texas.rr.com [24.93.33.16
6]
17 86 ms 85 ms 85 ms srp4-0.monrlahe-rtr2.texas.rr.com [24.93.33.85]

18 92 ms 92 ms 93 ms pos0-1-0.monrla-rtr1-jam.rr.com [24.162.64.6]

Trace complete.

Man, RR's links to AT&T really suck.

[LA_MERC_T4rg3T]

roxet, you're going through the same missouri att router that bayou goes through. You are basically going to that router and back to bayou, its in the same loop

[}{y|3ri|)]

i get 19 hops from here at work.

[JUNKY]

Toby -- here's my data from WM. Looks like we both ahve the same latenct building up at the Missourri router, but you seem to be affected more for some reason.

C:\Documents and Settings\Chris>tracert 209.209.214.5

Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 8 ms 7 ms 10.76.96.1
3 9 ms 9 ms 7 ms cs2416264-53.jam.rr.com [24.162.64.53]
4 24 ms 20 ms 20 ms srp0-0.hstntxtid-rtr3.houston.rr.com [24.93.33.8
8]
5 23 ms 20 ms 21 ms son0-1-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.16
5]
6 20 ms 32 ms 20 ms pop1-hou-P0-1.atdn.net [66.185.133.145]
7 20 ms 19 ms 19 ms bb1-hou-P2-0.atdn.net [66.185.150.148]
8 26 ms 25 ms 26 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
9 28 ms 25 ms 25 ms pop1-dls-P0-0.atdn.net [66.185.133.81]
10 26 ms 26 ms 28 ms ATT.atdn.net [66.185.134.38]
11 27 ms 27 ms 28 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
12 58 ms 58 ms 57 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
13 57 ms 58 ms 59 ms tbr2-p012501.la2ca.ip.att.net [12.122.9.146]
14 76 ms 75 ms 75 ms tbr2-cl2.sl9mo.ip.att.net [12.122.10.13]
15 73 ms 74 ms 74 ms gbr5-p20.sl9mo.ip.att.net [12.122.11.122]
16 74 ms 74 ms 73 ms gar2-p360.sl9mo.ip.att.net [12.123.24.233]
17 96 ms 94 ms 94 ms 12.125.74.138
18 96 ms 93 ms 93 ms lamerc.bayou.com [209.209.214.5]

Trace complete.

C:\Documents and Settings\Chris>

[eNdOfBeGinNinG]

anyone that plays on our server can tell there is something wrong with it. I can tell a huge difference just from going from merc server #1 to merc server #2 gameplay wise that is. I think merc getting the short end of the deal..=\

[Captain]

i take 17 hops to merc server and ping 120's in game


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert 209.209.214.5

Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 7 ms 7 ms 5 ms 10.76.96.1
2 50 ms 7 ms 5 ms cs2416264-49.jam.rr.com [24.162.64.49]
3 25 ms 23 ms 24 ms srp0-0.hstntxtid-rtr3.houston.rr.com [24.93.33.8
8]
4 26 ms 29 ms 27 ms son0-1-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.16
5]
5 29 ms 24 ms 25 ms pop1-hou-P0-1.atdn.net [66.185.133.145]
6 26 ms 44 ms 25 ms bb1-hou-P0-2.atdn.net [66.185.150.144]
7 33 ms 31 ms 30 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
8 31 ms 32 ms 31 ms pop1-dls-P0-0.atdn.net [66.185.133.81]
9 30 ms 32 ms 31 ms ATT.atdn.net [66.185.134.38]
10 31 ms 32 ms 32 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
11 64 ms 61 ms 61 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50]
12 62 ms 62 ms 81 ms tbr2-p012501.la2ca.ip.att.net [12.122.9.146]
13 81 ms 90 ms 100 ms tbr2-cl2.sl9mo.ip.att.net [12.122.10.13]
14 80 ms 78 ms 78 ms gbr5-p20.sl9mo.ip.att.net [12.122.11.122]
15 79 ms 82 ms 79 ms gar2-p360.sl9mo.ip.att.net [12.123.24.233]
16 97 ms 98 ms 99 ms 12.125.74.138
17 98 ms 101 ms 97 ms lamerc.bayou.com [209.209.214.5]

Trace complete.

[LA_MERC_LaTech]

yeah, my ping on #1 was 2-3 times what it was on #2

So my question is..."Who does #2 work for?!"

[LA_MERC_M@lACHi]

Here is mine, I get from 60-88 on Server #1

Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 9 ms 8 ms 11 ms 10.56.160.1
2 9 ms 9 ms 10 ms srp9-0.clmascmhe-rtr2.sc.rr.com [24.31.193.136]

3 14 ms 13 ms 13 ms pos0-1.chrlncsa-rtr2.carolina.rr.com [24.93.64.1
]
4 19 ms 18 ms 20 ms son0-0-3.chrlncsa-rtr6.carolina.rr.com [24.93.64
.61]
5 19 ms 19 ms 19 ms pop1-cha-P4-0.atdn.net [66.185.132.45]
6 20 ms 19 ms 20 ms bb2-cha-P0-2.atdn.net [66.185.132.38]
7 31 ms 31 ms 32 ms bb2-ash-P13-0.atdn.net [66.185.152.50]
8 31 ms 32 ms 31 ms pop2-ash-P1-0.atdn.net [66.185.139.211]
9 32 ms 32 ms 31 ms ATT.atdn.net [66.185.140.250]
10 34 ms 34 ms 33 ms tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
11 53 ms 52 ms 54 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
12 51 ms 52 ms 52 ms gbr5-p100.sl9mo.ip.att.net [12.122.11.106]
13 52 ms 52 ms 51 ms gar2-p360.sl9mo.ip.att.net [12.123.24.233]
14 71 ms 71 ms 70 ms 12.125.74.138
15 73 ms 70 ms 74 ms lamerc.bayou.com [209.209.214.5]

Trace complete.

[LA_MERC_Onji]

lol its nice from work


C:\>tracert 209.209.214.5

Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.1.2
2 3 ms 2 ms 2 ms router.willstaff.net [209.209.214.29]
3 5 ms 5 ms 4 ms router.bayou.com [209.209.192.1]
4 4 ms 5 ms 5 ms lamerc.bayou.com [209.209.214.5]

Trace complete.

[eNdOfBeGinNinG]

onji sucks... :p:

[LA_MERC_Onji]

trace from home on Bellsouth DSL:


1 16 ms 17 ms 16 ms 68.152.215.90
2 16 ms 17 ms 17 ms 68.152.215.101
3 23 ms 41 ms 23 ms 205.152.250.58
4 37 ms 47 ms 37 ms axr01asm-7-1-0-2.bellsouth.net [65.83.237.82]
5 37 ms 37 ms 37 ms pxr00asm-1-0-0.bellsouth.net [65.83.236.4]
6 46 ms 46 ms 46 ms so-1-0-0.gar1.Atlanta1.Level3.net [67.72.8.5]
7 46 ms 46 ms 47 ms so-6-0-0.gar2.Atlanta1.Level3.net [209.247.9.161]
8 46 ms 47 ms 46 ms so-0-3-0.bbr2.Atlanta1.Level3.net [209.247.11.225]
9 59 ms 59 ms 59 ms as-2-0.bbr1.Washington1.Level3.net [64.159.1.2]
10 64 ms 59 ms 59 ms so-6-0-0.edge2.Washington1.Level3.net [64.159.3.62]
11 61 ms 60 ms 60 ms ATT-Level3-oc48.Washington1.Level3.net [209.244.219.142]
12 61 ms 61 ms 63 ms tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
13 75 ms 75 ms 75 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
14 74 ms 73 ms 73 ms gbr6-p100.sl9mo.ip.att.net [12.122.11.110]
15 74 ms 74 ms 73 ms gar2-p370.sl9mo.ip.att.net [12.123.24.237]
16 96 ms 92 ms 92 ms 12.125.74.138
17 93 ms 91 ms 95 ms lamerc.bayou.com [209.209.214.5]

Trace Complete

[LA_MERC_T4rg3T]

Heater has the same connection as you, Onji. He was pinging in the 130's yesterday.

Seems that ATT changed up the router again before you did your tracert because I now see that its different and I'm back from 17 hops to 15 hops. It gets rediculas.

Also, you would think that Bellsouth would have you routed through TX then Missour instead of Atlanta then DC then Missouri.. Diesel? Dirge?

[LA_MERC_goose]

Someone give me a paypal link and I'll donate my 2cents for the new server location!

[Captain]

Damn Onji Play CS from work LoL

[LA_MERC_MadMAX]

mine....

[root@localhost root]# traceroute 209.209.214.5
traceroute to 209.209.214.5 (209.209.214.5), 30 hops max, 38 byte packets
1 10.56.128.1 (10.56.128.1) 10.020 ms 8.988 ms 7.882 ms
2 srp9-0.clmascmhe-rtr2.sc.rr.com (24.31.193.136) 12.578 ms 12.909 ms 11.819 ms
3 pos0-1.chrlncsa-rtr2.carolina.rr.com (24.93.64.1) 14.507 ms 14.960 ms 14.492 ms
4 son0-0-3.chrlncsa-rtr6.carolina.rr.com (24.93.64.61) 14.009 ms 17.960 ms 13.998 ms
5 pop1-cha-P4-0.atdn.net (66.185.132.45) 14.536 ms 17.019 ms 12.479 ms
6 bb2-cha-P0-2.atdn.net (66.185.132.38) 14.493 ms 12.525 ms 13.982 ms
7 bb2-ash-P13-0.atdn.net (66.185.152.50) 26.519 ms 26.209 ms 25.503 ms
8 pop2-ash-P1-0.atdn.net (66.185.139.211) 194.289 ms 24.551 ms 27.011 ms
9 aol-gw.wswdc.ip.att.net (192.205.32.5) 26.535 ms 25.311 ms 27.018 ms
10 tbr1-p011701.wswdc.ip.att.net (12.123.9.114) 27.015 ms 28.443 ms 26.957 ms
11 tbr1-cl4.sl9mo.ip.att.net (12.122.10.30) 47.116 ms 48.467 ms 48.040 ms
12 gbr6-p100.sl9mo.ip.att.net (12.122.11.110) 46.992 ms 47.432 ms 48.076 ms
13 gar2-p370.sl9mo.ip.att.net (12.123.24.237) 47.529 ms 49.416 ms 46.078 ms
14 12.125.74.138 (12.125.74.138) 64.572 ms 72.679 ms 65.154 ms
15 lamerc.bayou.com (209.209.214.5) 65.190 ms 66.307 ms 66.128 ms
[root@localhost root]#

[LA_MERC_Dirge]

The reason BellSouth routes through the others is that while BellSouth.Net acts as the ISP, once it hits the ATM "cloud" it can be routed anywhere. In fact, it's kind of like voice comm, the path is constantly changing. It's kind of hard to explain, but a multitude of different paths exist at any one time, and the software evaluates which path at each junction will produce the best signal and switches it back and forth through the junction points. The path changes due to load on paths. For example, at peak times, the primary path between two cities may fill up and alternate traffic will "spill over" to an alternate two or three or more paths in the ATM "cloud" Of course with all of this, each mega-service provider has their own paths which criss-cross all the other mega-ISP's. Also, ATM access points are still very expensive, so your signal may backhaul to several sites before it is able to bounce down out of the cloud.

Hope that helped explain why it looks like it bounces all over the place.

[1Str8G]

Some background on routing: (long and mainly for Toby and anyone else doing the CCNA thing)

The Open Shortest Path First (OSPF) protocol, defined in RFC 2328 , is an Interior Gateway Protocol used to distribute routing information within a single Autonomous System. This paper examines how OSPF works and how it can be used to design and build today's large and complicated networks.

OSPF versus RIP
The rapid growth and expansion of today's networks has pushed RIP to its limits. RIP has certain limitations that could cause problems in large networks:
RIP has a limit of 15 hops. A RIP network that spans more than 15 hops (15 routers) is considered unreachable.
RIP cannot handle Variable Length Subnet Masks (VLSM). Given the shortage of IP addresses and the flexibility VLSM gives in the efficient assignment of IP addresses, this is considered a major flaw.
Periodic broadcasts of the full routing table will consume a large amount of bandwidth. This is a major problem with large networks especially on slow links and WAN clouds.
RIP converges slower than OSPF. In large networks convergence gets to be in the order of minutes. RIP routers will go through a period of a hold-down and garbage collection and will slowly time-out information that has not been received recently. This is inappropriate in large environments and could cause routing inconsistencies.
RIP has no concept of network delays and link costs. Routing decisions are based on hop counts. The path with the lowest hop count to the destination is always preferred even if the longer path has a better aggregate link bandwidth and slower delays.
RIP networks are flat networks. There is no concept of areas or boundaries. With the introduction of classless routing and the intelligent use of aggregation and summarization, RIP networks seem to have fallen behind.
Some enhancements were introduced in a new version of RIP called RIP2. RIP2 addresses the issues of VLSM, authentication, and multicast routing updates. RIP2 is not a big improvement over RIP (now called RIP 1) because it still has the limitations of hop counts and slow convergence which are essential in todays large networks.

OSPF, on the other hand, addresses most of the issues presented above:
With OSPF, there is no limitation on the hop count.
The intelligent use of VLSM is very useful in IP address allocation.
OSPF uses IP multicast to send link-state updates. This ensures less processing on routers that are not listening to OSPF packets. Also, updates are only sent in case routing changes occur instead of periodically. This ensures a better use of bandwidth.
OSPF has better convergence than RIP. This is because routing changes are propagated instantaneously and not periodically.
OSPF allows for better load balancing.
OSPF allows for a logical definition of networks where routers can be divided into areas. This will limit the explosion of link state updates over the whole network. This also provides a mechanism for aggregating routes and cutting down on the unnecessary propagation of subnet information.
OSPF allows for routing authentication by using different methods of password authentication.
OSPF allows for the transfer and tagging of external routes injected into an Autonomous System. This keeps track of external routes injected by exterior protocols such as BGP.


OSPF uses a link-state algorithm in order to build and calculate the shortest path to all known destinations. The algorithm by itself is quite complicated. The following is a very high level, simplified way of looking at the various steps of the algorithm:
Upon initialization or due to any change in routing information, a router will generate a link-state advertisement. This advertisement will represent the collection of all link-states on that router.
All routers will exchange link-states by means of flooding. Each router that receives a link-state update should store a copy in its link-state database and then propagate the update to other routers.
After the database of each router is completed, the router will calculate a Shortest Path Tree to all destinations. The router uses the Dijkstra algorithm to calculate the shortest path tree. The destinations, the associated cost and the next hop to reach those destinations will form the IP routing table.
In case no changes in the OSPF network occur, such as cost of a link or a network being added or deleted, OSPF should be very quiet. Any changes that occur are communicated via link-state packets, and the Dijkstra algorithm is recalculated to find the shortest path.


In short, once you hit the cloud (the cloud is defined as the zone outside your ISP's border routers) you are using OSPF for packet routing. The internet is basically a mesh topolgy, you have multiple paths for everything. Each router in the "cloud" has a list of everything connected to each other, this is passed along by LSA's (look above). Based on the algorithm routers use it routed the packet via the shortest avialable path at that given time. You probably wonder wtf it routes all the way to L.A. and back then. You have primary switching stations across the country that most if not all traffic comes across, then you have the smallers nodes that everything paths into to get to the final destination. Say you go from Dallas to L.A. back to Dallas to get to the server, each location may have 20 routers moving packets at each location. You hit "router 1" in Dallas, the LSA is currently telling router 1 that all routers in Dallas are busy, it will be quicker to push the packet to L.A. to a free router that is connected to another router in Dallas that can push the packet now. This gives you all the hops and different hops for everyone, depending on current taffic and other factors. Sorry for the long post, hope this doesn't muddy the waters more :)

[JUNKY]

my brain hurts now

[LA_MERC_MadMAX]

I think it's the Flux capacitor

[LA_MERC_T4rg3T]

You left out BPG (border gateway protocol)

[}{y|3ri|)]

did i win? I do find it funny that i am the farthest away from the server, but get the best ping at home.. weeee too bad i suck though.

:dunno





Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert 209.209.214.5

Tracing route to lamerc.bayou.com [209.209.214.5]
over a maximum of 30 hops:

1 8 ms 7 ms 7 ms 10.228.32.1
2 8 ms 9 ms 7 ms 24.31.2.78
3 8 ms 10 ms 11 ms bic04-p2-0.rosehe1.mn.attbb.net [24.31.2.46]
4 20 ms 20 ms 21 ms 12.118.239.73
5 18 ms 17 ms 18 ms tbr2-p012301.cgcil.ip.att.net [12.123.6.13]
6 25 ms 24 ms 26 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
7 23 ms 23 ms 24 ms gbr5-p20.sl9mo.ip.att.net [12.122.11.122]
8 23 ms 23 ms 23 ms gar2-p360.sl9mo.ip.att.net [12.123.24.233]
9 42 ms 43 ms 41 ms 12.125.74.138
10 44 ms 45 ms 46 ms lamerc.bayou.com [209.209.214.5]

Trace complete.

C:\>

[Potential Threat]

My offer still stands. At the end of the summer I will have my xeon server up behind a t1 on a cisco network. If you want all I ask in return is admin privs. :D If so, give me till the end of this summer and I will have you ready to rock and role. By the way, the t1 is provided by CenturyTel in monroe who leases t1's from Bell South. That way the server can stay in the good ol Louisiana as well. Also, yeah, all server admins can have root ssh to my server as long as they dont mess with anything other than server stuff. ;)

[Pfhor]

What do you all ping to this?

165.95.168.2?

Ive heard different things from different people. Some people in Texas saying they ping 90+ and others pinging 20-30. Would you all run traces to it? Currently its on a dedicated DS3 that is also connected to I2.

IP ADDY changed from the original one. 165.95.168.2 now.