IPX: Network number collision 67: -This May WOrk.

[*snicker* <menion mindless com>]

What it kind of sounds like to me, although I have never seen Linux do
this...  If indeed the error is 'IPX Network Number Collision' then I
doubt that this is a physicaly protocol problem, it is a Network
enumeration problem.  I.E.  If you have a Novell server, you give it an
internal Net Number, and Hex number, that has you to 10 digits I
beleive, or maybe twelve.  It runs at layer 3 or 4 not sure.  Then for
every card that you bind the IPX transport to, you have to give the card
an individual 'netork number', for instance:
 
I have 2 Novell servers, each with  NICS, and Two Separate Hubs. (Just
an example)

         
Server1 
   IPX Internal Net Num: AAA
   NIC1: 001
   NIC2: 002

Server2
   IPX Internal Net Num: BBB
   NIC1: 001
   NIC2: 002	

   Each Novell server has an individual Network Number, as does each
card.   Each server has card 1 conntected to hub A, and card 2 connected
to hub b. 

   if you stack the hubs, you will get 'network number' collisions... I
don't recall the exact error, and I don't really know how to relate this
in terms of IP, except to say that it is ugly.  If this is the problem
then you need to......

everything that I am about to explain is explained in slightly more
extraneous detail in the LDP's IPX Howto by Terry Dawson,
terry perf no itg telstra com au   Obtainable here:
'http://sunsite.unc.edu/LDP/HOWTO/IPX-HOWTO.html'

Provided you have the ipxtools rpm installed the following will make
sense.  This also hinges on the basic belief that A. you have built a
custom kernel, and done it properly. and B. You have IP up and running. 
You should be compiled with the option 'Full IPX Network' (When you have
IPX selected or modularized in the 'menuconfig' for the kernel this
option appears. 

First try: 'ipx_configure --auto_interface=on --auto_primary=on'  then
reboot.  Even thought you don't really need to reboot, I have had a lot
better luck with this. (I have been messing with IPX for the last 3 days
under Linux)

if using 'ipx_configure --auto_interface=on --auto_primary=on' is not
working, then here is what to do.  Find out what Frame, and network
number you are using, and pick an 'internal net number'.  


  	 # ipx_internal_net add 0xab000000 1
         # ipx_interface add eth0 YourFrame 0xYourHexNetworkNumber


Now IPX Routing is something totally different, and I have no desire to
explain it, becuase I despise IPX,and I only use it out of nessecity. 

"ipx_route

     The command allows you to manually modify the IPX routing table.
For example to add a route to IPX network 39ab0222 via a router with
node
     number 00608CC33C0F on IPX network 39ab0108: 

          # ipx_route add 0x39ab0222 0x39ab0108 0x00608CC33C0F"



I hope this message is of use, IF it is, please feel free to direct any
further questions to me. I heave tried to read all the posts, but I lost
some mail in an HD crash a while back, and well... you know....

Joshua