× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Really has nothing to do with apache per se. This is all just basic
networking. I think Rob Berendt has investigated it before. You have two
interfaces on the same subnet. If the routes out of both interfaces are
the same, then the system is going to pick the interface you want to
use, and I don't think you can control it.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Dean
Eshleman
Sent: Friday, January 19, 2018 8:49 AM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Apache reverse proxy configuration and ip
addresses

As I stated in the original message, 10.2.0.109 is one of the IP
addresses
assigned to System 1 (IBMi). I know the ip address for my PC is
something
different. I'm just surprised that when System 1, Apache server 1
forwards
the request to the Apache server on System 2 that the client IP
address in
the access log file shows 10.2.0.109 instead of 10.2.0.31 since I
specified
10.2.0.31 port 10200 when calling the web service on System 1. I
wonder
how System 1 decides which ip address it uses to forward the request?

Dean Eshleman
Software Development Architect
Everence

On 1/18/2018 6:16 PM, Nathan Andelin wrote:
Maybe 10.2.0.109 the address of your PC on the network, that get's
picked up in the log as the originator of the requests.



On Thu, Jan 18, 2018 at 3:01 PM, Dean Eshleman
<Dean.Eshleman-d3hNrR/acMxWk0Htik3J/w@xxxxxxxxxxxxxxxx>
wrote:

Hi,

We have two Apache servers on our IBM I that is in the DMZ. They
are
setup to listen on different ip addresses and different ports.
These
servers are for web services.

System 1 - IBMi in DMZ
Apache Server 1 listens on IP Address 10.2.0.31 port 10200 Apache
Server 2 listens on IP Address 10.2.0.109 port 10000

I'm adding a reverse proxy setup to Server 1 so that it forwards
requests back to another Apache server on an IBM I (System 2) in
our
trusted network. When I test this setup, the Apache access log on
System 2 shows the client ip address as 10.2.0.109. I was
expecting it to
be 10.2.0.31.
Anyone know why that is?

Dean Eshleman
Software Development Architect
Everence

__________________________________________________________
____________
Confidentiality Notice: This information is intended only for the
individual or
entity named. If you are not the intended recipient, do not use or
disclose
this information. If you received this e-mail in error, please delete
or
otherwise destroy it and contact us at (800) 348-7468 so we can take
steps to
avoid such transmission errors in the future. Thank you.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list
To post a message email: WEB400@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.