Problem is the c-icap.conf file does not contain the line indicated in the instructions:

Remove ldap configuration'Manager:Apassword@ldap.chtsanti.net?o=chtsanti?mermberUid?(&(objectClass=posixGroup)(cn=%s))' from 'c-icap.conf' field.

In the c-icap.conf file, the ldap section looks like such:

# Module: ldap_module # Description: # Add LDAP support to c-icap. The user can use LDAP based lookup tables # using the following lookup table path: #       ldap://[username:password@]ldapserver?base?attr1,attr2?filter[{[cache=no]}] # The filter can contain the "%s" formating code which will be replaced by # the search key # Examples of supported ldap urls: #     ldap://ldap.chtsanti.net?o=chtsanti?cn,uid?uid=%s #     ldap://cn=Directory Manager:Apassword@ldap.chtsanti.net?o=chtsanti?mermberUid?(&(objectClass=posixGroup)(cn=%s)) # # WARNING: is not enough tested it may contain bugs! # Example: # Module common ldap_module.so # End module: ldap_module

So it appears that it is throwing an error although the .conf file does not contain the aforementioned lines?

I have no idea.  I don't use squid3 on pfSense anymore.

I'm a little late updating, but it was indeed a dns problem.

1.  Educate your users on what is acceptable and punish the users who don't comply with your policy
2.  Block these proxy sites one by one as you discover them.

That's about all you can do.

never was able to figure this one out  :'(

hi

Thanks to you All i have Read and followed the article and my issue has been resolved

https://forum.pfsense.org/index.php/topic,62263.0.html

Thanks to you all

Hi,

I ran into the same issue. Using Squid3.

Noticed that in my case the streaming would start after 3-5 min. Also check Services/Proxy Server/Real Time and noticed quite a few TCP_MISS_ABORTED. My interpretation was that these occurred due to the client application in my local network timed out trying to connect to the remote server.

Tried adding below in squidclamav.conf rendered no positive result:

# Do not scan audio streaming abort ^.*\.(m3u|pls|wmx|aac|mpeg)$ abortcontent ^audio/m3u$ abortcontent ^audio/pls$ abortcontent ^audio/wmx$ abortcontent ^audio/mpeg$ abortcontent ^audio/aac$ abortcontent ^.*audio\/mp4.*$

In my case the resolution was below parameter change in squidclamav.conf:

dnslookup 0

After restarting squid and c-icap services, audio streaming worked as expected.

//Jimmy

Yeah, stuff like that is almost always a CDN of some sort.

Hi rjcrowder
Can you tell me what values you are using?

Regards.

Same problem here, been working on this a few days with no result.  The fixes posted for 2.1 don't apply.

did you ever figure out how to get this going?

Edit –-

I was able to get AV with squid 3 to work from this post:

https://forum.pfsense.org/index.php?topic=91362.0

@killmasta93:

You cant block https unless you use WPAD (works but may or may not block on android phones) or explicit proxy which means installing CERTS on each computer/devices.

I'm not 100% in line with this view:
WPAD is used to avoid manual proxy configuration on each and every device (Web Proxy Auto Discovery). Nothing more nor less than this.
On the other hand, your point about certificates to be installed on each device is rather linked (perhaps) to some willingness to implement MITM at proxy level in order be able to scan HTTPS flow content.
Aside the fact that this is weird  :P this is different from access control, fully achievable without MITM.

Regarding MITM, I'm also surprised it's a matter of certificate installation. I would rather say that you have to trust, on each and every device, CA having signed certificate used by Squid. Either manually or deploying CA public key on each and every device  ;)

Or I misunderstand your point  :-[

I'm going to assume I can't do what I want to above.

I also just read that this package hasn't been updated since 2012 due to no freebsd port, so I am probably wasting time trying to configure this - will wait for the e2guardian package