Dansguardian 2.12.0.3_2 does not work

abbey

OK… so both clam and dans appear to be running. Is squid running? Is DG configured and listening on a port and talking to squid on the port that squid is listening on? What happens when you set dansguardian as your proxy and try to browse a page? What if you set squid as the proxy and try to browse?

Also - what do you mean when you say that the content scanner is "off".

Ok, i reinstalled the package and followed the steps in your other thread (linked earlier). Changed Dan to listen on LAN, proxy on loopback. It could have been my settings, since I frantically messed with various settings to get DG working. Now everything works great!!

I was under the impression that under General->Content Scanner->Clamdscan (on) would show once enabled. Now i see that it shows the default value even when calmav is running.

I greatly appreciate your efforts. Thanks

marcelloc

Hi guys,

There is no updates on dasguardian code for more then one year, a lot of patches were submitted but none merged.

Every manual patch I have applied to dansguardian source code are not commited/applied on freebsd port too, so it's hard to have it compiled my core team.

Fredb has pushed a lot of uncommited fixes that he forked the project to have it applied.
https://forum.pfsense.org/index.php?topic=61811.msg376192#msg376192

Full changelog from current dansguardian official code to e2guardian
https://raw.githubusercontent.com/e2guardian/e2guardian/master/e2guardian.release

rjcrowder

Marcello… I don't know if you've been watching the forums or not, but something definitely got broken in the 2.12.0.3_2 version of the package. There is something wrong with the content scanner stuff - multiple executables and configuration files are missing. Also, the blacklist download site is not being set.

At any rate... the workaround seems to be installing the 2.12.0.3 version from your repository...

marcelloc

@rjcrowder:

something definitely got broken in the 2.12.0.3_2 version of the package.

That's the official version from ports compiled by core team, the code doesn't have some patches

@rjcrowder:

At any rate… the workaround seems to be installing the 2.12.0.3 version from your repository...

I'm trying to port e2guardian to freebsd and then pfsense. As I said, dansguardian is no longer being updated by maintainers on sourceforge.
Many commits are pending.

AFAIK, e2guardian will not have use restrictions as dasnguardian has.
The gui will be almost the same, just the package name will change. If core team aproves, it will be applied to pfsense 2.1

rjcrowder

@marcelloc:

@rjcrowder:

something definitely got broken in the 2.12.0.3_2 version of the package.

That's the official version from ports compiled by core team, the code doesn't have some patches

@rjcrowder:

At any rate… the workaround seems to be installing the 2.12.0.3 version from your repository...

I'm trying to port e2guardian to freebsd and then pfsense. As I said, dansguardian is no longer being updated by maintainers on sourceforge.
Many commits are pending.

AFAIK, e2guardian will not have use restrictions as dasnguardian has.
The gui will be almost the same, just the package name will change. If core team aproves, it will be applied to pfsense 2.1

Very nice… I'll look forward to that... Thanks again Marcello