From: Patrick McHardy <kaber@trash.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Per-client NAT routing -- possible?
Date: Fri, 24 Mar 2006 13:58:56 +0100 [thread overview]
Message-ID: <4423ED10.6060008@trash.net> (raw)
In-Reply-To: <4423E4E2.9030303@ufomechanic.net>
Amin Azez wrote:
> Patrick McHardy wrote:
>
>> Amin Azez wrote:
>>
>>>> Could someone please point me in the right direction? Or is this not
>>>> possible?
>>>
>>>
>>>
>>> I think you can use ipt_route to select the output gateway or interface,
>>> NAT should then work after that.
>>
>>
>>
>> That sounds rather hackish. The normal way to do something like that
>> is to use normal multipath routes and, if NAT to different IPs needs
>> to be used, CONNMARK to bind connections to one of the paths.
>
>
> Respecting your experience and acknowledging my ignorance, but THAT
> seems like the hacky way to me. I realise most of the world thinks I'm
> wrong, I merely offer this insight into the strangeness of the "other"
> persons mind.
>
> I guess I do it this way because I do a lot of bridging.
I guess its a matter of taste which way you prefer, but one argument
against the route target is that it replicates lots of code from
the IP layer, which is never a good idea and most likely already
out of date. From a short look, it seems like it doesn't work with
IPsec for example.
next prev parent reply other threads:[~2006-03-24 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 17:16 Per-client NAT routing -- possible? Jeremy Elson
2006-03-23 2:49 ` Jeremy Elson
2006-03-23 10:07 ` Amin Azez
2006-03-23 18:26 ` Patrick McHardy
2006-03-24 12:24 ` Amin Azez
2006-03-24 12:58 ` Patrick McHardy [this message]
2006-03-24 13:28 ` Guy Martin
2006-03-27 6:37 ` Oskar Berggren
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=4423ED10.6060008@trash.net \
--to=kaber@trash.net \
--cc=azez@ufomechanic.net \
--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.