Unofficial E2guardian package for pfSense

Cino

@marcelloc:

@pfsensation:

Is there any way to turn off Tiny proxy once and for all? It's really frustrating because I use Squid and it keeps starting up when I change any configurations on E2Guardian.

I'll split it in two packages when I have time.

Thanks Marcello! Or you could create a off switch? :P

I can't remember what I did but I think I commented out a few lines in /usr/local/etc/rc.d/tinyproxy so it wouldnt started


#!/bin/sh

# $FreeBSD: branches/2017Q1/www/tinyproxy/files/tinyproxy.in 340872 2014-01-24 00:14:07Z mat $
#
# PROVIDE: tinyproxy
# REQUIRE: LOGIN
#
# Add the following lines to /etc/rc.conf.local or /etc/rc.conf to enable tinyproxy:
# tinyproxy_enable (bool): Set to "NO" by default.
#                          Set it to "YES" to enable tinyproxy 
# tinyproxy_config (path): Set to "/usr/local/etc/tinyproxy.conf" by default.

. /etc/rc.subr

name="tinyproxy"
rcvar=tinyproxy_enable

load_rc_config $name

# Make sure the pidfile matches what's in the config file.
: ${tinyproxy_enable="NO"}
: ${tinyproxy_pidfile="/var/run/tinyproxy.pid"}
: ${tinyproxy_config="/usr/local/etc/tinyproxy.conf"}

# pidfile=${tinyproxy_pidfile}
# command=/usr/local/sbin/tinyproxy
# command_args="-c $tinyproxy_config 2> /dev/null"

# run_rc_command "$1"

Thank you for sharing your block page!

marcelloc

@marcelloc:

False positive. I got the testing repo from e2guardian but compiled a 3.5.1 version instead of 4.1. :(

I've include the dump of the crash on e2guardian git

I could stop it from crashing but did not had time to see why this 4.1.1 BSD amd64 e2g binaries is not intercepting ssl.

Not sure if all http workers from 4.1.1 needs to be running or it's something that will happen with traffic.

https://github.com/e2guardian/e2guardian/pulls

pfsensation

@marcelloc:

@marcelloc:

False positive. I got the testing repo from e2guardian but compiled a 3.5.1 version instead of 4.1. :(

I've include the dump of the crash on e2guardian git

I could stop it from crashing but did not had time to see why this 4.1.1 BSD amd64 e2g binaries is not intercepting ssl.

Not sure if all http workers from 4.1.1 needs to be running or it's something that will happen with traffic.

https://github.com/e2guardian/e2guardian/pulls

Great we're making progress. Your pull was merged. :)

Don't worry, look at it when you have time. I'm very happy to see so much interest in E2Guardian now. Even at the stage it's in, it's way surpassed what SquidGuard could even hope to achieve.

That being said. On 4.1.1 the 'error too many redirects' issue was fixed and Philip Pearce, blamed the time out for Squid etc. I've tried messing with it, but still get the message from time to time although less so now after increasing time out to 60 secs.

pfsensation

@Cino:

I can't remember what I did but I think I commented out a few lines in /usr/local/etc/rc.d/tinyproxy so it wouldnt started


#!/bin/sh

# $FreeBSD: branches/2017Q1/www/tinyproxy/files/tinyproxy.in 340872 2014-01-24 00:14:07Z mat $
#
# PROVIDE: tinyproxy
# REQUIRE: LOGIN
#
# Add the following lines to /etc/rc.conf.local or /etc/rc.conf to enable tinyproxy:
# tinyproxy_enable (bool): Set to "NO" by default.
#                          Set it to "YES" to enable tinyproxy 
# tinyproxy_config (path): Set to "/usr/local/etc/tinyproxy.conf" by default.

. /etc/rc.subr

name="tinyproxy"
rcvar=tinyproxy_enable

load_rc_config $name

# Make sure the pidfile matches what's in the config file.
: ${tinyproxy_enable="NO"}
: ${tinyproxy_pidfile="/var/run/tinyproxy.pid"}
: ${tinyproxy_config="/usr/local/etc/tinyproxy.conf"}

# pidfile=${tinyproxy_pidfile}
# command=/usr/local/sbin/tinyproxy
# command_args="-c $tinyproxy_config 2> /dev/null"

# run_rc_command "$1"

Thank you for sharing your block page!

No problem, happy to give back to the community! :)

I'm not an expert with this, so I went with the safest method and set the bool tinyproxy_enable "NO" at the end of the script. Now Tinyproxy doesn't start up anymore! :D