Aces High Bulletin Board
General Forums => Axis vs Allies => Topic started by: Buzzbait on January 20, 2002, 04:14:54 AM
-
>>>>>>>>>>>>>
Ok, I still host the CT, so if you are having troubles there, I can do something about it, but I need information.
Please post me a traceroute to rt2.applink.net or to rt1.applink.net in the Internet forums if you are having troubles with the CT, as I cannot find a thing that would cause any problems on this side of the fence.
__________________
Roy "Skuzzy" Neese
President, AppLink Corp.
http://www.applink.net
skuzzy@applink.net
IP
-
how to do it? or do u just want us to ping the site?
-
use a program, i.e. ping plotter to do a traceroute, save the info, and then e-mail it to skuzzy, it's very easy to use.
-
didn't realize you were back from your cruise, welcome back!
-
Here's a couple typical traces to rt1 and rt2...
RT1...
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * xxx.xxx.xxx.xxx 1 40ms 39ms 0% 90 / 90 10ms / 230ms
rc2so-ge11-0.cg.shawcable.net 24.64.0.8 2 20ms 23ms 0% 90 / 90 0ms / 131ms
rc2ch-atm8-0-2.il.shawcable.net 204.209.214.150 3 40ms 54ms 0% 90 / 90 40ms / 150ms
ge-3-16.a01.chcgil01.us.ra.verio.net 129.250.223.53 4 50ms 66ms 0% 90 / 90 40ms / 241ms
ge-1-0-0.r02.chcgil01.us.bb.verio.net 129.250.27.29 5 40ms 57ms 0% 90 / 90 40ms / 141ms
p16-5-0-0.r01.chcgil01.us.bb.verio.net 129.250.2.220 6 100ms 60ms 0% 90 / 90 30ms / 130ms
p16-2-0-0.r01.chcgil06.us.bb.verio.net 129.250.5.70 7 80ms 58ms 0% 90 / 90 30ms / 130ms
p16-3-0-0.r01.dllstx01.us.bb.verio.net 129.250.5.85 8 71ms 82ms 0% 90 / 90 60ms / 170ms
ge-1-0-0.a10.dllstx01.us.ra.verio.net 129.250.28.164 9 120ms 86ms 0% 90 / 90 60ms / 171ms
fa-8-0-0.a09.dllstx01.us.ra.verio.net 129.250.28.170 10 60ms 96ms 0% 90 / 90 60ms / 340ms
rt1.applink.net 206.50.88.40 11 120ms 103ms 0% 90 / 90 70ms / 191ms
...and RT2
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * xxx.xxx.xxx.xxx 1 40ms 33ms 0% 71 / 71 10ms / 110ms
rc2so-ge11-0.cg.shawcable.net 24.64.0.8 2 20ms 23ms 1% 70 / 71 0ms / 120ms
VLN.Serialx-x-x.GWx.POPx.ALTER.NET 157.130.157.41 3 20ms 22ms 0% 71 / 71 10ms / 100ms
116.at-6-0-0.XR2.CAL1.ALTER.NET 152.63.137.158 4 20ms 20ms 0% 71 / 71 0ms / 90ms
192.at-1-0-0.TL2.CAL1.ALTER.NET 152.63.136.82 5 20ms 19ms 0% 71 / 71 0ms / 80ms
0.so-4-0-0.TL2.DFW9.ALTER.NET 152.63.0.182 6 80ms 77ms 0% 71 / 71 60ms / 150ms
0.so-7-0-0.XL2.DFW9.ALTER.NET 152.63.2.182 7 70ms 78ms 0% 71 / 71 60ms / 170ms
0.so-7-0-0.XR2.DFW9.ALTER.NET 152.63.102.2 8 70ms 80ms 0% 70 / 70 60ms / 140ms
184.ATM7-0.GW5.DFW9.ALTER.NET 152.63.100.45 9 70ms 83ms 0% 70 / 70 60ms / 130ms
savvis-dfw-gw.customer.ALTER.NET 157.130.155.234 10 71ms 87ms 1% 69 / 70 60ms / 150ms
savvis-internet.cntx04.usdlls2-bsn.savvis.net 64.241.96.94 11 110ms 91ms 0% 70 / 70 60ms / 220ms
* Unknown Host * 0.0.0.0 12 0ms
Only real difference between the two is RT2 doesn't reply to ICMP (what's the main peer point clients come in over anyway, RT1 or 2?). I have no idea what the setup is or how the code forces these pesky switches over to TCP. One would hope that is not an issue although anything is possibile. Nevertheless, both paths are fairly decent but I think its a given that the route across the Net isn't the cause. Something is triggering the push over to TCP at the point of hitting the arena server itself or coming into the local network. The problems with warps is of course that TCP is a poor gaming protocol and will cause problems for anyone coming in over anything less than a stellar connection. Stop that forced switch and make sure UDP remains the protocol being used, and you fix your problems.
Since this all started when the Stalingrad terrain was put in place, what happens when you switched the terrain back to the previous terrain? Does the problem still exist? If you haven't tried this I would suggest you do. I have no idea how or why the terrain would force you to TCP, but clearly that switch is triggered in the game code somewhere, so who knows by what. How or why a map would do it, I dunno. It certainly should be looked at if it hasn't already though, for nothing else just to eliminate a piece of the puzzle.
Also what are the packet sniffs saying? Someone should be doing these with the arena entry session. You should at least see from those what event is triggering the switch to TCP. That might give some insight.
Is the server side setup identical to the last session? Or were changes made there recently?
Vortex
-
No probs on RT1, but 100% packet loss on the last entry for RT2.
NeoTrace Trace Version 3.25 Results
Target: rt2.applink.net
Date: 1/20/2002 (Sunday), 9:24:13 PM
Nodes: 19
Node Data
Node Net Reg IP Address Location Node Name
1 - - ***.***.***.*** BRUXELLES (BRUSSE saintaw
2 1 - 212.68.228.1 Unknown
3 2 1 212.68.201.2 Unknown 212.68.201.2.brutele.be
4 2 - 212.68.203.194 Unknown
5 3 2 193.251.250.221 Unknown s2-0-0.bruar1.brussels.opentransit.net
6 3 2 193.251.128.137 Unknown p1-3.brubb1.brussels.opentransit.net
7 3 2 193.251.151.210 Unknown p0-0.brubb2.brussels.opentransit.net
8 3 2 193.251.154.162 AMSTERDAM p3-0.amsbb2.amsterdam.opentransit.net
9 3 2 193.251.240.157 Unknown p10-5.nykbb3.new-york.opentransit.net
10 3 2 193.251.241.237 Unknown p10-0.nykcr2.new-york.opentransit.net
11 3 2 193.251.241.234 Unknown p6-0.nykbb1.new-york.opentransit.net
12 - 3 144.232.235.189 New York sl-gw18-nyc-7-3.sprintlink.net
13 - 3 144.232.13.162 New York sl-bb21-nyc-12-1.sprintlink.net
14 - 3 144.232.18.69 Atlanta sl-bb21-atl-11-1.sprintlink.net
15 4 3 144.232.18.214 Fort Worth sl-bb20-fw-10-1.sprintlink.net
16 4 3 144.232.11.126 Fort Worth sl-gw20-fw-8-0.sprintlink.net
17 - 3 144.232.194.14 Unknown sl-savvis-2-0-0.sprintlink.net
18 5 4 64.241.96.94 Unknown savvis-internet.cntx04.usdlls2-bsn.savvis.net
19 6 5 216.91.192.44 Irving rt2.applink.net
Packet Data
Node High Low Avg Tot Lost
1 0 0 0 1 0
2 22 22 22 1 0
3 20 20 20 1 0
4 20 20 20 1 0
5 25 25 25 1 0
6 22 22 22 1 0
7 27 27 27 1 0
8 24 24 24 1 0
9 118 118 118 1 0
10 100 100 100 1 0
11 98 98 98 1 0
12 365 365 365 1 0
13 372 372 372 1 0
14 394 394 394 1 0
15 167 167 167 1 0
16 136 136 136 1 0
17 182 182 182 1 0
18 182 182 182 1 0
19 ---- ---- ---- 2 2
_____
NeoTrace Copyright ©1997-2001 NeoWorx Inc
-
Target Name: rt1.applink.net
IP: 206.50.88.40
Date/Time: 1/20/02 3:38:45 PM
1 24 ms 25 ms 24 ms 23 ms 23 ms 24 ms 24 ms 24 ms 25 ms 24 ms xxxx-xx-xxx-x.jax.bellsouth.net [xx.xx.xxx.x]
2 25 ms 26 ms 24 ms 25 ms 24 ms 24 ms 25 ms 25 ms 24 ms 25 ms xxxx-xx-xxx-x.jax.bellsouth.net [xx.xx.xxx.x]
3 25 ms 25 ms 24 ms 25 ms 24 ms 24 ms 25 ms 24 ms 24 ms 25 ms [xxx.xxx.xxx.xxx]
4 25 ms 25 ms 25 ms 25 ms 24 ms 24 ms 25 ms 24 ms 26 ms 25 ms 500.POS4-0.GW5.JAX1.ALTER.NET [63.122.229.249]
5 33 ms 33 ms 32 ms 33 ms 32 ms 32 ms 32 ms 32 ms 34 ms 33 ms 126.at-1-1-0.XR1.ATL1.ALTER.NET [152.63.84.226]
6 33 ms 33 ms 33 ms 32 ms 32 ms 33 ms 32 ms 32 ms 33 ms 33 ms 0.so-1-0-0.XL1.ATL1.ALTER.NET [152.63.86.85]
7 33 ms 33 ms 32 ms 32 ms 33 ms 32 ms 33 ms 32 ms 33 ms 32 ms 0.so-1-0-0.TL1.ATL5.ALTER.NET [152.63.85.217]
8 67 ms 69 ms 67 ms 68 ms 67 ms 69 ms 69 ms 68 ms 69 ms 67 ms 0.so-0-0-0.TL1.CHI2.ALTER.NET [152.63.13.17]
9 68 ms 72 ms 67 ms 67 ms 67 ms 68 ms 69 ms 68 ms 69 ms 68 ms 0.so-2-0-0.XL1.CHI2.ALTER.NET [152.63.67.126]
10 70 ms 71 ms 70 ms 70 ms 70 ms 70 ms 70 ms 70 ms 69 ms 70 ms POS6-0.BR1.CHI2.ALTER.NET [152.63.64.113]
11 68 ms 68 ms 67 ms 68 ms 67 ms 68 ms 68 ms 68 ms 67 ms 68 ms a3-0.uunet.chcgil01.us.bb.verio.net [204.255.169.14]
12 71 ms 71 ms 71 ms 72 ms 70 ms 71 ms 70 ms 71 ms 70 ms 70 ms p16-2-0-0.r01.chcgil06.us.bb.verio.net [129.250.5.70]
13 75 ms 74 ms 73 ms 74 ms 73 ms 73 ms 74 ms 74 ms 75 ms 74 ms p16-3-0-0.r01.dllstx01.us.bb.verio.net [129.250.5.85]
14 75 ms 75 ms 73 ms 74 ms 75 ms 73 ms 74 ms 74 ms 75 ms 73 ms ge-1-0-0.a10.dllstx01.us.ra.verio.net [129.250.28.164]
15 75 ms 75 ms 74 ms 74 ms 74 ms 75 ms 74 ms 74 ms 76 ms 74 ms fa-5-1-0.a09.dllstx01.us.ra.verio.net [129.250.31.61]
16 81 ms 88 ms 83 ms 80 ms 80 ms 83 ms 80 ms 81 ms 80 ms 82 ms rt1.applink.net [206.50.88.40]
Target Name: rt2.applink.net
IP: 216.91.192.44
Date/Time: 1/20/02 3:40:42 PM
1 25 ms 24 ms xxxx-xx-xxx-x.jax.bellsouth.net [xx.xx.xxx.x]
2 26 ms 24 ms xxxx-xx-xxx-x.jax.bellsouth.net [xx.xx.xxx.x]
3 24 ms 24 ms [xxx.xxx.xxx.xxx]
4 26 ms 24 ms 500.POS4-0.GW5.JAX1.ALTER.NET [63.122.229.249]
5 34 ms 31 ms 126.at-1-1-0.XR1.ATL1.ALTER.NET [152.63.84.226]
6 32 ms 32 ms 0.so-1-0-0.XL1.ATL1.ALTER.NET [152.63.86.85]
7 31 ms 31 ms 0.so-1-0-0.TL1.ATL5.ALTER.NET [152.63.85.217]
8 54 ms 53 ms 0.so-4-0-0.TL1.DFW9.ALTER.NET [152.63.0.181]
9 54 ms 55 ms 0.so-7-0-0.XL1.DFW9.ALTER.NET [152.63.0.194]
10 56 ms 54 ms 0.so-7-0-0.XR1.DFW9.ALTER.NET [152.63.101.250]
11 55 ms 54 ms 185.ATM7-0.GW5.DFW9.ALTER.NET [152.63.100.49]
12 58 ms 55 ms savvis-dfw-gw.customer.ALTER.NET [157.130.155.234]
13 55 ms 55 ms savvis-internet.cntx04.usdlls2-bsn.savvis.net [64.241.96.94]
14 * * [-]
15 * * [-]
16 * * [-]
17 * * [-]
18 * * [-]
19 * * [-]
20 * * [-]
21 * * [-]
22 * * [-]
23 * * [-]
24 * * [-]
25 * * [-]
26 * * [-]
27 * * [-]
rt2 unreachable even on rt1 and good pings on my end its so warpy in there its fer me unplayable. Always switches to tcp.
-
Skuzzy!
Trace to rt1:
1 19 ms 20 ms 21 ms adsl-40961.turboline.skynet.be [217.136.32.1]
2 29 ms 29 ms 29 ms at-0-1-0-45.adsl2.gam.brussels.skynet.be [194.78.255.237]
3 29 ms 29 ms 29 ms ge-1-1-0.intl1.gam.brussels.skynet.be [195.238.2.141]
4 31 ms 34 ms 32 ms gige5-0-115.ipcolo2.Brussels1.Level3.net [212.3.234.21]
5 26 ms 29 ms 30 ms unknown.Level3.net [212.3.239.165]
6 29 ms 29 ms 29 ms so-1-0-0.mp1.London1.Level3.net [212.187.128.1]
7 29 ms 29 ms 29 ms gigabitethernet1-0.core2.London1.Level3.net [212.187.131.14]
8 29 ms 29 ms 28 ms pos2-0.metro2-londencyh00.London1.Level3.net [212.113.0.117]
9 35 ms 34 ms 34 ms ge-1.linx.londen02.uk.bb.verio.net [195.66.224.139]
10 99 ms 99 ms 99 ms p4-1-0-0.r80.nycmny01.us.bb.verio.net [129.250.4.181]
11 99 ms 104 ms 108 ms p4-4-0-0.r04.nycmny01.us.bb.verio.net [129.250.5.11]
12 99 ms 104 ms 99 ms p16-4-0-0.r01.nwrknj01.us.bb.verio.net [129.250.5.12]
13 104 ms 99 ms 99 ms p4-2-1-0.r01.nycmny06.us.bb.verio.net [129.250.4.210]
14 99 ms 101 ms 104 ms p4-7-0-0.r00.nycmny06.us.bb.verio.net [129.250.4.192]
15 108 ms 106 ms 104 ms p4-4-0-0.r01.mclnva02.us.bb.verio.net [129.250.3.182]
16 104 ms 104 ms 105 ms p16-7-0-0.r00.stngva01.us.bb.verio.net [129.250.3.158]
17 140 ms 141 ms 163 ms p16-2-0-0.r02.dllstx01.us.bb.verio.net [129.250.5.34]
18 135 ms 139 ms 139 ms ge-0-0-0.a10.dllstx01.us.ra.verio.net [129.250.31.58]
19 139 ms 139 ms 139 ms fa-8-0-0.a09.dllstx01.us.ra.verio.net [129.250.28.170]
20 149 ms 149 ms 149 ms rt1.applink.net [206.50.88.40]
Trace to rt2:
1 22 ms 20 ms 19 ms adsl-40961.turboline.skynet.be [217.136.32.1]
2 29 ms 24 ms 24 ms at-0-0-0-101.adsl2.gam.brussels.skynet.be [194.78.255.181]
3 29 ms 25 ms 24 ms ge-1-1-0.intl1.gam.brussels.skynet.be [195.238.2.141]
4 24 ms 24 ms 29 ms gige5-0-115.ipcolo2.Brussels1.Level3.net [212.3.234.21]
5 25 ms 24 ms 24 ms unknown.Level3.net [212.3.239.165]
6 29 ms 29 ms 29 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]
7 100 ms 99 ms 99 ms so-1-0-0.mp2.Weehawken1.Level3.net [212.187.128.138]
8 129 ms 129 ms 129 ms so-2-0-0.mp1.Chicago1.Level3.net [64.159.0.233]
9 130 ms 129 ms 129 ms pos8-0.core1.Chicago1.Level3.net [209.247.10.162]
10 152 ms 132 ms 129 ms unknown.Level3.net [209.0.225.2]
11 159 ms 159 ms 154 ms at-1-2-0902.usdlls2-j20c.savvis.net [64.242.22.193]
12 156 ms 154 ms 154 ms savvis-internet.cntx04.usdlls2-bsn.savvis.net [64.241.96.94]
13 TIMEOUT from 13th hop (13th....what a coincidence ;) )
Last time I had a clean connection: last thursday.
Since then, I'm switched to TCP every time. And I tried a lot to get a clean connection...without any success. Game is still playable, but it reminds me 8-players rooms from MS CFS...lots of micro & mini-warps.
Thanks for you efforts,
-
Buzzbait = Skuzzy, am I the only one who didn't know this.
Skuzzbait
F.
-
WOT??? He is Him himself ?
:D
-
S!
No, I'm not Skuzzy.
I just enlisted his services after I saw a post of his.
Just trying to make the CT work... :confused:
-
ok