All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Giuseppe Longo <giuseppelng@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3] xtables: bootstrap xtables-eb for nftables
Date: Wed, 1 Oct 2014 21:20:11 +0200	[thread overview]
Message-ID: <20141001192011.GA7652@salvia> (raw)
In-Reply-To: <1412174830-3620-1-git-send-email-giuseppelng@gmail.com>

Hi Giuseppe,

On Wed, Oct 01, 2014 at 04:47:08PM +0200, Giuseppe Longo wrote:
> This patch bootstraps xtables-eb for the nftables compatibility layer

I have pushed these patches to this branch in iptables:

http://git.netfilter.org/iptables/log/?h=ebtables-compat-experimental

I have forward-ported the patchset to run on top of the recent
nft_xt_ctx changes.

There is still a good amount of work to be done to get this in good
shape:

1) The output of ebtables-compat -L should look the same like
   ebtables -L.

1) Fix segfaults. I detected one when you use -h, and another if you
   don't pass any target. Those should be easy to fix IMO.

2) Fix listing. If I add:

ebtables-compat -I INPUT --logical-in br0 -j ACCEPT

shows:

-d 62:72:30:0:0:0 --logical-in br0 -j ACCEPT

Note the -d seem incorrect.

3) I have added ebtables NAT table support. It's basically a filter
   table. I needed a small kernel patch though since the bridge filter
   chain type is not allowing to filter at prerouting and postrouting.

4) Add support for matches and targets.

I'll have a look at this later again, but it would be great if you can
send incremental patches to resolve the existing issues. Thanks.

      parent reply	other threads:[~2014-10-01 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 14:47 [PATCH 1/3] xtables: bootstrap xtables-eb for nftables Giuseppe Longo
2014-10-01 14:47 ` [PATCH 2/3] nft-shared: make compare_matches as public Giuseppe Longo
2014-10-01 14:47 ` [PATCH 3/3] Operations for bridge family Giuseppe Longo
2014-10-01 19:20 ` Pablo Neira Ayuso [this message]

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=20141001192011.GA7652@salvia \
    --to=pablo@netfilter.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.