From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Warren Kenny <warren.kenny@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Is libiptc still the preferred library for manipulating tables?
Date: Mon, 26 Feb 2007 13:23:02 +0100 [thread overview]
Message-ID: <45E2D126.7010003@netfilter.org> (raw)
In-Reply-To: <57f837150702251105y7d70c345n233a75fc2f328592@mail.gmail.com>
Warren Kenny wrote:
> This subject seems a bit hazy to me at the moment. Basically I'm
> writing a network intrusion detection and prevention system for Linux
> and I'd like to be able to use Netfilter to block packets coming from
> nodes which have been identified as malicious. I'd prefer to avoid the
> use of libnetfilter_queue since I'm already using libpcap for packet
> analysis and it has some extras that I rely on. Basically I want to
> add new tables and rules from within my application in order to filter
> out malicious traffic.
>
> There seem to be a lot of different guides on how to do this, most of
> which are obsolete, including the guide on libiptc. I need to know the
> latest and best way to manipulate iptables rules.
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.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2007-02-26 12:23 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 [this message]
2007-03-02 19:44 ` Henrik Nordstrom
-- 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=45E2D126.7010003@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter-devel@lists.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 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.