From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eyal Birger <eyal.birger@gmail.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org, shmulik@metanetworks.com,
Eyal Birger <eyal@metanetworks.com>
Subject: Re: [PATCH net-next 2/2] net: sched: add em_ipt ematch for calling xtables matches
Date: Tue, 23 Jan 2018 13:15:54 +0100 [thread overview]
Message-ID: <20180123121554.pj6ujqjijbw6w4ta@salvia> (raw)
In-Reply-To: <1516699052-19259-3-git-send-email-eyal.birger@gmail.com>
On Tue, Jan 23, 2018 at 11:17:32AM +0200, Eyal Birger wrote:
> From: Eyal Birger <eyal@metanetworks.com>
>
> This module allows performing tc classification based on data structures
> and implementations provided by netfilter extensions.
>
> Example use case is classification based on the incoming IPSec policy used
> during decpsulation using the 'policy' iptables extension (xt_policy).
>
> Signed-off-by: Eyal Birger <eyal@metanetworks.com>
>
> ---
>
> This ematch tries its best to provide matches with a similar
> environment to the one they are used to; Due to the wide range of criteria
> supported by matches, I am not able to test every combination of match and
> traffic.
Thanks! No objection to the Netfilter bits.
So I leave it up to the tc maintainers to decide what to do with this.
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
next prev parent reply other threads:[~2018-01-23 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 9:17 [PATCH net-next 0/2] net: sched: introduce em_ipt ematch Eyal Birger
2018-01-23 9:17 ` [PATCH net-next 1/2] net: sched: ematch: pass protocol to ematch 'change()' handlers Eyal Birger
2018-01-23 9:17 ` [PATCH net-next 2/2] net: sched: add em_ipt ematch for calling xtables matches Eyal Birger
2018-01-23 12:15 ` Pablo Neira Ayuso [this message]
2018-01-24 21:37 ` David Miller
2018-01-25 0:00 ` Pablo Neira Ayuso
2018-01-26 4:24 ` Eyal Birger
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=20180123121554.pj6ujqjijbw6w4ta@salvia \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=eyal.birger@gmail.com \
--cc=eyal@metanetworks.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=shmulik@metanetworks.com \
--cc=xiyou.wangcong@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox