From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Anand Raj Manickam <anandrm@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables-nftables] nft: fix interface wildcard matching
Date: Thu, 17 Oct 2013 15:27:49 +0200 [thread overview]
Message-ID: <20131017132749.GA12189@localhost> (raw)
In-Reply-To: <CAEyr1FShn1LJX27pePQfTP_gjcRZ=cQvfiqd-5O021rn1M+-Nw@mail.gmail.com>
On Thu, Oct 17, 2013 at 06:17:25PM +0530, Anand Raj Manickam wrote:
> On Thu, Oct 17, 2013 at 2:13 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > On Thu, Oct 17, 2013 at 02:09:05PM +0530, Anand Raj Manickam wrote:
> >> On Wed, Oct 16, 2013 at 7:37 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
[...]
> >> This again breaks the delete functionality .
> >
> > This is working here with a fresh compilation:
> >
> > # xtables -I INPUT -i eth+
> > # xtables -D INPUT -i eth+
> > # xtables -I INPUT -i eth0
> > # xtables -D INPUT -i eth0
> >
> > # which xtables
> > /usr/sbin/xtables
> > # ls -la /usr/sbin/xtables
> > lrwxrwxrwx 1 root root 13 oct 17 10:42 /usr/sbin/xtables -> xtables-multi
> >
> > What problem are you noticing?
>
> Sorry about it , i guess i had the wrong build .. works great ..
No problem.
> Do you still want to maintain the refrence for NFT_META_IIF / NFT_META_OIF ?
Yes, currently you cannot use nftables and xtables at the same time,
but some degree of interaction is desired. This should allow xtables
to interpret add rule added using ifindex from nft.
prev parent reply other threads:[~2013-10-17 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 14:07 [PATCH iptables-nftables] nft: fix interface wildcard matching Pablo Neira Ayuso
2013-10-17 8:39 ` Anand Raj Manickam
2013-10-17 8:43 ` Pablo Neira Ayuso
2013-10-17 12:47 ` Anand Raj Manickam
2013-10-17 13:27 ` 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=20131017132749.GA12189@localhost \
--to=pablo@netfilter.org \
--cc=anandrm@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).