Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of andrija.panic@gmail.com
 designates 209.85.213.181 as permitted sender)
MIME-Version: 1.0
Date: Tue, 17 Mar 2015 14:01:24 +0100
Message-ID: 
 <CAMvtBPOrMnpjrwYKqCKiUCQa6VpH9HOU9oO139w3v3GWitMJDQ@mail.gmail.com>
Subject: SNAT and remote IP problem
From: Andrija Panic <andrija.panic@gmail.com>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>,
	"dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a1142147067fae205117b90d9

--001a1142147067fae205117b90d9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

is anybody willing to share the result from the folowing command, run in VR
(VPC VR):

iptables -t nat -nvL

This should preferable be run from SSH-to-VR, instead of
ConsoleProxy-to-VR, because of nice output over SSH.


It seems in 4.3.0 and 4.3.2, SNAT is done on ALL incoming connections, no
matter to WHAT IP  the traffic from internet came - primary IP, or
additional one that is used for i.e. Static NAT - so SNAT rules always
replace remote cleint IP with MAIN IP of the VPC...

Please share your examples - this is serious bug in my opinion, and I wil
raise JIRA - but would like some examples from other guys first.

THanks,

--=20

Andrija Pani=C4=87

--001a1142147067fae205117b90d9--