Dansguardian package for 2.0
-
I made the changes to include 'bypasskey' and 'accessdeniedaddress' on the groups page.
Push these changes via github https://github.com/bsdperimeter/pfsense-packages/tree/master/config/dansguardian.
This way I can check changes and commit to the code.
OK…done.
BTW. I was looking at the main "report and log" page (dansguardian_log.xml). The way it really should work is if you pick reporting level 3, then it enables the editing of the html template in the text box. Otherwise, it should enable a field for entering the accessdeniedaddress... I was digging through the package directory and saw how to enable fields from a checkbox, but couldn't figure out how to enable/disable multiple fields based on the value selected from a list... Sorry for my ignorance.
-
OK…done.
I'm seeing only one push on github.
https://github.com/rjcrowder/pfsense-packages/commit/aa9fbaf910c0e1a3465826f9f5483646ab6b819e
What happen if user do not select any custom error page? Your code force this option on dansguardianfx.conf.template
accessdeniedaddress = '{$dansguardian_groups['accessdeniedaddress']}'
-
OK…done.
I'm seeing only one push on github.
https://github.com/rjcrowder/pfsense-packages/commit/aa9fbaf910c0e1a3465826f9f5483646ab6b819e
What happen if user do not select any custom error page? Your code force this option on dansguardianfx.conf.template
accessdeniedaddress = '{$dansguardian_groups['accessdeniedaddress']}'
K… I'll try to figure out what I did wrong on pushing to github - first time I've used it.
As far as the accessdeniedaddress, it should be fine to not specify a URL as long as the reportinglevel is 3. That's why I also "uncommented" the reportinglevel field in dansguardianfx.conf.template.
Like I said on the main page, the UI should only allow you to specify the template content if you choose level 3. Since the template file is global, there is no need to put it on the group page. However, the accessdeniedaddress field should be disabled on the group page if you pick reportinglevel 3 - since it would be ignored anyway.
-
OK…done.
I'm seeing only one push on github.
https://github.com/rjcrowder/pfsense-packages/commit/aa9fbaf910c0e1a3465826f9f5483646ab6b819e
What happen if user do not select any custom error page? Your code force this option on dansguardianfx.conf.template
accessdeniedaddress = '{$dansguardian_groups['accessdeniedaddress']}'
I'll figure out what I did wrong… but all the changes are out there under different patches...
-
Hi all,
Just published version 1.5.3 with per user reporting level, accessdenied url and passkey.
rjcrowder,
I did not found your chages except that I've posted. Take a look if my changes works like yours.att,
Marcello Coutinho -
That's exactly it. Thanks.
The only thing I did different was that I made the accessdeniedaddress field a "text area" (75 wide, 1 row) so that you could enter a long string and it would scroll…
Thanks a ton!
-
Can you test if startup issue is fixed too?
-
Can you test if startup issue is fixed too?
I have had no problem at all on the last two releases (since you made Squid3 start first and DG last)… of course that's working out of a VM. I will let you know if I get a chance to reinstall physical.
-
(since you made Squid3 start first and DG last)…
I didn't…
Maybe a install package order made this.
With this latest patch, Dansguardian startup time now is around 3 seconds :)
-
any news on ssl filtering?
-
-
(since you made Squid3 start first and DG last)…
I didn't…
Maybe a install package order made this.
With this latest patch, Dansguardian startup time now is around 3 seconds :)
Installing squid3 and latest dans package appears to have resolved my startup issues on my physical box. Thanks!
-
(since you made Squid3 start first and DG last)…
I didn't…
Maybe a install package order made this.
With this latest patch, Dansguardian startup time now is around 3 seconds :)
Interesting… Glad it works. However, I'm slightly concerned that it may break in the future if there is not a way to explicitly control startup order... Guess I'll have to wait and see.
-
Interesting… Glad it works. However, I'm slightly concerned that it may break in the future if there is not a way to explicitly control startup order... Guess I'll have to wait and see.
I'm quite sure it will not break as all my working dansguardians has squid started after.
Dansguardian does not crash or exit on the first squid test.
-
Interesting… Glad it works. However, I'm slightly concerned that it may break in the future if there is not a way to explicitly control startup order... Guess I'll have to wait and see.
I'm quite sure it will not break as all my working dansguardians has squid started after.
Dansguardian does not crash or exit on the first squid test.
Reinstalled physical tonight… no problem. Thanks for all the great work on this package!
-
Is there any way I could get "captive portal" style authentication with dansguardian either through the built-in pfsense captive portal or something else? Basically I'm looking for forms based authentication.
-
The content scanner timeout should read 60 seconds on the DansGuardian config page. Instead the field changes to the icapserver settings. The error I received was that Dans Guardian could not understand the config file.
-
The startup problem is solved for me. Dans Guardian now starts on reboot. Thanks.
-
Is there a doc that explains step by step how to configure Dansguardian? I am looking to replace SquidGuard (which works fine) with Dansguardian.
I have Snort, HAVP, Squid (null config) and SquidGuard installed. -
Is there a doc that explains step by step how to configure Dansguardian? I am looking to replace SquidGuard (which works fine) with Dansguardian.
I have Snort, HAVP, Squid (null config) and SquidGuard installed.Check out this thread http://forum.pfsense.org/index.php/topic,47856.0.html
