Squid 2.7.x on pfSense 2.0
-
I made some updates to the Squid package so it will run on pfSense 2.0 (on FreeBSD 8 )
I know there are still some bugs, but if you find an issue if you could please figure out step-by-step exactly how to recreate that issue it would be appreciated! It works for me: it installs, it runs, it caches, etc.
The main issue I'm tracking down is that somehow – and I'm still not sure how -- certain config sections are getting an empty <config>tag in them, which makes it appear as though the settings do not save. If you encounter this problem, you can usually edit your config and remove this tag and it all works fine.</config>
-
Does this work with multi-wan?
-
It should if you add the appropriate rules on the floating tab.
I do not know what those should be (I haven't gotten that far with it) but that is how it should work.
You add a floating rule to match traffic leaving from the proxy to remote hosts on port 80, and give it a gateway group. (I think)
-
Just tested,doesnt work with multiwan. Dont have time to dig much, but it seems that the traffic bypasses the proxy totally (in transparent mode).
OT: what happened to this http://forum.pfsense.org/index.php?topic=14877.0 ?
-
There was a problem with snapshots up until yesterday that was causing the transparent proxy rule to not get entered.
Update to a recent snap (4/1 or later) and try again.
-
hi
i downloaded april 2 snapshot, squid was installed and took very long time to install and configure, it did work but it didt save my modification i.e. hard disk size, memory, file size etc…
hadi57
-
hi
i downloaded april 2 snapshot, squid was installed and took very long time to install and configure, it did work but it didt save my modification i.e. hard disk size, memory, file size etc…
hadi57
That is one of the bugs I'm trying to track down but can't reproduce. If you look in the config file, there is probably an extra <config>entry under the <squidcache>tag, and removing it will fix the saving issue.</squidcache></config>
-
I committed another fix which will hopefully cure the settings saving bug once and for all.
Wait for another new snapshot after this post and try it again.
