All of lore.kernel.org
 help / color / mirror / Atom feed
From: "__ Radien__" <radien@zworg.com>
To: netfilter@lists.netfilter.org
Subject: to use or not to use stateful capabilities
Date: Mon,  5 Apr 2004 03:49:43 -0700	[thread overview]
Message-ID: <20705.1081162183@zworg.com> (raw)

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   Yes


2.   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__


             reply	other threads:[~2004-04-05 10:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 10:49 __ Radien__ [this message]
2004-04-05 11:02 ` to use or not to use stateful capabilities Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-04-05 10:59 __ Radien__
2004-04-05 11:06 ` Antony Stone
2004-04-05 12:53 __ Radien__
2004-04-05 13:19 ` Antony Stone
2004-04-06  7:01 __ Radien__
2004-04-06  7:26 ` Cedric Blancher
2004-04-07  6:27 __ Radien__

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=20705.1081162183@zworg.com \
    --to=radien@zworg.com \
    --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 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.