From owner-freebsd-questions  Tue Jul 23 11:42:44 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA03481
          for questions-outgoing; Tue, 23 Jul 1996 11:42:44 -0700 (PDT)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA03467
          for <questions@freebsd.org>; Tue, 23 Jul 1996 11:42:35 -0700 (PDT)
Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.5/8.7.3) id UAA11084; Tue, 23 Jul 1996 20:42:25 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199607231842.UAA11084@zibbi.mikom.csir.co.za>
Subject: Re: IPXrouted, Not seeing Netware 3.11
To: tcg@ime.net
Date: Tue, 23 Jul 1996 20:42:25 +0200 (SAT)
Cc: questions@freebsd.org
In-Reply-To: <31F50F59.1E3@ime.net> from Gary Chrysler at "Jul 23, 96 01:43:53 pm"
X-Mailer: ELM [version 2.4ME+ PL16 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > 
> > You should use the same net address on the FreeBSD machine as on the
> > Netware server's ethernet interface.
> > 
> 
> I have completly stripped my NW!
> and partially stripped FBSD, Removed ed1 = inet ... ...
> 
> NW: autoexec.ncf (the _whole_ thing as it is right now)
> 	file server name TCGUY-FS1
> 	ipx internal net 6345403
> 	load 386E-MCT slot 2 frame=ETHERNET_II name=IPXNET
> 	bind IPX to IPXNET net=36714239
> 	mount all
> 
> FBSD: /etc/sysconfig (in part)
> 	ed0="ipx 36714239
> 
> Now both show 36714239.
> Still no go..
> 
> During all of this I found another problem thats why I completly
> stripped my NW, my previous (And hopefully again) autoexec.ncf
> 	file server name TCGUY-FS1
> 	ipx internal net 6345403
> 	# changed to _ii to play with FBSD-IPX on 07/08/96 @02:37
> 	#load 386E-MCT slot 2 frame=ETHERNET_802.3 name=IPXNET
> 	load 386E-MCT slot 2 frame=ETHERNET_II name=IPXNET
> 	load 386E-MCT slot=2 frame=ETHERNET_II name=IPNET
> 	load STREAMS
> 	load CLIB
> 	load SNMP          _
> 	load TCPIP
> 	bind IPX to IPXNET net=14239
> 	bind IP to IPNET addr=10.1.29.3 mask=FF.FF.FF.00
> 	mount all
> 	load resolv DM tcguy.net TO 30 NS 10.1.29.4
> 	load ftpd use sys:system/ftpd/ftpd.cfg
> 	load pserver TCGUY-PS1
> 	#load monitor /p
> 
> And it _seems_ the TWO ethernet_ii frame types on two different
> protocols can't be done.
> I don't use tcp/ip on the NW very often and it's probably been
> broke since I changed from ethernet_802.3 to _II about 2 or 3
> weeks ago.. :(
> I do need it back! Is it possiable, Can two protocols share a
> frame type??
> (I know,  I need to ask that on a netware list/ng, I will, I'll
>  figure out the tcp/ip on the NW later. Just thought I would
>  throw it  out here maybe someone here will know)
> 

You don't need to have a frame for every protocol. You can just bind
both protocols to the same device/name.

> My main concern now is to get IPXrouted working.
> Any other ideas??
> 

Hmmm. Everything looks ok. Maybe you should look at the output of
ifconfig -a, netstat -sf ipx and netstat -rnf ipx to see if you
can learn something more from it. You might also try tcpdump to
see what is happening on the net.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za