Squid3 can't find libmd5.so.0
-
I'm getting "Signature for pkg not available" after the pkg command
Finish the pkg install axel cmd
-
Will the same procedure work on 2.1.5?
-
Will the same procedure work on 2.1.5?
It wont work on 2.1.5. The files that marcelloc complied are for freebsd10 amd64. 2.1.5 was built on 8.3.. Squid3-dev works on 2.1.5
-
Transparent proxy still does not work :(
-
Will the same procedure work on 2.1.5?
On 2.1.5, install squid3-dev package. I uses squid 3.3.10
-
Transparent proxy still does not work :(
Maybe related to some 2.2 RC issues, not squid itself.
Check if you don't have this error on your system logs
php: rc.filter_configure: PHP ERROR: Type: 2, File: /etc/inc/util.inc, Line: 184, Message: fsockopen(): unable to connect to unix:///var/run/check_reload_status:-1 (No such file or directory)
tracking this issue I've found this:
ldd /usr/local/sbin/check_reload_status /usr/local/sbin/check_reload_status: libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000) libevent-2.0.so.5 => not found (0) libc.so.7 => /lib/libc.so.7 (0x800a4f000)
trying a manual fix:
ln -s /usr/local/lib/libevent-2.0.so.5 /lib/libevent-2.0.so.5
and check_reload_status seems to be ok again
ldd /usr/local/sbin/check_reload_status /usr/local/sbin/check_reload_status: libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000) libevent-2.0.so.5 => /lib/libevent-2.0.so.5 (0x800a4f000) libc.so.7 => /lib/libc.so.7 (0x800c91000) libthr.so.3 => /lib/libthr.so.3 (0x801023000)
and also transparent proxy
grep 3128 /tmp/rules.debug rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128 pass in quick on em1 proto tcp from any to !(em1) port {80,443,3128,3127} flags S/SA keep state
I've opened a redmine for it, so core team can check this issue
-
I can confirm that error. It was also accompanied by sshd being unable to start. Reverting changes didn't help, but reinstalling the snapshot fixed sshd. I will try the fix you described sometime tomorrow. Thank you!
Transparent proxy still does not work :(
Maybe related to some 2.2 RC issues, not squid itself.
Check if you don't have this error on your system logs
php: rc.filter_configure: PHP ERROR: Type: 2, File: /etc/inc/util.inc, Line: 184, Message: fsockopen(): unable to connect to unix:///var/run/check_reload_status:-1 (No such file or directory)
tracking this issue I've found this:
ldd /usr/local/sbin/check_reload_status /usr/local/sbin/check_reload_status: libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000) libevent-2.0.so.5 => not found (0) libc.so.7 => /lib/libc.so.7 (0x800a4f000)
trying a manual fix:
ln -s /usr/local/lib/libevent-2.0.so.5 /lib/libevent-2.0.so.5
and check_reload_status seems to be ok again
ldd /usr/local/sbin/check_reload_status /usr/local/sbin/check_reload_status: libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000) libevent-2.0.so.5 => /lib/libevent-2.0.so.5 (0x800a4f000) libc.so.7 => /lib/libc.so.7 (0x800c91000) libthr.so.3 => /lib/libthr.so.3 (0x801023000)
and also transparent proxy
grep 3128 /tmp/rules.debug rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128 pass in quick on em1 proto tcp from any to !(em1) port {80,443,3128,3127} flags S/SA keep state
I've opened a redmine for it, so core team can check this issue
-
marcelloc
I ran into a small problem after following your steps
"(squid-1): Cannot open '/var/squid/logs/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf."
I was able to 'monkey' around with winscp to change permissions, not sure what I did but got past that. What would be the correct way of 'doing it right'transparent proxy still not working, under the real time tab this is what I see
09.01.2015 09:27:24 192.168.1.2 TCP_MISS/403 http://yahoo.com/favicon.ico - 127.0.0.1 09.01.2015 09:27:24 127.0.0.1 TCP_DENIED/403 http://yahoo.com/favicon.ico - - 09.01.2015 09:27:24 192.168.1.2 TCP_MISS/403 http://www.squid-cache.org/Artwork/SN.png - 127.0.0.1 09.01.2015 09:27:24 127.0.0.1 TCP_DENIED/403 http://www.squid-cache.org/Artwork/SN.png - -
grep 3128 /tmp/rules.debug rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128 pass in quick on em1 proto tcp from any to !(em1) port {80,3128} flags S/SA keep state
This seems to be fixed with the latest build 2.2-RC (amd64) built on Fri Jan 09 01:08:06 CST 2015
ldd /usr/local/sbin/check_reload_status /usr/local/sbin/check_reload_status: libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000) libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800a4f000) libc.so.7 => /lib/libc.so.7 (0x800c91000) libthr.so.3 => /lib/libthr.so.3 (0x801023000)
thanks for the steps, I'm learning a lot
-
transparent proxy still not working, under the real time tab this is what I see
09.01.2015 09:27:24 192.168.1.2 TCP_MISS/403 http://yahoo.com/favicon.ico - 127.0.0.1 09.01.2015 09:27:24 127.0.0.1 TCP_DENIED/403 http://yahoo.com/favicon.ico - - 09.01.2015 09:27:24 192.168.1.2 TCP_MISS/403 http://www.squid-cache.org/Artwork/SN.png - 127.0.0.1 09.01.2015 09:27:24 127.0.0.1 TCP_DENIED/403 http://www.squid-cache.org/Artwork/SN.png - -
fetch squid34_pfsense22.tar again. I've changed a compile option to include only pf transparent proxy.
remove squid package and reinstall it
pkg delete squid-3.4.10_2 pkg add squid-3.4.10_2.txz
-
marcelloc, it appears to be working now, websites are loading and the log looks back to normal - thanks!!
-
Talking about transparent proxy, latest 0.2.2 package works on Pfsense 2.2RC.
I still can't get squid 3 reverse to work, which is basically the main reason why I'm using squid3.
Same settings on 2.1.5 work like a charm.Thank you for all the efforts you are putting in fixing this.
/chapeau!
-
I haven't tried reverse proxy yet which is another feature I use from squid but I start-up another instance of squid using a conf i've created. For me, it keeps the logs separate since I use proxy for logging with lightsquid.
Anything in your system or squid logs that could pin point the issue?
-
Nothing particular that could point me in the right direction so far.
To be fairly honest, I didn't test it like it should be so can't say much so far.From what I've seen it will always try to forward pfsense webgui on the external FQDN, regardless of what you've set on the backend servers/redirets/mappings etc.
Again, I doubt it's a matter of settings since the same net, same webservers and so on are working right now on 2.1.5.
Will try to provide you some more informations as soon as I can.
Cheers ;) -
just a wild guess, compare your advanced settings under system. I think you have to disable the web GUI redirect
-
marcelloc, it appears to be working now, websites are loading and the log looks back to normal - thanks!!
I'm not having as much luck unfortunately. I've updated to the latest pfsense 2.2 release, removed squid3 package, recursively deleted /var/squid and re-installed squid3 and it is not working properly. With transparent proxy enabled it is passing http traffic (vs. error pages before) but the access.log is empty (not created actually) and the cache.log has a single entry in it from the installation:
2015/01/10 12:24:58 kid1| Creating missing swap directories
am I missing something here? I'm not running squidGuard or havp in conjunction with this, just attempting squid3 in transparent mode.
-
Check the folder permissions for /var/squid/logs. Make sure it's set to proxy:proxy. I ran into this earlier on my test box. After correcting the permissions, the access.log was created and started to log entries. I don't use transparent mode, but I don't think its related.
-
trouserless, install squid package from pfsense gui - 3.4.10_2 pkg 0.2.2 its been updated tp working. Once I configured the settings I had to stop and restart the service to get it going
-
just a wild guess, compare your advanced settings under system. I think you have to disable the web GUI redirect
That's the first thing I've checked.
The reverse proxy part seems to be broken, at least for me, at the moment. -
Check the folder permissions for /var/squid/logs. Make sure it's set to proxy:proxy. I ran into this earlier on my test box. After correcting the permissions, the access.log was created and started to log entries. I don't use transparent mode, but I don't think its related.
tried that and it is proxy:proxy
$ ls -la /var/squid/logs total 24 drwxr-xr-x 2 proxy proxy 512 Jan 10 12:43 . drwxr-xr-x 6 root wheel 512 Jan 10 12:24 .. -rw-r----- 1 proxy proxy 0 Jan 10 12:43 access.log -rw-r----- 1 proxy proxy 518 Jan 10 13:34 cache.log
I checked the cache.log because it had grown and found:
$ cat /var/squid/logs/cache.log 2015/01/10 12:24:58 kid1| Creating missing swap directories 2015/01/10 12:43:37 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.0... 2015/01/10 12:43:38 kid1| /var/run/squid.pid: (1) Operation not permitted 2015/01/10 12:43:38 kid1| WARNING: Could not write pid file 2015/01/10 13:33:55 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.0... 2015/01/10 13:33:56 kid1| /var/run/squid.pid: (1) Operation not permitted 2015/01/10 13:33:56 kid1| WARNING: Could not write pid file
I checked the /var/run directory is owned by root:wheel which looks proper.
One other bit of strangeness is that I no longer have access via ssh (I'm using the command prompt feature for the above troubleshooting). I goto the services page and sshd is showed as stopped. I try and start it and it does not. It worked before and it is enabled via the GUI toggle. I checked system logs and nothing about sshd. Is anyone else seeing this issue with sshd? Thanks for the help/ideas Cino (and others)
-
Are you using the official pbi from http://files.pfsense.org/packages/10/All/ now (i.e via pfsense GUI) or are you still using the manual method?
I noticed that there just have been an update to the pbi and curious to see if works the "official way" now.
squid-3.4.10_2-amd64.pbi, 09-Jan-2015 20:25
Would try it myself but I not at home this weekend…