I really dislike the lack of customization on the wan failover app but I also do not understand why it recovers so quickly?
Here is an offline event (note the timestamp):
and here is the online event:
If I have it set to fail if 10 out of 10 tests is done......oh god i think I just answered my own question but I hope not. Does it then consider the connection no longer a failure if even 1 test passes after that because it is technically no longer 10 out of 10? That is one strange way of doing things.
Here is an offline event (note the timestamp):
Event: WanFailoverEvent
Event Time: 2022-03-11 10:32:40.514.
Event Summary:
WAN went offline
Event Details:
action = DISCONNECTED
interface id = 1
name = WAN1 Comporium
os name = eth3
time stamp = 2022-03-11 10:32:40.514
Event Time: 2022-03-11 10:32:40.514.
Event Summary:
WAN went offline
Event Details:
action = DISCONNECTED
interface id = 1
name = WAN1 Comporium
os name = eth3
time stamp = 2022-03-11 10:32:40.514
and here is the online event:
Event: WanFailoverEvent
Event Time: 2022-03-11 10:32:41.253.
Event Summary:
WAN came online
Event Details:
action = CONNECTED
interface id = 1
name = WAN1 Comporium
os name = eth3
time stamp = 2022-03-11 10:32:41.253
Event Time: 2022-03-11 10:32:41.253.
Event Summary:
WAN came online
Event Details:
action = CONNECTED
interface id = 1
name = WAN1 Comporium
os name = eth3
time stamp = 2022-03-11 10:32:41.253
If I have it set to fail if 10 out of 10 tests is done......oh god i think I just answered my own question but I hope not. Does it then consider the connection no longer a failure if even 1 test passes after that because it is technically no longer 10 out of 10? That is one strange way of doing things.