wls@astrovax.UUCP.UUCP (05/18/86)
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 to control or
examine the routing tables. The campus network here is about to expand to the
point where some of the sites will be behind gateways. A gateway is about to
open to a site which has a node number with network part not the same as the
campus class B network number. How can I reach this site from our Ridge?
---
Bill Sebok Princeton University, Astrophysics
{allegra,akgua,cbosgd,decvax,ihnp4,noao,philabs,princeton,vax135}!astrovax!wlsdcass@NRTC.ARPA.UUCP (05/19/86)
"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