From: Feizhou <feizhou@linuxmail.org>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: netfilter@lists.netfilter.org, /dev/rob0 <rob0@gmx.co.uk>
Subject: Re: iptables leaking blocked ip addresses.
Date: Wed, 22 Jun 2005 00:52:16 +0800 [thread overview]
Message-ID: <42B845C0.70101@linuxmail.org> (raw)
In-Reply-To: <1119364294.4923.17.camel@anduril.intranet.cartel-securite.net>
Cedric Blancher wrote:
> Le mardi 21 juin 2005 à 17:36 +0800, Feizhou a écrit :
>
>>netfilter's conntrack module sucks in performance and at the same time
>>is not fully stateful.
>
>
> The last serious paper I could read about performances comparison was
> published on pf website long ago and desmonstrated a clear advantage for
> Netfilter against pf or ipf.
>
> http://www.benzedrine.cx/pf-paper.html
Yes...when NOT doing stateful. I have no arguments for netfilter's
filtering performance. Filtering barely adds overhead for my boxes.
Loading the conntrack module however had some painful effects...
>
> However, at this time, Netfilter was indeed not fully stateful. But it's
> no longer the case as Netfilter now implements TCP window tracking in
> stock kernels.
Ah, sorry, I knew that this was brought up some time ago but I did not
the end result. I take back my not fully stateful statement.
>
> If you know good comparisons published, I wuold be happy to read them.
>
I will try a Linux based bridge setup in place of our OpenBSD firewall
now that we can get some equivalency in function. Or just go stateless.
Any suggestions on what kernel version to use? A Fedora errata in case I
install Fedora Core 3/4? Or a stock Linux kernel?
next prev parent reply other threads:[~2005-06-21 16:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 15:34 iptables leaking blocked ip addresses terry l. ridder
2005-06-20 15:48 ` Jan Engelhardt
2005-06-20 16:01 ` terry l. ridder
2005-06-20 15:55 ` /dev/rob0
2005-06-20 16:00 ` /dev/rob0
2005-06-20 16:17 ` terry l. ridder
2005-06-20 16:59 ` /dev/rob0
2005-06-20 17:20 ` terry l. ridder
2005-06-20 18:29 ` /dev/rob0
2005-06-20 19:36 ` terry l. ridder
2005-06-20 20:19 ` /dev/rob0
2005-06-21 12:57 ` Jan Engelhardt
2005-06-21 13:10 ` Jozsef Kadlecsik
2005-06-21 13:13 ` Jan Engelhardt
2005-06-21 13:39 ` Jozsef Kadlecsik
2005-06-21 18:05 ` Jan Engelhardt
2005-06-22 7:10 ` Jozsef Kadlecsik
2005-06-22 12:55 ` Jan Engelhardt
2005-06-22 13:16 ` Jozsef Kadlecsik
2005-06-20 20:47 ` terry l. ridder
2005-06-21 12:17 ` /dev/rob0
2005-06-21 14:36 ` terry l. ridder
2005-06-21 14:57 ` Joakim Axelsson
2005-06-20 18:50 ` Jan Engelhardt
2005-06-20 19:12 ` /dev/rob0
2005-06-20 19:30 ` Sven-Haegar Koch
2005-06-20 20:07 ` /dev/rob0
2005-06-20 20:23 ` terry l. ridder
2005-06-20 22:29 ` Sven-Haegar Koch
2005-06-20 23:04 ` terry l. ridder
2005-06-20 20:39 ` terry l. ridder
2005-06-21 7:11 ` Jozsef Kadlecsik
2005-06-21 7:21 ` terry l. ridder
2005-06-21 7:56 ` Jozsef Kadlecsik
2005-06-21 8:24 ` terry l. ridder
2005-06-21 9:36 ` Feizhou
2005-06-21 9:40 ` Jozsef Kadlecsik
2005-06-21 14:31 ` Cedric Blancher
2005-06-21 16:52 ` Feizhou [this message]
2005-06-21 3:24 ` Alistair Tonner
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=42B845C0.70101@linuxmail.org \
--to=feizhou@linuxmail.org \
--cc=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.org \
--cc=rob0@gmx.co.uk \
/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.