Squid3-dev package doesn't work on 2.2 beta OOB.
-
So, I grabbed and installed pfSense 2.2 about 2 weeks ago. Tried to get squid3-dev going. Package binary wouldn't start. Running 'squid -d 9' from a command prompt gave a complaint of a missing 'libmd5.so.1' file.
Long story short, I discovered that squid3-dev wasn't compiled correctly - wrong compile-time flags, I think.
I fixed it with:
killall squid cd /usr/pbi/squid-amd64/ cp -r ./local/* /usr/local/ rm -rf ./local ln -s /usr/local ./local sync squidUnfortunately, I have to repeat the above commands all over, every time update the beta snapshot.
I hope this helps somebody.
I should also note, that although squid now runs, I am still unable to connect any clients to it. DansGuardian also cannot connect when it is enabled. Maybe something to do with a socket file??
-
I should also note, that although squid now runs, I am still unable to connect any clients to it. DansGuardian also cannot connect when it is enabled. Maybe something to do with a socket file??
Thank you every much for sharing this. You confirm my theory that it wasn't compile correctly.
You mention that clients can't connect to it… Have you rebooted you box since moving the files around? I've only tested with 1 client under a vm, but its working for me.. Both with squid3 and DansGuardian... I'm not using transparent mode if that helps
now if I can find the time, i' may update my box to 2.2..
-
Yes, I have rebooted after doing all of this. I am not running in transparent mode either. Before, squid process would die, now it runs, so some progress has been made.
I have installed FreeBSD onto a VM and am recompiling squid as we speak. DansGuardian will be next. I am using the latest stable versions of each as of Friday, September 26th, 2014.
More to come.
-
So there's no proxy working on 2.2 BETA at all, am I right?
Squid3 is too old and Squid3-dev can't start/use.
-
Correct!
There is no offical Package for Squid that runs. I reported this here –> https://forum.pfsense.org/index.php?topic=81118.msg448476#msg448476
You can test the workaround made by aaronouthier in Post #1Hopefully there is a fix/new package.
-
With the workaround squid3-dev is working for me.
squid2 is supported by the pfSense core team while the other squid3x packages are maintained by someone else..
report a bug here, redmine.pfsense.com and see if they accept it
-
I have DansGuardian recompiled and working. Although I had recompiled Squid, I had done so from the official squid source directly from their web site. This may seem the right way to go in theory, and indeed, everything worked on my development box. That is to say, that I could successfully connect and use DansGuardian and Squid on my test box. When I copied both (along with the required shared libraries) to my pfsense box, I again could not connect directly to squid, and DansGuardian also couldn't forward the connection. I am still working on it.
I have wiped & reinstalled my pfSense box, and am reinstalling my devel box as well.
Gotta run. I'm on a roll, and I don't want to lose my train of thought.
-
Is anybody running on amd64/x64 platform and willing to test my versions and give some critique on my changes. I don't want this to go public, only to find that is a blatant bug staring me in the face.
Also, I got of on a tangent in my last post. I am using the FreeBSD Ports catalog/repository for Squid this time around.
Note, that I am compiling both Squid and DansGuardian for FreeBSD 10.1 Beta and thus, pfSense 2.2 beta. Anyone wanting/willing to help with this would need to be on that platform. Anybody know who are the maintainers of the current DansGuardian and Squid packages?
-
Hello,
I would be willing to test, I am running 2.2 AMD64. Let me know what I need to do.
-
For the most part, sit tight for the moment.
I am reusing the menus and stuff from the existing packages, so I guess if you want to get started, you could download and install the squid3-dev and dansguardian packages.
I just started with a "clean slate" pfsense 2.2 install.
For what I hope are obvious reasons, do not try this on any kind of production unit. Also, don't follow my instructions to get the existing squid package working - the may conflict with my development version.
I am still compiling squid for the second go around, so when I have finished that, I'll need to see what I need to do to get my setup working. At THAT point, I'll post what I did and instructions for repeating what I did as soon as I have such instructions.
I will probably contact you via PM for the instructions, if that is ok? I don't want the every "Random Joe" trying this until I have a handle on it. General discussion, I expect, should take place here. Specifics to getting the files and using them, would be via PM.
I'll post the files to my dropbox account for you to pickup later.
I'm going to double-check that my privacy settings allow for members to contact me via PM. Anyone interested in testing should do the same.
Lastly, If anyone else wants to help test, DO NOT PM me directly to say so. Comment in this thread instead. I'll send you the instructions via PM.
I'll give x86 a try if/when x64 is successful.
-
I'll test x86 when they are ready :-) Thanks man
-
Files posted in another thread. Let me know if any problems arise.
-
With the workaround squid3-dev is working for me.
squid2 is supported by the pfSense core team while the other squid3x packages are maintained by someone else..
report a bug here, redmine.pfsense.com and see if they accept it
Appreciate all the work aaronouthier has been doing on squid3-dev, but I was wondering if anyone is working on squid2?
-
Since I couldn't configure lightsquid or sarg reports, I wasn't sure that squid2 was working so I kept looking for a squid3 solution. But as it turns out, squid2 works great in 2.2. There is a minor issue that every firmware update, I have to reinstall the package even though the firmware update supposedly does that (according to the CLI). I left squid on and it works just as well if not better.
The only thing I miss about squid3 is the real time status showing hits and misses. But squid2 works better with proxies so overall I'd stick with squid2.
-
Yep… I'll confirm the same. I went ahead and tried it with no issue. Thanks!