Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: 2 Questions--state (est, rel) and tuning
Date: Fri, 03 Jun 2005 16:38:25 +0200	[thread overview]
Message-ID: <42A06B61.4020009@mnemon.de> (raw)
In-Reply-To: <B80488675062364A909EE60F4A66603807840EAE@usilms23.ca.com>

Ginter, Jeff A schrieb:

> For example on a Checkpoint or PIX you would NOT need the 
> established or related rules.  They are aware that a 
> conversation has started and will let return packets in....of course, 
> it is possible that there is an implicit rule on a Checkpoint or PIX 
> that is "hidden" that allows established and related and the user just 
> doesn't see this and in iptables you do...but I thought this was part 
> of the state engine.

I can't give a proof for Checkpoint and PIX, but I think that's exactly
the way it is: You simply can't see these rules, they are generated in
the background, if you decide to have a stateful firewall, and are then
compiled into the rule set.

Looking at pf from the BSD folks, you can say "keep-state" and the
meaning is, that from this point on pf creates the needed rules on the
fly and puts it in the state table (and later on automatically deletes
these dynamic rules).

iptables - as far as I know - doesn't have such "automatics" and thus
you have to specify est,rel rules explicitely.

Any other / additional notions ?

Have a nice time,

Joerg



  reply	other threads:[~2005-06-03 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 14:06 2 Questions--state (est, rel) and tuning Ginter, Jeff A
2005-06-03 14:38 ` Jörg Harmuth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-03 12:59 Ginter, Jeff A
2005-06-03 13:23 ` Daniel Lopes
2005-06-03 15:40 ` Jason Opperisano

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=42A06B61.4020009@mnemon.de \
    --to=harmuth@mnemon.de \
    --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