Actions
Bug #3179
closed
JP
EL
Gateway failure not properly detected in certain cases using a monitor IP outside of the WAN's subnet
Bug #3179:
Gateway failure not properly detected in certain cases using a monitor IP outside of the WAN's subnet
Start date:
09/03/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
Description
Still researching this a bit but it needs an entry so things don't get lost.
Currently, I have two WANs, DSL and CABLE. DSL is the default. The CABLE WAN is having issues and at times experiencing 80-90% loss. The monitor IP on CABLE is 8.8.8.8. Apinger, however, is not reporting loss during these times. It is showing the gateway as online, even though the circuit is experiencing massive loss confirmed by other methods.
Because of the loss and lack of detected failure, manually reconfiguring the gateway groups is necessary to regain usable connectivity from behind the firewall.
This may possibly be due to the removal of static routes for apinger targets, but testing is needed to confirm.
Files
Actions