From owner-freebsd-hackers Wed Jan 6 00:45:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08467 for freebsd-hackers-outgoing; Wed, 6 Jan 1999 00:45:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08456 for ; Wed, 6 Jan 1999 00:45:37 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id KAA09819; Wed, 6 Jan 1999 10:45:05 +0200 (SAST) Received: by citadel via recvmail id 9760; Wed Jan 6 10:44:26 1999 From: Graham Wheeler Message-Id: <199901060852.KAA00920@cdsec.com> Subject: Re: bpf select() broke? To: dwhite@pond.net (Doug White) Date: Wed, 6 Jan 1999 10:52:48 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Doug White" at Jan 5, 99 02:13:50 pm X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do Berkeley packet filter devices (/dev/bpfX) supposed to respond like > normal files and devices to a select() system call? > > My experimentation (based on 2.2.7-RELEASE) shows that they don't. They > don't return when they have data waiting to read and they don't return > when they're ready to be written to. The bpf fd is definitely in the fd > list going into the select(), so don't try to pin pilot error on this one. We use select on read on BPF devices for all our BPF code on 2.2.7, and it works for us. Select on write definitely doesn't work (it isn't implemented). -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Internet/Intranet Network Specialists Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message