All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen Dinh Nam <64vn@cardvn.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: is this make sense: iptables -A PREROUTING -t nat -j SNAT --to 0.0.0.0
Date: Wed, 23 Mar 2005 01:56:26 +0700	[thread overview]
Message-ID: <42406A5A.10003@cardvn.net> (raw)
In-Reply-To: <20050322145522.GA12927@roonstrasse.net>

I use each -j SNAT for an interface because -j MASQUERADE doesn't work 
well with multipath routes, and SNAT has better performance than MASQ.

CONNMARK helps keeping packets of the same connection routed via a given 
nexthop which is selected by the multipath route for the first (--state 
NEW) packet, I wrote about it here:
http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking
it's a vital part of a multihomed internet gateway. With SNAT/MASQ 
available in PREROUTING, CONNMARK is no long required, hence save a lot 
of works and increase the performance.

Max Kellermann wrote:

> Why don't you just use -j MASQUERADE if writing one rule per interface
> is too much work for you?
>
> I don't understand how CONNMARK helps with your "traditional method".
>
> Max
>

  reply	other threads:[~2005-03-22 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 14:47 is this make sense: iptables -A PREROUTING -t nat -j SNAT --to 0.0.0.0 Nguyen Dinh Nam
2005-03-22 14:55 ` Max Kellermann
2005-03-22 18:56   ` Nguyen Dinh Nam [this message]
2005-03-25 17:28 ` Nguyen Dinh Nam
2005-03-25 19:07   ` Newbie question about fragmentation and the PRE_ROUTING hook Devesh Agrawal
2005-03-25 23:32     ` Devesh Agrawal
2005-03-26 12:03   ` is this make sense: iptables -A PREROUTING -t nat -j SNAT --to 0.0.0.0 Jonas Berlin
2005-03-26 15:02     ` Nguyen Dinh Nam

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=42406A5A.10003@cardvn.net \
    --to=64vn@cardvn.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.