From: jamal <hadi@cyberus.ca>
To: Adam Katz <adamkatz0@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: libpcap and tc filters
Date: Tue, 05 Jul 2011 09:56:53 -0400 [thread overview]
Message-ID: <1309874213.1765.45.camel@mojatatu> (raw)
In-Reply-To: <CAA0qwj5aBWrsqHGddW9FBV2srdGwVMzJKe84BTyRH0Dkr6KgVQ@mail.gmail.com>
On Tue, 2011-07-05 at 16:07 +0300, Adam Katz wrote:
> second, I just took at the libpcap source code and it seems it's using
> the same ETH_P_ALL option when binding to an interface. So based on
> what you're saying, the same solution of patching libpcap and
> replacing ETH_P_ALL with ETH_P_IP should also make these rules work
> with traffic sent using pure libpcap or any libpcap - based
> application.
ETH_P_ALL makes sense if you are unsure it is going to be IP. So i would
change/optimize apps only for IP if they are intended to deal with IP
only (same for ARP etc).
In your case, it seems it is tcp only - which runs on top of IP. So
it makes sense to do it for that specific use case etc.
cheers,
jamal
next prev parent reply other threads:[~2011-07-05 13:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 7:38 libpcap and tc filters Adam Katz
2011-07-04 10:20 ` Eric Dumazet
2011-07-04 11:11 ` jamal
2011-07-04 12:01 ` Adam Katz
2011-07-04 12:37 ` Adam Katz
2011-07-04 13:05 ` jamal
2011-07-04 13:24 ` Adam Katz
2011-07-04 14:06 ` jamal
2011-07-04 14:16 ` Adam Katz
2011-07-05 10:56 ` jamal
2011-07-05 12:47 ` jamal
2011-07-05 13:07 ` Adam Katz
2011-07-05 13:56 ` jamal [this message]
2011-07-05 14:21 ` Adam Katz
2011-07-05 14:41 ` jamal
2011-07-05 15:16 ` Adam Katz
2011-07-05 16:14 ` Eric Dumazet
2011-07-05 16:54 ` Adam Katz
2011-07-05 19:19 ` jamal
2011-07-05 20:07 ` Adam Katz
[not found] <CAA0qwj5Ktxi=v3XDAdTpKS_pWa+HjFL5XcN2qsK5m57JJ5G2Bg@mail.gmail.com>
2011-07-03 12:49 ` Adam Katz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309874213.1765.45.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=adamkatz0@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.