From owner-freebsd-bugs  Tue Apr 15 03:01:05 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA00441
          for bugs-outgoing; Tue, 15 Apr 1997 03:01:05 -0700 (PDT)
Received: from mail.crl.com (mail.crl.com [165.113.1.22])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA00429
          for <bugs@freebsd.org>; Tue, 15 Apr 1997 03:01:02 -0700 (PDT)
Received: from economic.acnit.ac.ru by mail.crl.com with SMTP id AA16994
  (5.65c/IDA-1.5 for <bugs@freebsd.org>); Tue, 15 Apr 1997 02:56:26 -0700
Received: (from bazilio@localhost)
          by economic.acnit.ac.ru (8.8.5/8.8.4)
	  id NAA00524; Tue, 15 Apr 1997 13:46:54 +0400 (MSD)
Date: Tue, 15 Apr 1997 13:46:54 +0400 (MSD)
From: "Vasily V. Grechishnikov" <bazilio@economic.acnit.ac.ru>
To: bugs@freebsd.org
Subject: IPX and Tulip needs promiscuous mode ??
Message-Id: <Pine.BSF.3.91.970415132624.492B-100000@economic>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

			Hi !
	I have FreeBSD 2.2 RELEASE. My FreeBSD box is an Internet gateway
and Samba file server for three LANs. I need an IPX gateway, in two of 
three LANs I have NetWare file servers. 
	My FreeBSD box :
	
 			   ed0 ( NE200)---NetWare 4.1
				|				
	NetWare 3.12----ed1( NE200)
				|
		           de0( DEC21040)-----NetWare clients
	
IPX routing works fine on my FreeBSD, but with following problem:
IPX packets forwards de0 <-> ed0 or de0 <-> ed1 only if on the de0 interface
promiscuous mode is enabled, forwarding through ed1 <-> ed0 works without
promiscuouty on the this interfaces.

	I try the following steps:
	1. I compiled the kernel with 
		options IPX 
		options IPX_PRINTFS=0
		options	IPX_ERRPRINTFS=0
	2. I ifconfig'ured my interfaces according to their correct IPX 
	   network numbers 
	3. I turned MIB variable net.ipx.ipx.ipxforwarding=1
	4. I ran IPXrouted with option -s .
	5. But it works only if I run tcpdump -i de0 or
	   my own program which simply turn promiscuouty on specified network 
	   interface.

	May be Tulip device driver contain some errors? I haven't expirience
to analyze /sys/pci/if_de.c ( 130K ) ;-) .

	Any suggestions?

  Thanks, Vasily .

 **********[FreeBSD it is coolest UNIX for PC!]***********
 |	 System admin , ftp and web master.    		 | 
 | 	 http://www.econ.acnit.ac.ru/~bazilio/ 		 | 
 *********************************************************
 |	Voronezh State Technical University		 |
 |	Industrial Economy Departament 			 |
 *********************************************************