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

    Squid3 - New GUI with sync, normal and reverse proxy

    Scheduled Pinned Locked Moved Cache/Proxy
    428 Posts 104 Posters 477.8k 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.
    • G
      geijt
      last edited by

      I've modified the squid-reverse package to support redirects.
      This was something I missed after migrating from Microsoft TMG 2010 to pfsense.

      You can redirect requests from mail.mydomain.com (protocol HTTP selected) to https://mail.mydomain.com
      Or in case of Microsoft Exchange redirecting from mail.mydomain.com and webmail.mydomain.com (both protocols selected) to https://webmail.mydomain.com/owa is also supported.
      You also can use it to support the Microsoft Exchange Autodiscover HTTP to HTTPS redirect function.

      I think you can expect the updated package soon.

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

        @Truster:

        1st: You have to correct the typo as descripted in my post before…

        I configured it like this:
        reverse Proxy Interface: WAN
        External FQDN webmail.domain.tld
        Reset TCP connections if request is unauthorized: active
        Enable HTTPS reverse proxy: Active
        reverse HTTPS port: 443
        reverse SSL certificate
        Ignore internal Certificate validation: active (we use self signed certs)
        OWA frontend IP address: IP Address four your Frontent OWA Server
        Enable ActiveSync: yes
        Enable Outlook Anywhere: yes
        Enable Exchange WebServices: yes
        Enable AutoDiscover:yes

        and of course, you have to open that port in the firewall rules.

        i'm using OWA/Exch2010...

        hope, this helps.

        Edit: if you correct the typo after enabling RPC-over-HTTPS you have to uncheck that box, save the configuration, recheck the box and save it again to apply the changes.

        I configured it like this:
        reverse Proxy Interface: WAN
        External FQDN secret.no-ip.org
        Reset TCP connections if request is unauthorized: active
        Enable HTTP reverse proxy: Active
        reverse HTTP port: 8080

        Web Servers:
        Enable this peer: active
        Peer Alias: mynas
        Peer Ip: 10.178.1.61
        Peer Port: 8080
        Peer Protocol: HTTP

        Mappings:
        Enable this URI: enabled
        Group Name: NAS-MyNAS
        Peers: mynas (selected)
        URIs: *

        Result: TCP Connection is being reset.
        –---

        When disabling the 'Reset if unauthorised' button, i'm getting an access denied Message of Squid.

        Can anyone help me, please?

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

          Redflag237,

          Did you tried entering some actual URIs instead of * on you mapping?

          The URIs field expects a regex, just * isn't a valid regex.
          If you really want to accept everything enter ^.*$ as URI, I didn't checked or squid accept this but it's a valid regex. ;-)

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

            I think I found a small bug leading to this message in system log:
            "Not calling package sync code for dependency squidreverse of squid3 because some include files are missing."

            This is my patch suggestion:

            –- /usr/local/pkg/squid_reverse.xml    2013-02-17 16:15:30.000000000 +0100
            +++ /usr/local/pkg/squid_reverse.xml    2013-02-17 16:15:49.000000000 +0100
            @@ -50,3 +50,3 @@
                   <title>Proxy server: Reverse Proxy</title>

            • <include_file>squid.inc</include_file>
            • <include_file>/usr/local/pkg/squid.inc</include_file>
                      <tabs>–Dennis</tabs>
            1 Reply Last reply Reply Quote 0
            • F
              fragged
              last edited by

              @fragged:

              I want to not cache Steam downloads. Shouldn't this work in "Custom settings" on the General-tab:

              
              acl steamtest url_regex -i ^http://.*/depot/.*/chunk/.*
              cache deny steamtest
              
              

              Squid is still caching Steam downloads (url http://81.171.70.221/depot/107202/chunk/52f888f7848537d725be13719ef9870f0b1da910). My regexp should match the url each time. The IP changes, but /depot/ and /chunk/ are always there.

              What am I doing wrong? :F

              Regards,
              Joona

              Can anyone help me with this? The custom settings pops up into /usr/pbi/squid-amd64/etc/squid/squid.conf, but content that falls under the url_regex is still being cached. My cache keeps getting filled by one time Steam downloads.

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

                Fragged,  did you enabled cache dynamic content?
                Can you check on squid conf for more cache options defined?

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

                Help a community developer! ;D

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

                  @marcelloc:

                  Fragged,  did you enabled cache dynamic content?
                  Can you check on squid conf for more cache options defined?

                  Dynamic content is off. Here's my full config.

                  
                  [2.1-BETA1][admin@pfsense.localdomain]/root(10): cat /usr/pbi/squid-amd64/etc/squid/squid.conf
                  # This file is automatically generated by pfSense
                  # Do not edit manually !
                  http_port 192.168.11.1:3128
                  http_port 127.0.0.1:3128 intercept
                  icp_port 7
                  dns_v4_first off
                  pid_filename /var/run/squid.pid
                  cache_effective_user proxy
                  cache_effective_group proxy
                  error_default_language en
                  icon_directory /usr/pbi/squid-amd64/etc/squid/icons
                  visible_hostname localhost
                  cache_mgr fragged@localhost
                  access_log /var/squid/logs/access.log
                  cache_log /var/squid/logs/cache.log
                  cache_store_log none
                  sslcrtd_children 0
                  logfile_rotate 30
                  shutdown_lifetime 3 seconds
                  # Allow local network(s) on interface(s)
                  acl localnet src  192.168.11.0/24
                  httpd_suppress_version_string on
                  uri_whitespace strip
                  
                  acl dynamic urlpath_regex cgi-bin \?
                  cache deny dynamic
                  cache_mem 4096 MB
                  maximum_object_size_in_memory 524288 KB
                  memory_replacement_policy heap GDSF
                  cache_replacement_policy heap GDSF
                  cache_dir ufs /var/squid/cache 4096 8 256
                  minimum_object_size 0 KB
                  maximum_object_size 1024 KB
                  offline_mode offcache_swap_low 90
                  cache_swap_high 95
                  
                  # No redirector configured
                  
                  #Remote proxies
                  
                  # Setup some default acls
                  acl allsrc src all
                  acl localhost src 127.0.0.1/32
                  acl safeports port 21 70 80 210 280 443 488 563 591 631 777 901  3128 1025-65535
                  acl sslports port 443 563
                  acl manager proto cache_object
                  acl purge method PURGE
                  acl connect method CONNECT
                  
                  # Define protocols used for redirects
                  acl HTTP proto HTTP
                  acl HTTPS proto HTTPS
                  
                  http_access allow manager localhost
                  
                  # Allow external cache managers
                  acl ext_manager src 127.0.0.1
                  acl ext_manager src 192.168.11.1
                  acl ext_manager src
                  http_access allow manager ext_manager
                  
                  http_access deny manager
                  http_access allow purge localhost
                  http_access deny purge
                  http_access deny !safeports
                  http_access deny CONNECT !sslports
                  
                  # Always allow localhost connections
                  http_access allow localhost
                  
                  request_body_max_size 0 KB
                  delay_pools 1
                  delay_class 1 2
                  delay_parameters 1 -1/-1 -1/-1
                  delay_initial_bucket_level 100
                  delay_access 1 allow allsrc
                  
                  # Reverse Proxy settings
                  
                  # Custom options
                  acl steamtest url_regex -i http://.*/depot/.*/chunk/.*
                  cache deny steamtest
                  
                  # Setup allowed acls
                  # Allow local network(s) on interface(s)
                  http_access allow localnet
                  # Default block all to be sure
                  http_access deny allsrc
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • J
                    jaredadams
                    last edited by

                    I see you guys trying to disable the cache of steam downloads.  But what about for LAN parties that would absolutely LOVE to do this?  How well does it work?  When ONE person on the LAN downloads a game from steam will everyone else then get it from the squid cache?

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

                      @jaredadams:

                      When ONE person on the LAN downloads a game from steam will everyone else then get it from the squid cache?

                      If you have storage to this and a good cache config, then yes :)

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

                      Help a community developer! ;D

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

                        I'm trying to create a reverse proxy for a Remote Desktop Gateway server, also a RPC over HTTP connection.
                        With all the different posts that are in this thread I was able to get the login prompt but now I stuck because it keeps giving me the prompt after entering the correct credentials.
                        I've read a post on a different forum from someone with a similar problem: http://www.mentby.com/Group/squid-users/ntlm-and-persistent-connections-reverse-proxy-3120-solved-patch.html

                        Has some been able to publish a RDGW with Squid3 already?
                        Here is my squid.conf.

                        
                        # This file is automatically generated by pfSense
                        # Do not edit manually !
                        http_port 172.30.244.10:3128
                        icp_port 7
                        dns_v4_first off
                        pid_filename /var/run/squid.pid
                        cache_effective_user proxy
                        cache_effective_group proxy
                        error_default_language en
                        icon_directory /usr/local/etc/squid/icons
                        visible_hostname proxy
                        cache_mgr admin@domain.intra
                        access_log /var/squid/logs/access.log
                        cache_log /var/squid/logs/cache.log
                        cache_store_log none
                        sslcrtd_children 0
                        logfile_rotate 5
                        shutdown_lifetime 3 seconds
                        # Allow local network(s) on interface(s)
                        acl localnet src  172.30.244.0/28
                        uri_whitespace strip
                        dns_nameservers 172.30.255.11 172.30.255.21 
                        acl dynamic urlpath_regex cgi-bin \?
                        cache deny dynamic
                        cache_mem 8 MB
                        maximum_object_size_in_memory 32 KB
                        memory_replacement_policy heap GDSF
                        cache_replacement_policy heap LFUDA
                        
                        minimum_object_size 0 KB
                        maximum_object_size 10 KB
                        offline_mode off
                        # No redirector configured
                        
                        #Remote proxies
                        
                        # Setup some default acls
                        acl allsrc src all
                        acl localhost src 127.0.0.1/32
                        acl safeports port 21 70 80 210 280 443 488 563 591 631 777 901  3128 1025-65535 
                        acl sslports port 443 563  2607
                        acl manager proto cache_object
                        acl purge method PURGE
                        acl connect method CONNECT
                        
                        # Define protocols used for redirects
                        acl HTTP proto HTTP
                        acl HTTPS proto HTTPS
                        
                        acl allowed_subnets src 172.30.252.0/22
                        http_access allow manager localhost
                        
                        http_access deny manager
                        http_access allow purge localhost
                        http_access deny purge
                        http_access deny !safeports
                        http_access deny CONNECT !sslports
                        
                        # Always allow localhost connections
                        http_access allow localhost
                        
                        request_body_max_size 0 KB
                        delay_pools 1
                        delay_class 1 2
                        delay_parameters 1 -1/-1 -1/-1
                        delay_initial_bucket_level 100
                        delay_access 1 allow allsrc
                        
                        # Reverse Proxy settings
                        http_port 172.30.248.100:80 accel defaultsite=sv002.domain.intra vhost
                        https_port 172.30.248.100:443 accel cert=/usr/local/etc/squid/51399e473ace0.crt key=/usr/local/etc/squid/51399e473ace0.key defaultsite=rdgw.domain.intra vhost
                        #rdgw001
                        cache_peer 172.30.255.16 parent 443 0 proxy-only no-query no-digest originserver login=PASS ssl sslflags=DONT_VERIFY_PEER front-end-https=auto name=rvp_rdgw001
                        
                        acl rvm_CAServers url_regex -i http://sv002.domain.intra/*
                        acl rvm_CAServers url_regex -i https://sv002.domain.intra/*
                        acl rvm_RDGWServers url_regex -i ^https://rdgw.domain.intra/.*$
                        cache_peer_access rvp_rdgw001 allow rvm_RDGWServers
                        cache_peer_access rvp_rdgw001 deny allsrc
                        never_direct allow rvm_CAServers
                        never_direct allow rvm_RDGWServers
                        http_access allow rvm_CAServers
                        http_access allow rvm_RDGWServers
                        
                        deny_info TCP_RESET allsrc
                        
                        # Custom options
                        
                        # Setup allowed acls
                        # Allow local network(s) on interface(s)
                        http_access allow allowed_subnets
                        http_access allow localnet
                        # Default block all to be sure
                        http_access deny allsrc
                        
                        
                        1 Reply Last reply Reply Quote 0
                        • E
                          eldersouza
                          last edited by

                          I'm trying to enable transparent mode, but after check Transparent HTTP Proxy (in LAN or Loopback - with NAT/rules ok) my client win7 receives an error message in all sites that I tried to open (print screen below).

                          When I opened squid.conf, I saw that SQUID GUI had put two lines http_port. One with "intercept" and another without this parameter. Then I removed the line without intercept and the squid worked fine.

                          And another crazy thing that I saw in this Squid3 GUI…

                          • If I select loopback interface and check Transparent Mode... it puts in squid.conf:
                                  http_port 127.0.0.1:3128
                                  http_port 127.0.0.1:3128 intercept
                          • If I select LAN (or WAN) interface and check Transparent Mode... it puts in squid.conf:
                                  http_port 10.0.0.1:3128
                                  http_port 127.0.0.1:3128 intercept

                          My configuration is:

                          • pfSense: 2.0.2-Release (i386) - (Clean install and configuration. I didn't update the firmware and didn't import configuration from my old pfSense)

                          • Squid: 3.1.20 pkg 2.0.6

                          Can anyone confirm if it is really a bug? Or I'm doing something wrong in the configuration Squid.

                          Thanks

                          Elder Souza

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

                            @eldersouza:

                            • If I select LAN (or WAN) interface and check Transparent Mode… it puts in squid.conf:
                                    http_port 10.0.0.1:3128
                                    http_port 127.0.0.1:3128 intercept

                            This config is fine, users that connect via lan will not use intercept but transparent access will.

                            @eldersouza:

                            Can anyone confirm if it is really a bug? Or I'm doing something wrong in the configuration Squid.

                            Check your config again, transparent proxy works.

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

                            Help a community developer! ;D

                            1 Reply Last reply Reply Quote 0
                            • Q
                              quetzalcoatl
                              last edited by

                              With fine tuning i got squid working in a beautiful way. It caches a lot, i get a byte hit ration between 5 and 20%. Sometimes even up to 50% when i install lots of windows updates in many OEM computers. It is very fast, stable and reliable.
                              Thanks to marcelloc and all others working here.

                              But there is a big problem going on at least with my config.
                              After about 2 months of squid working really nice, suddently it stops working, and i cannot browse anymore.
                              I think that only https pages work but http stuff doesn't work any more. or the other way around…i don't remember exactly.

                              I tested many different settings in a hurry because it is a production environment but still nothing.

                              The only way to make pfsense allow users to browse the web properly is uninstalling completely the squid package and only then people are able to browse again.
                              The weird thing is that before that problem, squid works really nice for more than a month 24/7.
                              No settings change is being done before squid crashes.
                              This happened to me at lease 3 times so i had to live for a while without squid until i install a new pfsense snapshots and squid again (always hoping for a newer updated squid package).

                              I'm pretty sure that if i give you some logs it will help you understand where the problem is but i don't know where and how to look those logs to see what squid does just before it stops working.

                              Something makes me thing like some sort of log or cached stuff that becomes way too big after 1 or 2 months with my current config.
                              I just neet to know what file, dir, log, or whatever inflates so big after that 60 days.

                              Thanks for your great support!

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

                                I had something like that happen as we'll. my question is to you remember that during the time it was not working, was there a lot of disk activity? Mine did like it was clearing out the cache. I had to stop squid and let traffic pass with out it and manually remove the cache directory. After I cleared it out, squid started working. I have since lowered the max cache size so cleanup happens more often and does not take as long. Is this something that can happen when the cache is large. I had it set to something like 100gb and it crashed around 50-60gb. I am guessing that if I let it go I am sure it would have cleared up and eventually started working.

                                1 Reply Last reply Reply Quote 0
                                • Q
                                  quetzalcoatl
                                  last edited by

                                  I didn't notice any disk activity, in fact it was completely quiet.

                                  Mind that in a 500 GB hard drive i set squid to save into disk up to 350 GB of cached data.

                                  Maybe that's too much and i should lower it to 50 Gigabytes.

                                  Maybe there is a limit of how much cache squid is able to handle.

                                  Also with RAM cache i noticed that if i set the maximum object size to 512kb or above it might crash.

                                  Setting the maximum object size in RAM below 384 kb gives me no problems at all, but it takes days to fill half of the 20 GB of RAM that i have dedicated to Squid.

                                  To take advantage of many gigabytes of RAM as cache, maximum object size should be at least 1024 KB but in some situations i had pfsense crashing over and over until i lowered that value below 512.

                                  Maybe the original squid is able to handle more than than, but the ported freeBSD version is having a hard time handling big object sizes, too many objects, too much cached data into disk.

                                  Hopefully someone can tell us the real squid limits inside pfsense, so we can stay within the limit for maximum performance and stability.

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    eldersouza
                                    last edited by

                                    marcelloc,

                                    My (simple) configuration is:

                                    SQUID:

                                    • Proxy Interface: loopback
                                      Proxy Port: 3128
                                      Transparent HTTP Proxy: Enabled

                                    Firewall: NAT

                                    • Proto: TCP
                                      Src.Addr.: LAN (my LAN network address and mask)
                                      Src.Ports: *
                                      Dest.Addr: ! LAN (everything except my LAN
                                      Dest.Ports: 80
                                      NAT IP: 127.0.0.1
                                      NAT Ports: 3128

                                    Firewall: Rules

                                    • Rule created automatically

                                    Squid.conf: This is what made the Proxy Server GUI (first lines)

                                    • This file is automatically generated by pfSense

                                      Do not edit manually !

                                      http_port 127.0.0.1:3128
                                      http_port 127.0.0.1:3128 intercept
                                      icp_port 7
                                      dns_v4_first on

                                    And this is the error:

                                    If I remove this line (http_port 127.0.0.1:3128) all works fine!

                                    So, what I'm doing wrong?

                                    Thanks

                                    @marcelloc:

                                    @eldersouza:

                                    • If I select LAN (or WAN) interface and check Transparent Mode… it puts in squid.conf:
                                            http_port 10.0.0.1:3128
                                            http_port 127.0.0.1:3128 intercept

                                    This config is fine, users that connect via lan will not use intercept but transparent access will.

                                    @eldersouza:

                                    Can anyone confirm if it is really a bug? Or I'm doing something wrong in the configuration Squid.

                                    Check your config again, transparent proxy works.

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

                                      Hi,

                                      I found that there is squid 3.2 available of FreeBSD ports. If I remember correct there were some bugs on 3.1 which were fixed on 3.2.
                                      I am no expert - just found this here:
                                      http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/squid32/Makefile?rev=1.13

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

                                        Do I need to uninstall the squid package before installing squid3 or can I install squid3 with squid already installed?

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

                                          Remove old squid package before installing squid3.

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

                                          Help a community developer! ;D

                                          1 Reply Last reply Reply Quote 0
                                          • Q
                                            quetzalcoatl
                                            last edited by

                                            I'm still waiting for squid 3.3 for freebsd.
                                            we know that squid 3.2 is already available for freeBSD but it does not appear in the squid packages yet.
                                            There is people that say that squid3.2 and squid3.3 are as efficient as the old 2.7.
                                            According to them squid 3.1 and 3.0 are much slower than 3.3/3.2 and can manage less clients and connections.

                                            I don'k know how true all that is but i did notice a bery big byte hit ratio comparing squid 3.1(the latest package for pfsense) with the lusca cache(based on squid 2.7)

                                            I didn't want to use lusca cache anymore because i saw newer squid 3.x packages coming out for pfsense and the latest lusca was released on 2010.

                                            lusca does not support IPv6 and it looks like it's not even updated anymore.

                                            but what should i do? stick with the best performance with lusca or keep using squid 3.1 even if i know it's slower and anyways updates come too slowly.

                                            I would like to be able to help marcelloc to port the latest squid 3.3 to pfsense but i don't know much about porting stuff, but i'm so desperate to get the latest squid that i'm seriously thinking about learning this stuff.

                                            Your opinions are warmly welcome!

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