🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.novell
Article #7752

Indirect IP routing

#7752
From: Bill Pottenger
Date: Mon, 15 Jun 1992 17:20
60 lines
2855 bytes
Myron Miller, a user of NCSA Telnet for the PC, requested that we post this
for him:

***

I am trying to establish connectivity between out Unix system and Novell
3.11.  I have three cards in our file server - this is our setup
(auto.ncf):

FILE SERVER NAME FS2
IPX INTERNAL NET A

#DIRECT TO HAL AND ALL OF BUILDING B EXCEPT ONE WING (FELIX)
LOAD NE2000 PORT=340 INT=2 FRAME=ETHERNET_II NAME=E2A
BIND IPX NE2000 [PORT=340 INT=2 FRAME=ETHERNET_II] NET=5

#BUILDING A (10-BASE-T)
LOAD EXP16 PORT=310 INT=3 FRAME=ETHERNET_802.3 NAME=INTEL
BIND IPX EXP16 [PORT=310 INT=4 FRAME=ETHERNET_802.3] NET=10

#BUILDING B (FELIX)
LOAD NE2000 PORT=360 INT=4 FRAME=ETHERNET_II NAME=E2B
BIND IPX NE2000 [PORT=360 INT=4 FRAME=ETHERNET_II] NET=11

SET DISPLAY LOST INTERRUPT ALERTS=OFF
SET DISPLAY SPURIOUS INTERRUPT ALERTS=OFF
SET MAXIMUM PACKET RECEIVE BUFFERS = 200

LOAD REMOTE XXXX
LOAD RSPX
TRACK ON

The first card is a direct connect to a unix system named HAL via a T1
microwave which goes to building C.  I have the tcp/ip working in Building
B through a cable connected to the first card in FS2, but the rest of it
won't work.  I've tried indirect ip routing, but don't understand it well
enough to get it working.  We are using packet drivers that came with the
ethernet and the 10-base cards with a generic kernel (PKTIPX.COM).  Both of
the NE2000's come up under the same driver and there is a second driver for
the intel card (this is all in a single machine, FS2).  I don't want to use
ODI because of the memory overhead.  We're using NCSA Telnet for the PC and
have hardware set to packet.  If anyone can help please call me collect
(Myron Miller) at (214) 301-9121.

Thanks,

Myron Miller
Network Administrtor
Spectradyne, Inc.

***

We will also take replies here at NCSA via email.  We do *not* have any
Novell products networking PC's here and are hoping that someone with more
experience can help this user.

Thank you,

Bill Pottenger
NCSA Consulting
Technical Details
Message-ID: <1992Jun15.172044.10411@ncsa.uiuc.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!billp

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe659,a6b54a4266891b06,start
X-Google-Attributes: gidfe659,public
X-Google-Thread: 10f035,a6b54a4266891b06,start
X-Google-Attributes: gid10f035,public
X-Google-Thread: 10a29b,a6b54a4266891b06,start
X-Google-Attributes: gid10a29b,public
X-Google-ArrivalTime: 1992-06-15 03:14:12 PST
Newsgroups: comp.sys.novell,comp.protocols.tcp-ip.ibmpc,bit.listserv.novell
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!billp
From: billp@ncsa.uiuc.edu (Bill Pottenger)
Subject: Indirect IP routing
Message-ID: <1992Jun15.172044.10411@ncsa.uiuc.edu>
Originator: billp@consult.ncsa.uiuc.edu
Sender: billp@ncsa.uiuc.edu (Bill Pottenger)
Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
Date: Mon, 15 Jun 1992 17:20:44 GMT
Lines: 60