All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: 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 16:47:22 +0200	[thread overview]
Message-ID: <46ADF9FA.4000901@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707301644360.26373@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Jul 30 2007 16:42, Ludovic wrote:
> 
>>sorry if there is already some patches about this but i've searched
>>one week how to make the ROUTE target work well.
>>
>>Here are two patches (one for ipv4 and one for ipv6) which change
>>ipt_register and ipt_unregister to xt_register and xt_unregister and
>>which add .family = AF_INET in the xt_target structure declaration.
> 
> 
> Somehow this feels like déjà-vu. ipt_ROUTE is, well, a hack
> and the proper solution to it is policy routing; e.g. based on fwmark.


Fully agreed (well, I made that argument for ages), I think we
should simply remove it from pomng to avoid misleading users
into thinking it would be the proper way to do things.

  reply	other threads:[~2007-07-30 14:47 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 [this message]
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
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=46ADF9FA.4000901@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.de \
    --cc=ludovic.mailinglist@gmail.com \
    --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.