On Mon, 11 Mar 2002, Rajesh P Jain wrote:
> 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.
I haven't run into this -- the circumstance under which I used (and first
added) BIOCSSEESENT was one in which I bound (n) BPF devices to (n)
seperate interfaces, and set BIOCSSEESENT=0 on each. We used such an
environment to create a userland bridging tool, and use this to avoid
first order cycles. Could you provide a code snippet demonstrating the
failure? What failure do you get?
Our loop consisted of (logically):
foreach interface (interface list) {
open bpf instance
set bpf capture length
set bpf interface
get and check bpf data link type
set bpf "complete header" flag to true
set bpf "see sent" flag to false
set bpf "immediate" flag to true
set bpf "promiscuous" flag to true
set bpf instructions
}
It appeared to work fine although I haven't tried it on recent -STABLE.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
