to use or not to use stateful capabilities
Dear All
For letting outside clients to access the webserver behind the
firewall:
I want to know, what is the difference
1. if I use connection states in rules tp accept for forwarding in the
firewall rulset:
Conn. State -s -d --proto
-sport -dport SYN ACK
New outside_client web_server tcp <1024
80 Yes No
Established web_server outside_client tcp 80
<1024 Yes No
Established outside_client web_server tcp <1024
80 No Yes
Established web_server outside_client tcp 80
<1024 No Yes2. or simple fwd rules:
iptables -t filter -A FORWARD -p tcp -s $WEBSERVER --sport 80 -d $OUT -j ACCEPT
iptables -t filter -A FORWARD -p tcp -d $WEBSERVER --dport 80 -s $OUT -j ACCEPT
I have a little knowledge about statefulness of the firewall, and can not underestand what is the deference in such a case. I mean practically.
Regards__Radien__
Quoted 9 lines · __ Radien__
Dear All
For letting outside clients to access the webserver behind the
firewall:I want to know, what is the difference
1. if I use connection states in rules tp accept for forwarding in the
firewall rulset:
Quoted 5 lines
Conn. State -s -d --proto
-sport -dport SYN ACKNew
outside_clientweb_servertcp <1024
80 Yes No
Why "source port <1024"? I would have thought most often it will be >1024,
although that's not always going to be true.
Quoted 2 lines
Established
web_serveroutside_clienttcp 80<1024 Yes No
I think you mean "SYN: Yes, ACK: Yes" here?
Quoted 14 lines
Established
outside_clientweb_servertcp <1024
80 No Yes
Establishedweb_serveroutside_clienttcp 80<1024 No Yes2. or simple fwd rules:
iptables -t filter -A FORWARD -p tcp -s $WEBSERVER --sport 80 -d $OUT -j ACCEPT
iptables -t filter -A FORWARD -p tcp -d $WEBSERVER --dport 80 -s $OUT -j ACCEPT
Quoted 3 lines
I have a little knowledge about statefulness of the firewall, and can not underestand what is the deference in such a case. I mean practically.
In this setup with only a single server behind the firewall, you are right in thinking there's not much practical difference between using the stateful and non-stateful versions of the rules.
However, once you've got five servers running behind the firewall (eg web, mail, ftp, dns, news), it's simpler to have one inbound rule per service plus one outbound rule for all the replies (- 6 rules) than to need one inbound rule plus one outbound rule per service (= 10 rules).
Also, stateful rules are much better for clients accessing the Internet, because it's impossible to think up a non-stateful rule which will allow replies inn to your network without also opening it up to port scanning attempts from people who use source port 80, 25, 53 etc for their port scanners.
Finally, some protocols such as ftp, irc etc are also very hard to support securely without using stateful rules.
So, in this simple case, pick whichever you prefer - no difference.
For a more complex situation, go stateful.
Regards,
Antony.
Signature · 6 lines
"Black holes are where God divided by zero."
- Steven Wright
Please reply to the list;
please don't CC me.