🚀 go-pugleaf

The Novell gurus here have asked my help with our first attempt at IP routing
thru 3.11 servers.  The application is a few macintoshes which will run
NCSA TELNET to get to our VAX.

                        ser0
                         +--->to WestNet
     VAX             CISCO                 NOVELL                MAC
      +--------------+   +-----------------+    +-----------------+
      VAX net        e   e  campus backbone       media lab net
      IP 192.80.27.0 t   t  IP 161.28.1.0         IP 161.28.64.0
      IPX C0501B00   h   h  IPX A11C0100          IPX A11C4000
                     1   0
                     
192.80.27.1    192.80.27.126                  161.28.64.254
Netware VMS           161.28.1.254      161.28.1.64            161.28.64.100
& Multinet           8.2(7)                 3.11

PC's sitting beside the Mac can see the VAX on SLIST.

I read the FM and set eveything up as (I think) it says.
Both the VAX net and the campus backbone are set for Ethernet II packet types.
TCPCON sees packets arriving every few seconds.
The cisco ARP cache has a correct entry for 161.28.1.64 .
BUT -- no traffic flow.  The cisco can't even get a "ping" echo from the
server.

--------------------
>From Newsgroups: comp.sys.novell
>Subject: comp.sys.novell: Frequently asked questions (FAQ)
>Date: Tue, 01 Sep 1992 00:01:00 GMT
[...]
>* 10. Why can't I get my 3.x server to forward TCP/IP packets?
>--- 08/19/92 ---
>With 2 or more network cards in the server, you can forward TCP/IP
>packets relatively simply.
>
>The first common problem is that when you load TCPIP.NLM the
>forward=yes options is forgotten.  Thus, the AUTOEXEC.NCF file should
>have the line:
>	load tcpip forward=yes

This one says: Load tcpip forward=Yes rip=Yes

>Another possibility is that the transmitting station is not sending the
>packets to the right place.  If packets must go through the server, you
>must set up a "gateway=aa.bb.cc.dd" option on the workstation. 

Done.  Mac says gateway is 161.28.64.254

> The
>server will then decide which network card the packet must be
>retransmitted on, thus leaving all routing to the server, instead of
>trying to have the programmers put it into the program itself.  Also,
>if you have some older routers on, say, a campus backbone, they might
>have to be reprogrammed as well, so that they can send packets back to
>your workstation, should they need to make several hops to get to their
>destination.  Older routers require this, while the newer ones will
>automatically "find" your server as a router through RIP.

Cisco is set "route rip"

>Another common problem that people have is that Novell will only
>forward between two different subnets, i.e.  
>	129.65.1  & 
>	129.65.2  with a mask of
>	mask=ff.ff.ff.00

OK there subnets and masks are set on both Novell interfaces
-----------

Still the server will not answer a PING.

So:
Q1:  Is a healthy 3.11 IP router supposed to PING?

Q2:  If so, what can stop it?

Q3:  (more advanced)  Do I need to worry about re-distributing the RIP
derived routing info out to westnet?

-- 
-- Vern Cole -- Systems Manager -- Utah Valley Community College --