netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: netfilter-devel@vger.kernel.org
Cc: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Subject: [iptables-nftables RFC PATCH 0/6] IPv6 Support
Date: Thu, 10 Jan 2013 16:29:33 +0200	[thread overview]
Message-ID: <1357828179-18664-1-git-send-email-tomasz.bursztyka@linux.intel.com> (raw)

Hi,

Here is an attempt to get iptables-nftables supporting IPv6.
I haven't tested it really, so I send it more as an RFC.

Starting from xtables.c which supports only IPv4, patch 2 combines the support for IPv6 in it.
The family attribute provided in patch 1 is set then used in nft.c to use it accordingly, in patch 3.

Patch 4 finalizes it in handling the right informations for rule manipulations depending on the family.

Patch 5 and 6 then adds the support of IPv6 when it comes to respectively save and print the firewall.

Please review,

Tomasz Bursztyka (6):
  nft: Add a family attribute to nft_handle
  xtables: Combine IPv6 support with IPv4 support
  nft: Use handle's family attribute instead of hardcoded AF_INET one
  nft: Support IPv6 rules manipulation
  nft: Use the right payload parsing function when saving a rule
  nft: Handle IPv6 when printing out firewall rules

 iptables/nft.c     | 651 +++++++++++++++++++++++++++++++++++++++--------------
 iptables/nft.h     |   1 +
 iptables/xtables.c | 378 +++++++++++++++++++++----------
 3 files changed, 741 insertions(+), 289 deletions(-)

-- 
1.8.0.2


             reply	other threads:[~2013-01-10 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 14:29 Tomasz Bursztyka [this message]
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 1/6] nft: Add a family attribute to nft_handle Tomasz Bursztyka
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 2/6] xtables: Combine IPv6 support with IPv4 support Tomasz Bursztyka
2013-01-11  9:10   ` [iptables-nftables RFC PATCH - v2 - " Tomasz Bursztyka
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 3/6] nft: Use handle's family attribute instead of hardcoded AF_INET one Tomasz Bursztyka
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 4/6] nft: Support IPv6 rules manipulation Tomasz Bursztyka
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 5/6] nft: Use the right payload parsing function when saving a rule Tomasz Bursztyka
2013-01-10 14:29 ` [iptables-nftables RFC PATCH 6/6] nft: Handle IPv6 when printing out firewall rules Tomasz Bursztyka
2013-01-13 19:23 ` [iptables-nftables RFC PATCH 0/6] IPv6 Support 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=1357828179-18664-1-git-send-email-tomasz.bursztyka@linux.intel.com \
    --to=tomasz.bursztyka@linux.intel.com \
    --cc=netfilter-devel@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 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).