From owner-freebsd-hardware@FreeBSD.ORG Tue May 13 03:10:18 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 243AF37B405 for ; Tue, 13 May 2003 03:10:18 -0700 (PDT) Received: from smtp808.mail.sc5.yahoo.com (smtp808.mail.sc5.yahoo.com [66.163.168.187]) by mx1.FreeBSD.org (Postfix) with SMTP id 5E99243F93 for ; Tue, 13 May 2003 03:10:16 -0700 (PDT) (envelope-from dbailey27@ameritech.net) Received: from adsl-67-38-18-210.dsl.sfldmi.ameritech.net (HELO ameritech.net) (dbailey27@ameritech.net@67.38.18.210 with plain) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 13 May 2003 10:10:16 -0000 Message-ID: <3EC0D251.3070503@ameritech.net> Date: Tue, 13 May 2003 06:09:05 -0500 From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: zoltan sandor References: <20030513061807.3223.qmail@web20907.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: questions@freebsd.org cc: hardware@freebsd.org Subject: Re: network problem: ep driver captures packets not intended for this host X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 10:10:18 -0000 From "Network problem: ep driver captures packets not intended for this host" off the Questions@ list: >>From this I see that my ip address is 10.10.6.39 and >the card is not in promiscuous mode. Still when I use >tcpdump -p it shows all the packets coming and going >to an other machine on the subnet with ip address >10.10.6.20. This machine generates a heavy traffic >which is passed to my kernel by the ep0 driver. >Is this the normal behaviour of the system and is >there >any way to drop these packets at the ep0 driver level? > Looks like the filters were not set up by the driver properly. Filter lists tell the card what hardware addresses to "listen" for, while promiscuous mode just negates isolation via filters. If the filters aren't set up properly, you'll see all packets on the wire. I'm sure a 3Com developer would be faster in resolving this issue than I, but, filter setup is definitely where to start looking. I've forwarded this to -hackers/-hardware. Don FYI, he is referring to a: 3COM Fast Etherlink 16-bit PC CARD (3c574-Tx)