netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 06 Jan 2012 07:28:24 +0000	[thread overview]
Message-ID: <1325834904.2270.362.camel@andybev-desktop> (raw)
In-Reply-To: <CAKywjPoHa_0kjvC0H_YT+RQ-pjeTN1aUoyULbhzYOmFT51giZw@mail.gmail.com>

On Fri, 2012-01-06 at 06:15 +0100, Anton Melser wrote:
> If the only way to do the NAT is with 1600 rules then I'll stop
> looking elsewhere, thanks!

I think it probably is the only option from what you've said, especially
given the variety of different networks you have. I can't comment on the
performance though, which was one of your original questions.

> There is also the matter of routing though. I agree that this question
> is more an iproute2 issue, and could/should be better asked on the
> iproute2 list.

Well, there isn't really an iproute2 list as such...

There's netdev and LARTC, both also hosted at VGER, but by all means try
your question here if you'd like.

>  In my mind marking the packets for ToS or fwmark was
> actually for use at the routing level.

Sounds like the way to go. Gives you plenty of flexibility.

> ps. I'll do a blog post when I get a coherent config set up and post
> back here for reference and your comments. It will need failover using
> connection tracking so could end up being a nice little article.

That would be excellent. The more "real life" examples there are, the
better.

Andy



  reply	other threads:[~2012-01-06  7:28 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 [this message]
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
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=1325834904.2270.362.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).