Dansguardian - Web upload is banned
-
Getting this error now with the latest Dansguardian while trying to post on forums.
"web upload is banned"
-
Every time you reinstall the package, you need to manual update the binary too.
-
how do I do that? can u give me the exact command for it please.
-
how do I do that? can u give me the exact command for it please.
amd64
fetch -o /usr/local/sbin/dansguardian "http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian"i386
fetch -o /usr/local/sbin/dansguardian "http://e-sac.siteseguro.ws/pfsense/8/dansguardian" -
Thank You !
-
Can't the binary update be automated after every re-install?
-
Can't the binary update be automated after every re-install?
Not until a new freebsd port for dansguardian. Packages are not allowed to push binaries out from official repo.
-
I am trying to update the binary and instructed in the thread but I am not able to access the http://e-sac.siteseguro.ws. Is there another location that I can get the new binary.
-
I am trying to update the binary and instructed in the thread but I am not able to access the http://e-sac.siteseguro.ws. Is there another location that I can get the new binary.
Check if you do have blocked traffic to Brazil.
You can compile it on any freebsd from the same version as your pfsense.
-
I am trying to update the binary and instructed in the thread but I am not able to access the http://e-sac.siteseguro.ws. Is there another location that I can get the new binary.
Check if you do have blocked traffic to Brazil.
You can compile it on any freebsd from the same version as your pfsense.
I had this same problem. The issue is with some of the internet providers. For some reason the routing to the repository is bad. If you try to do a tracert from you wan you will see it drop in brazil. The only solution I had was that I have a backup wan and was able to access it from there. Comcast is my primary connection and I have tried it from various locations that I have and none of them work. My backup T1 is able to access the repository.
Here is a copy of a trace
8 10 ms 10 ms 10 ms 64.208.27.97
9 155 ms 155 ms 155 ms 67.17.196.194
10 152 ms 154 ms 156 ms gvt-te-0-3-2-0-rt02.spo.gvt.net.br [189.59.249.3
4]
11 174 ms 174 ms 174 ms locaweb.static.gvt.net.br [177.135.153.234]
12 174 ms 173 ms 171 ms 186.202.44.22
13 175 ms 181 ms 174 ms 187.45.237.17
14 174 ms 175 ms 175 ms dist-ita06-01.br-ip.net [186.202.47.1]
15 * * * Request timed out.
16 * * * Request timed out. -
Marcelloc… this "web upload is banned" issue has resurfaced again with the latest package.
-
Marcelloc… this "web upload is banned" issue has resurfaced again with the latest package.
You still need to fetch the fix from my repo.
-
Darn..
Do I need to run the same command?amd64
fetch -o /usr/local/sbin/dansguardian "http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian" -
Darn..
Do I need to run the same command?Yes. Until a push a fix to freebsd ports, package maintainer commits it and Jimp compile it to pfsense.
-
getting this error after the fetch
php: /pkg_edit.php: The command '/usr/local/etc/rc.d/dansguardian.sh start' returned exit code '1', the output was 'kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting dansguardian. /usr/local/sbin/dansguardian: 1: Syntax error: ")" unexpected /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian'
-
Can you check if the downloaded file is not corrupt, with dansguardian -v?
-
I tried the fetch multiple times. Same result.
-
what you get with dansguardian -v
-
"Every time you reinstall the package, you need to manual update the binary too."
Thats quite the little bug. Thats the sort of thing I might put on the main menu at the top in big bold red blinky letters so that everyone sees it first thing, along with a handy link to a set of simple instructions.
-
dansguardian -v
/usr/local/sbin/dansguardian: Exec format error. Binary file not executable.This is the process I followed.
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian -
marcelloc .. any update on this?
-
What update? You are trying to run amd64 file on i386?
-
What update? You are trying to run amd64 file on i386?
Please don't make this thread longer than it needs to. Why the hell will I be trying to run amd64 on i386? Please read from the first page before commenting something which makes no sense.
-
Please don't make this thread longer than it needs to. Why the hell will I be trying to run amd64 on i386? Please read from the first page before commenting something which makes no sense.
Pardon my ignorance, but "/usr/local/sbin/dansguardian: Exec format error. Binary file not executable." suggests exactly what I said… Otherwise, provide some info, such as
file /usr/local/sbin/dansguardian ls -la /usr/local/sbin/dansguardian uname -a -
file /usr/local/sbin/dansguardian
/usr/local/sbin/dansguardian: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.3, not strippedls -la /usr/local/sbin/dansguardian
-r-xr-xr-x 1 root wheel 994216 Feb 7 23:07 /usr/local/sbin/dansguardian -
You omitted the
uname -aintentionally? -
root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
-
root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
You'd probably have more luck with running that on 2.1 for which it's been apparently compiled…
/usr/local/sbin/dansguardian: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.3, not stripped
-
I wish I could.. but clamd does not work on 2.1. Have tried many times and need content scanning on browsing.
Almost everything I need works great on 2.1 .. but only dansguardian clamd fails to work.
Anyways, I rebuilt the box again late last week.. looks like the download worked this time. Will have to stay on 2.0.3 till marcelloc works on the dansguardian package to run along with clamd function.
-
It's been 10 months since the last activity on this thread. Just checking that:
1. This is still the correct procedure, on 2.1.2 with the current Dansguardian, to fix the banned uploads?
2. The huge difference in the size of the replacement binary (971K) vs the original one (11.1K) is of no concern?
(actually, I replaced the file in /usr/pbi/dansguardian-amd64/.sbin)
[just noticed, this is my first post, though I've been a member here a long time]
