changelog

Version 2.06
    * Added loss threshold in checks logic.
    * Added route checks from @GWuk fork.
    * Added telegram notifications.

Version 2.05
    * MAX_LATENCY is specified in seconds, ping in ubuntu does not allow timeouts
      below 1 second.

Version 2.04
    * Added a cleanup function to remove added routes before exiting

Version 2.03
    * COOLDOWNDELAY - deprecated use COOLDOWNDELAY01 and COOLDOWNDELAY02
    * COOLDOWNDELAY01 - The period of time to wait after a FAILOVER event before commencing
      monitoring again
    * COOLDOWNDELAY02 - The period of time to wait after a FAILBACK even before commencing
      monitoring again
    * FIX: Email alerts were sent before routes were changed on failover / failback
      Moved to generate and send alerts after the route switch so that routing table
      included in email is correct
    * FIX: Some notices echoing to CLI even when QUIET=1, redirected to log file
    * ADD: README with description of variables and info now included in package & SVN
    * ADD: Changelog now included in package & SVN

Version 2.02 (See 2.05)

    WFS now checks the maximum latency as specfied in miliseconds. If this
    threshold is exceeded, a failover is performed. This may be useful for
    setups where the latency of a connection is as important as the connection
    itself. Low latency connections for VOIP for example.

Version 2.01

    WFS permits the user to execute (external) commands when a failover
    or restore event occurs. This feature did not work properly and has
    been fixed within this version. You can specify commands to be executed
    within the config file. Consult the manual for additional information.

Version 2.0

Initial release of the 2.x branch.