From: Daniel Borkmann <daniel@iogearbox.net>
To: pablo@netfilter.org
Cc: tgraf@suug.ch, challa@noironetworks.com,
netfilter-devel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH nf-next v3 0/3] Netfilter zone directions
Date: Wed, 22 Jul 2015 12:54:45 +0200 [thread overview]
Message-ID: <cover.1437561897.git.daniel@iogearbox.net> (raw)
This is v3 of the originally named flextuples [1] patch set, but
this time after discussions from NFWS completely reworked towards
integration into the existing zones infrastructure. Please see
individual patches for details.
Thanks!
[1] http://thread.gmane.org/gmane.comp.security.firewalls.netfilter.devel/57412/
v2 -> v3:
- Have a global default zone object, use it directly
- Do not touch uapi-exposed ct->status bits, but integrate
the marking flag into the zones structure
- Rebased onto latest nf-next, rerun all stress tests
v1 -> v2:
- Reworked entire set, integration into zones
- Rebased onto latest nf-next
Daniel Borkmann (3):
netfilter: nf_conntrack: push zone object into functions
netfilter: nf_conntrack: add direction support for zones
netfilter: nf_conntrack: add efficient mark to zone mapping
include/net/netfilter/nf_conntrack.h | 6 +-
include/net/netfilter/nf_conntrack_core.h | 3 +-
include/net/netfilter/nf_conntrack_expect.h | 11 +-
include/net/netfilter/nf_conntrack_zones.h | 82 ++++++++++--
include/uapi/linux/netfilter/nfnetlink_conntrack.h | 9 ++
include/uapi/linux/netfilter/xt_CT.h | 8 +-
net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c | 2 +-
net/ipv4/netfilter/nf_conntrack_proto_icmp.c | 4 +-
net/ipv4/netfilter/nf_defrag_ipv4.c | 18 +--
net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.c | 2 +-
net/ipv6/netfilter/nf_conntrack_proto_icmpv6.c | 5 +-
net/ipv6/netfilter/nf_defrag_ipv6_hooks.c | 19 +--
net/netfilter/ipvs/ip_vs_nfct.c | 2 +-
net/netfilter/nf_conntrack_core.c | 95 ++++++++------
net/netfilter/nf_conntrack_expect.c | 19 +--
net/netfilter/nf_conntrack_netlink.c | 139 ++++++++++++++-------
net/netfilter/nf_conntrack_pptp.c | 3 +-
net/netfilter/nf_conntrack_standalone.c | 24 +++-
net/netfilter/nf_nat_core.c | 24 ++--
net/netfilter/nf_synproxy_core.c | 4 +-
net/netfilter/xt_CT.c | 26 +++-
net/netfilter/xt_connlimit.c | 9 +-
net/sched/act_connmark.c | 6 +-
23 files changed, 366 insertions(+), 154 deletions(-)
--
1.9.3
next reply other threads:[~2015-07-22 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 10:54 Daniel Borkmann [this message]
2015-07-22 10:54 ` [PATCH nf-next v3 1/3] netfilter: nf_conntrack: push zone object into functions Daniel Borkmann
2015-07-30 16:07 ` Pablo Neira Ayuso
2015-07-30 16:34 ` Daniel Borkmann
2015-08-03 15:59 ` Pablo Neira Ayuso
2015-08-03 16:00 ` Daniel Borkmann
2015-08-05 10:51 ` Pablo Neira Ayuso
2015-08-05 14:00 ` Daniel Borkmann
2015-08-06 10:02 ` Pablo Neira Ayuso
2015-07-22 10:54 ` [PATCH nf-next v3 2/3] netfilter: nf_conntrack: add direction support for zones Daniel Borkmann
2015-07-22 10:54 ` [PATCH nf-next v3 3/3] netfilter: nf_conntrack: add efficient mark to zone mapping Daniel Borkmann
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=cover.1437561897.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=challa@noironetworks.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).