Squid 3.4.9 no traffic in transparent mode.

jeepster

While poking around looking for an issue not related to squid I saw something that looked out of place on the squid sockets. If you goto Diagnostics: Sockets there seems to be one squid setting that is outside the table. I don't notice any problems but cosmetic.
proxy squid 46690 14 udp4 6 *:60225 :

seems like there is something extra there…...??

sockets.JPG_thumb

Topper727

Well I got 503 error from UI and reinstalled pfsense now I get

Warning: dir(/usr/local/etc/squid/errors/): failed to open dir: No such file or directory in /etc/inc/pfsense-utils.inc on line 467 Fatal error: Call to a member function read() on a non-object in /etc/inc/pfsense-utils.inc on line 468

Found out that only the General Tab does that error.. I pulled up log and other tabs no problem in Squid 3.4.9

Guess I try another reinstall .. more problems with 2.2 then any other version I ever beta tested

marcelloc

@Topper727:

Well I got 503 error from UI and reinstalled pfsense now I get

I've got this when tried to install squid again without removing previous manual symlinks fixes.

The message tells that errors dir does not exists or points to a invalid dir.

Topper727

Well I reinstalled again and fixed that issue. And worked on LCDproc, put a request on github with fixes.

https://forum.pfsense.org/index.php?topic=83747.75#lastPost

Seems fingers crossed I got most working that I tried so far.. just I-cap won't start is all for me now.

So squid 3.4.10_2 pkg 0.2.5 works on my 1/16/15 64bit 2.2 version with clean install. I would guess this means that the problems that show maybe something to do with a bad install or other factors.

KOM

I would guess this means that the problems that show maybe something to do with a bad install or other factors.

Squid still doesn't work for me, and I'm thinking the same thing as you. Previous hacks trying to get things to work are giving me problems now. I think it's time for a fresh install.

asterix

Do you have loopback checked? If not, check it. In v2 Squid checking loopback never worked for me.. but it seems to do the trick in the latest v3.

marcelloc

Loopback is configured automatically on squid.conf when using transparent proxy.

JStyleG7X

My 5 cents: My "Invalid URL" issue was resolved by disabling the proxy from listening on the loopback adapter. The transparent proxy as marcelloc said is enabled by default which is fine.

Was not working.
http_port 192.168.x.1:3128
http_port 10.x.x.2:3128
http_port 127.0.0.1:3128
http_port 127.0.0.1:3128 intercept

Now Working.
http_port 192.168.x.1:3128
http_port 10.x.x.2:3128
http_port 127.0.0.1:3128 intercept

I also want to mention one side note if you're new to pfsense/squid and troubleshooting issues. If you are using any extra packages Dansguardian/Squidguard/HAVP etc… you might consider removing these until you ensure you have squid working just by itself. I've seen some packages when installed, even though they're disabled still add forwarding rules to squid in the integrations box - so basically it's forwarding to a proxy not running. This may give the illusion it's not working for those who are unfamiliar with what should normally be configured.

I'm always learning something new myself! :)

marcelloc

Thanks for the note :)

Topper727

I got my copy fixed of these issues and a friends now..

https://forum.pfsense.org/index.php?topic=85965.msg544817#msg544817