From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Ludovic <ludovic.mailinglist@gmail.com>,
netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] ipt_ROUTE for kernel 2.6.21.5
Date: Mon, 30 Jul 2007 17:34:25 +0200 [thread overview]
Message-ID: <46AE0501.3080107@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707301709370.4354@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
> 1. ROUTE has a very usefull option --tee. AFAIK it is not possible to do
> it other way.
Thats true. Not sure in what practical situation it is used though.
> 2. Policy routing based on fwmark is not always an option if you use
> marks for other purposes.
Maybe (trying to avoid getting into discussion about too small mark
values again :)).
> So, if it is going to be removed from pom-ng I would like to keep it in
> my external pomng-repository.
Please go ahead.
Just FYI: One more reason for removing it is that its broken wrt.
IPsec handling and the duplicated functions from ip_output are out
of sync (and I think there were a few smaller problems as well).
If there really is a need for something like the tee functionality
I'm not opposed to considering merging a clean patch without these
problems for that.
next prev parent reply other threads:[~2007-07-30 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 14:42 [PATCH] ipt_ROUTE for kernel 2.6.21.5 Ludovic
2007-07-30 14:45 ` Jan Engelhardt
2007-07-30 14:47 ` Patrick McHardy
2007-07-30 14:49 ` Jan Engelhardt
2007-07-30 14:50 ` Patrick McHardy
2007-07-30 15:17 ` Krzysztof Oledzki
2007-07-30 15:34 ` Patrick McHardy [this message]
2007-07-30 16:39 ` Patrick Schaaf
2007-07-30 19:44 ` Patrick McHardy
2007-08-29 11:23 ` Krzysztof Oledzki
2007-08-29 11:55 ` Jan Engelhardt
2007-08-29 12:12 ` Krzysztof Oledzki
2007-08-30 6:46 ` Patrick McHardy
2007-08-30 18:21 ` 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=46AE0501.3080107@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=ludovic.mailinglist@gmail.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=ole@ans.pl \
/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.