From owner-freebsd-hackers  Tue Jan 12 14:00:15 1999
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA17061
          for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:00:15 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA17056
          for <hackers@freebsd.org>; Tue, 12 Jan 1999 14:00:14 -0800 (PST)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <60851(3)>; Tue, 12 Jan 1999 13:59:34 PST
Received: by crevenia.parc.xerox.com id <177534>; Tue, 12 Jan 1999 13:59:25 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: dwhite@pond.net, hackers@FreeBSD.ORG
Subject: Re:  using raw sockets
Message-Id: <99Jan12.135925pst.177534@crevenia.parc.xerox.com>
Date: Tue, 12 Jan 1999 13:59:18 PST
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

What OS version, and what kind of ethernet card, are you using when you
see the BPF symptoms that you mention?  I've never seen either of the
problems you describe.  It seems to me that fixing bpf is a much better
target than creating a whole new mechanism.

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message