Announcement

Collapse
No announcement yet.

16.6.0 upgrade sending all network traffic over the failover interface

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 16.6.0 upgrade sending all network traffic over the failover interface

    Am having to disable the WAN Balancer and WAN Failover modules until this bug is addressed.

  • #2
    Can you describe what the issue is?
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email [email protected]

    Comment


    • #3
      Hi jcoffin -- I opened a support ticket with "Karl" outlining the details using the Untangle support protocol (if that detail also helps).

      Before upgrading to 16.6, there were no issues.

      Upon installing the 16.6 upgrade and rebooting, all WAN traffic was sent thru my backup cellular WAN interface. I was alerted of this when I received an AT&T email informing me that I had consumed 90% of my cellular allowance for the billing period. I then confirmed my public IP was that of the cellular interface. I then disabled both the WAN Failover and WAN Balancer apps that were previously installed and setup before 16.6 and unplugged the power on my cellular WAN interface and everything returned to normal. I had also attempted to re-save the settings for both the WAN Failover and WAN Balancer Untangle apps and to reboot to re-start these modules without success.

      NOTE: it seems similar to the known bug where after installing 16.6, all traffic is routed through the Tunnel VPN interface. I experienced that issue as well and have since disabled my Tunnel VPN module until a patch is deployed.
      Last edited by miles267; 11-24-2022, 08:30 AM.

      Comment


      • #4
        I'm experiencing the same issues with 16.6... Client is running all Data over the Backup 4G Connection... Only way to halt was to Disable the 4G Network Interface etc..
        Basically WAN Balancer/Failover appears broken..

        I've logged a Support Request (I think) via the Contact Us Section of my Admin Console...
        Last edited by BusinessConnected; 11-24-2022, 06:25 PM.

        Comment


        • #5
          Originally posted by BusinessConnected View Post
          I'm experiencing the same issues with 16.6... Client is running all Data over the Backup 4G Connection... Only way to halt was to Disable the 4G Network Interface etc..
          Basically WAN Balancer/Failover appears broken..

          I've logged a Support Request (I think) via the Contact Us Section of my Admin Console...
          Thanks for reporting this issue. I've done the same. It's currently unusable as is the Tunnel VPN module.

          Comment


          • #6
            Still unresolved at this stage..
            Bit of a concern that this has been ongoing for around 5 Days or so without a resolution.
            This sort of thing really shouldn't occur... especially since I'm running Untangle Hardware (Z4).

            Comment


            • #7
              Originally posted by BusinessConnected View Post
              Still unresolved at this stage..
              Bit of a concern that this has been ongoing for around 5 Days or so without a resolution.
              We are looking at the issue. The issue is in WAN Balancer, not WAN Failover.

              Attention: Support and help on the Untangle Forums is provided by
              volunteers and community members like yourself.
              If you need Untangle support please call or email [email protected]

              Comment


              • #8
                Is there any potential workaround etc at the moment?
                We've been advised that 16.6 is supposed to be released on December 6th..
                Should I be disabling automatic updates on all my Client Sites before then because you are pressing ahead with the release... or are you intending to resolve this before that date?

                Comment


                • #9
                  We run the Z4 Appliance exclusively... So we've never had any issue with Auto Updates being left on.
                  What's really left me concerned here is that this issue is pretty key in terms of functionality and it's been 7 days without resolution.

                  Only advise I've received at this stage is to revert to 16.5.2 and Restore Backup
                  (Not an easy process obviously).

                  Comment


                  • #10
                    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.

                    Comment


                    • #11
                      Is there anything new on this ? We have some affected customers, a downgrade would be very costly. (Locations widely distributed).

                      Comment


                      • #12
                        Areichmann:
                        I've been advised that 16.6.1 is supposed to provide a Fix for this... However only if your WAN Interfaces don't utilise a VLAN Tag.

                        Comment


                        • #13
                          I'm experiencing the same issues 16.6.1. I temporary added a rule in wan balance module "Route Rules" for force devices traffic on the correct wan. Don't found any better solution. My working interface is PPPOE
                          Last edited by Nannus; 12-21-2022, 04:09 AM.

                          Comment


                          • #14
                            Issue is still occuring for us.
                            Basically the WAN Balancer isn't working at all when one of the connections utilises VLAN Tagging.
                            I've logged another Support Request, my original request was never resolved because I couldn't have the risk of a Client going offline during Christmas/New Year so I reloaded the Untangle Z4 with 16.5 Software and restored a backup etc..

                            It just seems quite disappointing to me that these issues have been known about now for almost 6+ weeks and there isn't a solution.

                            Comment

                            Working...
                            X