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

    3 Wans Load Balanced.

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 4 Posters 4.1k 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.
    • T
      tamtap
      last edited by

      ok 20 pc's on a windows server netowork, using pfsense as the gateway. 3 wans all configured to load balance.

      problem is pfsense is puting ZERO traffic on wan 2 and 3. Why ?

      1 Reply Last reply Reply Quote 0
      • J
        jasonlitka
        last edited by

        Does your firewall rule use the LB group as the gateway?

        I can break anything.

        1 Reply Last reply Reply Quote 0
        • T
          tamtap
          last edited by

          here is a shot of my LAN rule, still seeing zero traffic on wans 2 and 3.

          If I change the "Default LAN > any" gateway from default to my load balance pool all clients lose internet access.

          Not sure what exaxctly is wrong here but load balanacing is definately NOT working for me and I can't see why so any help appreciated.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            You need to provide a lot more information about how your load balance pool is setup.

            You need to have the pool as the gateway for load balancing to work. If that does not work, your pools are probably setup incorrectly.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • T
              tamtap
              last edited by

              thanks for the reply, I have a shot of the load balance pool below. I followed the wiki i thought!

              1 Reply Last reply Reply Quote 0
              • J
                jasonlitka
                last edited by

                You need to set the firewall rule for outgoing traffic to use your "loadbalance" pool as the gateway.

                I can break anything.

                1 Reply Last reply Reply Quote 0
                • ?
                  Guest
                  last edited by

                  Also your default allow rule at the top is going to work before any of the other 3 rules are hit, so they are superfluous.  Remember that pfSense works on first match wins.  Kill the rest of those firewall rules and on the default LAN allow rule change the gateway to reference your load balance rule.  Keep in mind that certain protocols do not play nicely with load balancing (SSL, SSH, RDP) so your clients using HTTPS will have issues.  Create a failover load balancing scenario (see the documentation) and create a firewall rule above your default allow rule with source any, destination any, destination port TCP 443 and use your failover pool as the gateway.  You can repeat this scenario so that WAN1 fails to WAN2 and WAN2 fails to WAN3.  Similarly, you can do this same thing for SSH or RDP if those are needed by your clients.

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