1  cisco.NeoSoft.COM (198.64.6.254)  3 ms  3 ms  3 ms
 2  RICE4-S0.sesqui.net (128.241.9.49)  8 ms  99 ms  41 ms
 3  192.67.13.94 (192.67.13.94)  103 ms  6 ms  5 ms
 4  t3-3.cnss64.Houston.t3.ans.net (140.222.64.4)  5 ms  5 ms  5 ms
 5  t3-0.cnss112.Albuquerque.t3.ans.net (140.222.112.1)  34 ms  30 ms  30 ms
 6  t3-1.cnss16.Los-Angeles.t3.ans.net (140.222.16.2)  64 ms  57 ms  57 ms
 7  t3-2.cnss8.San-Francisco.t3.ans.net (140.222.8.3)  65 ms  65 ms  65 ms
 8  mf-0.cnss9.San-Francisco.t3.ans.net (140.222.8.193)  74 ms  72 ms  65 ms
 9  t3-0.enss128.t3.ans.net (140.222.128.1)  71 ms  66 ms  68 ms
10  SU-CM.BARRNET.NET (192.31.48.200)  69 ms  69 ms  74 ms
11  UCB1.BARRNET.NET (131.119.5.2)  71 ms  83 ms  72 ms
12  inr-108-dmz.Berkeley.EDU (192.31.161.22)  73 ms  81 ms  70 ms
13  inr-116.Berkeley.EDU (128.32.120.116)  71 ms  77 ms  81 ms
Address:  0.0.0.0

Non-authoritative answer:
Name:    sun-lamp.cs.berkeley.edu
Address:  128.32.138.88

I got 99% of the new netbsd package when the ftp stopped transferring
data.  That was last night.  sun-lamp still seems to be offline, or
is it something really weird?

 
As you can see, at least from my site, I can't quite reach the
subnet sun-lamp is on.  Am I alone here?


------------------------------------------------------------------------------