Dansguardian package for 2.0
-
Also, haven't been able to find anywhere that DG gives an error message as to why it won't start. Let me know if you have any idea where I should look.
Can you check boot process just like I've posted?
-
Also, haven't been able to find anywhere that DG gives an error message as to why it won't start. Let me know if you have any idea where I should look.
Can you check boot process just like I've posted?
I couldn't figure out how you got VirtualBox bigger - so I couldn't take a screenshot showing everything… However, the boot looks the exact same as the one you posted with the exception of dansguardian not running... in other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
-
I couldn't figure out how you got VirtualBox bigger
printscreens and paint/gimp ;)
In other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
I'm checking dansguardian boot process. I've fixed clamav startup error when enabled on dansguardian but I'll do more tests before publishing and I still have no idea why some systems are getting issues on boot and other don't.
-
I couldn't figure out how you got VirtualBox bigger
printscreens and paint/gimp ;)
In other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
I'm checking dansguardian boot process. I've fixed clamav startup error when enabled on dansguardian but I'll do more tests before publishing and I still have no idea why some systems are getting issues on boot and other don't.
So… can't explain it, but DG seems to be starting up fine in the new virtual that I built. This is the first time I've seen it startup without needing to be restarted post-boot. All of that said, I do think that DG should start after squid and suspect that doing so would solve problems that people are having.
I was also wondering if you have given any thought to changing how the GUI handles the "denied" page? The thing that is stopping me from fully switching to PFsense is the fact that the GUI doesn't properly support using an access denied URL and both the GUI and the bootup process insist on overwriting my manual DG bypass changes (see this threadhttp://forum.pfsense.org/index.php/topic,47856.30.html. Obviously I can create a script to restore my changes, but that's a pretty inconvenient hack…
Just wondering... thanks!
-
So I did a little more playing around so that I could be specific about what is necessary to make the bypass feature work correctly (without any overwrite issues)…
1. In the "Report and Log" page...
- Add the ability to specify the "accessdeniedaddress" value instead of just the HTML form content2. In the "Groups" page...
- Add the ability to specify the "accessdeniedaddress"
- Add the ability to specify the "bypasskey"That would basically do it...
-
I've just pushed some fixes do improve dansguardian boot process and checks.
On my tests, dansguardian startup time during boot process reduced to 20 seconds.
Wait 15 minutes, reinstall the package, apply config and reboot.
-
I've just pushed some fixes do improve dansguardian boot process and checks.
On my tests, dansguardian startup time during boot process reduced to 20 seconds.
Wait 15 minutes, reinstall the package, apply config and reboot.
Thanks for the updates… BTW. I made the changes to include 'bypasskey' and 'accessdeniedaddress' on the groups page. Turns out this was all I had to do in order to make my changes work (since the settings in dansguardianf1.conf override those that are set in dansguardian.conf). It was a pretty simple change, but you can drop me an email at randyj.crowder@gmail.com if you want me to send you the three files I had to touch - they were dansguardian_groups.xml, dansguardian.conf.template, dansguardian.inc (in /usr/local/pkg).
-
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.
-
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!
