From owner-freebsd-bugs Tue Jul 7 07:09:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01661 for freebsd-bugs-outgoing; Tue, 7 Jul 1998 07:09:07 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01654 for ; Tue, 7 Jul 1998 07:09:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id QAA02848; Tue, 7 Jul 1998 16:06:41 +0200 (CEST) To: Samuel S Thomas cc: dg@root.com, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/7191 In-reply-to: Your message of "Tue, 07 Jul 1998 14:04:15 -0000." <19980707140415.C1918@lart.net> Date: Tue, 07 Jul 1998 16:06:41 +0200 Message-ID: <2846.899820401@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980707140415.C1918@lart.net>, Samuel S Thomas writes: >On Tue, Jul 07, 1998 at 06:52:07AM -0700, David Greenman wrote: >> >please re-open this, as you have not investigated the matter in the >> >slightest, and seem to have false conceptions as to the real problem. I >> >have sent data clearly definig the problem, which should hopefully >> >clearly explain the situation to you. >> >> The "rainer" machine's interface appears to either be in promiscuous mode >> or perhaps might be defective. Based on your packet dumps, rainer shouldn't >> be seeing the packets since they are not broadcasts and the destination >> address is not that machine. What type of network interface is in rainer? > >rainier has a 3Com 3c589c ethernet card. it is running PAO-980430. >rfc1122 still states that a host must determine if it is the destination >of a packet before further processing of such packet. even if it was >promiscuous, this should be caught long before a reply is generated. >This would break networks where, for instance, a FreeBSD box was acting >as a DHCP server. Hmm, I added a check to the vx0 3com driver some time back for exactly that problem, the chip received all packets (to be able to hear multicast ?), you may need to do the same thing in this driver. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message