netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Longo <giuseppelng@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Giuseppe Longo <giuseppelng@gmail.com>
Subject: [iptables-compat PATCH 0/3] ebtables compat layer
Date: Fri, 22 Aug 2014 11:29:12 +0200	[thread overview]
Message-ID: <1408699755-17785-1-git-send-email-giuseppelng@gmail.com> (raw)

Hi Pablo,
the btables-compat is almost ready,
I've fixed the issues with flags, there are two small issues
to be fixed yet:

- rules with logical interfaces are not deleted
- when listing rule, the mask is printed when it's not set

The filter table is working properly except these issues,
that I'm going to fix in these days.

There is no support yet for nat and brouting,
I'm working on checksum expr.

I would know what you have in mind for these patches,
if you want to accept them when the issues are fixed
even if there is no nat support yet or or what else?

So I can organize the work to do.

There are still some extensions that have to be moved
to libxtables.

Thanks

Giuseppe Longo (3):
  xtables: bootstrap xtables-eb for nftables
  nft-shared: make compare_matches as public
  Operations for bridge family

 include/linux/netfilter/nf_tables.h         |    4 +
 include/linux/netfilter_bridge.h            |   33 +
 include/linux/netfilter_bridge/ebtables.h   |  276 +++++++
 include/linux/netfilter_bridge/ethernetdb.h |   58 ++
 iptables/Makefile.am                        |    6 +-
 iptables/getethertype.c                     |  161 ++++
 iptables/nft-bridge.c                       |  545 ++++++++++++
 iptables/nft-shared.c                       |   14 +-
 iptables/nft-shared.h                       |    3 +-
 iptables/nft.c                              |   28 +
 iptables/nft.h                              |   12 +
 iptables/xtables-compat-multi               |  210 +++++
 iptables/xtables-compat-multi.c             |    1 +
 iptables/xtables-eb-standalone.c            |   87 ++
 iptables/xtables-eb.c                       | 1186 +++++++++++++++++++++++++++
 iptables/xtables-ebtables.h                 |   49 ++
 iptables/xtables-multi.c                    |    1 +
 iptables/xtables-multi.h                    |    1 +
 18 files changed, 2667 insertions(+), 8 deletions(-)
 create mode 100644 include/linux/netfilter_bridge.h
 create mode 100644 include/linux/netfilter_bridge/ebtables.h
 create mode 100644 include/linux/netfilter_bridge/ethernetdb.h
 create mode 100644 iptables/getethertype.c
 create mode 100644 iptables/nft-bridge.c
 create mode 100755 iptables/xtables-compat-multi
 create mode 100644 iptables/xtables-eb-standalone.c
 create mode 100644 iptables/xtables-eb.c
 create mode 100644 iptables/xtables-ebtables.h

-- 
1.8.3.2


             reply	other threads:[~2014-08-22  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  9:29 Giuseppe Longo [this message]
2014-08-22  9:29 ` [iptables-compat PATCH 1/3] xtables: bootstrap xtables-eb for nftables Giuseppe Longo
2014-08-22  9:29 ` [iptables-compat PATCH 2/3] nft-shared: make compare_matches as public Giuseppe Longo
2014-08-22  9:29 ` [iptables-compat PATCH 3/3] Operations for bridge family Giuseppe Longo
2014-08-24 14:18 ` [iptables-compat PATCH 0/3] ebtables compat layer 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=1408699755-17785-1-git-send-email-giuseppelng@gmail.com \
    --to=giuseppelng@gmail.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).