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

    PfSense 2.1 Floating rules for Multi Wan doesn't work.

    Scheduled Pinned Locked Moved Routing and Multi WAN
    86 Posts 35 Posters 52.0k 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.
    • H Offline
      hyrol
      last edited by

      Admin edit to remove harmful instructions.

      DO NOT USE THAT LUSCA PACKAGE!

      Capture6.PNG
      Capture6.PNG_thumb
      Capture4.PNG
      Capture4.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • O Offline
        Oliver_
        last edited by

        Admin edit to remove harmful instructions.

        DO NOT USE THAT LUSCA PACKAGE!

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

          Do not use Lusca. It changes your package repository to look at a server that is not controlled by us, and it is not kept up-to-date. There is no telling what you're actually fetching from them.

          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
          • R Offline
            rubic
            last edited by

            Hi, jimp!
            I'm not very familiar with git and code, but I know for sure that squid multi-wan functionality in 2.0.3-RELEASE was provided by one of ermal patches (https://github.com/pfsense/pfsense-tools/commit/457052913414f7c2109fed415e66ed912a530ebe#diff-7304e60ae2121cfce1c817e216d6b95cR14, I think).
            I doubt if the patch applied in 2.1-RELEASE. This could be cause of the problem discussed here.

            1 Reply Last reply Reply Quote 0
            • C Offline
              craibo
              last edited by

              If you switched your package repository over to lusca,Ā  because you were desperate for a solution to this and a bit of an idiot, how would you switch it back?

              Thanks

              1 Reply Last reply Reply Quote 0
              • pttP Offline
                ptt Rebel Alliance
                last edited by

                https://doc.pfsense.org/index.php/Package_Manager_SettingsĀ  ;)

                1 Reply Last reply Reply Quote 0
                • C Offline
                  craibo
                  last edited by

                  @ptt:

                  https://doc.pfsense.org/index.php/Package_Manager_SettingsĀ  ;)

                  Unfortunately, Going to the pkg_mgr_settings.php page and saving with out checking the box, doesn't revert back to the pfsnese package repository.

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    cheonne
                    last edited by

                    @Tram:

                    @ptt:

                    https://doc.pfsense.org/index.php/Package_Manager_SettingsĀ  ;)

                    Unfortunately, Going to the pkg_mgr_settings.php page and saving with out checking the box, doesn't revert back to the pfsnese package repository.

                    To restore or use original repository.
                    you can no longer see lusca updates

                    ./package.sh off
                    
                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      pubmsu
                      last edited by

                      Does anyone know how to make this work? This is probably the number one issue for many users, which is stopping them from upgrading to 2.1.

                      There may have been a simple bug that is not letting squid and the quick floating rule work like before.

                      We really need the fix!

                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        SaFi
                        last edited by

                        Hello folks,

                        After about 8 months past, did someone try the new release of pf (2.1.1-RELEASE) to check if the issue still exist?
                        for myself I've removed squid for a long time ago waiting a one's hero report that it's was fixed.
                        I will keeping my eyes on this topic and I will waiting that HERO

                        God bless all of you

                        1 Reply Last reply Reply Quote 0
                        • H Offline
                          hyrol
                          last edited by

                          Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

                          1 Reply Last reply Reply Quote 0
                          • G Offline
                            georgio777
                            last edited by

                            @hyrol:

                            Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

                            I am on the latest version on pfSense and there has not been a fix yet to the issue. Still suffering from the same problem.

                            1 Reply Last reply Reply Quote 0
                            • T Offline
                              timthetortoise
                              last edited by

                              If you're only looking for failover capabilities, here's a workaround.

                              1 Reply Last reply Reply Quote 0
                              • H Offline
                                hyrol
                                last edited by

                                @georgio777:

                                @hyrol:

                                Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

                                I am on the latest version on pfSense and there has not been a fix yet to the issue. Still suffering from the same problem.

                                Hi georgio777 thanks for info.

                                1 Reply Last reply Reply Quote 0
                                • G Offline
                                  georgio777
                                  last edited by

                                  @timthetortoise:

                                  If you're only looking for failover capabilities, here's a workaround.

                                  By any chance do you know if it is possible to maintain Load Balancing for all traffic except HTTP traffic and use Failover for HTTP? The reason is that if the default gateway is down, Squid will stop working, if I can take the advantages of Failover only for the Squid traffic without stop using Load Balancing, that will be great.

                                  Thanks!

                                  1 Reply Last reply Reply Quote 0
                                  • T Offline
                                    timthetortoise
                                    last edited by

                                    You should be able to use standard gateways like normal for everything but HTTP. Floating rules are not broken, as evidenced by setting a rule for any source to any destination HTTP with the active gateway being something other than the default gateway. At this point squid is unable to pass traffic because it's trying to push it out the default gateway and it's actually being sent out another.

                                    As long as you have default gateway switching enabled, squid will switch to that gateway when it is restarted. I've tested this and it's working great.

                                    1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      Daouid
                                      last edited by

                                      Hello !
                                      Any news?
                                      I test an upgrade from 2.0.x to 2.1.4 and it don't work. Squid is very slow, and the http port don't work.
                                      We can't update pfsense :-(

                                      Thanks a lot

                                      1 Reply Last reply Reply Quote 0
                                      • A Offline
                                        arclegna
                                        last edited by

                                        Same question here, im on pfsense 2.1.4 and wondering if any solution yet to squid (no transparency) + loadbalance + failover, thanks in advance.

                                        1 Reply Last reply Reply Quote 0
                                        • K Offline
                                          klazoid
                                          last edited by

                                          I came back hoping that after one year there would be a fix butĀ  :'(
                                          Wasting 2 lines atm as long as the default gateway doesn't go down.

                                          1 Reply Last reply Reply Quote 0
                                          • S Offline
                                            Smithes
                                            last edited by

                                            I setup Multi-WAN like shown in the official tutorial…. Works only for Connections without squid. And works very fine. But I also need squid. So I installed the squid 3.3-dev package from the package-list, because squid supports the "radom" command since 3.2.
                                            I know it is a dev-package, but I run it on a wlan-network with 5000 Users on peek and its runs very fine. Also with squidguard.
                                            I also know that there is no failover for squid, if one of the lines will be offline, but that is not important for me, because the two lines are from the same provider and come over the same cable. It’s a cable internet connection from unitymedia(Germany).

                                            I added these lines, for split the traffic to two lines. *1

                                            acl fiftyPercent random 0.5
                                            tcp_outgoing_address 192.0.2.1 fiftyPercent
                                            tcp_outgoing_address 192.0.2.2

                                            *1: The information’s found here: http://wiki.squid-cache.org/Features/AclRandom
                                            greets Smithes

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