E2guardian package for pfsense - $??
-
Ok - I think I've figured out everything except how to add links to service and status->services.
Backup xml file and check menu section
<menu> <name>E2guradian</name> <tooltiptext>E2guradian</tooltiptext> Services <configfile>e2guardian.xml</configfile> </menu>
and service section
<service><name>e2guardian</name> <rcfile>e2guardian.sh</rcfile> <executable>e2guardian</executable></service>
you can add it via console direct on config.xml (if you really know how to edit it ) or restore a backup with modified xml file.
-
Ok - I think I've figured out everything except how to add links to service and status->services.
Backup xml file and check menu section
<menu> <name>E2guradian</name> <tooltiptext>E2guradian</tooltiptext> Services <configfile>e2guardian.xml</configfile> </menu>
and service section
<service><name>e2guardian</name> <rcfile>e2guardian.sh</rcfile> <executable>e2guardian</executable></service>
you can add it via console direct on config.xml (if you really know how to edit it ) or restore a backup with modified xml file.
I'd be willing to test this out - but my one concern is when the official e2guardian package eventually comes out will this mess that up? i.e. - will it cause a conflict that causes me to have to restore my system and thus undo all my work or will the system merely see that I have e2guardian already installed and then when future updates are applied allow me to update seamlessly?
-
I'd be willing to test this out - but my one concern is when the official e2guardian package eventually comes out will this mess that up?
Except for the freebsd package installed via pkg install, file download and xml changes will not mess your install.
If you prefer, you can try it on a vm and forward connectionts from your box to your vm
Another option is to install it on your backup box if exists.
you can unistall freebsd packages too via console before installing the pbi.
IMHO, pbi is messing up almost all packages I use on 2.2, so I'm doing on my installs a pbi remove and pkg install.
-
IMHO, pbi is messing up almost all packages I use on 2.2, so I'm doing on my installs a pbi remove and pkg install.
Cannot wait for 2.3; indeed extremely hard to find some more crappy packaging format, PBI is virtually unique. ::) >:(
-
Excellent news all round! :D
So we're currently just waiting for Renato to get back from holiday (vacation), at which time he'll be reviewing the code. Hopefully that doesn't take very long! I have no idea how much code needs to be reviewed, or how thorough that testing is, but hopefully it's not a major task.
Thanks for your findings knes1, please do update if you work out more. Maybe a new thread, with a link here.
@_jwsmiths_, I share your concern! With the e2guardian package so close, I'm wondering if it's better to wait. …but Marcello's comments about the packages not working reliably is also concerning. If I get time I'll create a pfSense VM for testing the manual install, as he (Marcello) suggests.
I'm glad we know where we are now, and that we just have one more task to complete (unless Renato finds any issues :-X). Thanks to everyone for all your input, and please keep us updated here if you discover anything relevant. :D
-
Thanks for your findings knes1, please do update if you work out more. Maybe a new thread, with a link here.
As promised, here's the guide (I wrote a blog post about it):
http://knes1.github.io/blog/2015/2015-07-18-manually-installing-e2guardian-to-pfsense.html
Let me know if you think it would be better to open up a separate thread about this (for discussing etc…).
Again, thanks to Marcello and others who made this possible :)
-
Please feedback package tests, it may speed up merge process.
-
ill try it out later this week on my test system…provided work doesnt have other plans for me.
-
Please feedback package tests, it may speed up merge process.
Here's my feedback:
- Daemon tab doesn't appear on first load, you have to click on it second time to appear
- Sometimes (happend to me on 2 out of 4 installs) when loading shalla list, some entries from the default site and url list (adv category) stays in the config file, which prevents e2guardian to start. When attempting to start e2guardian manually I received the following error:
Error reading file /usr/local/etc/e2guardian/lists/blacklists/ads/urls: No such file or directory Error reading file /usr/local/etc/e2guardian/lists/blacklists/ads/urls: No such file or directory Error opening file: /usr/local/etc/e2guardian/lists/blacklists/ads/urls Error opening bannedurllist Error opening filter group config: /usr/local/etc/e2guardian/e2guardianf1.conf Error reading filter group conf file(s). Error parsing the e2guardian.conf file or other e2guardian configuration files
This can be resolved by commenting out offending adv list in ACL configuration for sites and urls.
- When attempting to install e2guardian on production system where I had defunct dansguardian installed (and removed, both through package manager and by deleting files) e2guardian wouldn't start and when I attempted to start it from console I received the following message:
Starting e2guardian. Error binding ipc server file (try using the SysV to stop e2guardian then try starting it again or doing an 'rm /tmp/.dguardianipc'). Exiting with error
I resolved this by deleting the following 2 files:
/tmp/.dguardianipc /tmp/.dguardianurlipc
E2guardian is now running successfully on one production SG2440 in a small network with cca 10 devices. I will update this if I encounter any problems.
-
Well afraid most of the above is causes by the (incomplete) "DIY" install process.
-
the /usr/local/etc messages may be related to pbi vs pkg isntall
the /tmp/.dguardianipc errors are related to previous dansguardians install and tmp files it creates.
-
What can I do to help get this into the repo? Testing?
-
Testing it out now on my production home system. So far no major problems. Will update this post later.
-
I see period "Exited with status 11" messages in system logs. No obvious malfunction while browsing internet though.
-
I am so very excited about this going into the repo that I am checking the web page every few hours.
I appreciate the work from those who have contributed.
-
I was hoping Renato would post here with an ETA. As I mentioned before, I PM'd him (before I knew he was on holiday), with a link to this thread, but I have seen no post here, and received no reply by PM either. He's either ignoring me (us), or not checking his messages. :'(
Based on the fact he is checking code for pfSense, I'm going to assume he is a pfSense staff member. If that is the case then I'm very disappointed at the lack of updates the company is providing their customers.
Does anyone have any direct contact with him? It would quite excellent if we could get an ETA posted here. :)
-
Better ask for a comunity repo IMHO.
-
FYI - installing 2.2.4 borked my entire internet access. E2Guardian won't start (linked file missing) but even when I disable it and turn off the NAT rule that should be forwarding all traffic to E2Guardian I am unable to make http connections out (https still works). May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
-
May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
Yes. After any firmware upgrade, you need to check freebsd packages you've installed. Sometimes will be a dependence some times just the pkg itself.
-
FYI - installing 2.2.4 borked my entire internet access. E2Guardian won't start (linked file missing) but even when I disable it and turn off the NAT rule that should be forwarding all traffic to E2Guardian I am unable to make http connections out (https still works). May need to un-install E2guardian and then upgrade and then re-install it to make sure it works.
Ok, I've tried the following upgrade procedure in a VM: Firstly, I've uninstalled e2guardian using pkg, then upgraded pfSense to 2.2.4, and then reinstalled e2guardian freeBSD packages. This seems to work (I haven't tested it fully yet though).
Here are the steps:- Before the upgrade:
pkg delete e2guardian pkg delete pcre
-
Upgrade pfSense to 2.2.4
-
Reinstall e2guardian packages
pkg install e2guardian
- Go to e2guardian config and save a page (this is to reapply configs)
I believe this might work even if you applied the upgrade without deinstalling e2guardian first (e.g. do steps 1,3 and 4 after the upgrade). However, I haven't tried it.