<![CDATA[Squid and Blocked Production Servers]]>I activated Squid to enable virus scanning and it seems to work well. I got a call this morning that users on the production terminal server servers cannot access a website any more.

I have a rule to block all internet access accept for the websites I want to allow on servers. So there is an Alias with the IP address and domain names of sites to allow through.

Now that the traffic is going through Squid sites that worked before no longer work.

I checked the logs and saw that my rule to block all internet after the allow rules have been processed was blocking 127.0.0.1:3128.

If I add 127.0.0.1:3128 to the allow list it opens up access to the whole internet which is not good.

I tried adding:

acl local-servers dstdomain my.domain.net
always_direct allow local-servers

to Custom ACLS (Before Auth) and that didn't change anything.

Any ideas?

]]>https://forum.netgate.com/topic/106929/squid-and-blocked-production-serversRSS for NodeWed, 16 Sep 2026 18:32:37 GMTFri, 21 Oct 2016 16:37:43 GMT60<![CDATA[Reply to Squid and Blocked Production Servers on Sun, 23 Oct 2016 17:03:21 GMT]]>i would not recomend squid to use the virus scan, it takes a lot of resources and for what i saw its not that stable, i had this enabled it gave me issues when a user wanted to hear music though itunes or radio fm online

]]>https://forum.netgate.com/post/656719https://forum.netgate.com/post/656719Sun, 23 Oct 2016 17:03:21 GMT