Print Page - Auto trace route on disco

Help and Support Forums => Technical Support => Topic started by: eskimo on March 08, 2000, 08:22:00 AM

Title: Auto trace route on disco
Post by: eskimo on March 08, 2000, 08:22:00 AM

Hey Pyro, would it be hard for you guys to write a program that would automatically start a trace route when there is a disco? Something that would recognize the "Host Connection Lost" window, begin a trace route, and store the date, time and data in a windows file would be a huge help to all of us morons.

I have only just learned about trace routes, and suspect that I am not the only moron out there. The other night I left the computer on, and logged into the game to see if it would stay connected throughout the night. It didn't. In the A.M. I had the "Host Connection Lost" window, but had no idea when the disco occurred, and of course was not able to do an immediate trace route. I can do a trace route from DOS, but I don't know how to copy it to post to you.

Anyway, us morons could use an auto-trace-route, or at least some coaching on them, or suggestions as to which to use.

By the way, I recently switched from a phone modem + Earthlink to a digital cable modem /ISP. I don't think it uses regular phone lines at all, from what I understand;

Cable to hub in Co Springs
Either net/fiber to Denver
Either net/fiber to Texas

I don't understand how I could be having the same problems as I did with phone modems, unless it's just a new set of problems that look the same? Most of my squad mates are also in Co. Springs and do not have as many problems/discos as I do. I checked on the score page and found that they had 0% to about 7% of sorties ending in discos. I am having over 30%. 1 other squad mate in C.S. has about 38%.

This disco problem started with the last release (P-38, tour 2) and has been a major bummer. I am not flying nearly as often as I used to. For the first time, I have had nights that I did not enjoy playing and have quit frustrated and angry. Please help the people out there who are too stupid to help themselves.
eskimo

Title: Auto trace route on disco
Post by: Lephturn on March 08, 2000, 08:32:00 AM

To make tracing your connection easier, go get Ping Plotter. http://www.nessoft.com/pingplotter/ (http://www.nessoft.com/pingplotter/)

This little gem is great, and from the Edit menu you can copy the info as text or as an image to the clipboard, and then paste it into any appliation. If you copy it as text, you can paste it directly into this BBS window. (http://bbs.hitechcreations.com/smf/Smileys/default/smile.gif)

Be sure to trace for a few minutes, so you have enough data to really show what's happening. Then paste it back here to the newsgroup like this:

Target Name: beta.hitechcreations.com
IP: 216.91.192.19

1 10 ms 9 ms 7 ms 31 ms 11 ms 10 ms 9 ms 8 ms 9 ms 11 ms 10 ms 10 ms 10 ms 11 ms 10 ms 11 ms 10 ms 11 ms 11 ms 10 ms hfx-doc-r42.eastlink.ca [24.222.42.1]
2 9 ms 10 ms 8 ms 8 ms 9 ms 9 ms 10 ms 9 ms 11 ms 9 ms 11 ms 16 ms 10 ms 10 ms 10 ms 9 ms 9 ms 9 ms 9 ms 312 ms hfxcore-e2-2.andara.com [24.222.0.1]
<--snip-->
16 79 ms 85 ms 80 ms 84 ms 83 ms 88 ms 83 ms 81 ms 83 ms 82 ms 83 ms 92 ms 79 ms 81 ms 80 ms 76 ms 81 ms 96 ms 77 ms 77 ms applink-1.usdlls.savvis.net [216.90.2.66]
17 81 ms 77 ms 81 ms 83 ms 82 ms 82 ms 82 ms 85 ms 77 ms 78 ms 77 ms 92 ms 77 ms 84 ms 76 ms 76 ms 83 ms 81 ms 77 ms 82 ms beta.hitechcreations.com [216.91.192.19]

A picture version is even better, since it includes more info in a better format. Also, you should add the date/time information if it's not included. Mine was run at 3/8/00 from 10:32:13 AM (AST) to 10:32:33 AM (AST). Note, you can also change the ping interval. The default is every five seconds, but I go to once every 2.5 seconds, or every 1 second for a more realistic picture and more data in a short period of time.

------------------
Lephturn - Chief Trainer
A member of The Flying Pigs
Visit Lephturn's Aerodrome for AH news, resources, and training data.
http://users.andara.com/~sconrad/ (http://users.andara.com/~sconrad/)
(http://tuweb.ucis.dal.ca/~dconrad/ahf/lepht.gif)

"MY P-47 is a pretty good ship
And she took a round coming 'cross the Channel last trip
I was thinking 'bout my baby and lettin' her rip
Always got me through so far
Well they can ship me all over this great big world
But I'll never find nothing like my North End girl
I'm taking her home with me one day, sir
Soon as we win this war"
- Steve Earl

[This message has been edited by Lephturn (edited 03-08-2000).]

Title: Auto trace route on disco
Post by: Pyro on March 08, 2000, 11:54:00 AM

There's some pretty functional tracetools out there as Leph mentioned that are really good. We're looking at putting some of our own connection diagnostic tools right into the game, but I don't know when we'll get to that.

------------------
Doug "Pyro" Balmos
HiTech Creations

"If it's stupid but works, it's not stupid."

Title: Auto trace route on disco
Post by: eskimo on March 08, 2000, 12:48:00 PM

Thanks Lephturn, Pyro
I will try it
eskimo

Title: Auto trace route on disco
Post by: Gator on March 08, 2000, 10:21:00 PM

"UO Trace" is also good, and it's freeware. http://www.blackcastlesoft.com/uotrace/index.html (http://www.blackcastlesoft.com/uotrace/index.html)

Does a very good job showing packet loss and average. As an example, here's savvis.net doing me in once I hit Dallas (11:15 PM Eastern, 8 March).

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
fe0-0-0.core1.anp.md.rcn.net 10.65.34.1 2 119ms 110ms 0% 16 / 16 86ms / 159ms
poet0-0-1.core1.col.md.rcn.net 207.172.9.197 3 262ms 256ms 0% 16 / 16 103ms / 605ms
poet6-0-0.core1.blb.md.rcn.net 207.172.19.170 4 105ms 120ms 0% 16 / 16 89ms / 258ms
poet1-0-0.core1.blba.md.rcn.net 207.172.9.53 5 287ms 124ms 0% 16 / 16 103ms / 287ms
poet4-1-0.core1.dcb.dc.rcn.net 207.172.19.218 6 120ms 115ms 0% 16 / 16 111ms / 133ms
pos1-1-0.border1.tcob.va.rcn.net 207.172.19.249 7 117ms 115ms 0% 15 / 15 96ms / 148ms
ge3-0-0.core1.tco.va.rcn.net 207.172.19.213 8 112ms 142ms 0% 15 / 15 104ms / 351ms
fe1-0-0.border2.tco.va.rcn.net 207.172.9.222 9 108ms 149ms 0% 15 / 15 104ms / 281ms
serial2-0-4.hsa1.wdc1.Level3.net 209.244.200.5 10 116ms 118ms 0% 15 / 15 91ms / 170ms
core1.NewYork1.Level3.net 209.244.2.19 11 138ms 137ms 0% 15 / 15 121ms / 159ms
level3-1.CR-1.usnycm.savvis.net 209.83.160.25 12 144ms 149ms 0% 15 / 15 114ms / 250ms
atm9-0-030.CR-1.usdlls.savvis.net 209.83.222.30 13 754ms 766ms 6% 14 / 15 747ms / 802ms
applink-1.usdlls.savvis.net 216.90.2.66 14 744ms 800ms 13% 13 / 15 744ms / 952ms
beta.hitechcreations.com 216.91.192.19 15 785ms 810ms 6% 14 / 15 743ms / 997ms

What the heck, tried it again 11:35 PM Eastern, couple of minutes of polling:

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
fe0-0-0.core1.anp.md.rcn.net 10.65.34.1 2 96ms 103ms 0% 26 / 26 85ms / 133ms
poet0-0-1.core1.col.md.rcn.net 207.172.9.197 3 221ms 179ms 0% 26 / 26 109ms / 395ms
poet6-0-0.core1.blb.md.rcn.net 207.172.19.170 4 114ms 113ms 0% 25 / 25 91ms / 165ms
poet1-0-0.core1.blba.md.rcn.net 207.172.9.53 5 110ms 125ms 0% 25 / 25 85ms / 319ms
poet4-0-1.core1.dcb.dc.rcn.net 207.172.9.49 6 111ms 118ms 0% 25 / 25 87ms / 289ms
pos1-1-0.border1.tcob.va.rcn.net 207.172.19.249 7 115ms 117ms 0% 25 / 25 99ms / 186ms
ge3-0-0.core1.tco.va.rcn.net 207.172.19.213 8 112ms 118ms 0% 25 / 25 98ms / 198ms
fe1-0-0.border2.tco.va.rcn.net 207.172.9.222 9 111ms 125ms 0% 25 / 25 105ms / 316ms
serial2-0-4.hsa1.wdc1.Level3.net 209.244.200.5 10 147ms 116ms 0% 25 / 25 95ms / 149ms
core1.NewYork1.Level3.net 209.244.2.19 11 137ms 142ms 0% 25 / 25 123ms / 187ms
level3-1.CR-1.usnycm.savvis.net 209.83.160.25 12 139ms 138ms 0% 25 / 25 121ms / 160ms
atm9-0-030.CR-1.usdlls.savvis.net 209.83.222.30 13 787ms 791ms 24% 19 / 25 758ms / 931ms
applink-1.usdlls.savvis.net 216.90.2.66 14 780ms 785ms 7% 23 / 25 757ms / 817ms
beta.hitechcreations.com 216.91.192.19 15 791ms 786ms 24% 19 / 25 753ms / 813ms

[This message has been edited by Gator (edited 03-08-2000).]

Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: eskimo on March 08, 2000, 08:22:00 AM