Dear Mike, In my case firewall is not perform NAT. means NAT not configured in firewall.
> On 31-May-2019, at 12:00 AM, Mike Jumper <[email protected]> wrote: > > On Mon, May 27, 2019 at 11:43 PM Manoj Patil <[email protected] > <mailto:[email protected]>> wrote: > hi, > > i am done all the setting as per document but it shows the Firewalll WAN ip > not machine local ip address > > If the firewall in question is performing network address translation (NAT), > then this is really all that can be expected. The IP address visible to > servers on the internet will only be the WAN IP of the router. It is > (thankfully) not possible for a server to see past NAT. As far as your server > is concerned, that WAN IP address is the correct address of the client. > > > my server.xml setting > ... > > Assuming those addresses are correct for your reverse proxy, your server.xml > looks fine. > > My nginx setting is—— > ... > > Your Nginx configuration looks fine as well. > > > Username Start time Duration Connection name Remote > host > samho > 2019-05-28 12:07:55 0 seconds samta_ho 223.196.84.130 > > The above is a public IP. If the above public IP is that of a firewall in > front of your user (not your reverse proxy), then this is the behavior > expected. You are not going to be able to determine the internal IP of a user > behind a firewall performing NAT. You will only be able to determine the IP > of the machine actually connecting to your reverse proxy, which in this case > would be the WAN port of the router. > > - Mike >
