From: Benny Amorsen <benny+usenet@amorsen.dk>
To: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH,RFC] Route match
Date: Fri, 04 Jul 2008 15:47:56 +0200 [thread overview]
Message-ID: <m3mykxoj5f.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: alpine.LNX.1.10.0807031808550.23294@fbirervta.pbzchgretzou.qr
Jan Engelhardt <jengelh@medozas.de> writes:
> I fail to see why Xtables (not just a firewall) should be slower
> than the routing table (without routing cache, to make it fair).
What about the routing cache, though?
Our Linux-based routers handle considerably less than 1Gbps peak, and
they drop packets when the cache is flushed. (So I had to set the
automatic flush to 86400 seconds instead of 10).
It would be necessary to either reinvent the route cache or come up
with something better. Preferably the latter, of course.
/Benny
next prev parent reply other threads:[~2008-07-04 13:48 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
2008-07-03 16:14 ` Krzysztof Oledzki
2008-07-03 16:14 ` Jan Engelhardt
2008-07-04 13:47 ` Benny Amorsen [this message]
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=m3mykxoj5f.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--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