Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Problem with web uploads in new dansguardian 2.12.0.3

    Scheduled Pinned Locked Moved Cache/Proxy
    69 Posts 26 Posters 32.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cnd.fflv
      last edited by

      Till last week (I did fresh installation on Jan 20th) it had the same problem - issue was not fixed so far… :(

      1 Reply Last reply Reply Quote 0
      • D
        dvosburg
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • T
          timthetortoise
          last edited by

          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).

          1 Reply Last reply Reply Quote 0
          • C
            cnd.fflv
            last edited by

            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…

            1 Reply Last reply Reply Quote 0
            • C
              cirkit
              last edited by

              @marcelloc:

              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.tbz

              i386
              http://e-sac.siteseguro.ws/packages/8/All/dansguardian-2.12.0.3_1.tbz

              Do 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

              1 Reply Last reply Reply Quote 0
              • R
                rjcrowder
                last edited by

                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...

                1 Reply Last reply Reply Quote 0
                • C
                  cirkit
                  last edited by

                  Yes after the changes the script worked to start / stop /restart dansguardian.
                  Couple of issues still remain unresolved i.e

                  1. During startup the package complains about missing exceptionviruslist files in /usr/pbi/dansguardian-amd64/etc/dansguardian/lists
                  2. Its also complains about missing clamd.conf file
                  3. Webupload banned

                  Pl help
                  cirkit

                  1 Reply Last reply Reply Quote 0
                  • R
                    rjcrowder
                    last edited by

                    @cirkit:

                    1. During startup the package complains about missing exceptionviruslist files in /usr/pbi/dansguardian-amd64/etc/dansguardian/lists
                    2. 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.

                    @cirkit:

                    1. 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!!!

                    1 Reply Last reply Reply Quote 0
                    • C
                      cnd.fflv
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @rjcrowder:

                        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…  ::)

                        1 Reply Last reply Reply Quote 0
                        • R
                          rjcrowder
                          last edited by

                          Wow! That's incredibly inconvenient. Why was that change made?

                          1 Reply Last reply Reply Quote 0
                          • D
                            doktornotor Banned
                            last edited by

                            @rjcrowder:

                            Why was that change made?

                            You can ask at the relevant thread, already shared my thoughts there.  >:(

                            1 Reply Last reply Reply Quote 0
                            • C
                              cnd.fflv
                              last edited by

                              Hi there.

                              Any updates on these issues?

                              1 Reply Last reply Reply Quote 0
                              • M
                                mbrossar
                                last edited by

                                @dvosburg:

                                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

                                Had 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!

                                1 Reply Last reply Reply Quote 0
                                • P
                                  Pinnacle
                                  last edited by

                                  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

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    edosselio
                                    last edited by

                                    Got the same issue. For me, mschiek01's instructions at https://forum.pfsense.org/index.php?topic=75243.0 solved the issue. :D

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bmbeverst
                                      last edited by

                                      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.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Samuel_R
                                        last edited by

                                        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

                                        As 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)

                                        1 Reply Last reply Reply Quote 0
                                        • I
                                          ismaelnoble
                                          last edited by

                                          @Samuel_R:

                                          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

                                          As 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

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            TheLimey
                                            last edited by

                                            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. =(

                                            Everything is easy when you know how, …and have the right tools, ...and the time, ...and money.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.