Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!NRTC.ARPA!dcass
From: dcass@NRTC.ARPA.UUCP
Newsgroups: mod.computers.ridge
Subject: Re: networks on the Ridge
Message-ID: <8605190516.AA05942@ucbvax.Berkeley.EDU>
Date: Sun, 18-May-86 21:40:56 EDT
Article-I.D.: ucbvax.8605190516.AA05942
Posted: Sun May 18 21:40:56 1986
Date-Received: Mon, 19-May-86 19:43:17 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26
Approved: info-ridge@hopkins-eecs-bravo.arpa


  "How does set up the networking on a Ridge when one wants to send packets
   to a site that must go through a gateway to reach their goal?  I see an
   /etc/networks file but no route, routed, or netstat programs"

In point of fact, the reason you do not see these programs is that Ridge
has yet to port them.  I am currently in the same boat, being a Class B
site with a Ridge and a default gateway to the net.  I understand how
frustrating this is.

But, there is a little good news.  Route is VERY close.  I have a copy
of route which allows incomming traffic, but (for some reason) will not
establish an outgoing connection.  I will be talking with ridge about this
in the morning (5/19/86), and expect to have a beta-test solution available
around the first week of june.

Now for the bad news.  Remember that a Ridge does NOT have /dev/kmem.
As such, netstat has a bit of a problem finding data.  Ridge is working
on this, but it will be a while.  I may be able to get to it sooner (I have
sources..), but I will have to see.  My first priorities are route and
routed.  Note that route -f (flush all routes) may not be implemented in
the first version, again due to the /dev/kmem problem.

I will post progress to the bboard as it occurs,
DEC
dcass@NRTC.NORTHROP.COM