Dear Tom,
Yes I did.
Here follows providers entries
Voo1 1 1 - eth2 192.168.0.1 track,balance=1,optional
Voo2 2 2 - eth3 192.168.1.1 track,balance=1,optional
Don't bother about gateway addresses, this is just from my lab testing
Br,
Jean-François Bogaerts
------------------------------------------------------------------------
On 04/05/2018 17:23, Tom Eastep wrote:
On 05/03/2018 11:55 PM, Jean-Francois Bogaerts wrote:
Hi,
I'm trying to implement internet interface failover using foolsm.
Everything works fine except when physical link goes down.
For example starting the following command when connexion is down.
shorewall disable etx_
Gives
Error: "nexthop" or end of line is expected instead of "linkdown"
ERROR: Command "ip -4 route replace table 250 default nexthop via
192.168.0.1 dev eth2 weight 1 linkdown" Failed
Obviously if physical link is not manager then failover scenario is
uncomplete
Using Shorewall 5.0.15.6
Have you specified the 'optional' option on etx_ in
/etc/shorewall/interfaces?
-Tom
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
