Bug #11298
closedGateway Group Offline Bug
0%
Description
https://forum.netgate.com/topic/160153/gateway-group-offline-bug:
In 2.5.0.a.20210121.2350 I discovered an issue that if you set a Gateway Group's Trigger Level to "Packet Loss or High Latency" the gateway is endlessly seen as down. "rule * disabled because gateway * is down". This does not occur if you set the trigger level to one of Member Down, Loss, or Latency.
How to check/reproduce:
Set the gateway to be used in a policy based rule using that gateway group. The generated rule will not have the forced next-router.
You can view this by going to System -> Advanced -> Misc -> "Do not create rules when gateway is down" then after creating the rule and rebuilding your rules, check /tmp/rules.debug. You will see a comment where the rule should be stating that the gateway is down.
Updated by Viktor Gurov almost 4 years ago
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho almost 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Updated by Viktor Gurov almost 4 years ago
- Status changed from Feedback to Resolved
roundrobin/failover, down/packet loss/high latency/packet loss or high latency - all works as expected
2.5.0.a.20210201.2350