From: Phil Oester <kernel@linuxace.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: snat to multiple source ip
Date: Mon, 26 Sep 2005 10:47:28 -0700 [thread overview]
Message-ID: <20050926174728.GA17007@linuxace.com> (raw)
In-Reply-To: <BAY103-DAV122786F84D83782AC7249B28B0@phx.gbl>
On Mon, Sep 26, 2005 at 06:39:13PM +0200, Marco Berizzi wrote:
> > On Mon, Sep 26, 2005 at 05:38:48PM +0200, Marco Berizzi wrote:
> > > I would like to better understand the SNAT target when
> > > multiple --to-source are specified.
> >
> > This capability has been removed from newer (2.6.11+) kernels,
> > and was reported as being broken in kernels prior to that.
>
> Thanks for the reply. FYI tests were done with linux 2.4.31
> Is there any other equivalent under 2.4 or 2.6?
You could try the random match from pom, but to do this without
patching the kernel, probably could use multiple -s rules:
-s 10.0.0.0/24 -j SNAT x.x.x.x
-s 10.1.0.0/24 -j SNAT y.y.y.y
or somesuch.
Phil
next prev parent reply other threads:[~2005-09-26 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 15:38 snat to multiple source ip Marco Berizzi
2005-09-26 16:10 ` Phil Oester
2005-09-26 16:39 ` Marco Berizzi
2005-09-26 17:47 ` Phil Oester [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 19:00 Derick Anderson
2005-09-20 15:25 Harrison, Bruce (CXO)
2005-09-20 15:53 ` Marco Berizzi
2005-09-20 15:07 Derick Anderson
2005-09-20 15:16 ` Marco Berizzi
2005-09-20 15:24 ` Edmundo Carmona
2005-09-20 12:39 Marco Berizzi
2005-09-20 12:44 ` Edmundo Carmona
2005-09-20 13:37 ` Marco Berizzi
2005-09-20 13:58 ` /dev/rob0
2005-09-20 14:24 ` Marco Berizzi
2005-09-15 9:59 Marco Berizzi
2005-09-15 12:21 ` /dev/rob0
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=20050926174728.GA17007@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pupilla@hotmail.com \
/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.