From owner-freebsd-current@FreeBSD.ORG  Thu May 27 07:23:19 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1A2E016A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 27 May 2004 07:23:19 -0700 (PDT)
Received: from oasis.uptsoft.com (oasis.uptsoft.com [217.20.165.41])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 01EDD43D49
	for <freebsd-current@freebsd.org>;
	Thu, 27 May 2004 07:23:18 -0700 (PDT)
	(envelope-from devnull@oasis.uptsoft.com)
Received: (from devnull@localhost)
	by oasis.uptsoft.com (8.11.6/linuxconf) id i4REMNr18066
	for freebsd-current@freebsd.org; Thu, 27 May 2004 17:22:23 +0300
Date: Thu, 27 May 2004 17:22:23 +0300
From: Sergey Lyubka <devnull@uptsoft.com>
To: freebsd-current@freebsd.org
Message-ID: <20040527172223.B17016@oasis.uptsoft.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8D2A@mail.sandvine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C85337051D8D2A@mail.sandvine.com>;
	from don@sandvine.com on Tue, May 25, 2004 at 09:12:04AM -0400
X-OS: FreeBSD 4.5-STABLE
Subject: Re: 5.2.1 + snort, dropping packets
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2004 14:23:19 -0000

> This might be old information, but on stable branch, libpcap
> overrode the 'debug.bpf_bufsize' and always made it 4K. I made
> a local change and it fixed it for me. Not sure if that is
> corrected on current.
> 
> On the system you indicate you should be able to get ~300Kpps
> into user space via bpf, or at least, you can with stable.

thanks for the hint!
libpcap 0.8.3, which is already ported to -current,
fixes this problem.