From: Andrew Beverley <andy@andybev.com>
To: Lloyd Standish <lloyd@crnatural.net>
Cc: netfilter@vger.kernel.org
Subject: Re: problem with multi-level SNAT? (multiple uplinks/providers)
Date: Mon, 02 Jan 2012 18:25:33 +0000 [thread overview]
Message-ID: <1325528733.2270.32.camel@andybev-desktop> (raw)
In-Reply-To: <op.v7e0qja7x1lyi3@debiandesk2.net>
On Sun, 2012-01-01 at 11:12 -0600, Lloyd Standish wrote:
> I would like to know why SNAT without packet marking drops the
> connections for interfaces that have "upstream NAT," while the fwmark
> method succeeds.
I can't answer this, but on your other comment...
> As a related aside, I'd appreciate comments on whether or not the "-p
> tcp" in the following example rule is advisable (I omitted "-p tcp"
> from my SNAT rules.): iptables -t nat -A POSTROUTING -p tcp -o eth0 -j
> SNAT --to-source 194.236.50.155
Well, I never put a -p tcp in SNAT for any of my configurations. I'm not
sure why you would want to limit SNAT to just TCP?
Andy
next prev parent reply other threads:[~2012-01-02 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 17:12 problem with multi-level SNAT? (multiple uplinks/providers) Lloyd Standish
2012-01-02 18:25 ` Andrew Beverley [this message]
2012-01-02 19:01 ` Lloyd Standish
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=1325528733.2270.32.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=lloyd@crnatural.net \
--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