All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Ignacy Gawedzki <i@lri.fr>,
	Netfilter Developers <netfilter-devel@vger.kernel.org>,
	Jan Engelhardt <jengelh@medozas.de>
Subject: Re: Netfilter API and libiptc
Date: Wed, 11 Feb 2009 15:37:39 +0100	[thread overview]
Message-ID: <4992E2B3.3030009@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0902111408210.4822@ask.diku.dk>

Jesper Dangaard Brouer wrote:
> On Mon, 9 Feb 2009, Ignacy Gawedzki wrote:
>> My question was not about how to prevent the machine from crashing, 
>> but rather
>> how are we supposed to manipulate iptables, now that libiptc is not 
>> available.
>> <cut>
> 
> I would propose that we add libiptc again.
> 
> Possibly as a shared library, like we have libxtables.so?
> 
> Controlling API/ABI changes is going to be a lot harder when people 
> starts to incorporate the libiptc code into their own source 
> distributions. (I'm also guildy with the Perl IPTables::libiptc package...)
> 
> Patrick, what do you say?

Agreed on your reasoning. I don't have much of an opinion, we
mainly tried to hide it because it was never suitable for anything
else than a short "iptables ..." command because of memory leaks
etc. I think we're a lot better with this nowadays, if we can
get the worst remaining ones plugged and somewhat of a usable
API we can certainly add it as a library.

  reply	other threads:[~2009-02-11 14:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 14:17 Netfilter API and libiptc Ignacy Gawedzki
2009-02-09 17:10 ` Patrick McHardy
2009-02-09 18:39   ` Ignacy Gawedzki
2009-02-11 13:39     ` Jesper Dangaard Brouer
2009-02-11 14:37       ` Patrick McHardy [this message]
2009-02-11 16:02         ` Jan Engelhardt
2009-02-12  5:13           ` Patrick McHardy
2009-02-12  5:55             ` Jan Engelhardt
2009-02-12  5:58               ` Patrick McHardy
2009-02-12  6:14                 ` Jan Engelhardt
2009-02-12  6:18                   ` Patrick McHardy
2009-02-12  6:29                     ` Jan Engelhardt
2009-02-12  6:34                       ` Patrick McHardy
2009-02-16 13:08                 ` Jesper Dangaard Brouer
2009-02-16 13:47                   ` Jesper Dangaard Brouer
2009-02-16 14:08                     ` Patrick McHardy
2009-02-16 16:52                       ` Jan Engelhardt
2009-02-16 16:54                         ` Patrick McHardy
2009-02-12  9:17               ` Jesper Dangaard Brouer
2009-02-12 10:42                 ` Jesper Dangaard Brouer
2009-02-12 13:33                   ` Ignacy Gawedzki
2009-02-12 14:11                   ` Jan Engelhardt
2009-02-12 14:50                     ` Jesper Dangaard Brouer

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=4992E2B3.3030009@trash.net \
    --to=kaber@trash.net \
    --cc=hawk@diku.dk \
    --cc=i@lri.fr \
    --cc=jengelh@medozas.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.