On 10/08/2015 07:49 AM, Filippo Carletti wrote: > [Sorry to revive an old thread, Tom, I have a new idea] > > Tom, I followed your advice and added a couple of routes for the IP > addresses lsm have to ping. > While it works, this setup has a drawback: the ping IP can't be > reached when a link goes down.
What do you mean by 'link goes down'? Do you mean that a 'shorewall disable' has been done for the link? > Let's assume we have 2 providers: wimax and adsl. I can't use 8.8.8.8 > as ping IP in both, I need another IP (think of more than two links). > > So, I looked for an alternative approach: > - no static routes > - lsm interface option select link for pings Is this depending on route rules that direct traffic with a source IP address of a provider interface out of that interface? > - do not use shorewall disable in the lsm down script > - but adjust "balance" routing table on link status change > > It works and I like it because it seems cleaner and simpler. > > But I think I'd like to have a couple more commands in shorewall, > similar to enable/disable to adjust default route (and maybe the > provider fwmark rules). > Supposing to call them up and down, I'd use "shorewall down wimax" > (provider name) in lsm event script instead of "shorewall disable > wimax". > down will adjust the default routing, but leave untouched both rules > and provider routing. The generated script already has 'up' and 'down' commands that do something else. We could consider a new option in shorewall.conf that alters the behavior of 'disable' and 'enable'. > > For some background on the setup I'm aiming to obtain see this forum: > http://community.nethserver.org/t/wan-link-not-getting-switched-to-wan2-if-wan1-is-down/669/5 > > -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
