Squid Returned to Packages *** PLEASE TEST ***
-
well just 1 small bug left. i dunno if this is a bug or intentional but the squid package cant work in transparent mode if the webgui is on the port 80 so have to change the port of the webgui. if this is intentional i think it's better to have a better notice to ask user to change the webgui port. anyways great job on the package it's working well now
No that's not a bug, you will lock yourself out of the webgui if you do that.
There can't be both services on the same port.About creating a cache dir.
I'll do a reinstall to be sure, but the problem is, if you had a squid version installed allready, it could give problems, because the cache dir is allready there but for another version
I'll take a look at it, maybe we can cange the install procedure that it will remove the old default cahce dir if it's there during install. -
nope mine is on fresh instalation of pfsense latest snapshot. it would not run unless i change the cache dir and change back and the blocklist is not working as well. anyways thanks for all the hardwork put into it. seems like the new squid breaks a lot of things. i'll try to test more features of the package for everyone
-
I have some other update…
in the resync functions after
log_error($disk_cache_location." does not exist. Creating.");
there must be mwexec("/usr/local/sbin/squid -k kill");otherwise it won't make the new cahce dir
Ok the kill option is not that nice, but who cares? we start with a new cache dir... so it's not a problem to shut it down this way.
I tried to do it nice, with the shutdown function, but that takes agesThis will be the new code:
if(!is_dir($disk_cache_location.'01/')) {
log_error($disk_cache_location." does not exist. Creating.");
mwexec("/usr/local/sbin/squid -k kill");But I'll give a new update later on.
I want to delete the old cache dir aswell, but that ain't as easy as I hope it would be.P.s This peace of code fixes the problem of having to setup the cache dir twice
-
Just a note to say thanks - the update is working here at the moment in transparent mode.
-
Squid package tested on bridge in transparent mode?
-
This is looking really good. Transparent mode is working well, but I'm not seeing any effects of the blacklist/whitelist. I know before I had to put an '*' in the blacklist if I wanted to fliter the web down to only the whitelisted sites. Is this still the case or am I missing another configuration step somewhere? I've tried adding the * but I'm still getting right through.
-
Newest CVS has seen some cleanups. Blacklisting appears broken to me. Can someone confirm this?
-
Databeesje I saw you didn't add the lines I sugest, but now if you change your cache dir, you have to save twice… once to let scquid "crash" and the 2nd time to actually make the cahce dir (you can't make the cache dir while squid is running) so I sugest you add the -k kill when you change the cash dir...
about removing the cache, I have to figure out how I can give an hidden value in the form, so I can pass some vars while the user hits save... anyone an idea how to do that in squid?
-
Makes sense, I'll fix this.
Have you been able to test blacklists? I have been unable to make them work.
-
not yet, I just arrived home…
But I'll try it out..
-
I think the squid version we use has no acl support..
If I just remove all acl lines and add http_access deny all
you would suspect no data will get thru, but it keeps running. -
May be one seriouse bug when installed any redirector package (squidGuard for example) who need Squid package.
*** When redirector installed - we can't correctly full reinstall or delete squid package - redirector block delete Squid package ***May be need check installation known redirector packages and notify user about this.
-
I did not know squidguard already worked.
About the ACL support. From what I can see the unrestricted acl does have a effect. Normally windows update fails, but it works if I put the IP in the unrestricted box on the access control page.
Weird
-
I did not know squidguard already worked.
About the ACL support. From what I can see the unrestricted acl does have a effect. Normally windows update fails, but it works if I put the IP in the unrestricted box on the access control page.
Weird
This not only squidGuard - any other who need squid.
ps: minimum 2 variant of squidGuard package worked
http://forum.pfsense.org/index.php/topic,3107.0.html
and
http://forum.pfsense.org/index.php/topic,3111.0.htmlbut this no in official packages
-
Downloading package configuration file… done.
Saving updated package information... done.
Downloading squid and its dependencies... done.
Checking for successful package installation... failed!Installation aborted.
Any suggestions?
-
On boot, the screen freezes on the line "Stopping /usr/local/etc/rc.d/proxy_monitor.sh" I know this was an issue under previous versions as well but never really got resolved. The system boots, the proxy runs, there is just no console.
-
You need to update to the latest testing snapshot…
http://www.pfsense.com/~sullrich/1.0.1-SNAPSHOT-12-14-2006/
-
Running 1.0.1-SNAPSHOT-12-20-2006 and the 2.6.5_1-p2 release of squid and cannot get the blacklist to work at all. there is nothing being output to show an error. Its like its just ignoring the list. also i noticed that I could not get my browser to connect directly to port 3128 when setting it to manually use the proxy until i changed it to a different port.
-
Running 1.0.1-SNAPSHOT-12-20-2006 and the 2.6.5_1-p2 release of squid and cannot get the blacklist to work at all. there is nothing being output to show an error. Its like its just ignoring the list. also i noticed that I could not get my browser to connect directly to port 3128 when setting it to manually use the proxy until i changed it to a different port.
That works good over here, did you dissable the transparent proxy? In transparent proxy the port setting does nothing..
-
yes i did. i turned it off before trying it manually. with it not blacklisting, its next to impossible to tell if the transparent proxy is even doing anything so I wanted to see what was happening when i ran it manually thru the proxy. both ways ignore the blacklist. just providing feedback for the guys working on this port.