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

    PfSense 1.2.3-RC2 Outbound Load Balancer Replaced

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    15 Posts 10 Posters 23.5k 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.
    • B
      biatche
      last edited by

      so, is the latest snapshot 1.2.3-RC2? Or is this just pre-information?

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

        This is a bit ahead of the curve. There is none yet, but this is for reference.

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

          I've noticed changes in outbound load balancing in 1.2.3 snapshot from 29.05. I've failover setup with two WAN interfaces. It works much better than slbd except one thing - it stops work after these log messages:

          Jun 3 09:12:07 apinger: 217.66.16.44: Received packets buffer: ################################################## ####….............
          Jun 3 09:12:07 apinger: 217.66.16.44: Lost packet count mismatch (-4!=0)!
          Jun 3 09:12:07 apinger: 77.72.248.2: Received packets buffer: ################################################## ####................
          Jun 3 09:12:07 apinger: 77.72.248.2: Lost packet count mismatch (-4!=0)!

          Then it doesn't actual do any failover (but quality RRD graphs are still being updated). If I make noop save of load balancing pool, it became functional again (I believe that apinger is simply restarted). I've no idea when it breaks, in general it doesn't works longer than 1 day, so I've to  resave pool settings manually to make it alive agin.

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

            I have committed a fix to prevent apinger from quitting when this happens. You will still see this log message occasionally though.

            We are still tracking the source of this message as we have not seen this message before in the past year that we ran apinger on 2.0. So where this is coming from is a mystery as of yet.

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

              the big problem with apinger is the fact that it switches back to main WAN as soon as it recieves ping from it. If main WAN is jumping from up to down, then pfSense switches WAN too frequently.

              If main WAN lost pings it waits for timeout and switches to backup one, same behaviour should be applied for opposite direction, ie if main WAN is in fail state and ping is recieved, then wait some time and if no ping loss was detected then switch back to main WAN.

              1 Reply Last reply Reply Quote 0
              • C
                cheesyboofs
                last edited by

                Thank you for backporting this.

                Its good that you guys have not shut the door on 1.2.x and are still actively tweaking it.

                Author of pfSense themes:

                DARK-ORANGE

                CODE-RED

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

                  Looks like all those debug messages were caused by my lack of C skills. It may or may not be fixed in upcoming snapshots.

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

                    @redbaron:

                    the big problem with apinger is the fact that it switches back to main WAN as soon as it recieves ping from it. If main WAN is jumping from up to down, then pfSense switches WAN too frequently.

                    This problem is not specific to apinger, if you have a dual or more dhcp wan it fail in the exact same way. The filter code in 1.2 has not link detection which is making things worse.

                    This is a not so common failure as most of the times it will do the right thing. However, sometimes dhclient will remove the static route for that monitor IP on the interface causing this behaviour to happen.

                    1 Reply Last reply Reply Quote 0
                    • G
                      GoldServe
                      last edited by

                      @databeestje:

                      Looks like all those debug messages were caused by my lack of C skills. It may or may not be fixed in upcoming snapshots.

                      May I ask which file or what got updated to fix these error messages? I'm using an Aug 8th build and everything is working perfectly for me, I don't want to upgrade but do want to fix this rather annoying error message in the logs every night.

                      Cheers.

                      1 Reply Last reply Reply Quote 0
                      • K
                        kevindd992002
                        last edited by

                        Is there a guide for this new load balancing scheme?

                        1 Reply Last reply Reply Quote 0
                        • C
                          cmb
                          last edited by

                          @kevindd992002:

                          Is there a guide for this new load balancing scheme?

                          The changes were only in the back end, the front end is completely identical to how it's always been.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kambeeng
                            last edited by

                            Thank you for information i hop the load balance better than before alaso Traffic shapping :D

                            1 Reply Last reply Reply Quote 0
                            • S
                              smbsmb
                              last edited by

                              Can new Load Balancer work with 2 or more PPPoE/PPtP connections?

                              1 Reply Last reply Reply Quote 0
                              • W
                                wdavid
                                last edited by

                                Can this be the reason that I have problems routing ip addresses that ends with specific numbers (223-239) described in my post http://forum.pfsense.org/index.php/topic,19763.0.html

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