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

    Multi-WAN acting as Load Balancing instead of Failover

    Scheduled Pinned Locked Moved Routing and Multi WAN
    6 Posts 4 Posters 333 Views 4 Watching
    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.
    • S Offline
      Stewart
      last edited by

      I have 2 gateways in a single gateway group.
      WAN1 is a physical connection and is TIER1.
      WAN2 is a wireless connection with a data cat on TIER2.
      It triggers on Member Down.

      I would expect it to be a failover but it appears to be load balancing. I can force it to be a failover if I add the group to the outbound firewall rule as the gateway.

      Why is it defaulting to load balancing instead of failover?

      chpalmerC 1 Reply Last reply Reply Quote 0
      • chpalmerC Offline
        chpalmer @Stewart
        last edited by chpalmer

        @Stewart System / Routing / Gateways

        What do you have for your "Default Gateway"s ?

        I have a similar setup here.

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          Stewart @chpalmer
          last edited by

          @chpalmer There is a globe next to WAN1 which indicates default gateway, but down below the group is selected for Default Gateway IPv4.

          chpalmerC 1 Reply Last reply Reply Quote 0
          • chpalmerC Offline
            chpalmer @Stewart
            last edited by chpalmer

            @Stewart By a very big cooincidence I am actually on my failover for the last four plus hours here..

            But.. My failover group (which it appears by your comment you do have set up" is named
            "FailoverWAN"

            On my routing page my Default Gateway IPv4 is "FailoverWAN ()"

            I do not have IPv6 set up at this time..

            failover.jpg

            Im curious if you have skipped this step..?

            I guess important to know is that pfSense will use WAN2 for its own use for various items if you have it set up such as DNS queries. And there is a constant ping to make sure the gateway is still live.. You will see traffic slowly grow on that interface.

            Triggering snowflakes one by one..
            Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

            1 Reply Last reply Reply Quote 0
            • N Offline
              nltechie
              last edited by

              Maybe I'm missing it, but shouldn't we be posting what version we're using?

              I have a Netgate 6100 running 25.11

              I just started having or at least noticing this issue which is obviously causing some issues... I too have a gateway group configured, Cable Company WAN is Tier 1, Wireless ISP is Tier 2, and member down is the trigger... Default LAN route out is using * (default gateway) and under routing I have the gateway group as the default gateway.

              Today I started getting calls about certain things not working due to our public IP address flapping from WAN to WAN2, I check the state table for WAN2 and sure enough there are a decent number of users on that interface and there shouldn't be any.

              Anyone figured out the fix? Is this a bug?

              1 Reply Last reply Reply Quote 0
              • J Offline
                Jiffy6534
                last edited by Jiffy6534

                FreeBSD 14.0-CURRENT #1 RELENG_2_7_0-n255866-686c8d3c1f0

                I can see similar issues. Have two WAN interfaces in a gateway group with one on a lower tier. Trigger level is set to member down.

                Despite this, if I tcpdump both my main WAN and lower tier failover WAN, I see traffic on both while both interfaces are up and reporting no packet loss.

                Model is https://www.mini-box.com/APU-2E4-System?sc=8&category=2019 AFAIK.

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