tcpdump mailing list archives
Re: why not filtering at driver level ?
From: Guy Harris <guy () alum mit edu>
Date: Mon, 23 Oct 2006 22:15:36 -0700
Guy Harris wrote:
You forgot option 3: 3. Raise the limit on the maximum number of BPF instructions.You're going to have to add stuff to, or change stuff in, the kernel to implement this *anyway*, so you might as well just boost the maximum number of BPF instructions and not have to change libpcap *at all*.
You might also have to raise the limit on socket options; see http://www.tcpdump.org/lists/workers/2004/05/msg00007.htmlIt might be that you're running into the limit on socket options, rather than the limit on BPF instructions, in which case you don't have to change any code.
- This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Current thread:
- Sniffing inbound ethernet frames only Jost-DVSB (Oct 21)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 21)
- Re: Sniffing inbound ethernet frames only Jost-DVSB (Oct 23)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 23)
- why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? Jefferson Ogata (Oct 23)
- Re: why not filtering at driver level ? Jefferson Ogata (Oct 23)
- Re: Sniffing inbound ethernet frames only Jost-DVSB (Oct 23)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 21)
- Re: Sniffing inbound ethernet frames only Jost-DVSB (Oct 23)
- Re: Sniffing inbound ethernet frames only Hannes Gredler (Oct 24)