Re: binding TCP for FTP/SSL to a specific interface

[John Jones <chianime@xxxxxxxxx>]

CFGTCP/2.  Create a route entry that can bind traffic destined to an IP
address (or subnet) to a specific IP interface on your machine.  Here's a
sample from one of our LPARs:
Route            Subnet           Next             Preferred
Destination      Mask             Hop              Interface

*DFTROUTE        *NONE            204.44.18.129    *NONE
10.9.48.0        255.255.255.0    10.8.10.1        10.8.10.176
10.9.48.49       *HOST            204.44.18.129    204.44.18.176

Here's how you read it:
The Default Route sends everything to the gateway @ 204.44.18.129.
Exception: Traffic that's destined for the 10.9.48 subnet routes through
the gateway @ 10.8.10.1 and uses the iSeries's IP interface on 10.8.10.176.
Exception to the exception: Traffic to the remote system (*HOST) with IP
10.9.48.49 goes through the gateway 204.44.18.129 using IP interface
204.44.18.176.

On Thu, May 17, 2012 at 9:19 AM, <Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Is there a way to bind an interface to a specific NIC/IP address to be
> used for routing to an external IP (or DNS name preferably but I'm pretty
> sure the domain name isn't possible but I've been wrong before).  We have
> a situation with IPLs, etc "changing which NIC interface being used for a
> FTP/SSL connection to an external vendor.  This causes many headaches
> (especially for the Firewall admin) since the firewall can't set up rules
> for more than one internal IP address to send traffic via the SSL
> connection.  If this can be done it would definitely lighten the burden
> for me & the admin.  I know there has to be a way but I'm not a sys admin
> type but am being forced to wear that hat anyway...
>
>
> Thanks,
> Tommy Holden
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.