From owner-freebsd-current Sun Jan 31 18:17:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02973 for freebsd-current-outgoing; Sun, 31 Jan 1999 18:17:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02967 for ; Sun, 31 Jan 1999 18:17:18 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA17157; Sun, 31 Jan 1999 21:17:10 -0500 (EST) Message-ID: <19990131211710.B12496@netmonger.net> Date: Sun, 31 Jan 1999 21:17:10 -0500 From: Christopher Masto To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <19990129180612.C3237@netmonger.net> <199901292328.SAA26781@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901292328.SAA26781@skynet.ctr.columbia.edu>; from Bill Paul on Fri, Jan 29, 1999 at 06:28:46PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote: > - Change the if() clause so that it looks like this: > > if (sc->pn_promisc_war /*&& ifp->if_flags & IFF_PROMISC*/) { > > (In other words, comment out the test for the IFF_PROMISC flag.) > > This will enable the workaround all the time and allow the receiver bug > to be detected and handled properly. > > Compile a new kernel with this change and see if the problem persists. > Report back your findings (one way or the other) so that I'll know if > I should modify the code in the repository. I'm sad to say, this didn't solve the problem. It still happens exactly as before, and still goes away immediately if I run a tcpdump on another console (but not if I do tcpdump -p). I did add a printf when pn_promisc_war is set to 1 just to make sure that it was being properly detected and turned on, and it is.. but enabling the workaround all the time doesn't seem to help. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message