netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: Issue with latest nftables
Date: Mon, 01 Jul 2013 10:22:25 +0200	[thread overview]
Message-ID: <1372666945.421.23.camel@ice-age.regit.org> (raw)
In-Reply-To: <51D1282D.1050007@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Hi,

Le lundi 01 juillet 2013 à 09:56 +0300, Tomasz Bursztyka a écrit :
> Hi Pablo,
> >> netlink: Error: unknown expression type 'match'
> >> name=iprange rev=1
> >>
> >>
> >> netlink: Error: unknown expression type 'target'
> >> name=LOG rev=0
> >>
> >> Should this problem be trivial for someone, I let him do the job. If
> >> not, I will start to work on it.
> > We don't have support for compat from nft yet. That should be
> > relatively easy to fix.
> >
> 
> Do we want to support those totally, or just when listing the rules? I 
> would rather do the later one, nft is not meant to maintain 
> iptables-nftables rules.
> Where were could only handle then the expression itselsf and the name of 
> the match/target, but nothing more. (No blob parsing etc...)

IMHO, the minimum task here is to have examples in libnftables that are
compatible with nft and don't use compat layer. Adding compat layer to
nft is another story.

BR
--
Eric

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2013-07-01  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 20:08 Issue with latest nftables Eric Leblond
2013-06-29  9:45 ` Pablo Neira Ayuso
2013-07-01  6:56   ` Tomasz Bursztyka
2013-07-01  8:22     ` Eric Leblond [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=1372666945.421.23.camel@ice-age.regit.org \
    --to=eric@regit.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=tomasz.bursztyka@linux.intel.com \
    /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).