Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Apr 1997 22:13:46 +0200 (SAT)
From:      John Hay <jhay@zibbi.mikom.csir.co.za>
To:        bazilio@economic.acnit.ac.ru (Vasily V. Grechishnikov)
Cc:        freebsd-bugs@freebsd.org
Subject:   Re: IPX and Tulip needs promiscuous mode ??
Message-ID:  <199704162013.WAA20666@zibbi.mikom.csir.co.za>
In-Reply-To: <Pine.BSF.3.91.970416143723.237A-100000@economic> from "Vasily V. Grechishnikov" at "Apr 16, 97 02:39:25 pm"

index | next in thread | previous in thread | raw e-mail

> 
> On Tue, 15 Apr 1997, John Hay wrote:
> 
> > > 	May be Tulip device driver contain some errors? I haven't expirience
> > > to analyze /sys/pci/if_de.c ( 130K ) ;-) .
> > > 
> > > 	Any suggestions?
> > > 
> > 
> > I have never tried it with the deX driver. What is the order of the
> > devices in the network_interfaces variable in /etc/sysconfig? If
> > the de0 device is after the ed0 devices try to put it in front
> > and see if it make a difference.
> > 
> 
> 	I reorder my sysconfigs network_interfaces="de0 ed.. lo0", and
> IPX frowarding works ok !! But ,why ? 
> 

Because of the stupid current behaviour of the ipx code. It tries to
use the same host-part of the ipx address on all the interfaces. For
that it use the MAC address of the first interface that is ifconfig'ed
with an ipx address. But for ipx to work on ethernet, the mac address
of the interface must be the same as the host part of the ipx address,
so the mac address of the 2nd and 3d interface must be changed. This
works correctly on the edX devices, but not on the deX devices.

I have this fixed here (so that each interface keeps its own mac address
and ipx use that), but I want to fix a few more things before I commit it.

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


help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704162013.WAA20666>