Mike Lander wrote:
>     I am building a shorewall box that the last post has the SSH error and 
> wanted
> some feedback from the list if possible. At first I thought the two ISP's I 
> building this
> for had two T-1's with FQ ip's as it. I have the box built for this ready to 
> go.
>     Now I find out that one of the T-1's is non-routed with 5 useable ips 
> /29--Good
> the other T-1 is natted in using one of the local lan Ip's. Both full 
> T-1's-----Not so Good
> The Idea is to load balance and route specific stuff like mail etc:
> The second ISP will NOT give me a FQ ip. Shorewall fits the bill
> perfect for this need.
>     Currently the network is using routeback and static routes
> to route specific traffic to the natted ISP gateway. The only solution I 
> could
> think of was, I asked the ISP if they could change the currently
> natted gateway (lan ip on internal) to a different Class 3 IP such as 
> 10.15.75.1
> then  I could configure my second ISP to the same network
> 10.15.75.2 and track and balance the routes.
>     Now would there be a better way to do this and leave the
> Natted ISP with the same IP as the lan (loc) if ??
> 

I think you had better stick with your first idea (get the network number
changed); otherwise, you bound to end up in ARP/routing hell.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ [EMAIL PROTECTED]
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to