RE: IP Issue

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Define your route to the bank or the internet to use the interface you want.
Then all outbound connections thru that route will use the same outbound IP.
This will not affect inbound connections.

For Example:
ADDTCPRTE RTEDEST(*DFTROUTE)    
          SUBNETMASK(*NONE)     
          NEXTHOP('192.168.1.1')
          BINDIFC('192.168.1.2')

Chris Bipes



-----Original Message-----
mwalter@xxxxxxxxxxxxxxx

Hello all,

I am having an issue with IP addresses. We have 3 interfaces defined for
our single ethernet line. One is the regular interface for telnet and other
stuff. It's internal IP is 192.168.0.2. We have two more for our two Domino
Servers. .151 and .152 of our private network.  I have static mappings
defined in our Pix firewall that map the .2 address to xxx.xxx.xxx.102, and
the .151 address to xxx.xxx.xxx.100. We connect to our bank via FTP. It
allows the 102 public address into it's firewall. Suddenly, for no apparent
reason, their firewall is seeing the 100 address. The firewall config still
looks correct. Any idea why the iSeries is using the 151 address for FTP?
Am I missing something here? Not even sure where to assign an interface to
a TCP application.