Re: Binding all traffic to one destination to one IP address being served.

That confirms what I'm hearing at the IBM Community. Thank you.

On Tue, Aug 22, 2023 at 11:24 AM Marc Rauzier <marc.rauzier@xxxxxxxxx>
wrote:

Le 22/08/2023 à 16:51, Rob Berendt a écrit :

I have a DMZ lpar with multiple addresses of 208.x.x.x on subnet
255.255.255.0
I have an internal lpar at address 10.y.y.y on subnet 255.255.254.0
The *DFTROUTE for the DMZ lpar is 208.x.x.1, subnet *NONE.
The DMZ lpar supports multiple interfaces (IP addresses). However I

would

like all traffic from the DMZ lpar to this one internal lpar to bind from
address 208.x.x.2
Is it as easy as adding another route like:
ADDTCPRTE RTEDEST('10.y.y.y') SUBNETMASK('255.255.254.0')
NEXTHOP('208.x.x.1') BINDIFC('208.x.x.2') TEXT('Route for BRMS to

SGCTLKIT')

On the ADDTCPRTE I believe I use the subnet mask of the destination and

not

the subnet mask of the source, right?

Yes, but if you want to bind to 208.x.x.2 IP *only* the traffic to your
10.y.y.y destination, you should use SUBNETMASK(*HOST) I think.

Sounds easy but I had a bad experience years ago trying to set up

Schowler

routes and I am a little cautious since.
I know that a few IBM i applications have their own way of "bind
specific". This app is not one of them. And none of the other IP
addresses have any business talking to this destination.

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.