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

    PfSense Squid Proxy for Multi-WAN

    Scheduled Pinned Locked Moved Routing and Multi WAN
    36 Posts 15 Posters 31.2k 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
      hyrol
      last edited by

      Step Multi-WAN LoadBalancer with squid. I separate post in every step to simplify the configuration.
      I'm confused on step 3 you mean whether floating or routing. I am waiting for your decision.

      1 Reply Last reply Reply Quote 0
      • N
        Nachtfalke
        last edited by

        Hi,

        thank you for the tutorial. Which IP address do I have to enter into "wpad" files when using different VLANs/interfaces?

        Thank you.

        1 Reply Last reply Reply Quote 0
        • J
          jikjik101
          last edited by

          i mean this:

          DNS Forwarder
          Enable DNS Forwarder

          DHCP server
          In Additional BOOTP/DHCP: wpad.dat, wpad.da and proxy.pac

          Create wpad.dat, wpad.da and proxy.pac
          Use vi editor to create file wpad.dat, wpad.da and proxy.pac

          I have a DNS fowarder but without the wpad thing.

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

            @Nachtfalke:

            Hi,

            thank you for the tutorial. Which IP address do I have to enter into "wpad" files when using different VLANs/interfaces?

            Thank you.

            IP Address option depends on the current selection in the squid proxy interface, refer to the first post of the second picture.

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

              @jikjik101:

              i mean this:

              DNS Forwarder
              Enable DNS Forwarder

              DHCP server
              In Additional BOOTP/DHCP: wpad.dat, wpad.da and proxy.pac

              Create wpad.dat, wpad.da and proxy.pac
              Use vi editor to create file wpad.dat, wpad.da and proxy.pac

              I have a DNS fowarder but without the wpad thing.

              What results did you get, I've never tried it. If successful it is good news.

              1 Reply Last reply Reply Quote 0
              • N
                Nachtfalke
                last edited by

                @hyrol:

                @Nachtfalke:

                Hi,

                thank you for the tutorial. Which IP address do I have to enter into "wpad" files when using different VLANs/interfaces?

                Thank you.

                IP Address option depends on the current selection in the squid proxy interface, refer to the first post of the second picture.

                Hi,

                thank you for your response. But the picture shows just one interface (LAN) which is a listening interface on squid. I do have 6 different (V)LAN interfaces which are listening interfaces of squid but as far as I can see I am only able to create one wpad file.

                So let's say I Have a host-A in VLAN-A which is not allowed to talk to VLAN-B (firewall rules) then how would it work if the IP of the wpad file is the interface IP of VLAN-B ?

                Thank you!

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

                  try this…

                  function FindProxyForURL(url,host)
                  {
                  if (isInNet(host,"your.vlan.ip.address","your.vlan.subnet.mask"))
                     (isInNet(host,"your.vlan.ip.address","your.vlan.subnet.mask"))
                     (isInNet(host,"your.vlan.ip.address","your.vlan.subnet.mask"))
                     (isInNet(host,"your.vlan.ip.address","your.vlan.subnet.mask"))
                  return "DIRECT";
                  else
                  return "PROXY your.pfsense.ip.address:port";  DIRECT";
                  }

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

                    @jikjik101:

                    i mean this:

                    DNS Forwarder
                    Enable DNS Forwarder

                    DHCP server
                    In Additional BOOTP/DHCP: wpad.dat, wpad.da and proxy.pac

                    Create wpad.dat, wpad.da and proxy.pac
                    Use vi editor to create file wpad.dat, wpad.da and proxy.pac

                    I have a DNS fowarder but without the wpad thing.

                    What you say is true, I have tried to remove the step, it can work.

                    Skip this
                    DHCP server
                    In Additional BOOTP/DHCP: wpad.dat, wpad.da and proxy.pac

                    Create wpad.dat, wpad.da and proxy.pac
                    Use vi editor to create file wpad.dat, wpad.da and proxy.pac

                    ![08. DHCP Server.png](/public/imported_attachments/1/08. DHCP Server.png)
                    ![08. DHCP Server.png_thumb](/public/imported_attachments/1/08. DHCP Server.png_thumb)
                    ![09. Editor WPAD.png](/public/imported_attachments/1/09. Editor WPAD.png)
                    ![09. Editor WPAD.png_thumb](/public/imported_attachments/1/09. Editor WPAD.png_thumb)

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

                      For some reason, this setup not working on pfsense 2.1 and squid 3.3.4, my box was working very well with 2.0.3, but now it´s not with 2.1, any ideas?

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

                        Nice way summing it up!  Thanks!

                        1 Reply Last reply Reply Quote 0
                        • B
                          binarymind
                          last edited by

                          @hyrol:

                          Firewall Floating rules
                          Squid proxy use port 80 and use interface WAN, WAN it's default for squid proxy server
                          Select Gateway: Multi-WAN

                          Till Last week i was using Version 2.0.2 now upgraded to 2.0.3
                          Thanks!!!
                          The following tutorial helped me alot
                          http://securite-ti.com/pfSense_Web_Proxy_with_multi-WAN_links.pdf

                          I have some doubts [Confused]
                          My Scenario:
                          Configured my Gateway in Fail Over mode. [WAN1–-Tire1, WAN2---Tire2]
                          I want to make my Tire2 connection as default Gateway for 15 LAN Users. Does the policy based routing will work since WAN1 is the default for squid proxy server.
                          I have tested it but some times the Traffic goes through the Tire1 [Especially for DHCP Clients]

                          Interfaces: Lan Protocol: ANY Source: LAN IP Destination ports: ANY Gateway: WAN2GW

                          All configurations are same as shown in the PDF Tutorial. Do the same configurations will work on Version 2.0.3

                          1 Reply Last reply Reply Quote 0
                          • A
                            AMD_infinium05
                            last edited by

                            has anyone tried this on 2.0.3 ?

                            I have tried it earlier and I think i have messed up…... i have removed packages and revert to original settings, now my internet is working fine with load balancing, and failovers.

                            1 Reply Last reply Reply Quote 0
                            • V
                              vielfede
                              last edited by

                              @fabianoheringer:

                              For some reason, this setup not working on pfsense 2.1 and squid 3.3.4, my box was working very well with 2.0.3, but now it´s not with 2.1, any ideas?

                              ON
                              2.1-RC1 (amd64)
                              built on Thu Aug 15 16:30:12 EDT 2013
                              FreeBSD 8.3-RELEASE-p9

                              I solved by activating "Allow default gateway switching" option in Advanced configs (failover only) and removing all floating and NAT rules..
                              Hope this helps…

                              1 Reply Last reply Reply Quote 0
                              • M
                                Makje
                                last edited by

                                @vielfede:

                                @fabianoheringer:

                                For some reason, this setup not working on pfsense 2.1 and squid 3.3.4, my box was working very well with 2.0.3, but now it´s not with 2.1, any ideas?

                                ON
                                2.1-RC1 (amd64)
                                built on Thu Aug 15 16:30:12 EDT 2013
                                FreeBSD 8.3-RELEASE-p9

                                I solved by activating "Allow default gateway switching" option in Advanced configs (failover only) and removing all floating and NAT rules..
                                Hope this helps…

                                that is not solved, it still has 2 problems that aren't an issue for your specific use.
                                It doesn't help with loadbalancing or when someone has more than 2 WANs of which 1 WAN reallly should not do http traffic (because it is reserved for other use like VoIP, or because the ip can't be known publicly etcetera)

                                It really is a stupid bug in 2.1. Worse is that 2.0.x had a bug that failover doesn't work for connections like VoIP/SIP so going back isn't an option either, at least for me… really nice

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

                                  Finally, after a long time trying pfSense Squid Package + Multi Wan and I have managed to find its way in a deadlock.
                                  pfSense 2.1 Squid Package + Multi Wan, no longer using the Floating Rules, but using the Interface Groups.
                                  Good Luck Everyone.

                                  ![Interface Groups.jpg](/public/imported_attachments/1/Interface Groups.jpg)
                                  ![Interface Groups.jpg_thumb](/public/imported_attachments/1/Interface Groups.jpg_thumb)
                                  ![Proxy Server.jpg](/public/imported_attachments/1/Proxy Server.jpg)
                                  ![Proxy Server.jpg_thumb](/public/imported_attachments/1/Proxy Server.jpg_thumb)
                                  ![Internet Rules.jpg](/public/imported_attachments/1/Internet Rules.jpg)
                                  ![Internet Rules.jpg_thumb](/public/imported_attachments/1/Internet Rules.jpg_thumb)
                                  ![Floating Rules.jpg](/public/imported_attachments/1/Floating Rules.jpg)
                                  ![Floating Rules.jpg_thumb](/public/imported_attachments/1/Floating Rules.jpg_thumb)

                                  1 Reply Last reply Reply Quote 0
                                  • N
                                    niebla
                                    last edited by

                                    Thanks, and congratulations!

                                    What version of squid and squidguard are you using?

                                    Please send a screenshot of your system->routing screen showing your default route.

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      niebla
                                      last edited by

                                      Created the interface group, but how are you getting squid to use the group and not the default gateway?

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

                                        Still configure the same as pfSense 2.0.3 Squid Package Multi Wan, only changes to the Floating Rules to Interface Group.

                                        ![Lan Rules.jpg_thumb](/public/imported_attachments/1/Lan Rules.jpg_thumb)
                                        ![Lan Rules.jpg](/public/imported_attachments/1/Lan Rules.jpg)
                                        Groups.jpg_thumb
                                        Groups.jpg
                                        Gateways.jpg_thumb
                                        Gateways.jpg

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          niebla
                                          last edited by

                                          Thanks but I am not seeing where or how you have used the interface group.

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

                                            Under Menu Interface

                                            Interface.jpg
                                            Interface.jpg_thumb

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