Create errorCheck() reports even when the normal state is a failure
Current state: A lot of the datacenter connections will never reply on the last hop making their normal state "Failed". Errors on these routes will in other words not trigger new reports. Can we still get useful information from these routes using errorCheck()?
-
Can we just have the route print reports about errors even if the route's normal state is "Failed"? -
Can we print reports when the last seen IP changes even if the route is normally "Failed" indicating a route change?