From: Mistick Levi <gmistick@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: Fwd: API For Iptables
Date: Wed, 23 Jun 2010 22:59:54 +0300 [thread overview]
Message-ID: <AANLkTile0HeVPti8gk29TMFTkJvyoW2ewPVtEqy_DNkP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilUo7x6OWPkIifJM-rvcFWCgHmRVoDXgMi7TkxV@mail.gmail.com>
Hi,
Ofcourse there is a demand for an API as libiptc ( though libiptc is
not an API )
>From what i read on the list, the main reason libiptc is to be
replaced is because it is too low-level.
I was wondering if there is still a reason to try and create a
HighLevel API for iptables, or because of nftables that idea is
worthless?
If the idea is a good one, i'd like to try and work on it :)
Kind regards
Yechiel Levi
parent reply other threads:[~2010-06-23 19:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AANLkTilUo7x6OWPkIifJM-rvcFWCgHmRVoDXgMi7TkxV@mail.gmail.com>]
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=AANLkTile0HeVPti8gk29TMFTkJvyoW2ewPVtEqy_DNkP@mail.gmail.com \
--to=gmistick@gmail.com \
--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 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).