From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Krzysztof Oledzki <ole@ans.pl>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Phil Oester <kernel@linuxace.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH,RFC] Route match
Date: Thu, 03 Jul 2008 18:10:55 +0200 [thread overview]
Message-ID: <486CFA0F.7050900@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0807031806310.23294@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2008-07-03 17:51, Krzysztof Oledzki wrote:
>
>>> You know what's been bugging me... why don't we replace the entire
>>> routing infrastructure by an xtables "route" table, with something like
>>>
>> Because routing in a firewall is slow and too complicated?
>>
>
> Proof?
Its obvious, routing lookups are optimized for the specific case while
iptables is trying to be generic.
next prev parent reply other threads:[~2008-07-03 16:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:39 [PATCH,RFC] Route match Phil Oester
2008-07-03 7:18 ` Jan Engelhardt
2008-07-03 9:50 ` Jozsef Kadlecsik
2008-07-03 11:22 ` Jan Engelhardt
2008-07-03 12:39 ` Jozsef Kadlecsik
2008-07-03 13:13 ` Jan Engelhardt
2008-07-03 13:31 ` Jozsef Kadlecsik
2008-07-03 14:15 ` Jan Engelhardt
2008-07-03 22:02 ` Jozsef Kadlecsik
2008-07-03 23:02 ` Jan Engelhardt
2008-07-04 0:19 ` James King
2008-07-04 0:37 ` Jan Engelhardt
2008-07-03 15:51 ` Krzysztof Oledzki
2008-07-03 16:07 ` Jan Engelhardt
2008-07-03 16:10 ` Patrick McHardy [this message]
2008-07-03 16:14 ` Krzysztof Oledzki
2008-07-03 16:14 ` Jan Engelhardt
2008-07-04 13:47 ` Benny Amorsen
2008-07-04 15:15 ` Henrik Nordstrom
2008-07-03 18:53 ` Patrick McHardy
2008-07-03 22:21 ` Jozsef Kadlecsik
2008-07-04 20:26 ` Jozsef Kadlecsik
2008-07-03 7:22 ` [PATCH,RFC] Route match, kernel Jan Engelhardt
2008-07-03 16:27 ` Phil Oester
2008-07-03 7:26 ` [PATCH,RFC] Route match, user Jan Engelhardt
2008-07-03 16:29 ` Phil Oester
2008-07-03 16:55 ` Jan Engelhardt
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=486CFA0F.7050900@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=kernel@linuxace.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
/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.