Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Low Watermark Latency Thershold doesn't trigger recovery to original gateway

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bateau009
      last edited by

      We have a Gateway Group with Tier 1 and 2 gateways set to trigger exclusion of a member based on high latency.

      Tier 1 gateway is set with 120/200 Low/High Latency Thersholds.
      Tier 2 gateway doesn't have any thershold set.

      As far as I understand, Low water mark is used by the failover mechanics to trigger the recovery of the previously failed gateway, although this doesn't works as expected.
      Actual behaviour results on failover being correctly triggered to the Tier2 gateway when 200ms are reached but it doesn't recover to the Tier1 gateway when latency goes back the low watermark of 120ms.

      We found that only forcing a filter reload put the Tier1 gateway back in the routing table.

      Any clues?

      Running pfSense 2.1 i386

      1 Reply Last reply Reply Quote 0
      • B
        bateau009
        last edited by

        Anyone ?

        We still have this problem also after having upgraded to 2.0.3 release.

        Running pfSense 2.1 i386

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.