Hi, there seems to be an issue with this PFSense version and Squid3 making Squid3 unavailable in the package list. There also is an issue with Squid3 when you upgrade from < 2.2.4 making that it doesn't start. The resolution for that issue is discribed in another post. You could install 2.2.3, install squid3 and then upgrade to 2.2.4 and follow a short fix that I described in this post https://208.123.73.68/index.php?topic=97211.0.

Hi, I had the same issue. Logging in using SSH and executing: /usr/pbi/squid-i386/bin/squid Did the trick for me and fixed some issue; even after a reboot squid seems to work fine again. After that i was able to execute the start and stop from the GUI too. Or from the command line: /usr/local/etc/rc.d/squid.sh start Note: I have squid running on a port above 1024 Check the tunables under system -> advanced and set the minimum port value from 1024; (default) to 0 to disable this and run squid on i.e. port 80

Use explicit mode with WPAD instead. https://doc.pfsense.org/index.php/WPAD_Autoconfigure_for_Squid

@KOM: Please don't hijack an unrelated thread.  Post your problem in its own thread and I;ll be happy to help. Thanks , I'm going to start new thread  :)

Regardless, your throughput is going to stink if you have a virus scanner in the mix.  You're better off running an acceptable AV package on your clients instead of loading the firewall with extraneous stuff that's guaranteed to slow the flow.

Hi, It was on port 80 but I've changed it to 8080 yet it still doesn't work, it no longer gives the error but just sits there and times out trying to access remotely. regards Jamie

I'm starting to believe that disk caching is not very useful anymore due to low hit rates, and squid is only good now for URL filtering with squidguard.

Gdsnytech, I'm currently on vacation, so I don't have access to my system at this moment, but I'll try and help as much as I can ( from memory). :-) The first step is probably to make sure that the "squidtrustIII.exe" is working and reporting the system information correctly. Use the squidtrustIII files from the sourceforge page. They are the most current. http://sourceforge.net/projects/squidtrust/files/SquidtrustIII/ Run the exe file on the workstation, and you should see a small penguin pop up in the lower right system tray. From a second workstation telnet to the workstation running the agent on port 2199. You should then be able to press the number keys 1-7 (if I recall correctly), and the agent should return various system/user information, then disconnect. Please verify that the agent is working as expected, and if not, please provide any information that may help in troubleshooting…ie: windows OS, any anti virus running? Can you connect to port 2199 or does the connection not work? .....etc.....

How did you set it up? Either way, your best bet would be to use VHost to "advertise" it. You can also use Windows DHCP to push it. Also take a look here: https://forum.pfsense.org/index.php?topic=93060.0 http://irj972.co.uk/articles/pfSense-WPAD-PAC-configuration Though i would suggest the former.

I understand you your speaking quite well as I have a few family members by marriage of German decent. I have spent a great deal of time with and have come to be able to pickup what they are saying quite easily. As far as the reading you mentioned goes, reading is not the issue. The issue is understanding the terminology and most writings about pfsense, don't go into great detail " in laymen's terms " on what things do in the program. When coming to these threads, one really has to rely on the quality of the responses which can be shaky at times. Answers are answers; but if they are not intelligible by the reader, then they haven't provided the help desired and this is my biggest issue so far. I really appreciate that you have taken time to assist and it has definitely pushed me to tinker a little harder and see what does what. For squid and squid guard. since I figured out that the blacklist requires daily updating, I followed the instructions I mentioned for cron and it seems to be doing what it is supposed to. Frankly, I'm a little blown away that squid doesn't have a native option for this. For proxy and wpad. I worked my way through he directions and the proxy works. WPAD not so much. Even though I created the files, placed them in the correct directories and added the DHCP rule, my computers still bypass the proxy unless I go into the internet option on my browsers and point them to the proxy. I can verify this using light squid. Additionally, with squid guard, the rules set for website types don't pickup unless, I add the setting for the proxy in the browser. These above are the issues that still remain and I'm not ruling out user error in my settings. Just really hoping that someone else has experience the same issues and can pass along what they did to fix them.

The culprit i have found it in fact to be the "Antivirus", ClamAv and I-cap. The speeds are nearly identical, up above 90/70 with it turned off. With it on upload in particular is hitting around the 30 mark. Barely over at times. Any suggestion(s) in tuning ClamAV and I-Cap?

I think that it has something to do with your Squid config. Check the ACL and throttle tabs. Make sure that your settings are correct. Read the directions.

on a clean install of 2.2.3 it starts up and runs (needs to sit a while after doing the first update) then it gives the "Warning: file_put_contents(/usr/local/etc/havp/havp_conf.xml): failed to open stream: No such file or directory in /usr/local/pkg/havp.inc on line 604" but does work with the latest update

Sigh. No, pfSense does not reinstall package on reboots. It reinstalls them on upgrade. It clearly failed with the squidGuard junk.

Are you blocking port 80 on the Lan2(wifi) interface? Also, if squid is on the default Lan interface you need a both in both interfaces that allows them to talk to each other or just the squid Lan address to port 80. These rules have to be above the rule that blocks port 80 (if any) on both interfaces. i.e. LAN                                                                        LAN2 lan add – lan2 * (allow)                                  lan2 * --- 80 lan add (allow) lan2  *  -- 80  lan add (allow)                          lan add  --- 80  lan2 * (allow)                                lan *  ---  80 * (block)                                    lan2* --- 80 * (block) This is of course if you only want the two interfaces to communicate via port 80 only. Otherwise set for allow all.

@commy: Squid3 seems to ignore IPv6 traffic, which is coming over a tunnel with HE. I do not see any options to switch IPv6 on. Is it not supported? It looks like the used verision 3.0 of Squid does not support IPv6, it only listens on IPv4. According to Squid documentation, Squid 3.1 is required for IPv6. I hope that it will bundled with pfSense, soon.