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

    Multi-WAN Failover problem with Squid Proxy

    Scheduled Pinned Locked Moved Routing and Multi WAN
    12 Posts 3 Posters 6.4k 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.
    • marcellocM
      marcelloc
      last edited by

      What squid version?

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • F
        fernando36
        last edited by

        @marcelloc:

        What squid version?

        Running Squid 2.7.9 pkg v.4.3.1 on pfSense 2.0.1

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          Did you tried with squid3 and "dnsv4 first" option?

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • F
            fernando36
            last edited by

            @marcelloc:

            Did you tried with squid3 and "dnsv4 first" option?

            I have now installed squid3, and get the following error message:

            51 network is unreachable

            1 Reply Last reply Reply Quote 0
            • marcellocM
              marcelloc
              last edited by

              Check your routes, both versions return routing errors.

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

              1 Reply Last reply Reply Quote 0
              • F
                fernando36
                last edited by

                @marcelloc:

                Check your routes, both versions return routing errors.

                I have no static routes, these are my gateway and proxy config:



                1 Reply Last reply Reply Quote 0
                • marcellocM
                  marcelloc
                  last edited by

                  Are you using gateway ip to monitor gateway ip? If so, pfsense will only detect offline gateway when it's powered off.

                  Treinamentos de Elite: http://sys-squad.com

                  Help a community developer! ;D

                  1 Reply Last reply Reply Quote 0
                  • F
                    fernando36
                    last edited by

                    @marcelloc:

                    Are you using gateway ip to monitor gateway ip? If so, pfsense will only detect offline gateway when it's powered off.

                    Yes , I didn't change monitor IP, what should I use there?

                    Anyway, on Dashboard I can see the gateway is down, not sure this is related to what you said

                    1 Reply Last reply Reply Quote 0
                    • marcellocM
                      marcelloc
                      last edited by

                      Did you forced a gateway on dns config?

                      Does your dns server works on both links?

                      Treinamentos de Elite: http://sys-squad.com

                      Help a community developer! ;D

                      1 Reply Last reply Reply Quote 0
                      • F
                        fernando36
                        last edited by

                        @marcelloc:

                        Did you forced a gateway on dns config?

                        Does your dns server works on both links?

                        I don't think I forced it

                        As I said DNS works on backup connection

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

                          See http://forum.pfsense.org/index.php/topic,38882.0.html and make certain you have followed all of the steps.  The floating rule and "tcp_outgoing_address 127.0.0.1" are important pieces of the puzzle which are not immediately obvious.

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