Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: gapsf@yandex.ru
Cc: netfilter@vger.kernel.org, Jan Engelhardt <jengelh@medozas.de>
Subject: Re: nftables: introspection capabilities?
Date: Thu, 26 May 2011 19:33:45 +0200	[thread overview]
Message-ID: <4DDE8EF9.8090208@netfilter.org> (raw)
In-Reply-To: <1510322597.20110524161458@yandex.ru>

On 24/05/11 11:14, gapsf@yandex.ru wrote:
>>> There is no doubt that for nftables frontends will be written too, so the question is:
>>> "Will nfatbles be able to find out various information
>>> about their own current state: tables, chains, rules, etc?"
> 
> JE> You can already obtain this information by using libiptc, iterating over 
> JE> all rules and testing for a particular src/dst address (very much like 
> JE> poor man's `grep -s 1.2.3.4\b` on the text output).
> According to Wikipedia "libiptc ... shouldn't be used as a public API,
> and is known to change, which breaks programs that use it"
> and libiptc is a 3d party project - not netfilter.org's and outdated, isn't it?
> 
> As for nftables: means native capabilities of it's kernelspace code (aka virtual machine).

just to clarify, that's not a virtual machine but a pseudo-state machine
in the BPF fashion, OK?

      parent reply	other threads:[~2011-05-26 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24  8:21 nftables: introspection capabilities? gapsf
2011-05-24  8:33 ` Jan Engelhardt
2011-05-24  9:14   ` Re[2]: " gapsf
2011-05-24  9:25     ` Jan Engelhardt
2011-05-26 17:33     ` 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=4DDE8EF9.8090208@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=gapsf@yandex.ru \
    --cc=jengelh@medozas.de \
    --cc=netfilter@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