All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Heinz <creatix@hipac.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [Fwd: ACCEPT/DROP]
Date: Wed, 25 Dec 2002 12:48:41 +0100	[thread overview]
Message-ID: <3E099B19.50705@hipac.org> (raw)
In-Reply-To: Pine.LNX.4.44.0212241649520.27999-100000@el-zoido.localnet

Hi Patrick

You wrote:
> This may be true for code, but iptables rules describe sets of packets

This is true for the basic cases only. In general the matches of a rule
must be considered to be arbitrary packet action (ACCEPT, DROP,
CONTINUE) returning functions that may even return different actions for
the same packet. The only constraint for matches is that they should
work read-only on the packet content, i.e. not modify it.

Of course your statement is correct in the context of the classical
packet classification problem.


Thomas

  parent reply	other threads:[~2002-12-25 11:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 13:54 [Fwd: ACCEPT/DROP] Venkatesh Prasad Ranganath
2002-12-21 14:12 ` Markus Schaber
2002-12-24 16:04   ` Patrick McHardy
2002-12-24 16:57     ` Miguel Amador L.
2002-12-25 11:48     ` Thomas Heinz [this message]
2003-01-01 23:10       ` Markus Schaber

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=3E099B19.50705@hipac.org \
    --to=creatix@hipac.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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.