[comp.sys.novell] IP routing on NW 3.11

george@webb.psych.ufl.edu (Stephanie George) (06/17/91)

IP does work with Netware 3.11.  Finally.

Earlier I wrote to this group describing the problems we were having getting
our server to pass IP.  Using a couple of protocol analyzers that we had in
for evaluation, we could see that IP was going through from the backbone 
side to the subnet side and that the workstation on the subnet side was 
generating IP but it just wasn't getting back through to the backbone.

Since we are the network administrators here at the Health Center, we knew
that the Wellfleet router we have connecting us to the campus backbone
knew about the new Netware router (BB-FS2) and in turn, the server knew 
the correct address for the Wellfleet.

The solution was really quite simple and turned out not to be a server 
problem at all.  The workstation that was running NCSA Telnet on the subnet
behind BB-FS2 didn't have the server listed as its gateway to the backbone.
We added the lines 
	host=128.227.188.1
	gateway=1
to the config.tel file for the workstation and it instantly started working.

Though we didn't have the problem, the reverse situation can exist if the
workstations or other IP entities on the backbone don't have the Netware
server listed as a gateway in their host or configuration files as well.
That is, the workstations on the subnet behind the server will be able to
get IP traffic out, but will not be able to recieve traffic from the other
hosts on the backbone.



-----------------+--------------------+---- Backbone network
                 |                    |
128.227.104.111  | NE2000          +--+--+
          +------+------+          | WS1 |  128.227.104.101
          |    server   |          +-----+
          |    BB-FS2   |
          +------+------+
128.227.188.1    | NE1000
                 |
-----------------+---------------------+---- Subnet
                                       |
                                    +--+--+
                                    | WS2 |  128.227.188.106
                                    +-----+
Fig. 1. Server acting as a router for subnet 188 behind it.


This is what my autoexec.ncf looks like (to act like an IP router):

file server name BB-FS2
ipx internal net 30001
load c:\ne2000.lan port=340 int=5 frame=ethernet_802.3 name=backbone
LOAD C:\ne1000.LAN PORT=300 int=3 FRAME=ETHERNET_802.3 name=subnet
bind IPX to backbone net=30000
BIND IPX TO subnet NET=30002
load tcpip forward=yes
load c:\ne2000.lan port=340 int=5 frame=ethernet_ii name=bb-ip
LOAD C:\ne1000.LAN PORT=300 int=3 FRAME=ETHERNET_ii name=sn-ip
bind ip to bb-ip addr=128.227.104.111 mask=255.255.254.0 bcast=128.227.105.255
bind ip to sn-ip addr=128.227.188.1 mask=255.255.254.0 bcast=128.227.189.255
mount all
load remote xxxxxx
load rspx
load monitor
load tcpcon 128.227.104.111 sort=yes


I have also tried this in a server running with two Western Digital cards:
a 8003EP - Ethercard Plus Elite; and a 8013EP - Ethercard Plus Elite16.
Both cards had to be software configured with I/O address of 300h or greater
and memory addresses of D0000h or greater to be compatible with VGA.

Unfortunately, this is an IP-expensive solution since every server will have to have
an internet subnet behind it to work.  We don't find it an acceptable 
solution for our environment since we cannot afford the subnets.  We 
currently have 46 Netware servers here in the Health Center alone and that
number has been increasing at a rate of about one every 2 weeks.  It will 
surely top out sometime, but we are administering about one third of the
campus network.

As you can see from the mask, the campus is currently a class B network,
subnetting on an odd boundary which gives us 500+ hosts per subnet.
However, this cuts the number of available subnets to 128.  With Novell 3.11
requiring a subnet behind each server running IP, we would have to have
the entire campus shift to an even boundary to give us 250 subnets with
250 hosts each.  We will probably have to apply for another class B if
our growth continues at this rate for very long.

For the next attempt at providing workstations with IP, we will try the
IP-IPX gateway software written by Paul Kranenberg of Leiden University
in Holland paired with the "NET.EXE" routing software from Phil Karn (KA9Q).
Both of these packages and documentation for the IPXPKT.EXE program are
available for anonymous FTP from sun.soe.clarkson.edu.





--
Stephanie George        DoD #218         Box J-14, JHMHC 
george@psych.ufl.edu                     University of Florida
(904) 392-8450                           Gainesville, FL  32610