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

Yes I have a virtual IP setup and it has 2 physical IPs associated with
it. Can I bind it to the virtual IP or do I have to bind it to a specific
physical IP?


Thanks,
Tommy Holden



From: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Cc: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Date: 05/17/2012 09:55 AM
Subject: Re: binding TCP for FTP/SSL to a specific interface
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Do you have Virtual IP addresses set up and therefore multiple Ethernet
lines each with a separate Physical IP?

If that's the case the simple answer is usually to modify the *DFTROUTE
(CFGTCP option 2.) You want to have two of them there, one with a
preferred interface of each Physical IP. The one you wish to use for
this routing would be given a higher duplicate route priority (the
default is 5). In this case a 6 IS higher than a 5 so it would use that
route first.

Note that this should solve your headache here but of course means you
don't have redundancy for this because of your router.

- Larry "DrFranken" Bolhuis

On 5/17/2012 10: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