RE: Selecting an ethernet line

["York, Albert" <albert.york@xxxxxxxxxxxxxx>]

Andy,

I did try bouncing TCP/IP with the same results. 

Just to clarify, I am only interested in traffic originating from the
AS/400. Incoming traffic will be routed to one of the interfaces by the IP
address assigned to that interface.

Here is what I have:

     Internet         Subnet             Line       Line  
Opt  Address          Mask             Description  Type  
     10.64.103.211    255.255.255.0    ETHLINE      *ELAN 
     10.64.103.212    255.255.255.0    ETHLINE2     *ELAN


     Route            Subnet           Next             Preferred     
Opt  Destination      Mask             Hop              Interface     
     *DFTROUTE        *NONE            10.64.103.2      10.64.103.211 
     *DFTROUTE        *NONE            10.64.103.2      10.64.103.212

BTW, here is what the BookManager says, which doesn't clarify it for me at
all.

BINDIFC
    The local IP interface to bind this route to. The binding is preferred
and not absolute.
 
    If the IP interface defined for BINDIFC is active then the route
specified will be bound to that interface. If the 
    IP interface defined for BINDIFC is not active then another active IP
interface using the same line description 
    will be used. If the IP interface defined for BINDIFC is not active and
no other interfaces using the same line 
    description are active then any route and no other interfaces using the
same line description are active then 
    any active interface on the same network will be used. If no IP
interfaces on the same network are available 
    then the route will be disabled.


Albert York                          



        -----Original Message-----
        From:   Andy Nolen-Parkhouse [SMTP:aparkhouse@xxxxxxxxx]
        Sent:   Friday, May 09, 2003 9:54 AM
        To:     'Midrange Systems Technical Discussion'
        Subject:        RE: Selecting an ethernet line

        Albert,

        I don't know about the requirement for restarting TCP/IP, it doesn't
        strike me as reasonable, but that doesn't mean it would not help.

        I'm assuming that you have removed your old default route.

        This should only work for connections initiated from the iSeries.
        Connections initiated from the network should go to the IP address
        specified in your DNS.  Would your network application have a
problem
        communicating to an IP address other than that specified in the DNS?

        If all else fails, You could try ensuring that you only have the two
        default routes bound to the different interfaces and then bounce
TCP/IP
        when you have the opportunity.  It doesn't make sense that this
should be
        required however.

        Regards,
        Andy


        > bounces@xxxxxxxxxxxx] On Behalf Of York, Albert
        > Subject: RE: Selecting an ethernet line
        > 
        > Andy,
        > 
        > I figured out how to create routes for each line. However, the
AS/400
        > seems
        > to be ignoring the DUPRTEPTY parameter. It always selects the line
in
        > the
        > order that I create the routes. I can tell this because I have an
        > application that works on one line but not the other. I suspect
the
        > problem
        > is caused by a missing firewall rule somewhere on the LAN.
        > 
        > If I inactivate the first interface the application works fine. If
I
        > create
        > the route for the second interface first the application works
fine.
        > The
        > result is always the same regardless of the value of DUPRTEPTY.
        > 
        > Do I  have to restart TCP/IP before it uses that value?
        > 
        > Thanks,
        > 
        > Albert




        _______________________________________________
        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.cgi/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.