Unofficial E2guardian package for pfSense
-
Hola Marcelloc!
Will this package's configuration be kept in the system config.conf file? So if I restore that file, my E2Guardian config will be restored as well?
-
Hola Marcelloc!
Will this package's configuration be kept in the system config.conf file? So if I restore that file, my E2Guardian config will be restored as well?
Yes it will ! :)
-
Thank you, sir. Could I make a humble suggestion? Is there a way to implement a config backup/restore/reset function in the package itself? This would be more efficient to restore a config than restoring the system conf file. Also, could be used to replicate the configuration of just this package to other firewalls.
Also, a question… will the package automatically find Squid and configure its integration? Or is that a manual process?
Thanks!
-
The sync config between boxes is already there. The squid integration is a manual process.
The restore function I'll think about later.
-
Thank you, sir. Could you please post instructions on how to integrate E2 with Squid?
Thanks a bunch, muito obrigado!
-
Basically, define the ip and squid port on squid config on first tab. The second tab shows the authentication e2guardian support to pass through squid.
All other tabs flow the configure from left-to-right, viewing each tab and saving config.
-
Looks nice. I'll have to give it a try. A couple of questions:
1. Why a custom script and not get it officially into the Package Manager?
2. Is there documentation to get up and running? It looks like you create separate entries under the various ACLs and then create a Group and assign the ACLs to it. There's a lot of options on a lot of screens and they aren't all clear to me.
3. Aside from AD, how do we assign users to different groups? With squidGuard I needed to use the persons MAC to assign an IP through DHCP and then I could use that IP under a different ACL. I don't see a way to tie an IP or MAC into a group in here.Thanks for the work. This would be a big improvement over squidGuard if I can figure it out.
-
Looks nice. I'll have to give it a try. A couple of questions:
2. Is there documentation to get up and running? It looks like you create separate entries under the various ACLs and then create a Group and assign the ACLs to it. There's a lot of options on a lot of screens and they aren't all clear to me.
The e2guardian configuration is really complex but extremely powerfull. Some options you get on general configuration but most is applied per group.
A basic setup:
-
Apply the shalist under blacklist tab
-
Configure the default group under acl
-
save config
At this point, E2guardian users are required only when you have more then one group. All unauthenticated users or unlisted users will match first filter group.
So if you want to test a user based configuration, create a second group
-
Configure squid as your parent proxy under daemon tab
-
Select the Auth Plugin you want to interact with your squid configured user authentication
-
save and apply config
-
-
Is there any difference in the AV of E2guardian vs Squid? They both appear to be Clam but Squid seems to give more options for custom databases.
-
Is there any difference in the AV of E2guardian vs Squid? They both appear to be Clam but Squid seems to give more options for custom databases.
IIRC e2guardian has per group scan options but I agree clamd on squid has more options.
Maybe you need to test both bu for now, you can keep on squid.
we need a lot of tests to archive the best config for e2guardian on pfSense.
I'm planning an captive portal integration just the same way I did on squid.
-
I'm going to try to get some testing done tomorrow to see what I can come up with. Looking through the config options is a bit daunting, especially the Pics area since the value ranges keep changing. And where do I add in phrases to block? Can we create our own phrase lists?
-
Can we create our own phrase lists?
sure.
This is a wiki of Dansguardian. Most options works the same way on e2guardian.
http://contentfilter.futuragts.com/wiki/doku.php
https://github.com/e2guardian/e2guardian/wiki/Configuration
-
I've changed the submenu display style. I think it's better to see and undertand where you are.
What do you think?
images style1 are current pkg framework
images style2 has new style view.
What do you think?
-
To me, the original style is better. I can see that I'm in ACL's -> Phrase Lists by the underlining. It just sticks out better. In the second one I can see that I'm in ACLs but can't tell which sub-menu I'm in becasue it isn't showing any different. The bread-crumbs up top show it but it just isn't as easy to follow. I like your current style better.
-
I think style 2 is cleaner but would be even nicer if it did highlight the sub menu item too ;)
-
I think style 2 is cleaner but would be even nicer if it did highlight the sub menu item too ;)
I'll put the highlight as an option. For now I've changed de text on each xml to identify what tab you are.
-
I'm starting to test e2guardian but it won't start.
/root: /usr/local/etc/rc.d/e2guardian.sh start kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting e2guardian. In mapauthtoports mode you need to setup one port per auth plugin Error parsing the e2guardian.conf file or other e2guardian configuration files /usr/local/etc/rc.d/e2guardian.sh: WARNING: failed to start e2guardian
Can those files be regenerated? I've pointed to shallalist but that's about it. The Default values in bold, those are the values used if the boxes are left blank? They don't need to be filled in do they?
EDIT:
I copied the e2guardian.conf.sample and overwrote /usr/local/etc/e2guardian/e2guardian.conf and I'm getting further. Now it tells me:/root: /usr/local/etc/rc.d/e2guardian.sh start kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting e2guardian. Error opening/creating log file. (check ownership and access rights). I am running as nobody and I am trying to open /var/log//access.log /usr/local/etc/rc.d/e2guardian.sh: WARNING: failed to start e2guardian
-
What options did you selected to enable multiport?
-
What options did you selected to enable multiport?
What page has that option? I don't think I intentionally selected anything, just clicked through.
-
I have it working on my setup, including ssl interception. Try to selext just one interface. I'll try another clean setup and see how how to reproduce this.