Problem with web uploads in new dansguardian 2.12.0.3
-
Here is the fix for 32-bit, applied today (01/28/2014) and it worked beautifully:
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-i386/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh start -
Please note that you actually want the executable in the /usr/pbi/dansguardian-xxx/sbin folder and not /usr/local/sbin. It is only actually launched in scripts from the /usr/pbi folder (and /usr/local/sbin/dansguardian should be a symlink to the PBI executable).
-
Hi there.
Actually, it seems like you do not need to delete /usr/local/etc/dansguardian and make a soft link after that.
I just replaced /usr/pbi/dansguardian-i386/sbin/dansguardian with provided one (fetch http://e-sac.siteseguro.ws/pfsense/8/dansguardian), made it executable, restart DG and it works fine. I am uploading this post after above operations.
PS. but I still did killall dansguardian before…
-
I've fixed the code. ;D
The patch 11 was malformed and broke up web upload check.
I did not pushed it to dansguardian devel or freebsd patch yet.
Test my dansguardian package and see if it works
I've also included the code to limit upload size(was not working on 2.12.0.2 AFAIK)
amd64
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.3_1.tbzi386
http://e-sac.siteseguro.ws/packages/8/All/dansguardian-2.12.0.3_1.tbzDo not forget to kill dansguardian process before trying new packge binaries.
The above patched version worked perfect but since 9th april 2014 the available packages webpage within pfsense shows only 2.12.0.3_2 version which is partially broken and gives errors of contentscanner directories missing while booting…also start/ stop /restart of dansguardian from ssh via /usr/local/etc/rc.d/dansguardian.sh also reports errors..Pl restore the 2.12.0.3_1 link in the available packages so everything works fine again
Thanks
-
It seems that the problem with /usr/local/etc/rc.d/dansguardian.sh is that it is looking for "/usr/local/sbin/dansguardian" in the process name. However, the process name is being created with "/usr/pbi/dansguardian-amd64/sbin"…
Not sure why... A temporary workaround would be to edit the file /usr/local/pkg/dansguardian_rc.template and change the path in the variable "command" (line number 29)
Change
command="/usr/local/sbin/${name}"
to
command="/usr/pbi/dansguardian-amd64/sbin/${name}"Note that if you are running the 32 bit version or "i386" you would put that instead of "amd64"... Anyway - make the above change and reboot. Script should work now.
Not having much luck figuring out the other startup errors...
-
Yes after the changes the script worked to start / stop /restart dansguardian.
Couple of issues still remain unresolved i.e- During startup the package complains about missing exceptionviruslist files in /usr/pbi/dansguardian-amd64/etc/dansguardian/lists
- Its also complains about missing clamd.conf file
- Webupload banned
Pl help
cirkit -
- During startup the package complains about missing exceptionviruslist files in /usr/pbi/dansguardian-amd64/etc/dansguardian/lists
- Its also complains about missing clamd.conf file
I haven't figured these two out yet, but if I have time I will look over the weekend.
- Webupload banned
This can be fixed by overwriting the dansguardian executable with a different version… look through previos posts in this same thread.
Marcello - are you watching these posts? Any chance you could make changes quickly or simply roll back the version? Thanks!!!
-
Hi guys…
I need to make a new pfSense box, but can't get DansGuarding working properly - facing the same problem as cirkit.
Will you please (at least for now) roll back the version? It worked fine with just replacing binary...
Thanks.
-
Marcello - are you watching these posts? Any chance you could make changes quickly or simply roll back the version? Thanks!!!
Not really sure what you are expecting from him since he cannot commit anything anyway. Another "improvement" in development… ::)
-
Wow! That's incredibly inconvenient. Why was that change made?
-
Why was that change made?
You can ask at the relevant thread, already shared my thoughts there. >:(
-
Hi there.
Any updates on these issues?
-
Here is the fix for 32-bit, applied today (01/28/2014) and it worked beautifully:
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-i386/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh startHad the same problem as everyone else. ssh-ed into my pfsense box. Opened a shell. Executed this exactly as entered above. Works perfectly!
Thanks dvosburg!
-
I had the same issue on a amd64 setup, the commands are nearly the same but I thought I would post it again for clarity.
Here is the fix for 64-bit, worked like a charm:
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-amd64/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh start -
Got the same issue. For me, mschiek01's instructions at https://forum.pfsense.org/index.php?topic=75243.0 solved the issue. :D
-
I found that these fixes did not work for pfsense 2.1.3 and 2.12.0.3_2 pkg v.0.1.12 on a 32 bit system.
I was able to fix it by backing up and overwriting the dansguardian executable at /usr/pbi/dansguardian-i386/sbin.
Commands:
cd /usr/pbi/dansguardian-i386/sbin/ mv dansguardian{,.org} fetch http://e-sac.siteseguro.ws/pfsense/8/dansguardian /usr/pbi/dansguardian-i386/etc/rc.d/dansguardian onerestart
Please note that the commands will be different if you are on a 64 bit machine.
-
Here is the fix for 64-bit, worked like a charm:
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-amd64/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh startAs a note: this does not work on 2.2.2. libssl.so.6 and libcrypto.so.6 no longer exist. they are .7's. Soft linking to these files as .6 causes a permission denied error. (yes, I did chmod +x on the dansguardian download.
This is on the x64 version. Not sure of the 32 bit version.
Also, is there an ETA on E2Guardian being a package for pfsense?
(edited for spelling)
-
Here is the fix for 64-bit, worked like a charm:
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-amd64/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh startAs a note: this does not work on 2.2.2. libssl.so.6 and libcrypto.so.6 no longer exist. they are .7's. Soft linking to these files as .6 causes a permission denied error. (yes, I did chmod +x on the dansguardian download.
This is on the x64 version. Not sure of the 32 bit version.
Also, is there an ETA on E2Guardian being a package for pfsense?
(edited for spelling)
i am also experienceing the above mentioned issue regarding the dansguardian upload limit, and the fixed bin file needing the lib crypto.so.6 on amd64 install. has anyone managed to put this to rest. or am i looking at a downgrade to pf 2.1
-
I'm curious as to how this is still an issue over two years later. If there is a fix why isn't it included in the repo's? :o
I just set a customer up with a pair of SG-2440's ($1,000 wasn't pocket change for them) and found that this isn't working, …and now it appears there is no way to even patch it as they are running 2.2.3 (I upgraded the boxes from the 2.2.2 they came with).
Any ideas other than a downgrade (which isn't an option)? :'(
NOTE: Sorry for the mini rant, but I just don't understand why this hasn't been fixed in the package yet. :)
EDIT: OK, I just found that it's being replaced by e2guardian, but although it seems to be ready, a pfSense package doesn't seem to be happening. =(
-
I tried the old fix (just to be sure) and can confirm that it doesn't work:
```
Shared object "libssl.so.6" not found, required by "dansguardian"I've had to disable the filtering until an e2guardian package appears, but I'm not too expectant as there hasn't been ANY action for over a month now. Filtering was pretty much the point of having the SG-2440's, so this is very disappointing. :-\