No announcement yet.

WAN Failover/Balancer Fuctionality Broken in Untangle 16.6

  • Filter
  • Time
  • Show
Clear All
new posts

  • WAN Failover/Balancer Fuctionality Broken in Untangle 16.6

    I've posted in the WAN Balancer Sub-Forum but thought I'd post here also.
    This functionality appears broken in 16.6. I only have 1 x Client that has upgraded to this however basically all traffic is now going over 4G Backup Connection.
    WAN Failover is reporting no drops on either Connection.
    WAN Balancer is set to 100 for Main Connection and 0 for Secondary.

    Only change to setup has been the 16.6 Upgrade in last couple of days.

    Only way to resolve for now (remotely) was to disable the Network Interface for 4G Connection.
    (Which is risky if main connection goes down)

  • #2
    Just an update... Received response from Support looking into issue today.. Requested i revert setup back to how it was so they could investigate.
    Stated they would contact me before 5pm PST to let me know status but issue resolution shouldn't take that long.
    Now almost 7pm PST...

    Client in Australia has been running on 4G for no reason until 2pm of a Business Day, purely so Untangle could sort their own Software Out etc..
    Pretty frustrated right now.


    • #3
      Confirmed. This feature was broken by the 16.6 upgrade. I too have an open support ticket on this. Thanks for reporting.


      • #4
        This patch should help:
        Græme Ravenscroft • Technical Marketing Engineer
        ('gram', like the unit of measurement)
        How can we make Arista ETM products better?


        • #5
          Unfortunately that Patch doesn't resolve my issues..
          Secondary 4G WAN which is set to 0% in WAN Balancer continues to use all Traffic etc after application of the Patch.


          • #6
            The issue I had mentioned here was not well described by me, so I've deleted it.
            Last edited by woodsky; 12-10-2022, 03:55 AM. Reason: Actually, my problem is a little different to that described in this thread, I need to better understand it before posting further.


            • #7

              Unfortunately I haven't been able to resolve this issue with Untangle Support...
              I've had to manually re-load the Untangle Z4 to Software Version 16.5.2 so I can get functionality working again correctly.


              • #8
                Has there been any update on this issue?


                • #9
                  Anyone know if this issue was resolved in 17.0 ?