I have a DMZ lpar which supports multiple interfaces (IP addresses).

Many IBM i products do not "bind specific".  I want to ensure that all communication between this DMZ lpar and our Safe Guarded Copy lpar is only on one of these interfaces.  If it wasn't for BRMS I'd have no comm going to this SGC lpar.

DMZ lpar:

Internet address:  208.xxx.xxx.xxx

subnet:  255.255.255.0

SGC lpar:

Internet address:  10.yyy.yyy.yyy

subnet:  255.255.254.0

I'm thinking it's as easy as:

ADDTCPRTE RTEDEST('10.yyy.yyy.yyy') SUBNETMASK('255.255.254.0') NEXTHOP('208.xxx.xxx.1') BINDIFC('208.xxx.xxx.xxx') TEXT('Route for BRMS to SGCTLKIT')    

But I remember trying to deal with the concept of Schowler routes years ago and that experience left me cautious about dealing with routes.

Also, on ADDTCPRTE, do you enter the subnetmask of the source or the destination?  I think it's the destination.

Standard routing decisions are based on destination.

So yes, it is the subnetmask of the destination, otherwise wouldn't make sense.

I don't know what a "Schowler route" route is, never heard such term in networking (maybe IBM specific?), maybe are you referring to Equal Cost Balancing/Routing?

BTW, it is possible in networking do routing decisions based on different variables, normally one uses routers for that (Policy Based Routing).

Anyway, the particular sending software decides the source address of the packet and interface, the standard routing stack rule just act on the destination address.

I have a DMZ lpar which supports multiple interfaces (IP addresses).

Many IBM i products do not "bind specific".  I want to ensure that all communication between this DMZ lpar and our Safe Guarded Copy lpar is only on one of these interfaces.  If it wasn't for BRMS I'd have no comm going to this SGC lpar.

DMZ lpar:

Internet address:  208.xxx.xxx.xxx

subnet:  255.255.255.0

SGC lpar:

Internet address:  10.yyy.yyy.yyy

subnet:  255.255.254.0

I'm thinking it's as easy as:

ADDTCPRTE RTEDEST('10.yyy.yyy.yyy') SUBNETMASK('255.255.254.0') NEXTHOP('208.xxx.xxx.1') BINDIFC('208.xxx.xxx.xxx') TEXT('Route for BRMS to SGCTLKIT')    

But I remember trying to deal with the concept of Schowler routes years ago and that experience left me cautious about dealing with routes.

Also, on ADDTCPRTE, do you enter the subnetmask of the source or the destination?  I think it's the destination.

I have a DMZ lpar which supports multiple interfaces (IP addresses).

Many IBM i products do not "bind specific".  I want to ensure that all communication between this DMZ lpar and our Safe Guarded Copy lpar is only on one of these interfaces.  If it wasn't for BRMS I'd have no comm going to this SGC lpar.

DMZ lpar:

Internet address:  208.xxx.xxx.xxx

subnet:  255.255.255.0

SGC lpar:

Internet address:  10.yyy.yyy.yyy

subnet:  255.255.254.0

I'm thinking it's as easy as:

ADDTCPRTE RTEDEST('10.yyy.yyy.yyy') SUBNETMASK('255.255.254.0') NEXTHOP('208.xxx.xxx.1') BINDIFC('208.xxx.xxx.xxx') TEXT('Route for BRMS to SGCTLKIT')    

But I remember trying to deal with the concept of Schowler routes years ago and that experience left me cautious about dealing with routes.

Also, on ADDTCPRTE, do you enter the subnetmask of the source or the destination?  I think it's the destination.

I have a DMZ lpar which supports multiple interfaces (IP addresses).

Many IBM i products do not "bind specific".  I want to ensure that all communication between this DMZ lpar and our Safe Guarded Copy lpar is only on one of these interfaces.  If it wasn't for BRMS I'd have no comm going to this SGC lpar.

DMZ lpar:

Internet address:  208.xxx.xxx.xxx

subnet:  255.255.255.0

SGC lpar:

Internet address:  10.yyy.yyy.yyy

subnet:  255.255.254.0

I'm thinking it's as easy as:

ADDTCPRTE RTEDEST('10.yyy.yyy.yyy') SUBNETMASK('255.255.254.0') NEXTHOP('208.xxx.xxx.1') BINDIFC('208.xxx.xxx.xxx') TEXT('Route for BRMS to SGCTLKIT')    

But I remember trying to deal with the concept of Schowler routes years ago and that experience left me cautious about dealing with routes.

Also, on ADDTCPRTE, do you enter the subnetmask of the source or the destination?  I think it's the destination.

I have a DMZ lpar which supports multiple interfaces (IP addresses).

Many IBM i products do not "bind specific".  I want to ensure that all communication between this DMZ lpar and our Safe Guarded Copy lpar is only on one of these interfaces.  If it wasn't for BRMS I'd have no comm going to this SGC lpar.

DMZ lpar:

Internet address:  208.xxx.xxx.xxx

subnet:  255.255.255.0

SGC lpar:

Internet address:  10.yyy.yyy.yyy

subnet:  255.255.254.0

I'm thinking it's as easy as:

ADDTCPRTE RTEDEST('10.yyy.yyy.yyy') SUBNETMASK('255.255.254.0') NEXTHOP('208.xxx.xxx.1') BINDIFC('208.xxx.xxx.xxx') TEXT('Route for BRMS to SGCTLKIT')    

But I remember trying to deal with the concept of Schowler routes years ago and that experience left me cautious about dealing with routes.

Also, on ADDTCPRTE, do you enter the subnetmask of the source or the destination?  I think it's the destination.