Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of terbolous@gmail.com designates
 209.85.212.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMvtBPN3Amr+u0jCwPPj4sf-KPo-MyN=0xavO_iAq=VMm60TMA@mail.gmail.com>
References: 
 <CAMvtBPN3Amr+u0jCwPPj4sf-KPo-MyN=0xavO_iAq=VMm60TMA@mail.gmail.com>
Date: Tue, 9 Dec 2014 00:02:22 +0100
Message-ID: 
 <CAP997UdHp4nA879pd2H+rvE_c8kkgDCy5e=EHaPooE4Ha8C+fQ@mail.gmail.com>
Subject: Re: Port forwarding (web) - doesnt show real client IP
From: Erik Weber <terbolous@gmail.com>
To: dev <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=f46d043be1aa4f4e210509bc6bf2

--f46d043be1aa4f4e210509bc6bf2
Content-Type: text/plain; charset=UTF-8

On Mon, Dec 8, 2014 at 11:42 PM, Andrija Panic <andrija.panic@gmail.com>
wrote:

> Hi,
>
> when doing port forwarding on VPC VR - port 80 - when some client access
> web site - only the main Public IP of the VPC is logged in apache access
> logs as remote IP.
>
> Why is this behaviour - and can this be changed ?
> My understanding is that this is kind of bug (unless needed for some other
> reasons) - port forwading is DNAT in essence, so only the destination
> IP/port should be changed, not proxied all the way, as it seems to be the
> case here...
>
> I read on other guys mailing list - same behavior for loadbalancer...
>
>
This is common for all load balancers.
Haven't checked, but you could see if the CloudStack LB expose the client
IP as X-Forwarded-For header, which is the normal way of doing it.


-- 
Erik

--f46d043be1aa4f4e210509bc6bf2--