From owner-freebsd-security Wed Nov 8 11:41:11 2000 Delivered-To: freebsd-security@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 800FE37B479 for ; Wed, 8 Nov 2000 11:41:08 -0800 (PST) Received: (qmail 60807 invoked from network); 8 Nov 2000 19:41:04 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 8 Nov 2000 19:41:04 -0000 Message-ID: <06e701c049bb$df3a8440$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: References: Subject: Re: TCPDUMP patch v1.1 and AppleTalk Date: Wed, 8 Nov 2000 14:41:21 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > If you are running the daemon that supports Appletalk (is it netatalk?), > perhaps the Appletalk daemon becomes confused when tcpdump puts the > Ethernet interface into promiscuous mode. It may be that the daemon > expects to see only the Appletalk traffic directed to it, and seeing *all* > Appletalk traffic on the wire makes it go nuts. > > This is very unlikely. I use a couple of machines with the netatalk+asun package installed and I never ever had the problems described above. None of the machines I use have the recent tcpdump patches so I can not check the bug. However I am positive that puting the interface in promiscuous mode does not confuse netatalk. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message