Adding additional IPs is not the issue.
Configuring/Adding/opening those IPs/ports on the multiple firewalls is where we run into issues.
Also, most of are apps are configured to use DNS, and because SSL is enabled, the port cannot be specified.
So, new URLS must be created which point to the specific SSL IP/port.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, May 28, 2019 12:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: Why adulterate ports vs using an additional IP address? Was: Ports IP specific?
I differ on the definition of "a lot easier" for number 1. ADDTCPIFC and STRTCPIFC do not seem like "a lot" to me.
I don't really understand 2. Not arguing with it, I just don't understand it.
I will grant you some credence to number 3. I've underwent that a few times. Sometimes due to data center moves, sometimes due to a whim on the network guy to clean things up.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of David Gibbs via MIDRANGE-L
Sent: Tuesday, May 28, 2019 11:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: David Gibbs <david@xxxxxxxxxxxx>
Subject: Re: Why adulterate ports vs using an additional IP address? Was: Ports IP specific?
On Tue, May 28, 2019 at 10:23 AM Rob Berendt <rob@xxxxxxxxx> wrote:
I hear of people using off the wall ports to support multiple listeners. I'm not talking about anything difficult to bind specific, I'm just referring to the easy stuff, like TCP/IP.
Why would anyone set up a web server on port 80, another one on port xx, another one on port yy, etc? Instead, why not just supply multiple IP addresses to the box? Doesn't using multiple port numbers like this cause one to either use some redirects, or have the end user have to specify the port in the url, like http://myserver.com:xx?
Is it because it appears to be a drudgery to talk to the network guy and get another IP address? Or why else?
A few reasons come to mind ...
1. Listening on a different port is a lot easier than reconfiguring the system to have an additional IP address.
2. If the port is higher than 1024, you don't need to be a privileged user to bind to the port.
3. If your network guys decide to reconfigure the network and assign new IP's, there are fewer addresses to change.
david
--
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding 615 miles (Yes, you read that right) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.
You can see where my donations come from by visiting my interactive donation map ...
https://mideml.diabetessucks.net/map (it's a geeky thing).
I may have diabetes, but diabetes doesn't have me!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
