netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 10:43:50 +0200	[thread overview]
Message-ID: <20131017084350.GA8423@localhost> (raw)
In-Reply-To: <CAEyr1FQtVEGHM0KD1qxDi6gLkVgrYhc0C46A2bPXE4nfewU-sQ@mail.gmail.com>

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:
> > In (73ea1cc nft: convert rule into a command state structure), the
> > interface wildcard matching got broken. The previous handling was
> > flawed by the use of ifnametoindex in scenario where the interface
> > may vanished after a rule was added.
> >
> > This approach relies on the trailing '\0' to identify if this is
> > an exact or wildcard matching, based on discussion with Florian.
> >
> > Based on initial patch from Anand Raj Manickam.
> >
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > ---
> >  iptables/nft-shared.c |   38 ++++++++++++++++----------------------
> >  1 file changed, 16 insertions(+), 22 deletions(-)
> >
> > diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
> > index 3987f74..e0eaa17 100644
> > --- a/iptables/nft-shared.c
> > +++ b/iptables/nft-shared.c
> > @@ -124,13 +124,11 @@ void add_iniface(struct nft_rule *r, char *iface, int invflags)
> >         else
> >                 op = NFT_CMP_EQ;
> >
> > -       if (iface[iface_len - 1] == '+') {
> > -               add_meta(r, NFT_META_IIFNAME);
> > +       add_meta(r, NFT_META_IIFNAME);
> > +       if (iface[iface_len - 1] == '+')
> >                 add_cmp_ptr(r, op, iface, iface_len - 1);
> > -       } else {
> > -               add_meta(r, NFT_META_IIF);
> > -               add_cmp_u32(r, if_nametoindex(iface), op);
> > -       }
> > +       else
> > +               add_cmp_ptr(r, op, iface, iface_len + 1);
> >  }
> >
> >  void add_outiface(struct nft_rule *r, char *iface, int invflags)
> > @@ -145,13 +143,11 @@ void add_outiface(struct nft_rule *r, char *iface, int invflags)
> >         else
> >                 op = NFT_CMP_EQ;
> >
> > -       if (iface[iface_len - 1] == '+') {
> > -               add_meta(r, NFT_META_OIFNAME);
> > +       add_meta(r, NFT_META_OIFNAME);
> > +       if (iface[iface_len - 1] == '+')
> >                 add_cmp_ptr(r, op, iface, iface_len - 1);
> > -       } else {
> > -               add_meta(r, NFT_META_OIF);
> > -               add_cmp_u32(r, if_nametoindex(iface), op);
> > -       }
> > +       else
> > +               add_cmp_ptr(r, op, iface, iface_len + 1);
> >  }
> >
> >  void add_addr(struct nft_rule *r, int offset,
> > @@ -251,15 +247,14 @@ void parse_meta(struct nft_rule_expr *e, uint8_t key, char *iniface,
> >                         *invflags |= IPT_INV_VIA_IN;
> >
> >                 memcpy(iniface, ifname, len);
> > -               iniface[len] = '\0';
> >
> > -               /* If zero, then this is an interface mask */
> > -               if (if_nametoindex(iniface) == 0) {
> > +               if (iniface[len] == '\0')
> > +                       memset(iniface_mask, 0xff, len);
> > +               else {
> >                         iniface[len] = '+';
> >                         iniface[len+1] = '\0';
> > +                       memset(iniface_mask, 0xff, len + 1);
> >                 }
> > -
> > -               memset(iniface_mask, 0xff, len);
> >                 break;
> >         case NFT_META_OIFNAME:
> >                 ifname = nft_rule_expr_get(e, NFT_EXPR_CMP_DATA, &len);
> > @@ -267,15 +262,14 @@ void parse_meta(struct nft_rule_expr *e, uint8_t key, char *iniface,
> >                         *invflags |= IPT_INV_VIA_OUT;
> >
> >                 memcpy(outiface, ifname, len);
> > -               outiface[len] = '\0';
> >
> > -               /* If zero, then this is an interface mask */
> > -               if (if_nametoindex(outiface) == 0) {
> > +               if (outiface[len] == '\0')
> > +                       memset(outiface_mask, 0xff, len);
> > +               else {
> >                         outiface[len] = '+';
> >                         outiface[len+1] = '\0';
> > +                       memset(outiface_mask, 0xff, len + 1);
> >                 }
> > -
> > -               memset(outiface_mask, 0xff, len);
> >                 break;
> >         default:
> >                 DEBUGP("unknown meta key %d\n", key);
> 
> Pablo,
> 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?

  reply	other threads:[~2013-10-17  8:43 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 [this message]
2013-10-17 12:47     ` Anand Raj Manickam
2013-10-17 13:27       ` 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=20131017084350.GA8423@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).