From: jsin@smogland.janet.ucla.edu (John Sin)
Newsgroups: rec.games.netrek
Subject: Re: trouble in the net
Keywords: calvin, lag
Date: 20 Aug 92 18:13:15 GMT
Organization: University of California at Los Angeles, EE Dept.

In article <l93rv4INNlor@girtab.usc.edu> rone@girtab.usc.edu (Ron Echeverri) writes:
>In article <josh.714185047@mowgli> josh@cqs.washington.edu (Josh Hayes) writes:
>
>>11  134.24.99.2 (134.24.99.2)  35 ms  504 ms  188 ms
>>				       ^^^     ^^^
>>					  yowee!
>hang-sdsc.cerf.net
>appropriately named, eh? :)
>
>nah.  somehow somehting is wrong with calvin's connections.  

Speaking of bad connections, here's what I get from my network to calvin:

traceroute to calvin.usc.edu (128.125.62.143), 30 hops max, 40 byte packets
 1  gw.janet.ucla.edu (128.97.92.1)  10 ms  0 ms  0 ms
 2  * * *
 3  canon.ucla.edu (128.97.128.70)  40 ms  10 ms  10 ms
 4  canon.ucla.edu (128.97.128.70)  10 ms  10 ms  10 ms
 5  cerfnet.ucla.edu (128.97.130.10)  10 ms  20 ms  10 ms
 6  losnet.ucla.edu (128.97.130.11)  10 ms  20 ms  20 ms
 7  cit-ucla-gw.ln.net (130.152.96.2)  70 ms  20 ms  30 ms
 8  usc-cit-gw.ln.net (130.152.128.1)  20 ms  120 ms  60 ms
 9   (128.125.253.8)  10 ms  20 ms  20 ms
10  calvin.usc.edu (128.125.62.143)  370 ms  20 ms  10 ms

traceroute to 128.125.253.129 (128.125.253.129), 30 hops max, 40 byte packets
 1  gw.janet.ucla.edu (128.97.92.1)  0 ms  10 ms  0 ms
 2  * * *
 3  canon.ucla.edu (128.97.128.70)  20 ms  10 ms  40 ms
 4  canon.ucla.edu (128.97.128.70)  10 ms  10 ms  10 ms
 5  cerfnet.ucla.edu (128.97.130.10)  10 ms  110 ms  10 ms
 6  losnet.ucla.edu (128.97.130.11)  10 ms  10 ms  20 ms
 7  isi-ucla-gw.ln.net (130.152.64.1)  20 ms  40 ms  10 ms
 8  usc-isi-gw.ln.net (130.152.32.2)  30 ms  10 ms  10 ms
 9  calvin.usc.edu (128.125.253.129)  80 ms  20 ms  20 ms

So UCLA - ISI - USC route seems a bit better (one less hop) then the
UCLA - CIT - USC route.  All in all, it's a pretty good connection as long
as all the gateways and routers are in working order (which seems to be
questionable sometimes).  Oh, and please, no jokes about the losnet.ucla.edu.

My typical ping time for 1000 byte packets is (recorded 11am, weekday):
   ----128.125.253.129 PING Statistics----
   200 packets transmitted, 200 packets received, 0% packet loss
   round-trip (ms)  min/avg/max = 58/85/356

Now, compare this to my next door neighbor, newton.physics.ucla.edu:

traceroute to newton.physics.ucla.edu (128.97.23.41), 30 hops max, 40 byte packe
ts
 1  gw.janet.ucla.edu (128.97.92.1)  0 ms  10 ms  0 ms
 2  * * *
 3  physics.ucla.edu (128.97.64.63)  10 ms  20 ms  60 ms
 4  physics.ucla.edu (128.97.64.63)  10 ms  10 ms  10 ms
 5  newton.physics.ucla.edu (128.97.23.41)  20 ms  10 ms  10 ms

Looks great, doesn't it?  But when I ping it, I get (recorded 11am, weekday):
   ----newton.physics.ucla.edu PING Statistics----
   200 packets transmitted, 193 packets received, 3% packet loss
   round-trip (ms)  min/avg/max = 19/109/3420

No wonder no one plays there.

UCLA is slowly converting to fiber internally (don't know when/how soon) 
and that would help some, but we also need to get spiffier routers/bridges
instead of using IBM PCs as routers.

It would be shame if Terence sets up a server for us and then no one came 
to play...
--
John Sin       <jsin@janet.ucla.edu>  ...!(uunet,ucbvax)!janet.ucla.edu!jsin
UCLA EE Dept.  53-109 Engineering IV, Los Angeles,  CA 90024   (310)206-7983
Newsgroups: rec.games.netrek