All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
	Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>,
	Amin Azez <azez@ufomechanic.net>,
	Hendrik Nordstrom <henrik@henriknordstrom.net>
Subject: Re: NF structural changes (was: dangerous?)
Date: Wed, 14 Mar 2007 22:05:01 +0100	[thread overview]
Message-ID: <45F8637D.3060600@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0703142148430.1199@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> As a result of the "dangerous? Setting mark in nat table" thread, I have 
> just drawn this idea of mine down, where:
> 
>  - filter and mangle tables are merged

We need to preserve compatibility (meaning we must keep the rerouting
in mangle), so I don't see the advantage over simply removing the
restrictions to mangle.

>  - filtering comes early, even before nat
>    (so that, for example, packets do not needlessy be MARKed, mangled,
etc.)

Would probably make life easier (no more -m conntrack --ctorigdst),
but I don't see how this could be changed without breaking rulesets.

  reply	other threads:[~2007-03-14 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 20:57 NF structural changes (was: dangerous?) Jan Engelhardt
2007-03-14 21:05 ` Patrick McHardy [this message]
2007-03-14 21:23   ` Jan Engelhardt
2007-03-14 21:48     ` Amin Azez
2007-03-15  2:24       ` Jan Engelhardt
2007-03-15  9:09         ` Henrik Nordstrom
2007-03-14 22:02     ` Patrick McHardy
2007-03-14 22:29       ` Amin Azez
2007-03-14 21:41 ` Krzysztof Oledzki
2007-03-14 21:49   ` Jan Engelhardt

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=45F8637D.3060600@trash.net \
    --to=kaber@trash.net \
    --cc=azez@ufomechanic.net \
    --cc=henrik@henriknordstrom.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kadlec@blackhole.kfki.hu \
    --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.