squid3 access_log option fixed?

[cyber7]

Hi guys
I have reported the problem to pfSense where squid3's instruction to not log a single IP in April this year, but it is still not working.  I have also posted a workaround, but pfSense is not doing anything about it (4 months later)...

Could someone from your developers please test and see if the same goes for OPNSense?  If it has been fixed and the problem sorted, I am going to switch all my products to your release.

sick of being ignored by pfSense
cyber7-out

Link to technical writeup of the access_log acl problem in squid: https://aubreykloppers.wordpress.com/pfsense-exclude-an-ip-out-of-your-squid3-log/

[franco]

I am not the author of our squid implementation, but I can say that we've written it from scratch. You should double check if our implementation can do what you are expecting, because we can't be certain the feature set matches other vendors implementations.

[AdSchellevis]

Hi cyber7,

I've looked at your issue, although I really think it's a feature I did put it into our code-base.
The feature looks pretty useful to me.

Commit https://github.com/opnsense/core/commit/c51ac453ac463816942e682e1782d8b80f750065 contains the necessary code to add it.

We will decide later if this commit makes it to the stable release, but given the low impact I think it will.

If you want to add a feature or bug request in the future, I want to ask you to place them on GitHub. This one I've created for you (https://github.com/opnsense/core/issues/287).

Don't expect all issues to be fixed this fast, you could always first try to fix it yourself and send us a pull request.

Enjoy OPNsense,

Cheers,

Ad

[franco]

Thanks Ad! As soon as 15.7.6 is out, you can test the development version of OPNsense by doing the following on the console:

# pkg install -y opnsense-devel

The development package may be rough, but for testing particular features it is really handy.

To go back to a default install, type:

# pkg install -y opnsense