netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Nordstrom <henrik@henriknordstrom.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org,
	Warren Kenny <warren.kenny@gmail.com>
Subject: Re: Is libiptc still the preferred library for manipulating tables?
Date: Fri, 02 Mar 2007 20:44:21 +0100	[thread overview]
Message-ID: <1172864661.3183.24.camel@henriknordstrom.net> (raw)
In-Reply-To: <45E2D126.7010003@netfilter.org>

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

mån 2007-02-26 klockan 13:23 +0100 skrev Pablo Neira Ayuso:

> Unfortunately, libiptc is not a supported as a standalone library, it is 
> just a directory inside iptables. The only interface available, at the 
> moment, is iptables, the command line tool. You can blame us for not 
> providing an appropiate library interface yet.

This said, "iptables-restore -n" is a quite effective and potent batch
interface for rule updates. 

And if it (or actually the underlying iptables code it's using) had an
option for dumping rules in iptables-save format then it could be as
potent for read access as well.. Today iptables-restore can only read
rules to the same level of detail as iptables -L -v.

Regards
Henrik

[-- Attachment #2: Detta är en digitalt signerad meddelandedel --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

  reply	other threads:[~2007-03-02 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 19:05 Is libiptc still the preferred library for manipulating tables? Warren Kenny
2007-02-26 12:23 ` Pablo Neira Ayuso
2007-03-02 19:44   ` Henrik Nordstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-12  1:34 Hal Moroff
2007-05-15  7:07 ` Henrik Nordstrom

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=1172864661.3183.24.camel@henriknordstrom.net \
    --to=henrik@henriknordstrom.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@netfilter.org \
    --cc=warren.kenny@gmail.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).