pfSense » pfSense Packages

How can you say this isn't a bug if you don't know what it's referencing? There is most definitely a problem with this package. Many have reported it on the forums, myself included.

Finally was able to replicate it here. Found the cause, best solution is yet to be determined.

truss shows it trying to open /dev/pf and failing (permission denied), squid runs as "squid" now, /dev/pf is root:proxy

"chgrp squid /dev/pf" and it works but that's not a good fix.

At some point on 2.3 squid was changed to use the squid user, which seems more appropriate, but won't work as-is there. Looks like either the squid package needs to go back to using the proxy group at least, or add the squid user to the proxy group so we don't have to alter the permissions or ownership of /dev/pf

I installed new pfsense 2.3 and installed squid.
I did this command: chgrp squid /dev/pf
problem is same exist: Squid non-functional in transparent mode in 2.3

Jim Pingle wrote:

Looks good now, others on the forum and here have also confirmed it is working now. Closing.

I installed new pfsense 2.3 and installed squid.
I did this command: chgrp squid /dev/pf
problem is same exist: Squid non-functional in transparent mode in 2.3

If that didn't work, this is not your issue. Please start a forum thread to discuss and troubleshoot.

Please come to https://forum.pfsense.org/index.php?topic=110731.0

Here’s the mail I got recently for my problem
I was not able to get to these sites at the time of my first post but now for the last day I have been able to access them. Also, there were times during the prior 2-3 weeks that I was able to get to "problem" sites but it definitely was infrequently.

The error message, in addition to the ERROR 324 said the "server did not send any data." I'm sorry I didn't "snip" the exact error message. I will when I see it again.

I will now proceed until the "problem" resurfaces. Then I will go through Methods 1-3 and see what I find. I have my fingers crossed but since I was only able to go back to a restore point from one week ago, it was still in the middle of the "problem" time period, so I believe there still is potential for the issue to resurface.
Or otherwise try this: http://www.deskdecode.com/err_empty_response/