E2guardian package for pfsense - $??

Mobile_Bob

I know the biggest wait is 2.3, but I was wondering if you plan on upgrading to the latest build of e2guardian on the FreeBSD port. As much benefit as I have already gotten, and as much as I am invested in seeing this package be finished, and continue to improve. I'm willing to donate $100 for all your hard work. I have no doubt you're busy but hopefully this will help, and maybe get some interest going again :) Anyone else who hasn't yet donated willing to chip in a little?? This is A LOT of work!!! Lets thank Marcello and give him incentive to continue!

StuBoy

Hi,

I'm a new to pfSense, also looking for e2Guardian to be available for pfSense, just wanted to check my understanding of where it is :-

I understand that e2Guardian will not be available as a pfSense package until v2.3 is released ? Is that correct ?

Do we have any estimate on when pfSense 2.3 will be available ?

I believe e2Guardian can be installed natively in FreeBSD, how easy is that for a novice ?

Stu.

Mobile_Bob

See here for a general feel for how 2.3 is coming (no dates): https://redmine.pfsense.org/projects/pfsense/roadmap#2.3

It's not to hard to install, but does take some poking around to get everything working: http://knes1.github.io/blog/2015/2015-07-18-manually-installing-e2guardian-to-pfsense.html

Both are found earlier in this thread. I would suggest reading through the whole thing if you want to try to do it manually.

marcelloc

I've started fixing packages to 2.3. If postfix gets merged and works fine, e2guardian(on current port version) is on the list.

michaeleino

first I want to say that no words are enough to thank marcelloc for his efforts,
what is the version of e2guardian you implement ?
I can compile the latest one v3.2 easily & start it in a freebsd 10.1 environment, but I can't create the pkg to try with pfsense… tell me if I can help.


./configure --enable-clamd --enable-avastd --enable-icap --enable-kavd --enable-sslmitm --enable-email --enable-trickledm --localstatedir=/var --with-logdir=/var/log --with-piddir=/var/run

Downloadski

I followed the above link: https://github.com/pfsense/FreeBSD-ports/pull/23
And there is a question of marcelloc which is answered by rbgarga and after that no more..

Issues seemed to be: Packages will never be allowed to touch system files anymore. It's wrong and dangerous

Cino

@Downloadski:

I followed the above link: https://github.com/pfsense/FreeBSD-ports/pull/23
And there is a question of marcelloc which is answered by rbgarga and after that no more..

Issues seemed to be: Packages will never be allowed to touch system files anymore. It's wrong and dangerous

https://github.com/pfsense/pfsense-packages/pull/866 is the pull request for E2guardian

bfrost

I am a crap coder but I would be willing to try my hand at this if no one else will. The pfsense guys are top notch and have created a beautiful system but I need to provide a little filtering.

Can someone point me in the right direction on this to just get started?

bfrost

Or I could just pitch money if someone else who knows what they are doing wants to pick this back up.

zythra

@bfrost:

Can someone point me in the right direction on this to just get started?

I've got the BSD package working. I've just been playing with it in the hopes that the pfSense package will come soon. I am coming from Ubuntu server (and a strong Windows background) so some of the BSD structure isn't familiar to me, at this point I still have to start E2guardian up manually, haven't figured out how to get it to run at boot.

If you want to try installing the BSD package you can from the console with the following command:

pkg add http://pkg.freebsd.org/freebsd:10:x86:64/release_3/All/e2guardian-3.0.4_1.txz

cmb991

I'll give whatever else is needed, but I need this to work on all interfaces/vlans. In my environment, we have multiple vlans and subnets. Also need some type of DNS blocking option so we don't have to worry about the HTTPS cert errors. Just tell me the price.

andresense

Any news?

asterix

what seems to be the the issue here? Can someone with packaging knowledge pick this up?

jetberrocal

@marcelloc:

@aGeekHere:

Will this still be E2guardian 2.2 or will it be a later version? as they are up to version 3.2.0 now

For now, e2guardian 3.0.4

As of this date, what is the e2guardian version available for pfsense?

I need at least 3.1, for a working ssl_bump funtion

dotdash

@jetberrocal:

As of this date, what is the e2guardian version available for pfsense?
I need at least 3.1, for a working ssl_bump funtion

The current version in ports is 3.4.0.3, so if a package ever gets built, it will be at least that version.

jetberrocal

@dotdash:

@jetberrocal:

As of this date, what is the e2guardian version available for pfsense?
I need at least 3.1, for a working ssl_bump funtion

The current version in ports is 3.4.0.3, so if a package ever gets built, it will be at least that version.

I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?

Mobile_Bob

You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.

dotdash

@jetberrocal:

I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?

pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
This just installs the FreeBSD port, not the pfSense bits…

jetberrocal

@Mobile_Bob:

You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.

Can you send me a configuration file example for e2g, squid and NAT (screenshot) to follow your suggestion?
By the way the NAT is the one at Ubuntu or the one at pfsense (Newbie question) ?

jetberrocal

@dotdash:

@jetberrocal:

I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?

pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
This just installs the FreeBSD port, not the pfSense bits…

Can I use this pkg to follow the manual installation procedure with Marcello codes?