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

    LoadBalanced 2 WANs: Second request sloooooow

    Routing and Multi WAN
    2
    5
    2.0k
    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.
    • D
      dabassman
      last edited by

      Hi there,
      I have a Double-WAN setup and created the three Loadbalancer items as figured out in http://doc.pfsense.org/index.php/MultiWanVersion1.2
      So I have three loadbalancer items: WAN1foWAN2, WAN2foWAN1, BalancedWAN. If I use the first or the second as the gateway in my firewall rule for http traffic, everything works fine and fast. If I use the third, every second webpage I want to load is very slow (not really; it seems to be a timeout before anything begins to load. After that timeout (approx. 3 seconds) its fine again). Any ideas why the gateway shows this behaviour?
      I use 1.2.1 RC2.

      Regards

      Matthias

      1 Reply Last reply Reply Quote 0
      • P
        Perry
        last edited by

        Are you using sticky connection?
        IMO it is better to use fail over pools anyway. As you can split the load with Alias or CIDR and only missing function would be downloading with a download manager.

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • D
          dabassman
          last edited by

          Yes, I am using sticky connections (btw, the behaviour without is the same). Balancing via alias or cidr is not really what I wanted since the target addresses are very random; but I'll try that.

          Regards

          Matthias

          1 Reply Last reply Reply Quote 0
          • P
            Perry
            last edited by

            On Source not Destination.
            source 192.168.1.0/26 using WanFailsToWan2 as gateway
            source 192.168.1.64/26 using Wan2FailsToWan as gateway

            /Perry
            doc.pfsense.org

            1 Reply Last reply Reply Quote 0
            • D
              dabassman
              last edited by

              Nice idea, thanks. Does not fit completely what I want, but if no one has another hint on whats going wrong on my pfsense, I'll try that.

              Regards

              Matthias

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