All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Olaf Rempel <razzor@kopf-tisch.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [iptables 1.3.0 / libiptc patch] sort chains by hooknum/names
Date: Sat, 05 Mar 2005 00:04:02 +0100	[thread overview]
Message-ID: <4228E962.8090005@trash.net> (raw)
In-Reply-To: <20050304212114.130e2a7c@coruscant>

Olaf Rempel wrote:
> OK, why two patches? 
> The first one need some preconditions: 
> *all* buildin chains need to be "in order" and in front of *any* user chain 
> when parsing the kernel-list.
> 
> I was not sure about this, so I made a second patch, that does not need these
> preconditions. 

I assume with "in order", you mean it relies on the current numbering of
the hooks:

/* After promisc drops, checksum checks. */
#define NF_IP_PRE_ROUTING       0
/* If the packet is destined for this box. */
#define NF_IP_LOCAL_IN          1
/* If the packet is destined for another interface. */
#define NF_IP_FORWARD           2
/* Packets coming from a local process. */
#define NF_IP_LOCAL_OUT         3
/* Packets about to hit the wire. */
#define NF_IP_POST_ROUTING      4

This seems fine to me. I'm going to apply your first patch, thanks.

Regards
Patrick

  parent reply	other threads:[~2005-03-04 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 20:21 [iptables 1.3.0 / libiptc patch] sort chains by hooknum/names Olaf Rempel
2005-03-04 22:08 ` Phil Oester
2005-03-04 22:38   ` Patrick McHardy
2005-03-04 23:15   ` Olaf Rempel
2005-03-04 23:04 ` Patrick McHardy [this message]
2005-04-19 14:51   ` Jonas Berlin
2005-03-05  2:07 ` Herve Eychenne

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=4228E962.8090005@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=razzor@kopf-tisch.de \
    /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.