From: gremaux@en.ecn.purdue.edu (Douglas A Gremaux)
Newsgroups: rec.games.netrek
Subject: Re: Ping Times - Grrrr!
Summary: sesqui.net is hosed...
Date: 12 Apr 92 11:56:12 GMT
Distribution: na
Organization: Purdue University Engineering Computer Network

In article <12241@tamsun.tamu.edu> jeffw@cs.tamu.edu (Jeffrey A Waller) writes:
>In article <1992Apr11.014324.6669@wuecl.wustl.edu>, von@wucs1.wustl.edu (Steve Von Worley) writes:
>|> Has anyone noticed a stellar improvement in ping times to bronco within
>|> the last two days?  It used to be that average times below 130 ms were
>|> rare for me, with 150-200 ms being the average before midnight. 
>
>Actually I've noticed just the opposite.  We used to have ping times 
>like you (about 100-250ms).
>
>but now:
>
>----BRONCO.ECE.CMU.EDU PING Statistics----
>159 packets transmitted, 139 packets received, 12% packet loss
>round-trip (ms)  min/avg/max = 83/573/3934
>
>traceroute to bronco.ece.cmu.edu (128.2.210.65), 30 hops max, 40 byte packets
> 1  cscisco-gw (128.194.2.254)  22 ms  4 ms  4 ms
> 2  RTEVANS.TAMU.EDU (128.194.15.254)  6 ms  4 ms  4 ms
> 3  SESQUINET.TAMU.EDU (128.194.15.1)  6 ms  6 ms  6 ms
> 4  * RICE1-S10.sesqui.net (128.241.0.97)  471 ms  425 ms
  ^^^^^^^^^ this is where your problem is ^^^^^^^^^^^^^^^
  The rest of the numbers are rather meaningless since most of the
  lag is coming from RICE1-S10.  It seems to me though, the best you
  will get to bronco is about 80ms.
> 5  ENSS.sesqui.net (128.241.0.94)  418 ms  565 ms  239 ms
> 6  t3-1.cnss65.t3.nsf.net (140.222.65.2)  459 ms  176 ms  38 ms
> 7  t3-3.cnss64.t3.nsf.net (140.222.64.4)  242 ms  244 ms  180 ms
> 8  t3-0.cnss80.t3.nsf.net (140.222.80.1)  481 ms  301 ms  297 ms
> 9  t3-1.cnss24.t3.nsf.net (140.222.24.2)  612 ms  604 ms  547 ms
>10  t3-2.cnss40.t3.nsf.net (140.222.40.3)  444 ms  672 ms  496 ms
>11  t3-0.cnss41.t3.nsf.net (140.222.41.1)  432 ms  64 ms  63 ms
>12  t3-0.enss132.t3.nsf.net (140.222.132.1)  251 ms  216 ms  67 ms
>13  comet.psc.edu (192.5.146.16)  547 ms  110 ms  159 ms
>14  ROUTER.ECE.CMU.EDU (128.2.1.15)  161 ms  311 ms  524 ms
>15  BRONCO.ECE.CMU.EDU (128.2.210.65)  347 ms  621 ms  351 ms
>
 [pings deleted]
rhino.ecn.purdue.edu% traceroute  hpserv.tamu.edu  (6:30am EST sunday 4/12)
traceroute to hpserv.tamu.edu (128.194.7.8), 30 hops max, 38 byte packets
 1  zoo (128.46.152.78)  0 ms  0 ms  0 ms
 2  nsc1 (128.46.129.55)  20 ms  20 ms  20 ms
 3  enss152.gw.purdue.edu (192.5.102.1)  0 ms  0 ms  0 ms
 4  t1-1.cnss27.t3.nsf.net (140.222.27.2)  40 ms  20 ms  40 ms
 5  t3-3.cnss25.t3.nsf.net (140.222.25.4)  20 ms  40 ms  20 ms
 6  t3-3.cnss24.t3.nsf.net (140.222.24.4)  20 ms  40 ms  20 ms
 7  t3-2.cnss80.t3.nsf.net (140.222.80.3)  40 ms  20 ms  20 ms
 8  t3-1.cnss64.t3.nsf.net (140.222.64.2)  40 ms  60 ms  60 ms
 9  t3-0.cnss65.t3.nsf.net (140.222.65.1)  60 ms  40 ms  40 ms
10  t3-0.enss139.t3.nsf.net (140.222.139.1)  60 ms  60 ms  60 ms
11  rice2-ut1.sesqui.net (128.241.3.130)  60 ms  60 ms  60 ms
12  ut1-tamu.sesqui.net (128.241.0.33)  500 ms  520 ms  980 ms
13  RTEVANS.TAMU.EDU (128.194.15.254)  860 ms  1100 ms  640 ms
14  MILNER-STAR.TAMU.EDU (128.194.51.253)  460 ms  520 ms  660 ms
15  hpserv.math.tamu.edu (128.194.7.8)  740 ms  940 ms  880 ms

It seems other sesqui.net machines have problems too.

>						-Jeff

Douglas Gremaux