E2guardian package for pfsense - $??

marcelloc

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.

knes1

@jwsmiths:

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.

bfrost

Is anything happening with this?

doktornotor

@bfrost:

Is anything happening with this?

https://github.com/marcelloc/pfsense-packages/pull/2/files
https://github.com/marcelloc/pfsense-packages/pull/4/files

TheLimey

@bfrost:

Is anything happening with this?

I haven't seen any updates with regards to the pfSense e2guardian package, so I assume we are still just waiting for Renato (renatohtpc - https://forum.pfsense.org/index.php?action=profile;u=265729) to finish the code review.

He was apparently on holiday, and would be working on it when he got back, but that should have been over a week ago. I PM'd him a while back with a link to this thread with the hope he might let us know what is happening. I assume he either isn't checking his messages, or he doesn't want us to know what is happening. =(

Marcello suggests just installing the code, but I haven't had a chance to try that out. some others seem to have had some success though.

Mobile_Bob

Watching the pull request daily, it looks extremely close…

marcelloc

@Mobile_Bob:

Watching the pull request daily, it looks extremely close…

After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.

If you need the e2guardian package, I suggest testing the manual install.

Mobile_Bob

@marcelloc:

After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.

If you need the e2guardian package, I suggest testing the manual install.

I was hoping to be able to wait it out, but i'm going to have to go ahead and do the install manually. Thanks for all your hard work on this. I agree with you that we need a community package list, something that can be turned on for those that don't mind an unofficial list… I think it would help get new and fixed packages out faster. All the code in the pull requests that has just been abandoned because of (undocumented) code format requirements etc... It's sad... A lot of the packages seem very out of date.

doktornotor

@Mobile_Bob:

I think it would help get new and fixed packages out faster.

No panic. We are already cleaning up

:o :o :o ;D ;D ;D

Mobile_Bob

@doktornotor:

No panic. We are already cleaning up

:o :o :o ;D ;D ;D

I do appreciate the work you have been doing to clean up the packages! You have been committing clean up and fixes like crazy and I really do appreciate it! I will revoke my previous opinion only if the packages continue to be well maintained after this blitz :) . To me the packages are one of the greatest strengths of PFSense!

Mobile_Bob

@marcelloc:

@Mobile_Bob:

Watching the pull request daily, it looks extremely close…

After the gui code merge, it will still need a pbi build and on current release, pbi is messing up a lot of binaries with "missing" libs.

If you need the e2guardian package, I suggest testing the manual install.

I went ahead and installed manually. First off thank you Marcelloc for all your work on this and everyone else! Content filtering is such a HUGE option to have in my opinion. I did hit a couple of issues however… First the tabs, Users, and IPs, do not work. They both point to xml files but the only files that match are template files. I could see where the users template files (There are two) could be combined and be a working XML, but the IPs file is only half of the xml file. Second and it's not a break issue, the first tab doesn't load correctly until you click on it and have it reload. I can see that it's just how the original menu option loads the url is slightly off. Everything else seems to be working great and I was able to get it all up and running without much work! Love it!

Thanks again for all your hard work on this!!!!

doktornotor

@Mobile_Bob:

I do appreciate the work you have been doing to clean up the packages! You have been committing clean up and fixes like crazy and I really do appreciate it! I will revoke my previous opinion only if the packages continue to be well maintained after this blitz :) . To me the packages are one of the greatest strengths of PFSense!

Hopefully packages will be much more self-maintaining and uptodate with 2.3. The PBI packaging format was one of the worst disasters that could happen here. Hopefully, someone would also

provide documentation
provide some VM image with pre-built package server set up ready for testing

The current state with exactly ZERO documentation had led to all this shit, certainly NOT the way to go on!

P.S. Don't count on me maintaining ~100 of packages. I'm ~ half way done with the cleanup, considerably tired, disgusted by the shitty code and annoyed by the absence of any docs. Even the very little we had (a howto on setting up a custom package repo) has vanished.

:( >:( >:(

Mobile_Bob

@doktornotor:

@Mobile_Bob:

I do appreciate the work you have been doing to clean up the packages! You have been committing clean up and fixes like crazy and I really do appreciate it! I will revoke my previous opinion only if the packages continue to be well maintained after this blitz :) . To me the packages are one of the greatest strengths of PFSense!

Hopefully packages will be much more self-maintaining and uptodate with 2.3. The PBI packaging format was one of the worst disasters that could happen here. Hopefully, someone would also

provide documentation

provide some VM image with pre-built package server set up ready for testing

The current state with exactly ZERO documentation had led to all this shit, certainly NOT the way to go on!

P.S. Don't count on me maintaining ~100 of packages. I'm ~ half way done with the cleanup, considerably tired, disgusted by the shitty code and annoyed by the absence of any docs. Even the very little we had (a howto on setting up a custom package repo) has vanished.

:( >:( >:(

I definitely don't expect that any one person can keep up with all the packages. I hope they implement the things your suggesting and provide documentation on packages so that you won't ever have to clean the mess you are dealing with right now.

aGeekhere

Does E2guardian have "Use SafeSearch engine"?

pfSense2User

It's been a while since I used pfSense until my old setup died of capacitor failure for the memory. Currently, I have pfSense 2.2.4 i386 installed on another computer that I received from my grandpa a couple of months ago.

It's running on a Compaq Presario 6300us (6000 Series) Desktop with the following specs:

Intel Celeron (Pentium III/Pentium III Xeon) Socket 370 clocked at 1.4GHz (100MHz FSB Multiplier of 14)
512MB PC-133 SD-RAM (Max is 512MB unfortunately)
Intel i810 Chipset (reason the system has 512MB max memory)
Intel Integrated Graphics (up to 11MB Memory)
Syba SATA PCI Controller Card
Syba USB 2.0 PCI Card (might remove)
Intel Pro/1000GT Desktop Gigabit Ethernet PCI Card (WAN)
Integrated Realtek RTL8139 FastEthernet Adapter (LAN)
1.44MB Floppy Drive (as fellow YouTuber uxwbill would like to say: "All real computers have floppy drives")
Mitsumi 48x CD ROM
Lite-On DVD Burner
200W ATX PSU
60GB SATA Slim HDD (pulled from my old Xbox 360 that had a graphics card failure, copied all of my files from the drive to the new Xbox 360)
Vantec 2.5" Slim to 3.5" SATA HDD converter

pfSense 2.2.4 i386

I have done the manual installation of E2guardian, and I have to say it's more stable than the Dansguardian package, however, I am running into two issues: The first issue is the Daemon tab (not too serious), but clicking on the tab again brings the menu to its knees, and whenever I try to run the clamav in the General settings, the service stops, and starts back up after I disable the clamav since the one supplied in the Squid3 causes the internet to crash (page not found errors galore). Other than that, the package is in great progress. So far, so good.

Just have to add the blacklist, make new ACLs for me, and test to see what would happen.

Mobile_Bob

@Mobile_Bob:

I went ahead and installed manually. First off thank you Marcelloc for all your work on this and everyone else! Content filtering is such a HUGE option to have in my opinion. I did hit a couple of issues however… First the tabs, Users, and IPs, do not work. They both point to xml files but the only files that match are template files. I could see where the users template files (There are two) could be combined and be a working XML, but the IPs file is only half of the xml file. Second and it's not a break issue, the first tab doesn't load correctly until you click on it and have it reload. I can see that it's just how the original menu option loads the url is slightly off. Everything else seems to be working great and I was able to get it all up and running without much work! Love it!

Thanks again for all your hard work on this!!!!

It looks like after a reboot the Users and IPs tabs both work. Unfortunately the E2guardian service wouldn't start at all. After checking the logs it appears that the black list I was using didn't have an AD folder which for some reason threw everything off. I created it manually with a "domains", and "URLs" file inside, and the service started back up. Not sure if that's an issue with the black list (www.shallalist.de) or E2guardian…

Mobile_Bob

@aGeekHere:

Does E2guardian have "Use SafeSearch engine"?

I haven't found that as an option anywhere. Google has changed the way it implements forced safe search though. It's DNS based now.
https://support.google.com/websearch/answer/186669?hl=en

I'm sure that the filter/proxy could do a redirect of some sort also, but I just implemented it through DNS as Google suggests.

aGeekhere

It would be nice if it did it automatically for all search engines with this feature.

I am having trouble find a step by step guide for setting this up with pfsense, do you have a link?

Mobile_Bob

@aGeekHere:

It would be nice if it did it automatically for all search engines with this feature.

I am having trouble find a step by step guide for setting this up with pfsense, do you have a link?

Most of the step by steps talk about using the nossl.google.com which doesn't work anymore.

Basically you just have to be running DNS Resolver and all your computers pointing to it as their primary DNS (can be done through DHCP easy enough), then at the bottom of DNS Resolver add an override for www.google.com and have it point to 216.239.38.120 which is what forcesafesearch.google.com resolves to. (Hint you can also do this for www.youtube.com)

It's not the best solution since it would be better to use the FQDN forcesafesearch.google.com, but you can't do CNAME records in DNS Resolver so using the IP address works.

Also if this is in a Microsoft Domain environment you want all windows boxes pointing to your DNS server running on the Domain Controller. To work around that, you can add a forwarder to the MS DNS server to point to your pfSense box that is running DNS Resolver. (You can't add a CNAME record to MS DNS for www.google.com because Server 2008 r2 and above won't allow it)…

Also to make sure things are locked down, block all dns requests from going out your firewall. That way people can't specify a DNS server outside your control to grab www.google.com from.
https://doc.pfsense.org/index.php/Blocking_DNS_queries_to_external_resolvers

Hope that's clear enough...

Mobile_Bob

@aGeekHere:

It would be nice if it did it automatically for all search engines with this feature.

I am having trouble find a step by step guide for setting this up with pfsense, do you have a link?

I just found this that looks promising.. I don't know if it would work with HTTPS though. Or at least not until you setup HTTPS filtering.

https://groups.google.com/forum/#!topic/e2guardian/1ieUvbsNDkU

In urlregexplist

"(^http://[0-9a-z]+.google.[a-z]+[-/%.0-9a-z]/images?)"->"\1safe=vss&"
"(^http://[0-9a-z]+.google.[a-z]+[-/%.0-9a-z]/search?)"->"\1safe=vss&"
"(^http://[0-9a-z]+.google.[a-z]+[-/%.0-9a-z]*/s?)"->"\1safe=vss&"

vss = very safe search