mstraubac / wanfailoverscript Goto Github PK

What steps will reproduce the problem?
1. Disconnecting eth0 link so system fails over to eth1
2. route table doesn't change
3. /var/log/messages shows wfs inital start entry but nothing after eth0 goes 
offline

What is the expected output? What do you see instead?
I did this this section
May 29 21:47:08 server WFS: INFO ------------------------------
May 29 21:47:08 server WFS: INFO  WAN Failover Script 2.0
May 29 21:47:08 server WFS: INFO ------------------------------
May 29 21:47:08 server WFS: INFO  Primary gateway: 10.0.0.1
May 29 21:47:08 server WFS: INFO  Secondary gateway: 10.0.0.1
May 29 21:47:08 server WFS: INFO  Threshold before failover: 3
May 29 21:47:08 server WFS: INFO  Number of target hosts: 4
May 29 21:47:08 server WFS: INFO  Tests per host: 2
May 29 21:47:08 server WFS: INFO ------------------------------

but I didn't see anything WFS afterwards. 


What version of the product are you using? On what operating system?
2.03 on centos 6.5

Please provide any additional information below.
what is the highest debug level I can set to see more diag info? 

I've tried several linux boxes and ping will return error "bad linger time" 
when a MAX_LATENCY greater than 2147 is specified.

This will permanently mark the primary link as down without any error messages.

I suggest using 2147 instead of the specified value or returning an error on 
boot.

If this value is diferent on other OSes on boot it could test if "ping -W 
MAX_LATENCY 127.0.0.1" returns an error for the sanity test.

Out put of route -n
X.X.X.X         0.0.0.0   255.255.255.255 UH    0      0        0 ppp0
172.16.16.0     0.0.0.0   255.255.255.252 U     0      0        0 eth2
10.10.1.0       0.0.0.0   255.255.255.248 U     0      0        0 eth0
192.168.1.0     0.0.0.0   255.255.255.0   U     0      0        0 eth1
169.254.0.0     0.0.0.0   255.255.0.0     U     0      0        0 eth2
0.0.0.0         0.0.0.0   0.0.0.0         U     0      0        0 ppp0

Hello
I found small problem in info log which can be confusing.

line 154 in wfs - version 2.04 (and 2.03 too)
log INFO "Max latency in ms: $MAX_LATENCY"

but correct is 
log INFO "Max latency in seconds: $MAX_LATENCY"

because paramter of ping -W is in seconds

Thanks for your work

Wan Fail over script works fine for me when i make DSL connection as Primary 
and 3g connection as Secondary. And default gateway in routing table updates 
correctly based on the link failure of this connection. But after interchanging 
modes (primary and secondary) , it doesn't work for me. The scenario is,
I made ppp0 connetion as primary and DSL connection as secondary . In this case 
wfs script running fine upto failover occurs. Thats if i disconnect 3g dongle 
for the failover to occur, all routing entries associated with ppp0 interface 
disappear. And the wfs doesn't find the host gateway for the checking of 
primary connection. So whats the solution for me ?


Thanks in Advance,
Sanju

Is there any chance to remove the dependency to bash?

I'm asking because I'd like to run the script on OpenWRT and on my router 
(Edimax 6200n) isn't enough space availabe to install bash. There is only "ash" 
and "sh" available.

I've tested your fine script and found two major issues with it

1. It will just "bounce" between gateways for me. As I see it, script will test 
for availability with icmp but as it fails on primary gw targets are once again 
reachable from secondary and the script once again switch to primary!? Are you 
sure you can test without -I ping command option and get desired behavior?

2. Default value of MAX_LATENCY is total overkill, ping will just stall if
default gw isn't available on primary interface which is most probable cause of 
failure.

Best regards,

Nikola