From owner-freebsd-net@FreeBSD.ORG Wed Jun 17 15:04:59 2015 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD1B4A54 for ; Wed, 17 Jun 2015 15:04:59 +0000 (UTC) (envelope-from elof2@sentor.se) Received: from smtp-out.sentor.se (smtp-out.sentor.se [176.124.225.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F01FF89 for ; Wed, 17 Jun 2015 15:04:59 +0000 (UTC) (envelope-from elof2@sentor.se) Received: from localhost (localhost [127.0.0.1]) by farmermaggot.shire.sentor.se (Postfix) with ESMTP id 92BF1B61D3E2; Wed, 17 Jun 2015 17:04:49 +0200 (CEST) Date: Wed, 17 Jun 2015 17:04:49 +0200 (CEST) From: elof2@sentor.se To: Sergey Akhmatov cc: Borja Marcos , freebsd-net Subject: Re: oce(4) promiscous mode bug(?) In-Reply-To: <55817E80.7020003@genossen.ru> Message-ID: References: <5581427D.9070007@genossen.ru> <106C87E2-7097-416B-841B-B1C4D74E9ABA@sarenet.es> <55816EE1.7030004@genossen.ru> <55817E80.7020003@genossen.ru> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 15:04:59 -0000 It sounds like a promisc bug in the driver, just as you say, but just to test it some more: I see that you are running both in PPROMISC and PROMISC. What happen if you remove the PPROMISC and only let tcpdump set it's own PROMISC? Running in monitor mode is the correct way to sniff traffic. But just to rule out errors in the oce driver, what happen if you do not run in monitor mode? Do 'netstat -in' show the same input errors as your sysctl counter? (I assume you're running tcpdump with no bpf filter at all) What do a couple of 'netstat -B' say while tcpdump is running? /Elof On Wed, 17 Jun 2015, Sergey Akhmatov wrote: > Tried disabling all offloadings available, doesn't help. > >> Sorry, in that case I don't know what it might be. >> >> Have you tried disabling "adapter intelligence"? rxcsum, txcsum, lro, etc? > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >