On Mon, 2007-03-05 at 13:18 +0000, Andy Green wrote: > Not sure I explained well enough: looking at libpcap sources, it > compiles the filter you request into a bytecode and then gives it to the > kernelside using an ioctl. When you recv() or select() on the monitor > interface after that, you block until something matching your filter > definition turns up. Userspace doesn't hear about the rest of it. Uh eh right, I'm confused :) The power save mode argument still holds though, we might address that with non-promisc monitor interfaces even though they do have a couple of problems (you need to be associated on a different virtual netdev for it to make sense...) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part