From: Feizhou <feizhou@linuxmail.org>
To: David Cannings <lists@edeca.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Is this firewall good enough?
Date: Wed, 09 Jun 2004 04:14:13 +0800 [thread overview]
Message-ID: <40C61E15.4050702@linuxmail.org> (raw)
In-Reply-To: <200406081617.05230.lists@edeca.net>
David Cannings wrote:
> On Tuesday 08 June 2004 15:03, Feizhou wrote:
>
>>Antony Stone wrote:
>>
>>>On Tuesday 08 June 2004 10:42 am, Feizhou wrote:
>>>
>>>>>2. /sbin/iptables -A INPUT -p tcp -m state --state
>>>>>ESTABLISHED,RELATED -j ACCEPT
>>>>
>>>>Forget about this. It makes things easier yes but it is too slow if
>>>>you come under attack...but then you put everything on one box
>>>>seemly so I guess you don't get much traffic.
>>>
>>>How do you recommend dealing with reply packets instead?
>>
>>So to avoid loading the connection tracking module, I would put rules
>>to handle return packets in the proper chain.
>
>
> A lot of work has gone into connection tracking and, whilst it is entirely
> possible to implement it yourself using many flag matches, it's hardly
> worth it. Connection tracking works very well for me and I imagine many
> others, I see no reason to try and circumvent that.
>
> Is there any good reason not to load connection tracking?
SLOW. It isn't good enough to use on a high traffic server.
You don't even have to use stateful checks. Just do iptables -t nat -L
-n which will load the conntrack module and boom, you've just slowed
down your box big time network wise if you have a high packet rate.
next prev parent reply other threads:[~2004-06-08 20:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 9:14 Is this firewall good enough? Sagara Wijetunga
2004-06-08 9:42 ` Feizhou
2004-06-08 9:57 ` Antony Stone
2004-06-08 15:03 ` Feizhou
2004-06-08 15:23 ` Antony Stone
2004-06-08 20:11 ` Feizhou
2004-06-09 9:48 ` Antony Stone
2004-06-09 10:03 ` Feizhou
2004-06-08 16:17 ` David Cannings
2004-06-08 20:14 ` Feizhou [this message]
2004-06-09 9:28 ` Jozsef Kadlecsik
2004-06-09 9:57 ` Feizhou
2004-06-09 11:05 ` Jozsef Kadlecsik
2004-06-09 13:18 ` Feizhou
2004-06-09 13:23 ` Feizhou
2004-06-09 8:36 ` Sagara Wijetunga
2004-06-08 9:44 ` Rob Sterenborg
2004-06-09 8:14 ` Sagara Wijetunga
2004-06-09 9:56 ` Rob Sterenborg
2004-06-09 15:12 ` Aleksandar Milivojevic
2004-06-09 15:15 ` Aleksandar Milivojevic
2004-06-11 14:24 ` Sagara Wijetunga
2004-06-08 9:55 ` Antony Stone
2004-06-08 12:38 ` Chris Brenton
2004-06-09 7:32 ` Sagara Wijetunga
2004-06-09 13:47 ` Chris Brenton
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=40C61E15.4050702@linuxmail.org \
--to=feizhou@linuxmail.org \
--cc=lists@edeca.net \
--cc=netfilter@lists.netfilter.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