Author Topic: AT&T packet loss (Read 508 times)

38ruk · « **on:** March 30, 2006, 01:38:36 AM »

Hey skuzzy , i seem to be having some packet loss at AT&T , any suggestions ? thx

Skuzzy · « **Reply #1 on:** March 30, 2006, 09:17:57 AM »

Is it constantly happening or has it calmed down?

38ruk · « **Reply #2 on:** March 30, 2006, 09:48:31 AM »

Nope it's still at it , looks like the route has changed towards the end . One question , how often does AH2 update ingame, every second, or is it in milliseconds? I'm running pingplotter at a 2.5 second ping interval , is that too fast ? Thx

Waffle · « **Reply #3 on:** March 31, 2006, 03:06:20 AM »

Oh man - I've been having that crap for the last 3-4 days. I'll see if I can dig up some plots.

Waffle · « **Reply #4 on:** March 31, 2006, 03:16:10 AM »

38ruk · « **Reply #5 on:** March 31, 2006, 08:02:11 AM »

How's your like to the MA waffle , i see your pinging the ip for all the other servers (AVA , DA ect. ect.).It's funny , ive only noticed the issue for the last 4-5 days .

Waffle · « **Reply #6 on:** March 31, 2006, 12:37:28 PM »

Yeah about last 4-5 days theres times when the whole net just slows down - actually took over 20 seconds one day to load this bullitin board..lol

I would fly over a feild strafing ack in a niki....didn't kill a one...figured my connex getting porked.

Skuzzy · « **Reply #7 on:** March 31, 2006, 01:45:35 PM »

Heya Waffle. Check this out. I traced to your second hop IP address and look what happened.

traceroute to 208.180.23.145 (208.180.23.145), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.655 ms 0.513 ms 0.475 ms
2 mdf1-gsr12-1-gig-1-0.dal1.attens.net (63.241.192.249) 0.195 ms 0.192 ms 0.150 ms
3 gar1-p310.kc9mo.ip.att.net (12.122.255.173) 0.962 ms 0.932 ms 0.906 ms
4 tbr2-p013801.dlstx.ip.att.net (12.123.17.62) 2.269 ms 2.404 ms 2.702 ms
5 gbr6-p40.dlstx.ip.att.net (12.122.12.90) 31.179 ms 1.363 ms 21.478 ms
6 gar3-p370.dlstx.ip.att.net (12.123.17.53) 1.565 ms 1.589 ms 1.100 ms
7 12.119.145.126 (12.119.145.126) 1.398 ms 1.372 ms 1.344 ms
8 dllsdsrj01-so000.rd.dl.cox.net (68.1.0.145) 1.368 ms 1.365 ms 1.339 ms
9 68.1.206.38 (68.1.206.38) 3.378 ms 68.1.206.6 (68.1.206.6) 172.587 ms 68.1.206.38 (68.1.206.38) 8.972 ms
10 bcstbbrc01-gew0501.ma.dl.cox-internet.com (66.76.45.146) 8.570 ms bcstbbrc02-gew0501.ma.dl.cox-internet.com (66.76.45.150) 5.215 ms bcstbbrc01-gew0501.ma.dl.cox-internet.com (66.76.45.146) 8.454 ms
11 cdm-208-180-23-130.bcst.cox-internet.com (208.180.23.130) 8.793 ms * *
12 10.20.0.1 (10.20.0.1) 7.793 ms * 7.795 ms

The IP address 10.20.0.1 should never show up in a trace, unless it is from the source. Pretty cool. I have not seen one those in a long time. Might want to point your ISP at this post.

Skuzzy · « **Reply #8 on:** March 31, 2006, 01:49:28 PM »

Now 38ruk, your trace is more typical. Here it is back your second hop.
==

traceroute to 69.95.14.65 (69.95.14.65), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.625 ms 0.535 ms 0.477 ms
2 mdf1-gsr12-1-gig-1-2.dal1.attens.net (63.241.192.205) 0.370 ms 0.219 ms 0.202 ms
3 gar1-p310.kc9mo.ip.att.net (12.122.255.173) 1.034 ms 0.935 ms 0.916 ms
4 tbr2-p013801.dlstx.ip.att.net (12.123.17.62) 2.494 ms 2.569 ms 2.184 ms
5 ggr1-p370.dlstx.ip.att.net (12.123.16.245) 1.046 ms 1.090 ms 0.985 ms
6 IPP-dllstx9lce1-pos5-0.wcg.net (64.200.232.201) 1.731 ms 1.827 ms 1.714 ms
7 dllstx1wcx2-pos11-2-oc48.wcg.net (64.200.105.45) 1.992 ms 1.976 ms 1.802 ms
8 dllstx1wcx3-pos9-0-oc48.wcg.net (64.200.110.74) 1.847 ms 1.875 ms 2.111 ms
9 hstntx1wcx3-pos1-0-oc192.wcg.net (64.200.210.66) 6.691 ms 6.714 ms 6.675 ms
10 hstntx1wcx2-pos6-0.wcg.net (64.200.186.77) 6.794 ms 6.841 ms 6.664 ms
11 drvlga1wcx2-pos12-0.wcg.net (64.200.240.78) 222.500 ms 186.309 ms 204.855 ms
12 hrndva1wcx3-pos14-0-oc192.wcg.net (64.200.210.238) 30.977 ms 31.164 ms 31.020 ms
13 hrndva1wcx2-pos4-0-oc192.wcg.net (64.200.89.121) 31.954 ms 32.884 ms 31.588 ms
14 nycmny2wcx2-pos1-0-oc192.wcg.net (64.200.210.177) 37.425 ms 37.425 ms 37.298 ms
15 nycmny2wcx3-pos11-3.wcg.net (64.200.68.98) 37.242 ms 37.253 ms 37.181 ms
16 nycmny1wce2-pos3-0.wcg.net (64.200.68.102) 37.554 ms 37.468 ms 37.586 ms
17 nycmny1wce2-choiceone-5-0.wcg.net (65.77.98.82) 46.100 ms 46.145 ms 46.173 ms
18 66.202.102.190 (66.202.102.190) 45.784 ms 45.837 ms *

Note the last hop IP address and note what I actually traced to. Also note it is an asynchronous route. Meaning, if the packet loss was really at the hop you indicate, it would have shown up in my trace. But due to the route back to your ISP being different than the one taken to the server, you cannot see where the actualy issue lies.

Of course, the really silly thing in this trace is how AT&T routes all outbound data to Kansas City, regardless of its destination, then from there back to Texas again. OY!!!! And no, they will not change it. They consider this to be efficient.

Waffle · « **Reply #9 on:** March 31, 2006, 02:01:31 PM »

I winged them an email with a link to this thread...will see what happens.

So what's the big deal with the 10.20.0.1?

Do I save more on long distance if I dial that?

Skuzzy · « **Reply #10 on:** March 31, 2006, 02:42:34 PM »

LOL!

The 10.x.x.x Class A IP address is not routable over the Internet. They are meant to be used for internal LAN use only.

38ruk · « **Reply #11 on:** March 31, 2006, 04:46:51 PM »

LOL from dallas to kansas city back to dallas ? Thats nuts lol. Thx for the trace back Skuz , basically that access number is now crossed off my list . I have many different routes i can take . I have a whole area code worth of numbers , with like 5 different routes , so ill find the next best one and check it . If i email you another route , think you could do a trace back to me again?? Pretty please 8) thx 38

IronDog · « **Reply #12 on:** March 31, 2006, 07:03:07 PM »

Bring back the other outfit,at least they tried.My con has went to heck.
IronDog

38ruk · « **Reply #13 on:** March 31, 2006, 11:03:22 PM »

Hey skuzzy , here are 2 other routes i can take . Can you check them for an asynchronous route please . Guess dial up has one advantage. My cable Co is supossed to have my street wired any day , good by dialup hell , well i better wait and see what the cable route is like heh. THX 38

Target Name: N/A
IP: 206.16.60.39
Date/Time: 3/31/2006 11:56:37 AM to 3/31/2006 11:57:00 AM

1 106 ms 112 ms 108 ms 105 ms 108 ms 112 ms 108 ms 110 ms 108 ms 107 ms nas50.chicago3.il.us.da.qwest .net [63.152.11.26]
2 107 ms 104 ms 107 ms 105 ms 114 ms 127 ms 114 ms 105 ms 103 ms 106 ms [63.152.30.254]
3 124 ms 112 ms 125 ms 118 ms 105 ms 195 ms 110 ms 119 ms 111 ms 124 ms cer-edge-02.inet.qwest.net [63.152.125.25]
4 117 ms 108 ms 123 ms 109 ms 122 ms 114 ms 127 ms 115 ms 128 ms 121 ms cer-core-02.inet.qwest.net [205.171.139.85]
5 108 ms 121 ms 115 ms 126 ms 114 ms 127 ms 119 ms 127 ms 125 ms 133 ms cer-brdr-01.inet.qwest.net [205.171.139.62]
6 128 ms 120 ms 129 ms 120 ms 108 ms 127 ms 114 ms 253 ms 220 ms 294 ms qwest-gw.cgcil.ip.att.net [192.205.32.97]
7 155 ms 141 ms 161 ms 148 ms 163 ms 153 ms 161 ms 154 ms 176 ms 159 ms tbr2-p014001.cgcil.ip.att.net [12.123.6.70]
8 146 ms 159 ms 152 ms 165 ms 156 ms 165 ms 158 ms 143 ms 162 ms 145 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
9 161 ms 155 ms 162 ms 156 ms 141 ms 161 ms 147 ms 177 ms 147 ms 159 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
10 156 ms 141 ms 161 ms 147 ms 163 ms 153 ms 160 ms 156 ms 168 ms 156 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
11 146 ms 159 ms 151 ms 166 ms 154 ms 164 ms 159 ms 171 ms 160 ms 173 ms gbr1-p70.dlstx.ip.att.net [12.122.12.78]
12 150 ms 136 ms 150 ms 143 ms 128 ms 147 ms 135 ms 150 ms 134 ms 154 ms gar1-p360.dlstx.ip.att.net [12.123.16.233]
13 142 ms 128 ms 146 ms 134 ms 150 ms 135 ms 147 ms 141 ms 152 ms 145 ms mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
14 135 ms 148 ms 161 ms 156 ms 142 ms 154 ms 147 ms 132 ms 148 ms 134 ms [63.241.192.50]
15 145 ms 137 ms 151 ms 142 ms 151 ms 149 ms 136 ms 144 ms 136 ms 149 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 136ms, Maximum = 151ms, Average = 144ms

Target Name: N/A
IP: 206.16.60.39
Date/Time: 3/31/2006 11:53:30 AM to 3/31/2006 11:53:53 AM

1 120 ms 122 ms 113 ms 120 ms 122 ms 118 ms 126 ms 124 ms 119 ms 120 ms roc1-dial2.popsite.net [64.24.144.3]
2 115 ms 112 ms 114 ms 111 ms 111 ms 113 ms 116 ms 113 ms 114 ms 114 ms roc1-core1-f0-0.starnetusa.net [64.24.144.1]
3 115 ms 112 ms 119 ms 115 ms 112 ms 114 ms 117 ms 111 ms 113 ms 115 ms ag-uslecroc-gigabitethernet9-34.rocny01.paetec.net [63.246.207.57]
4 148 ms 143 ms 145 ms 137 ms 138 ms 143 ms 139 ms 140 ms 141 ms 144 ms bb-vlan2-et1-1.rocny01.paetec.net [66.155.216.2]
5 136 ms 136 ms 141 ms 136 ms 132 ms 137 ms 136 ms 138 ms 133 ms N/A bb-oc12chi01-so6-0.chiil01.paetec.net [64.80.254.193]
6 134 ms 132 ms 133 ms 130 ms 126 ms 132 ms 139 ms 127 ms 128 ms 154 ms bb-vlan2-eth2-0-0.chiil01.paetec.net [66.155.191.4]
7 133 ms 130 ms 132 ms 128 ms 130 ms 142 ms 129 ms 130 ms 126 ms 128 ms [12.118.183.57]
8 155 ms 159 ms 153 ms 157 ms 148 ms 159 ms 151 ms 153 ms 149 ms N/A tbr2-p010901.cgcil.ip.att.net [12.123.6.6]
9 153 ms 153 ms 149 ms 151 ms 147 ms 149 ms 153 ms 153 ms 155 ms N/A tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
10 156 ms 159 ms 156 ms 150 ms 147 ms 168 ms 151 ms 148 ms 160 ms N/A tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
11 155 ms 152 ms 165 ms 156 ms 152 ms 164 ms 151 ms 147 ms 183 ms N/A tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
12 156 ms 159 ms 171 ms 157 ms 150 ms 152 ms 154 ms 158 ms 174 ms N/A gbr2-p100.dlstx.ip.att.net [12.122.12.82]
13 153 ms 150 ms 176 ms 153 ms 150 ms 151 ms 148 ms 149 ms 157 ms N/A gar1-p370.dlstx.ip.att.net [12.123.16.237]
14 153 ms 150 ms 171 ms 153 ms 149 ms 156 ms 153 ms 150 ms 151 ms N/A mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
15 155 ms 151 ms 163 ms 155 ms 148 ms 153 ms 151 ms 152 ms 153 ms N/A mdf1-bi8k-1-eth-2-2.dal1.attens.net [63.241.192.226]
16 153 ms 150 ms 147 ms 153 ms 155 ms 152 ms 148 ms 146 ms 157 ms N/A [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 146ms, Maximum = 157ms, Average = 151ms

Waffle · « **Reply #14 on:** April 07, 2006, 12:37:41 PM »

Well here's you answer on the AT&T routing:

http://www.hitechcreations.com/forums/showthread.php?s=&threadid=175160

lol!

I think the NSA is still holding some of my AH packets.....lmao!