Squid3 - New GUI with sync, normal and reverse proxy

marcelloc · Sep 23, 2012, 4:27 AM

The best way is to use freebsd ports to compile.

Portsnap fetch
Portsnap extract

CD /usr/ports/www/squid31
make package

Hobby-Student · Sep 23, 2012, 12:09 PM

why don't we use version 3.2.1?

marcelloc · Sep 23, 2012, 1:01 PM

It's not on ports yet. To create the package for 3.2.1 we need first a port for it.
We can try to create it based on 3.1.20 dir

Hobby-Student · Sep 23, 2012, 3:12 PM

did it.

here we go:
compiled squid 3.1.20 with ports on FreeBSD 8.1. I modified the source and now squid is able to authenticate users with certs (all digests) in reverse mode… i try to find some place to upload the binaries.

EDIT:
forgot to ask… are you interested in including "my" squid version? I just added the mentioned one line in the source....

marcelloc · Sep 23, 2012, 7:19 PM

Post what you did. Maybe I can send it as a feature request to squid port maintained @ freebsd

Hobby-Student · Sep 23, 2012, 8:11 PM

this is what i did:

source file: ssl_support.cc, around line 593 (in squid 3.2.1 the file is located in "ssl" subdir named "support.cc")

function: ssl_initialize(void)

original:

SSL_load_error_strings();
SSLeay_add_ssl_algorithms();

to:

SSL_load_error_strings();
OpenSSL_add_all_algorithms();
SSLeay_add_ssl_algorithms();

would you like to include my binaries in your package?

marcelloc · Sep 26, 2012, 6:11 PM

@namek:

I am using this mainly for content filtering/caching/logging…

squid3 has some new features on it's gui too, check it on a test machine first.

marcelloc · Sep 27, 2012, 7:23 PM

@namek:

Oh yes, one the features I found was 'patch captive portal' - which I believe that if the users are on a proxy they will not be able to bypass captive portal?

yes. I did it based on some topics on this forum with problems on using captive and squid.

@namek:

And ofcourse there are more features..are many users using this in production? as you have marked it as "Beta"
another striking feature are the realtime logs integrated in the GUI itself. So i believe that somewhat eliminates the need of using the 'realtime' feature of both sarg and lightsquid…

The realtime tab on squid3 package is to help debug access while using squid and squidguard.

TyperX · Oct 1, 2012, 3:40 AM

Hi all, i have install squid3 package and just use standard config, squid reverse not config yet. After install i have problem to access banking website and got error msg from squid Unable to determine IP address from host name "www.cimbclicks.com.my". How can i solve this problem? Below my squid config.

# This file is automatically generated by pfSense
# Do not edit manually !
http_port 192.168.10.1:3128
http_port 127.0.0.1:3128 intercept
icp_port 7
dns_v4_first on
pid_filename /var/run/squid.pid
cache_effective_user proxy
cache_effective_group proxy
error_default_language English
icon_directory /usr/local/etc/squid/icons
visible_hostname localhost
cache_mgr ikhwans@kbc.com.my
access_log /var/squid/logs/access.log
cache_log /var/squid/logs/cache.log
cache_store_log none
sslcrtd_children 0
logfile_rotate 0
shutdown_lifetime 3 seconds
# Allow local network(s) on interface(s)
acl localnet src  192.168.10.0/24
uri_whitespace strip

acl dynamic urlpath_regex cgi-bin ?
cache deny dynamic
cache_mem 32 MB
maximum_object_size_in_memory 64 KB
memory_replacement_policy heap GDSF
cache_replacement_policy heap LFUDA
cache_dir ufs /var/squid/cache 1000 16 256
minimum_object_size 0 KB
maximum_object_size 4 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 8888 3128 1025-65535 
acl sslports port 443 563 8888 
acl manager proto cache_object
acl purge method PURGE
acl connect method CONNECT

http_access allow manager localhost

# Allow external cache managers
acl ext_manager src 127.0.0.1
acl ext_manager src 192.168.10.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

# Package Integration
redirect_program /usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf
redirector_bypass on
redirect_children 3

# Custom options

# Setup allowed acls
# Allow local network(s) on interface(s)
http_access allow localnet
# Default block all to be sure
http_access deny allsrc

marcelloc · Oct 1, 2012, 4:47 AM

Dns v4 first turned on was the latest workaround for this https issue.

Did you tried to stop and start squid after this change?

TyperX · Oct 1, 2012, 5:44 AM

It's working now, i have restart the pfsense. Thanks for the help ;D

Nachtfalke · Oct 6, 2012, 10:51 PM

Hi,

short question:
Is squid3 completly ready fpr pfsense 2.1 ?
It installs and it starts on pfsense 2.1 but there are some errors on systemlog because of the wrong path "/usr/local/etc/".

Further in the squid.inc there is no code to differentiate between pfsense 2.0.x and 2.1.
Did I miss something or does the squid3 package need some more work to be ready for 2.1?

Thank you :-)

marcelloc · Oct 8, 2012, 1:33 PM

@Nachtfalke:

It installs and it starts on pfsense 2.1 but there are some errors on systemlog because of the wrong path "/usr/local/etc/".

I've committed a folder check right now, check and feedback :)

Nachtfalke · Oct 8, 2012, 6:13 PM

@marcelloc:

@Nachtfalke:

It installs and it starts on pfsense 2.1 but there are some errors on systemlog because of the wrong path "/usr/local/etc/".

I've committed a folder check right now, check and feedback :)

Your commit fixed squid3 on pfsense 2.1 and it broke squidguard on 2.1 ;-)
SquigdGuard does not make any decision on pfsense version. But it seems that only "squidguard_configurator.inc" need to be changed but not "squidguard.inc".

Hmm, perhaps I should post this on this thread:
http://forum.pfsense.org/index.php/topic,50603.0.html

For curiosity squid3 and squidguard are marked as "working"…

Anyway - thanks for that fix on your package :)

nesense · Oct 10, 2012, 9:22 AM

Hi, I've been trying to get this package to work since it first appeared, I always get the same problem, it doesn't seem to cache any content, not in memory nor in HDD, I'm using NanoBSD, I always get TCP_MISS/200 on content that should be cached, is anyone facing this too? please help, its the only thing stopping me from using this great package, same settings work fine with squid 2.7x. I've posted about this here a couple of times but never got a reply :(

podilarius · Oct 10, 2012, 10:02 AM

I didn't think you could run squid in the Nano builds. Do you have to have an extra drive for the cache?

nesense · Oct 10, 2012, 10:59 AM

yes i use a separated CF for caching

marcelloc · Oct 10, 2012, 11:33 AM

try to uncheck dynamic content like YouTube cache option and see if it starts caching

nesense · Oct 10, 2012, 11:42 AM

Yes! disabling dynamic content caching fixed it. Thank you marcelloc, but honestly its the only reason I want squid 3 ;D

marcelloc · Oct 10, 2012, 11:52 AM

It needs some improvements, current dynamic cache rules are based on squid wiki.