I wrote a small application that does an automatic Isp switch
it isn't complete, but for my situation seems to work (in a primary/backup situation)
>> In much earlier versions of Shorewall, I had a setup that had two ISP's
>> that I was load balancing outbound requests via custom ip rules and
>> routes. Shorewall didn't yet have it's multi-isp capabilities, so it
>> wasn't very involved in the functionality of this configuration. I
>> could happily eliminate one ISP from all routes by taking down the
>> corresponding interface physically (unplug it) or virtually (ifdown).
>> Routing of outbound requests immediately failed over to the sole
>> remaining WAN connection.
>>
>Isn't a good idea if you can share this scripts with the communit, or even
>integrate them as a new feature of shorewall. Some way you can 'ping' a
>defined host to decide if that ISP is ok and if is not remove it from
>routing and disable NATs from that ISP.
>
>> While I KNOW Shorewall wasn't designed for any sort of automatic
>> failover, I'm wondering what you folks use for manual failover routines.
>> I'm trying to come up with something simple that anyone near the
>> firewall can do, as I'm not always physically present to change the
>> Shorewall config and restart it.
>>
>> Does anyone have any suggestions?
>
>So if you share knowlegde.. you make the world better.
dynaroute-multi.tgz
Description: GNU Zip compressed data------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
