System transit time, Latency -

[Bob Goodwin - Zuni, Virginia, USA]

On 04/07/2012 06:03 PM, Joe Zeff wrote:
> On 04/07/2012 08:39 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
>>         How can I measure system transit time in this satellite system.
>>         I don't need great precision, just a rough idea of the time from
>>         here to the satellite, back down to the earth station/gateway,
>>         destination, and return.
>
> Traceroute will give you the IP address of the first router after the 
> satellite and the transit time.  Once you have that, you can simply 
> ping the router to get current data.


        I think traceroute probably tells me what I wanted to know, The
        system delay is > 600 ms.

            [bobg at box7 ~]$ traceroute cnn.com
            traceroute to cnn.com (157.166.226.26), 30 hops max, 60 byte
            packets
              1  192.168.1.1 (192.168.1.1)  1.551 ms  1.497 ms  1.452 ms
              2  * * *
              3  10.73.101.1 (10.73.101.1)  617.646 ms  629.846 ms 
            658.736 ms
            .............   snip   ................



        Putting that address into mtr system2 produces the same complaint.

            [bobg at box7 ~]$ mtr system2 --address  10.73.255.21
            Failed to resolve host: Name or service not known


        But now I know what I was looking for, apparently the "latency,"
        I prefer to think of it as system delay is about half what it
        had been on the old system. This is ViaSat/Wildblue's new 
        system. I'm seeing download speeds of 20 mbps best case,
        typically 13 - 14, about ten times what we had for the last six
        years.

        And no, I could not find ntpq for F-16/64. I found an RPM for
        F-15 but that wanted another that wasn't available ...

        Thanks for the help,

        Bob

        -- 
        http://www.qrz.com/db/W2BOD

        box7