Project

General

Profile

Bug #11298

Gateway Group Offline Bug

Added by Viktor Gurov about 1 month ago. Updated 28 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Rules / NAT
Target version:
Start date:
01/23/2021
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.5.0
Affected Architecture:

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.

Associated revisions

Revision 9985ed7f (diff)
Added by Viktor Gurov about 1 month ago

Gateway Group Policy rule creation fix. Issue #11298

History

#2 Updated by Jim Pingle about 1 month ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#3 Updated by Renato Botelho about 1 month ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

#4 Updated by Viktor Gurov 28 days 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

Also available in: Atom PDF