From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Abhishek Singh <abhishek@abhishekonline.info>,
netfilter-devel@vger.kernel.org
Subject: Re: TEE patch [was: ROUTE patch]
Date: Thu, 26 Feb 2009 11:03:46 +0100 [thread overview]
Message-ID: <49A66902.2060505@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902251543370.4191@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2009-02-25 11:29, Patrick McHardy wrote:
>>>> An index is probably useful when you want to mirror packets
>>>> somewhere outside of regular routing.
>>> ifindex?
>> Yes.
>
> Hm. I previously had removed fl.nl_u.ip4_u.tos = RT_TOS(iph->tos)
> since I reasoned:
>
> The cloned packet would theoretically go through the OUTPUT
> chain (if we did not skip Xtables to guard against
> reentracy), even if the original packet went through FORWARD
> instead. As such, it is not a true clone, and does not need
> to be treated as such.
Not sure what a true clone is ...
> Adding ifindex to the routing key also makes me wonder whether the
> mark should be used too, noting however, that it may lead to a trap
> (order of MARK vs TEE in a ruleset) - or some kinky feature:
>
> -t mangle -A PREROUTING -j TEE --gw 192.168.1.15
> -t mangle -A PREROUTING -j MARK --set-mark 1
> -t mangle -A PREROUTING -j TEE --gw 192.168.1.15
>
> I pretty much have no opinion on this.
I think it would make sense to simply allow setting all routing
keys.
next prev parent reply other threads:[~2009-02-26 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 8:59 ROUTE patch Abhishek Singh
2009-02-24 9:35 ` Jan Engelhardt
2009-02-24 13:41 ` Patrick McHardy
2009-02-24 15:30 ` Jan Engelhardt
2009-02-24 15:33 ` Patrick McHardy
2009-02-25 3:14 ` Abhishek Singh
2009-02-25 10:00 ` TEE patch [was: ROUTE patch] Jan Engelhardt
2009-02-25 10:19 ` Patrick McHardy
2009-02-25 10:26 ` Jan Engelhardt
2009-02-25 10:29 ` Patrick McHardy
2009-02-25 14:57 ` Jan Engelhardt
2009-02-26 10:03 ` Patrick McHardy [this message]
2009-03-07 0:26 ` 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=49A66902.2060505@trash.net \
--to=kaber@trash.net \
--cc=abhishek@abhishekonline.info \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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.