From: Feizhou <feizhou@linuxmail.org>
To: netfilter@lists.netfilter.org
Subject: Re: Is this firewall good enough?
Date: Wed, 09 Jun 2004 04:11:05 +0800 [thread overview]
Message-ID: <40C61D59.1090505@linuxmail.org> (raw)
In-Reply-To: <200406081623.15400.Antony@Soft-Solutions.co.uk>
>>So to avoid loading the connection tracking module, I would put rules to
>>handle return packets in the proper chain.
>>
>>eg: iptables -A tcp_packets -p tcp --sport 1024:65535 --dport 80 -j ACCEPT
>
>
> That rule allows packets *to* port 80 - I was asking how you deal with *reply*
> packets - the ones *from* port 80 on the remote server.
Sorry, the OP was about packets to his box and not from replies from a
box he is trying to access.
iptables -A tcp_packets -p --sport 80 --dport 1024:65535 -j ACCEPT
>
>
>>Then i put tcp/udp/icmp packets to the proper chain
>>
>>eg: iptables -A INPUT -p tcp -j tcp_packets
>>
>>You could make a catch all for return packets like:
>>
>>iptables -A INPUT -p tcp ! --syn -j ACCEPT
>
>
> You seem to be advocating not using the ESTABLISHED,RELATED match - which
> would render the firewall stateless (like ipchains) instead of stateful.
> That seems a backwards step to me - or have I misunderstood something?
>
Stateful is expensive. If you have a high traffic load, it is not worth
it. The context is when the box is a server. If you are protecting your
home box, by all means, use stateful.
next prev parent reply other threads:[~2004-06-08 20:11 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 [this message]
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
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=40C61D59.1090505@linuxmail.org \
--to=feizhou@linuxmail.org \
--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