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: ROUTE patch
Date: Tue, 24 Feb 2009 16:33:18 +0100 [thread overview]
Message-ID: <49A4133E.4070703@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902241629550.23542@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Tuesday 2009-02-24 14:41, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> On Tuesday 2009-02-24 09:59, Abhishek Singh wrote:
>>>> What I would like to know is that if someone would like to add it to
>>>> the main iptables tree and the patchomatic repository. I am not sure
>>>> how to go about it. If someone is interested, please let me know. I
>>>> shall contribute the code and if would be happy to incorporate review
>>>> comments by other developers.
>>> [omg timeline!]
>>>
>>> Short answer, no. There is iproute2 and xt_TEE which replace it,
>>> and even patchomatic is gone.
>>>
>>> [/me takes a leap forward]
>> Perhaps we can finally get this merged. IIRC the only reason against
>> it is the IP layer duplication instead of simply using dst_output().
>>
> It cannot use dst_output because that would cause reentrancy into iptablse.
> Want a patch, though?
I would like to have a look at the current patch, yes. Don't
bother fixing anything though, I mainly want to have a look
at the routing part.
next prev parent reply other threads:[~2009-02-24 15:33 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 [this message]
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
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=49A4133E.4070703@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.