Transparent proxy not working after upgrade to 2.2
-
Foud this in the log:
php-fpm[83033]: /pkg_edit.php: The command '/usr/pbi/squid-i386/sbin/squid -k shutdown' returned exit code '1', the output was 'Shared object "libz.so.5" not found, required by "libmd5.so.1"'That thing gets removed. https://github.com/pfsense/pfsense/blob/master/etc/pfSense.obsoletedfiles
$ ls -l /usr/lib/libz.so* lrwxr-xr-x 1 root wheel 14 Jan 24 06:00 /usr/lib/libz.so -> /lib/libz.so.5 $ ls -l /lib/libz.so.5 ls: /lib/libz.so.5: No such file or directory $ ls -l /lib/libz.so.6 -r--r--r-- 1 root wheel 79180 Jan 22 22:07 /lib/libz.so.6This clearly is not done properly on FULL installs, as seen from the dangling dead symlinks.
Cf. that with nanobsd:
$ ls -l /usr/lib/libz.so* lrwxr-xr-x 1 root wheel 14 Jan 22 22:07 /usr/lib/libz.so -> /lib/libz.so.6 $ ls -l /lib/libz.so.6 -r--r--r-- 1 root wheel 79180 Jan 22 22:07 /lib/libz.so.6Is this setup a migration from 2.1 or any 2.2RC version?
Not getting it on amd64. :-\Apparently an upgrade process bug on full installs, rendering the updated library pretty much useless as it cannot be found. Just a few examples:
/usr/lib/libcrypto.so -> /lib/libcrypto.so.6 $ ls -l /lib/libcrypto.so.6 ls: /lib/libcrypto.so.6: No such file or directory /usr/lib/libmd.so -> /lib/libmd.so.5 $ ls -l /lib/libmd.so.5 ls: /lib/libmd.so.5: No such file or directory $ ls -l /usr/lib/libusb.so* lrwxr-xr-x 1 root wheel 11 Jan 24 06:00 /usr/lib/libusb.so -> libusb.so.2 -r--r--r-- 1 root wheel 65068 Jan 22 22:07 /usr/lib/libusb.so.3 /usr/lib/libufs.so -> /lib/libufs.so.5 $ ls -l /lib/libufs.so.5 ls: /lib/libufs.so.5: No such file or directoryBadly, badly broken. >:( => https://redmine.pfsense.org/issues/4328
-
I think this can be resolved by creating a link between those libs.
and restarting squid.ln -s /lib/libz.so.5 /usr/lib/libz.so.6(if the file is in /lib of course)
You can do a search to make suresu find / -name libz.so.*I had the same problem with squid and snort a while back
let me know what happens ;) -
I think this can be resolved by creating a link between those libs.
and restarting squid.ln /lib/libz.so.6 /lib/libz.so.5Uh no, this is completely wrong "fix".
-
Uh no, this is completely wrong "fix".
So you're saying it won't work untill 2.2.1 is rolled out ?
-
You are fixing the wrong thing! That .5 vs .6 actually has a meaning - the new version of the library does not have a backward-compatible ABI! If you want to fix something, then fix the dead /usr/lib/*.so symlinks so that they point to proper file. Don't create "compatibility" symlinks pretending a deliberately removed outdated ABI library is still there.
-
Renato is going to rebuild squid pbi under i386, this may fix most issues.
-
Yes you're right, but do you expect users to have a non functional box for god knows how long.
like i said, its a temp fix that works for me.
when squid is rebuild and functioning again, I will undertake the needed steps to make it point to the right libs.On the other hand, disable squid and wait for an update is also a solution…
But where is the fun in that :PAnd yes, I know the .5 - .6 has a meaning, thank you for being so condescending.
also i made a typo, it should be```
ln -s /lib/libz.so.6 /usr/lib/libz.soand i'm guessing squid points to /usr/lib/ to find the files ? -
Yes you're right, but do you expect users to have a non functional box for god knows how long.
Is this question for me? ???
-
Is this question for me? ???
No ;)
Its was an answer to doktornotor -
Hello,
for me after the 2.1.5 to 2.2 version, the captive portal not worked.
I added an new Rules in Firewall to accept 8002 port and it's works.
-
for me after the 2.1.5 to 2.2 version, the captive portal not worked.
Captive portal itself(better start a new thread) or Squid integration with captive portal?
-
Hi,
My name is fred and I am sorry if I write in your post but but I did not find how to start a discussion
I have a problem with pfsense installation script was ok but now I cannot access to the box anymore. What can I do? Is it possible to reset the box?You can write me directly fredbovyeirl@gmail.com
The in advance and sorry again
Fred -
although it's not a squid issue, I've tried to use netcat to listen to the same port as squid and I don't receive any traffic
this is what I get with pfctl while trying to connect to google.com from a client(192.168.1.9)
rdr on fxp0 inet proto tcp from any to ! (fxp0) port = http -> 127.0.0.1 port 3128 pass in quick on fxp0 proto tcp from any to ! (fxp0) port = 3128 flags S/SA keep state fxp0 tcp 127.0.0.1:3128 (173.194.40.3:80) <- 192.168.1.9:55613 CLOSED:SYN_SENTHi Brandhor,
Have you got anywhere with this?
I started a similar thread pfSense 2.2: Squid 3.4.10_2 pkg 0.2.6 redirection not working in transparent mode before spotting you had the same issue.
You'll see below that I did exactly the same as you (great minds think alike) and came to the same conclusion.
To prove the point that the redirected transparent connection is not getting through to squid, I stopped the squid process and then ran the following on the pfSense console.
: nc -l 3128I then telnetted to pfsense from my laptop and a connection was established and characters passed.
$ telnet 10.5.1.1 3128 Trying 10.5.1.1... Connected to pfsense.scevans.com. Escape character is '^]'. hello: nc -Dl 3128 helloI repeated trying to telnet to port 80 on news.bbc.co.uk which should have been directed by the redirect, and no connection was made.
Steve
It was later in this thread that Marcelloc commented on the compile settings I'd got from squid.
Now here's an oddity.
This is one of pbi behaviors. same binary, different folder, different results. (Imagine get all it working together :))
And here is the confirmation that pbi build on i386 is outdated
'--disable-ipf-transparent' '--disable-ipfw-transparent'Go to amd64 and it will work :)
Thanks for your feedback
Seeing that there was a firewall related compile time option I decided to wait for the squid update, but alas when that came the behaviour was unchanged.
Trying to understand what was going on I started another thread Order of rule application for redirects to which there has been no response.
Keen to hear where you are with this issue.
Thanks,
Steve
-
I haven't tried again since I got an mpls line upgrade and now I route all the traffic through another pfsense via openvpn
-
Hi Steve / all
Although it's my first post I can confirm that I have the same issue with the transparent proxy not processing requests. This was a clean 64 bit 2.2 install on an APU4 appliance.
Chris
-
After update to 2.2 and some fixes, seems that squid is working, but transparent mode is not available. If I configure a client to navigate through port 3128, proxy filters connection, but in transparent mode proxy doesn't listen. May be config error? Any rule to add in 2.2 not needed in 2.1?
I've x86 version and 2.1 was working like a charm.
Thx.
FIRST LINES OF squid.conf - is correct to entries with http_port at 3128?
# Do not edit manually ! http_port 192.168.0.254:3128 http_port 127.0.0.1:3128 transparent icp_port 0 -
I get the same configuration and the same problem: in transparent mode the connection doesn't work. No squid log available.
First lines of squid.conf are the same:
http_port (laninterface):3128 http_port 127.0.0.1:3138 interceptMaybe it is a routing (tcp *:80 to 127.0.0.1:3138) problem?
-
I get the same configuration and the same problem: in transparent mode the connection doesn't work. No squid log available.
First lines of squid.conf are the same:
http_port (laninterface):3128 http_port 127.0.0.1:3138 interceptMaybe it is a routing (tcp *:80 to 127.0.0.1:3138) problem?
Yes, it seems only a routing problem. But this redirection (tcp *:80 to 127.0.0.1:3138) should be done by squid itself checking transparent proxy option. I've tested squid on 3128 and it's working fine, but port 80 comunications aren't redirected. Any ideas?
Thx
-
I get the same configuration and the same problem: in transparent mode the connection doesn't work. No squid log available.
First lines of squid.conf are the same:
http_port (laninterface):3128 http_port 127.0.0.1:3138 interceptMaybe it is a routing (tcp *:80 to 127.0.0.1:3138) problem?
Yes, it seems only a routing problem. But this redirection (tcp *:80 to 127.0.0.1:3138) should be done by squid itself checking transparent proxy option. I've tested squid on 3128 and it's working fine, but port 80 comunications aren't redirected. Any ideas?
Thx
from what I remember from my tests it's a firewall issue, if you manually try to create a nat rule that redirects outgoing connections to the firewall address(either 127.0.0.1 or the LAN one) it doesn't work
the only thing I can think of is that maybe it's a driver issue with some nics since pfsense 2.2 uses freebsd 10, my lan nic is an intel 82801BA/BAM/CA/CAM (device id 2449) and is listed as fxp0 on pfsense -
I had these errors on my squid log:
2015/03/18 12:54:28 kid1| Starting Squid Cache version 3.4.10 for i386-portbld-freebsd10.1... 2015/03/18 12:54:28 kid1| commBind: Cannot bind socket FD 18 to 192.168.2.1:800: (13) Permission denied 2015/03/18 12:54:28 kid1| commBind: Cannot bind socket FD 19 to 192.168.16.1:800: (13) Permission denied FATAL: Unable to open HTTP Socket Squid Cache (Version 3.4.10): Terminated abnormally.Using sockstats I didn't have nothing on the 800 port. I lurked around and I found the solution on the Bugtracker of pfSense [1]. Run this command on console or add it to System/Advanced/Tunables
sysctl net.inet.ip.portrange.reservedhigh=0[1] https://redmine.pfsense.org/issues/4196
