|
No NAT on the 400. You need to make the firewall PAT to the appropriate IP / Port on the 400. If the URL's are all the same server / IP address, this makes it more difficult. For instance: App1.domain.com = public IP 1 App2.domain.com = public IP 2 App3.domain.com = public IP 3 Then PAT public IP 1 port 80 to as400 ip port 8080 (or what ever port you used.) PAT public IP 2 port 80 to as400 ip port 8081 (or what ever port you used.) PAT public IP 3 port 80 to as400 ip port 8082 (or what ever port you used.) Now if you have www.domain.com/app1 and www.domain.com/app2 and www.domain.com/app3, you can do virtual servers and run all three on the same IP/Port on your AS400. More info required to go further Christopher Bipes Information Services Director CrossCheck, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Day Sent: Thursday, November 16, 2006 10:32 AM To: midrange-l@xxxxxxxxxxxx Subject: tcp/ip port mapping and url path Hi Everyone, I've run into a situation with HTTP where I have 3 different HTTP web instances running on an AS/400 v5r3, and before they go through our firewall and hit the outside world, I need to bring them all together on port 80 (default HTTP.) To clarify, the url paths for all 3 are different/unique as well. The other side of this is, when the requests come into our network on port 80, I need to segregate the requests to their correct ports, before the requests hit the web server on the 400. I have been looking at a variety of ways to do this, including NAT on the 400, which seems to be able to handle all of what I need EXCEPT the segregating by url path. I am curious if there are Exit Point Programs available, that may do this last piece for me. The other question is, if I turn NAT on, will it only affect what I specify, or will it affect all TCP/IP activity on that machine? I'd really appreciate any advice, comments, etc. you can share with me on this.
As an Amazon Associate we earn from qualifying purchases.
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.