Linux Netfilter discussions
 help / color / mirror / Atom feed
From: richard lucassen <netfilter@lucassen.org>
To: netfilter@lists.netfilter.org
Subject: iptables jump to userdefined chain and ESTABLISHED,RELATED rules
Date: Fri, 10 Oct 2003 13:26:41 +0200	[thread overview]
Message-ID: <20031010132641.2591d3b5.netfilter@lucassen.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

Hello,

I want all traffic on port 80 be handled by a userdefined chain
"CH_WWW". Now my question: What is better, this way (I let the port
80 packets jump first, then I have _two_ ESTABLISHED,RELATED rules, as
well in the INPUT as in the CH_WWW chain):

********************************************************************
${IPT} -A INPUT -p tcp --dport 80 -j CH_WWW
${IPT} -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
[..]

And an extra ESTABLISHED,RELATED in the CH_WWW:
${IPT} -A CH_WWW -m state --state ESTABLISHED,RELATED -j ACCEPT
${IPT} -A CH_WWW (first rule)
[..]
********************************************************************

or this (I have _one_ ESTABLISHED,RELATED rule, and then let port 80 
jump):

********************************************************************
${IPT} -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
${IPT} -A INPUT -p tcp --dport 80 -j CH_WWW
[..]

And an extra ESTABLISHED,RELATED in the CH_WWW:
${IPT} -A CH_WWW (first rule)
[..]
********************************************************************

Both ways work, but I'd say the second way is the best. Am I right?

Richard.

-- 
___________________________________________________________________
Recursion: see recursion

+------------------------------------------------------------------+
| Richard Lucassen, Utrecht                                        |
| Public key and email address:                                    |
| http://www.lucassen.org/mail-pubkey.html                         |
+------------------------------------------------------------------+


[-- Attachment #2: 00000000.mimetmp --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

             reply	other threads:[~2003-10-10 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 11:26 richard lucassen [this message]
2003-10-11 16:26 ` iptables jump to userdefined chain and ESTABLISHED,RELATED rules Cedric Blancher
2003-10-11 17:45   ` CAM IT Solutions
2003-10-12 11:16     ` Willy TARREAU
2003-10-12 17:53       ` richard lucassen
2003-10-12 18:54         ` Cedric Blancher
2003-10-12 21:40           ` richard lucassen
2003-10-12 19:02         ` Cedric Blancher
2003-10-12 15:10   ` Joel Newkirk
2003-10-12 15:15     ` Cedric Blancher
  -- strict thread matches above, loose matches on Subject: below --
2003-10-09 20:20 richard lucassen

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=20031010132641.2591d3b5.netfilter@lucassen.org \
    --to=netfilter@lucassen.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