Routes are the magic. You can create routes for a specific target to use
a specific local interface and further set the priority so that if one
isn't available another can be used. You can really make it complicated,
and hard to understand too!
However, you are setting up a scenario though that I refer to as
*LANDMINE. If you end up with many static routes and anything changes
you're stuck with many static changes. Clearly some static routes may be
needed in various situations but fewer is always better. None is the
best number if you can make that work.
Note that the routes are used only for connections initiated from IBM i.
Also note that IBM i will NOT respond to an inbound packet if there is
no configured route available in IBM i. This is different (and better)
behavior from most other O/Ss found in the average shop.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 5/9/2016 2:50 PM, Rob Berendt wrote:
There is some potential for that, but routing is not a cure all.
Suppose I want to ftp from LparA to LparB and I want it to use interface
34 when it goes out from LparA.
Now I want to use one of my Domino servers (let's say 37) and I want to
open a DB2 connection to LparB. That should come from 37.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.