From: Andrew Beverley <andy@andybev.com>
To: Anton Melser <melser.anton@gmail.com>
Cc: "Rob Sterenborg (lists)" <lists@sterenborg.info>,
netfilter@vger.kernel.org
Subject: Re: Advice on best way to set up multi-route NAT for lots of IPs
Date: Thu, 05 Jan 2012 16:59:59 +0000 [thread overview]
Message-ID: <1325782799.2270.339.camel@andybev-desktop> (raw)
In-Reply-To: <CAKywjPpBW-KMfS72n_fpLk10gTvZm=iDV5PjGJgPvja6sQN6NQ@mail.gmail.com>
On Thu, 2012-01-05 at 12:59 +0100, Anton Melser wrote:
> On 5 January 2012 09:59, Rob Sterenborg (lists) <lists@sterenborg.info> wrote:
> > On Sun, 2012-01-01 at 17:10 +0100, Anton Melser wrote:
> >> I thought that the best way to go would be to set up NAT using blocks
> >> in the 10.0.0.0 range. So say for each external IP I would have a /24,
> >> giving me up to 250-odd potential internal machines. So 10.1.1.1,
> >> 10.1.1.2, 10.1.1.3, etc. would map to 1.1.1.1; 10.1.2.1, 10.1.2.2,
> >> 10.1.2.3, etc. would map to 1.1.1.2, etc.
> >> I have been reading as many sites as I can but I can't work out the
> >> best way to go forward.
> >
> > So, I think I understand that you want to SNAT a complete private subnet
> > to a corresponding public subnet. Is the NETMAP target usable for you,
> > or am I misunderstanding you completely?
> > Something like:
> >
> > iptables -t nat -A POSTROUTING -s ${private_subnet} -j NETMAP --to
> > ${public_subnet}
>
> Thanks for the suggestion. It appears that NETMAP does 1:1 and both
> SNAT and DNAT. I need to do many:1 lots of times (so (many:1)*n),
Are you sure? Remember: we're talking IP addresses here (not physical
devices), and I thought you actually wanted to do one IP address from
the internal network to one external IP address. The IP address on the
internal network stipulating which external address to use.
So, I've never used NETMAP, but it sounds like it would work for you.
> and
> I don't need (or want actually) DNAT.
Especially, if as Rob says, it'll do SNAT when used in POSTROUTING.
Andy
next prev parent reply other threads:[~2012-01-05 16:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 16:10 Advice on best way to set up multi-route NAT for lots of IPs Anton Melser
2012-01-01 20:24 ` Lloyd Standish
2012-01-01 20:41 ` Anton Melser
2012-01-01 21:36 ` Anton Melser
2012-01-01 22:11 ` Lloyd Standish
2012-01-02 9:00 ` Anton Melser
2012-01-02 16:10 ` Lloyd Standish
2012-01-02 22:14 ` Anton Melser
2012-01-03 0:46 ` Lloyd Standish
2012-01-03 8:56 ` Anton Melser
2012-01-04 15:15 ` Anton Melser
2012-01-05 7:37 ` Andrew Beverley
2012-01-02 18:01 ` Pete
2012-01-02 21:14 ` Anton Melser
2012-01-02 12:38 ` Ed W
2012-01-02 13:17 ` Anton Melser
2012-01-27 23:54 ` Ed W
2012-01-05 7:35 ` Andrew Beverley
2012-01-05 8:15 ` Anton Melser
2012-01-05 17:06 ` Andrew Beverley
2012-01-05 18:39 ` Rob Sterenborg (Lists)
2012-01-06 5:15 ` Anton Melser
2012-01-06 7:28 ` Andrew Beverley
2012-01-05 8:59 ` Rob Sterenborg (lists)
2012-01-05 11:59 ` Anton Melser
2012-01-05 13:17 ` Rob Sterenborg (lists)
2012-01-05 16:59 ` Andrew Beverley [this message]
2012-01-05 17:08 ` Rob Sterenborg (lists)
2012-01-05 17:14 ` Andrew Beverley
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=1325782799.2270.339.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=lists@sterenborg.info \
--cc=melser.anton@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).