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

    Load balancing and sticky connections

    Scheduled Pinned Locked Moved Routing and Multi WAN
    4 Posts 2 Posters 2.8k 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.
    • R
      rafaelcsx
      last edited by

      Hi All,

      I have a multi-WAN environment with two dedicated WAN links, both links are working fine, but I had to configure them using Fail-Over instead of Load-Balancing.

      I did this because some sites use the IP address to validate their sessions, I tried to use stick connections, but with no success, when it starts to work in one of the links, but when tries to use the second one, the connection will not be established.

      Does anyone face this issue before?

      Kind Regards,
      Rafael.

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        AFAIK, sticky is still broken. Look at the 1.2 doc here: http://doc.pfsense.org/index.php/MultiWanVersion1.2
        Ignore the stuff about using sticky connections and read the section 'Setting up for protocols that don't like load balancing'

        1 Reply Last reply Reply Quote 0
        • R
          rafaelcsx
          last edited by

          Thanks a lot for the information.

          Accordingly to the document, I should have two LB services configured, one with FailOver and the other with LoadBalancing, and use them accordingly to my demand, right?

          Thanks in advance,
          Rafa.

          1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash
            last edited by

            Yeah, I always make three- load-balance both lines, failover from WAN to OPT, failover from OPT to WAN.
            Just to be flexible. You want to use the failover pools and not an interface gateway so you don't break https (or whatever) when a line drops.

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