From: Fan Du <fan.du@windriver.com>
To: <pablo@netfilter.org>
Cc: <davem@davemloft.net>, <steffen.klassert@secunet.com>,
<netfilter-devel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] netfilter: IPv4/v6 IPcomp match support
Date: Fri, 13 Dec 2013 20:18:00 +0800 [thread overview]
Message-ID: <1386937082-30412-1-git-send-email-fan.du@windriver.com> (raw)
Hi,
This patchset adds IPv4/v6 IPComp 'match' plugin to enables user setting
ACTONs for IPcomp flows sepecified with SPI value.
Corresponding iptables patchset will be sent here after soon.
Fan Du (2):
netfilter: add IPv4 IPComp extension match support
netfilter: add IPv6 IPComp extension match support
include/uapi/linux/netfilter_ipv4/ipt_comp.h | 18 ++++
include/uapi/linux/netfilter_ipv6/ip6t_comp.h | 18 ++++
net/ipv4/netfilter/Kconfig | 9 ++
net/ipv4/netfilter/Makefile | 1 +
net/ipv4/netfilter/ipt_comp.c | 101 +++++++++++++++++++++++
net/ipv6/netfilter/Kconfig | 8 ++
net/ipv6/netfilter/Makefile | 1 +
net/ipv6/netfilter/ip6t_comp.c | 110 +++++++++++++++++++++++++
8 files changed, 266 insertions(+)
create mode 100644 include/uapi/linux/netfilter_ipv4/ipt_comp.h
create mode 100644 include/uapi/linux/netfilter_ipv6/ip6t_comp.h
create mode 100644 net/ipv4/netfilter/ipt_comp.c
create mode 100644 net/ipv6/netfilter/ip6t_comp.c
--
1.7.9.5
next reply other threads:[~2013-12-13 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 12:18 Fan Du [this message]
2013-12-13 12:18 ` [PATCH 1/2] netfilter: add IPv4 IPComp extension match support Fan Du
2013-12-13 12:18 ` [PATCH 2/2] netfilter: add IPv6 " Fan Du
2013-12-17 13:05 ` [PATCH net-next 0/2] netfilter: IPv4/v6 IPcomp " Pablo Neira Ayuso
2013-12-19 3:30 ` Fan Du
2013-12-20 9:04 ` Pablo Neira Ayuso
2013-12-20 9:21 ` Fan Du
2013-12-23 12:13 ` Pablo Neira Ayuso
2013-12-24 6:19 ` Fan Du
2013-12-24 18:16 ` Pablo Neira Ayuso
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=1386937082-30412-1-git-send-email-fan.du@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).