From: Patrick McHardy <kaber@trash.net>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: hamid jafarian <hamid.jafarian@gmail.com>,
Netfilter-devel <netfilter-devel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jan Engelhardt <jengelh@medozas.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Harald Welte <laforge@gnumonks.org>, Eric Leblond <eric@inl.fr>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Amin Azez <azez@ufomechanic.net>
Subject: Re: [PATCH 00/09]IPtablestng/Kernel - New Framework For IPtables
Date: Tue, 28 Oct 2008 13:30:11 +0100 [thread overview]
Message-ID: <490705D3.4040809@trash.net> (raw)
In-Reply-To: <20081028122554.GA12945@ioremap.net>
Evgeniy Polyakov wrote:
> On Tue, Oct 28, 2008 at 01:07:38PM +0100, Patrick McHardy (kaber@trash.net) wrote:
>> I think these patches are a lost cause. Besides the fact that they
>> move things to the kernel instead of to userspace, they
>
> What about part which replaces rules array with a list?
> That's the main part I was interested in though.
Thats also the part that breaks userspace compatibility and requires
to move a lot of userspace code to the kernel, at least in that
design. Its not possible to do this with iptables without breaking
userspace compability.
next prev parent reply other threads:[~2008-10-28 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 4:28 [PATCH 00/09]IPtablestng/Kernel - New Framework For IPtables hamid jafarian
2008-10-28 0:00 ` Evgeniy Polyakov
2008-10-28 0:02 ` David Miller
2008-10-28 10:02 ` hamid jafarian
2008-10-28 10:43 ` Evgeniy Polyakov
2008-10-28 12:07 ` Patrick McHardy
2008-10-28 12:25 ` Evgeniy Polyakov
2008-10-28 12:30 ` Patrick McHardy [this message]
2008-10-28 12:43 ` Evgeniy Polyakov
2008-10-28 12:57 ` hamid jafarian
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=490705D3.4040809@trash.net \
--to=kaber@trash.net \
--cc=azez@ufomechanic.net \
--cc=eric@inl.fr \
--cc=hamid.jafarian@gmail.com \
--cc=jengelh@medozas.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rusty@rustcorp.com.au \
--cc=zbr@ioremap.net \
/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.