Problem with SquidGuard - redirecting clients to localhost instead of pfSense.

aaronouthier · Jul 21, 2014, 9:41 PM

Hello,

I have seen this error mentioned, but I have not found any posts that have an actual solution.

I am running 2 pfSense boxes in tandem:
"pfsense1" has both a WAN and a LAN interface, and is running NAT, etc.
"pfsense2" has only a WAN interface, and is running DHCP, "unbound" DNS, Squid3, and SquidGuard for Squid3.

SquidGuard has downloaded and installed Shalla Blacklist. DNS forwarding service is disabled on both boxes. Default GWs are setup on both boxes, as well as on the DHCP server. DNS is also setup and working on both boxes and DHCP. Client Proxy settings are manual for now, but I will get wpad working once I have squidguard working. Squid is operating in NON-transparent mode, WITHOUT authentication, and Cache and logs are being saved to a 2 GB, CF-type Microdrive, which I have formatted and setup in /etc/fstab.

Squidguard correctly passes and serves web content for allowed content, but for blocked content, it redirects to the client's 127.0.0.1 address, when it should be redirecting to 192.168.55.2 .

I am down to my final 25 hairs or so - I've already torn the others out!!!

vcamposm31 · Mar 30, 2016, 3:44 PM

I am having the same problem, you solve at the time?

Gian · Apr 4, 2016, 6:37 PM

Hi,

I had the same problem as yours.

I have one pfSense box as my firewall/gateway, and I have another pfSense box as a proxy/filter. Both are Hyper-V VMs.
The proxy box had only one WAN interface, and I did not manage to change the configuration in SquidGuard to take the IP of that interface instead of the localhost IP.
I solved the problem adding a private network between my Firewall pfs and the Proxy pfs. With both LAN and WAN, SquidGuard take the correct IP of my Proxy box.