From owner-freebsd-hackers Mon Mar 11 0:52:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from shared1-mail.whowhere.com (shared1-batch.whowhere.com [209.185.123.82]) by hub.freebsd.org (Postfix) with SMTP id 0EA6337B417 for ; Mon, 11 Mar 2002 00:52:35 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by shared1-mail.whowhere.com; Mon Mar 11 00:52:26 2002 To: freebsd-hackers@FreeBSD.org Date: Mon, 11 Mar 2002 14:22:26 +0530 From: "Rajesh P Jain" Message-ID: Mime-Version: 1.0 Cc: "Robert Watson" X-Sent-Mail: on Reply-To: rpjain_1977@eudoramail.com X-Mailer: MailCity Service Subject: BPF - Problem with ioctl calls of BPF X-Sender-Ip: 203.197.138.199 Organization: QUALCOMM Eudora Web-Mail (http://www.eudoramail.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, In the BPF - Berkeley Packet Filter, when a file descriptor is associated to an interface to send and receive packets, there is an ioctl parameter "BIOCSSEESENT", which is by default set to 1. Hence the packets both from "remote systems" and "locally generated" are received. If "locally generated" packets needs to be filtered, we can use the option "BIOCSSEESENT" and set the value to 0. After using this ioctl(BIOCSSEESENT) call for one of the ethernet intrfaces (successfully) and associating the BPF using the BIOCSETIF. Now, if we try to assocaite one more BPF to the second interface of the machine (using the BIOCSETIF), the association of the BPF with that interface fails. Am I missing something ??? Please throw light on this issue. Of course, without using the BIOCSSEESENT, I am able to associate 2 interfaces to separate BPF's. With Regards Rajesh P Jain Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message