Installing the Dansguardian package in PFSense - One user's experience

Couple of issues that some people may have. By the way this is a great easy to follow Dans setup, thanks!

#1 When I installed squid my Proxy interface in squid was at "loopback", I changed that to LAN an things are fine now.
#2 Just a note if you use the firewall to redirect port 80 to 8080. Make sure that your firewall rule that was created by the portforward, is located above your "LAN-any" rule so that it gets executed properly.

I did get the Dansguardian to work if I manually set the proxy, but I've added the rules to FW without any luck.
I've put the rule
Proto: TCP
Source: LAN net
Port: *
Destination: 192.168.1.1
Port: 8080
above the lan-any rule, so it should work but it does not?
How to solve?
I can provide screenshots if asked.

I'm going to make a suggestion Chris but I've not tried this solution, it's speculative, so feel free to shoot me down if I missed something.

Firewall>Schedule is possibly what you're looking for to solve the problem. If you only want content filtering between 9 - 5 then apply the schedule to the redirect rule such that DG and Squid are bypassed outside of the access hours. If you don't want any access at all outside of those hours then you can construct a rule that blocks certain IP and is only activate outside of those hours.

Update - I don't seem to be able to edit the original post which I can see makes some sense for integrity reasons so I'll add some updates here (these aren't necessarily requests for change just observations for fellow travellers).

Refreshing Dansguardian when changes have been made seems to be a bit hit or miss. The only entirely reliable method I've found is that suggested by Zgruk from the command line issue "dansguardian -Q". The "save" buttons work sometimes but not others which I suspect is entirely to do with DG and not the packaging.

Rebooting the PFsense box caused me some odd problems. DG started before Squid and doesn't seem to keep trying to establish a socket with Squid, hence, any requests to DG fell into a black hole including the access to PFsense to fix the problem. Because of my (insecure) set up I could manually direct the browser at Squid to access PFsense, refresh DG using a simple save and that seemed to establish the socket between DG and Squid giving me back normal access.

If you're not as insecure as me (and I don't recommend it for any professional set up) then the way to get back access would be to use the command line refresh I mentioned above.

There may be a way to force squid to come up before DG I'm not sure. I'm more of a Linux man than BSD and despite their shared heritage they're different enough for me to have to research that change. If there's anyone out there who can supply the answer I'd be really grateful.

Checked the thread and this appears to be the same problem as reported by Cino :

I think the problem I have, dansguardian is starting before squid.

We've had a long weekend in the UK so I did some checking into how the start up tasks are set in BSD. Forgive me if I'm telling you things you already know but it seems BSD uses directives (e.g #PROVIDES) within the start up jobs to create a dependency order. The directives show what a daemon provides and requires, which in turn are used by rcorder to order the job starts.

Marcello uses the directives in the Dansguardian start up job but squid doesn't use them which results in a random start order at best. The way to fix this would be to use the native BSD system consistently but it seems that historically this hasn't been done. I can imagine a work around which alters the "squid.inc" file to copy a template start up script in the same way that Marcello does it and in this squid template include the standard directives hence dictating the start up sequence.

The other idea I had was to check for squid.sh in /usr/local/etc/rc.d and if it exists start it in the Dansguardian script. Something like this before the code to start DG:

Curious to me that it worked for you… I had the same problem - DG wasn't working because it started before Squid. I couldn't figure out how the package manager controlled the order of startup scripts, so I did a little hack. I simply created another startup script called z_fixstartup.sh and placed it in /usr/local/etc/rc.d. Contents of the script is...

#!/bin/sh

This file was automatically generated

by the pfSense service handler.

I had another small issue that someone else might want to be aware of. If you create a NAT rule to autoforward port 80 traffic, this somehow breaks XBox downloads. I had to exclude the IP address of the XBox in the forwarding rule.

RJ - Nice fix I'm going to try that one. What I still don't understand though is, as you say, how does the package manager control the start up order ? Is there no consideration to the order designed in to the mechanism ?

Marcello - I don't get it and I'm wonder if it's somehow random ? Does DG sometimes start after Squid or does it sometimes retry the connection, I have no idea, but it's very frustrating particularly when we can't reliably recreate the problem. Your comment about the time taken makes me wonder if I wait longer would the connection between DG and Squid eventually start ?

I don't get it and I'm wonder if it's somehow random ? Does DG sometimes start after Squid or does it sometimes retry the connection, I have no idea, but it's very frustrating particularly when we can't reliably recreate the problem. Your comment about the time taken makes me wonder if I wait longer would the connection between DG and Squid eventually start ?

If you check boot-up process, you will see dansguardian taking about a minute to startup. Did you tried to wait boot process finish before trying to connect to dansguardian?

I'll move the startup script somewhere else and try it again… but I'm fairly certain that it was never coming up - or at least not consistently.

This one might be a little off topic, but let me throw out another "feature" idea from something that I originally had working on my IPCop box. I had IPCop running with DG/Squid by using the copplus addon. In addition, found a script that got me started and then made some changes to implement a "Dansguardian Bypass" that would allow you to enter a password and bypass filtering for a time period. It's nice because sometimes DG is overly aggressive in filtering. I don't remember where I got the setup script, but on IPCop it was doing perl CGI to a web server on port 81. It also looks like someone did the same thing with PHP on ClearOS (see http://honestpchelp.com/2011/clearos-dansguardian-accessdenied-php-bypass-script/).

I'm going to play around trying to get it to work on PFSense. However, the forum instructions I found for setting up a web server required installing a couple packages and mysql (see http://forum.pfsense.org/index.php/topic,47086.msg247364.html#msg247364)… it just seemed a little excessive to me since there's already a web server running for the web interface. Is there an easy way to get a web server instance that supports perl CGI or PHP on another port? Or... better yet, has anyone already implemented the bypass feature?

This one might be a little off topic, but let me throw out another "feature" idea from something that I originally had working on my IPCop box. I had IPCop running with DG/Squid by using the copplus addon. In addition, found a script that got me started and then made some changes to implement a "Dansguardian Bypass" that would allow you to enter a password and bypass filtering for a time period. It's nice because sometimes DG is overly aggressive in filtering. I don't remember where I got the setup script, but on IPCop it was doing perl CGI to a web server on port 81. It also looks like someone did the same thing with PHP on ClearOS (see http://honestpchelp.com/2011/clearos-dansguardian-accessdenied-php-bypass-script/).

It's a dansguardian feature, but I did not included on gui. check dansguardian.conf to see the secret.

I'm going to play around trying to get it to work on PFSense. However, the forum instructions I found for setting up a web server required installing a couple packages and mysql (see http://forum.pfsense.org/index.php/topic,47086.msg247364.html#msg247364)… it just seemed a little excessive to me since there's already a web server running for the web interface. Is there an easy way to get a web server instance that supports perl CGI or PHP on another port? Or... better yet, has anyone already implemented the bypass feature?

I'm in the same position having come from Smoothwall where I had this feature working. Exactly as you say, DG can be a little harsh at times so I simply implemented the "Bypass Button" which gave access for 10 minutes and then reset. Mine wasn't as sophisticated as a userid and password since my filtering is only to provide a warning almost, I'm not really trying to ban my daughters from anything on the net, I'm just trying to stop them accessing stuff accidentally that they probably don't want (and of course remove adverts and such).

But anyway, I'm rambling on, if you do get that feature working I'd be really interested in how you've done it for this implementation with PFsense.

2. Followed the instructions for setting up the override page from here http://honestpchelp.com/2011/clearos-dansguardian-accessdenied-php-bypass-script/.
This was pretty straight forward, I just had to change the directories to be appropriate to the light http web server. For example, I put the accessdenied.php file in the directory /usr/local/vhosts/vhost01.local/. Of course, I also had to change the URL's to be appropriate to my box and port. I put the password text file in /var/etc/.

On a related note… It did not work when I tried booting without the script to restart dansguardian at the end of the bootup. Without the script it appears that dansguardian starts up, squid starts after and then dansg eventually shuts down.

This one might be a little off topic, but let me throw out another "feature" idea from something that I originally had working on my IPCop box. I had IPCop running with DG/Squid by using the copplus addon. In addition, found a script that got me started and then made some changes to implement a "Dansguardian Bypass" that would allow you to enter a password and bypass filtering for a time period. It's nice because sometimes DG is overly aggressive in filtering. I don't remember where I got the setup script, but on IPCop it was doing perl CGI to a web server on port 81. It also looks like someone did the same thing with PHP on ClearOS (see http://honestpchelp.com/2011/clearos-dansguardian-accessdenied-php-bypass-script/).

It's a dansguardian feature, but I did not included on gui. check dansguardian.conf to see the secret.

I'm going to play around trying to get it to work on PFSense. However, the forum instructions I found for setting up a web server required installing a couple packages and mysql (see http://forum.pfsense.org/index.php/topic,47086.msg247364.html#msg247364)… it just seemed a little excessive to me since there's already a web server running for the web interface. Is there an easy way to get a web server instance that supports perl CGI or PHP on another port? Or... better yet, has anyone already implemented the bypass feature?

I'll test it this week.

It appears that there is no way to get the GUI to not overwrite my changes when the config is saved (for the access denied php page that I put in place)… Would it be possible to add an option to the GUI so that you can specify a URL for the access denied page rather than having the user supply the HTML page content?

Yes, it is there but RJCrowder is suggesting specifying a URL instead (or that's how I read it)

Would it be possible to add an option to the GUI so that you can specify a URL for the access denied page rather than having the user supply the HTML page content?

I'm merely asking to have both which could be achieved quite easily by allowing the reporting level and a redirect URL to be exposed through the GUI. Dansguardian will use the local HTML when the reporting level is 3 and the redirect URL when it is at levels 1 or 2.

Think I may have tracked down why Dans doesn't start properly on bootup (on my setup)
I get this error:
php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was '2012/04/25 10:17:58| WARNING: '192.168.0.0/255.255.255.0' is a subnetwork of '192.168.0.0/255.255.255.0' 2012/04/25 10:17:58| WARNING: because of this '192.168.0.0/255.255.255.0' is ignored to keep splay tree searching predictable 2012/04/25 10:17:58| WARNING: You should probably remove '192.168.0.0/255.255.255.0' from the ACL named 'localnet' squid: ERROR: No running copy'

On my squid setup I have chosen to select LAN + loopback, so that the children go through the 8080 dans proxy and my machine uses 3128 (for caching purposes)
Is it possible that this is causing the error and not allowing dans to start automatically.

Still starts when I go in and press start.
Or am I just completely barking up the wrong tree…. ::)
Thanks
Chris

Just another quick note on something that needs to be done… it appears that DG log rotation is not setup. You can enable the "logrotation" script in /usr/local/share/dansguardian/scripts/. To get it working, do the following.

1. Edit /usr/local/share/dansguardian/scripts/logrotation and change
LOG_DIR=/var/log/ to
LOG_DIR=/var/log/dansguardian
2. Make the file executable
chmod +x /usr/local/share/dansguardian/scripts/logrotation
3. Add it to your list of scheduled tasks in cron so that it executes once a week. To do so, I installed the "cron" package and added an entry as follows (executes at 2:30am on Saturday):
30 2 sat root /usr/local/share/dansguardian/scripts/logrotation

Firstly - Thanks Marcello that's excellent news. Can I just clarify that where you say "apply config and reboot" do you mean manually apply the config or restore from a saved xml config ? Would that work ? (Just saves me some time if it does).

Secondly and totally unconnected here's a strange one for Netflix users.

I recently re-installed my windows system onto a new SSD and subsequently my Netflix gave a Silverlight N8152 DRM error when starting. I tried every suggested fix I could find for what is apparently a fairly common error all to no avail. The solution I found that worked for me was to disable the Dansguardian redirect rule, start Netflix, watch a moment of some content then stop Netflix and re-enable the redirect rule for DG, no more DRM N8152 Silverlight problem…..

Firstly - Thanks Marcello that's excellent news. Can I just clarify that where you say "apply config and reboot" do you mean manually apply the config or restore from a saved xml config ? Would that work ? (Just saves me some time if it does).

Reinstall the package, go on dansguardian gui, manually apply the config. If you whant to test boot process, reboot after apply config.

The Problem:
If I set on the configuration page of Dansguardian (>Services>Dansguardian>Daemon) the Proxi-IP to 127.0.0.1 and leave the value for the Proxy-Port empty (for the default) in the config file of Dansguardian (/usr/local/etc/dansguardian/dansguardian.conf) the value 127.0.0.1 will be written for the proxy-port entry (proxyport = 127.0.0.1).

My Solution:
Manually set the value of the proxyport setting in /usr/local/etc/dansguardian/dansguardian.conf
(In the pfSense-webgui for example by browsing to the config-file via >Diagnostics>Edit File).

The Problem:
If I set on the configuration page of Dansguardian (>Services>Dansguardian>Daemon) the Proxi-IP to 127.0.0.1 and leave the value for the Proxy-Port empty (for the default) in the config file of Dansguardian (/usr/local/etc/dansguardian/dansguardian.conf) the value 127.0.0.1 will be written for the proxy-port entry (proxyport = 127.0.0.1).

My Solution:
Manually set the value of the proxyport setting in /usr/local/etc/dansguardian/dansguardian.conf