Dansguardian package for 2.0
-
Same here. I thought it was ready for 2.1 - running PfSense 2.1 64 Beta, Squid 3 in transparent mode and Squidguard - no other packages.
-
Same here.
I've pushed a fix right now with no version change. wait 15 minutes and reinstall the package.
-
Installs fine now..
For some reason it takes a while before filtering kicks in.
Some issues. Banned sites/urls are not getting filtered. Reboot hasnt helped.
Also how do I fix this.. cant find categories anywhere
Web upload is banned.
Categories:
Web upload
-
Wish I could help but I am only starting to experiment with this.
Have you added a blacklist such as Shalla?
Once you add and download it will show the various categories you want to ban.
-
Did you configured and applied a blacklist?
-
Yes Shalla is what I use.
It used to be straight forward. I see the lists after download and I have selected those. But filtering still fails to works
Service restart now gives this error..
Jan 29 22:35:56 dansguardian[55285]: Error connecting via ipc to url cache: No such file or directory
Jan 29 22:35:56 dansguardian[55285]: Error connecting via ipc to url cache: No such file or directory
Jan 29 22:30:17 root: /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian
Jan 29 22:30:17 dansguardian[80665]: Exiting with error
Jan 29 22:30:17 dansguardian[80665]: Error binding server socket (is something else running on the filter port and ip?
Jan 29 22:30:17 dansguardian[80665]: Error binding socket: [8080 10.0.1.1 0] (Address already in use) -
Seems other daemon is running on the same port.
Try to stop service and then save config.
Can you check what else is running on 8080? -
Tried a clean install. Dont get the port 8080 clash but filtering still doesn't work.
Kinda beats the purpose as bad sites are not filtered.. actually the categories are not going into effect.
Can you re-check and see if the rules are being committed after a save?
-
Can you re-check and see if the rules are being committed after a save?
what auth plugins did you selected?
what you have on dansguardian logs?
My acls are working fine here. I've removed and re included some sites and it reflected on config files.
I'm also seeing log files registering users and groups as well.
-
Something I've noticed is that multiple plugins selected have different behavior depending on how dansguardian is configured (dansguardian-> squid or squid-> dansguardian->squid).
Try to select only one plugin before including others.
-
Tried selecting each of them. I can only select one as I have multiple interfaces.
Thinking of going back to SquidGuard as this is turning out to be a headache.
Was wondering if the older version of Dansguardian be resurrected with the pcre fix.
-
Was wondering if the older version of Dansguardian be resurrected with the pcre fix.
I'ts basically the same gui version. Most work was on pfsense 2.1 dir checks. Pcre and other fixes were done on freebsd ports.
What you have on dansguardian log files?
Did you tried to listen it on only one interface and then nat it to other?
-
whats the path for the log files?
I know the service is running and I get that Web Upload banned page.. so I know its working to some degree. Also some pics (not all) are being blocked on porn sites.. so that is kinda working to some degree as well.
It's working on very few little things that might go unnoticed. Site/URL blocking, weighted phrases..etc is not working. After 3 clean installs and configuration I can confirm this.
-
Log file is /var/log/dansguardian/access.log
Choose dansguarian report type to see more detailed log.
-
Checked the logs. As reported earlier.. logs are all filled with .jpg being blocked from bad sites. No bad sites being blocked.
-
Checked the logs. As reported earlier.. logs are all filled with .jpg being blocked from bad sites. No bad sites being blocked.
I have bad sites blocked in my log files, filter group identification, users as well and exception sites too.
How can I help you????
-
Darn. Dunno what to do. Never faced this issue before.
Are you on a 2.1 amd64 snapshot? How did u install Dans? All I did was install squid3 .. configure all the interfaces for squid (as each interface services a separate subnet) and then install dans and select the usual options that worked on first try.. always.
One thing which I have done differently is I have Squid3 rather than the Squid2. Could that be the issue? Will try to do a clean install again and use Squid2 instead and see if that helps.
BTW, any major difference between Squid 2 & 3 versions?
EDIT:
Confirmed extensions being blocked as well. So there is a definite issue (at least in my cofiguration) that is not blocking bad sites and URLS. -
So, I had a backup config of 2.0 saved which had working settings for Squid2 and Dans. I applied that to a clean new install of 2.1. Upon reboot Dans worked but the response to bad sites was like 5 to 8 secs. So I knew its working on the Phrase weight. I checked in Dans and found no change in what I was doing earlier. But to test I clicked save and boom it killed dans again with the exact same behavior.
For now I am moving back to SquidGuard as I need IPv6 for some RND and Dans is taking too much of my time. Will check on this package in a few months.
Adios!
-
as I need IPv6 for some RND
Dansguardian 2.12 does not have ivp6 support yet.
I have no idea how to reproduce your config, all I can tell is that my config is still running.
BTW, I'll keep doing testes to see if I find/reproduce same limitations/issues you found. -
What I have noticed is that for Sites and URLs .. the "DEFAULT" config does not stick to the "Group" (there is only one group in the list). In the categories list I selected specific categories to ban ..for example costtraps, porn..etc. The selection list is there but the moment you click save it does not apply the settings to the "Group". File extensions download ban works and even Pics ban are working.
You might wanna check and compare the code from the previous working dans version for Site and URL and more importantly the directory paths for the categories list downloaded that need to be applied on the Site and URL tabs.
