Re: one iSeries ethernet card and two routers

> Remove the default route for 10.10.10.11 and replace it with a route
> specific for the 172.x.x.x subnet.  If the first x is always the same
> number, you can use a subnet mask of 255.255.0.0.  You can cover the
entire
> private address range with 172.16.0.0 / 255.240.0.0.
Ken - I did try this last week and it failed to work for us. I think of
routes as pointing
to the lan side of a router, which telco has lan router address as
10.10.10.11 and at same
time is assigning a 172. address to all inbound traffic. In earlier post
this morning, Bryan
posted what is now working for us, to have each default route with a
preferred binding,
(2 different 10. addresses for the iSeries).
jim franz
----- Original Message ----- 
From: "Ken Sims" <mdrg5003@xxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 02, 2005 11:43 AM
Subject: Re: one iSeries ethernet card and two routers


> Hi Jim -
>
> >(continued from dsl dilemna thread)
> >I think my problem is that I defined 2 *dftroutes and have the 2 routers
> >in same lan segment:
> >a dsl router for vpn access for remote iSeries users,
> >and a T1 router/firewall for iSeries webserver & pc internet traffic,
> >email, etc.
> >iSeries with 1 ethernet card  10.10.10.10 subnet 255.0.0.0
> >and a public ip 70.x.x.x for web traffic (firewall only allows port 80
> >thru to iSeries).
> >dsl router 10.10.10.11 (all users thru vpn assigned a 172.x.x.x private
> >address)
> >T1 router 10.10.10.12
> >I have a *dftroute to each router. This has never worked. For a while
> >webserver worked fine,
> >but dsl did not. Telco changed dsl config & now it works but then
> >webserver unreachable from web.
> >iSeries can ping both routers on the lan. It seems confused by 2 default
> >routes.
>
> Keep the default route for 10.10.10.12.
>
> Remove the default route for 10.10.10.11 and replace it with a route
> specific for the 172.x.x.x subnet.  If the first x is always the same
> number, you can use a subnet mask of 255.255.0.0.  You can cover the
entire
> private address range with 172.16.0.0 / 255.240.0.0.
>
> --
> Ken
> http://www.ke9nr.net/
> Opinions expressed are my own and do not necessarily represent the views
of
> my employer or anyone in their right mind.
>
> -- 
> 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.
>
>