× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.