Koozali.org: home of the SME Server
Obsolete Releases => SME 8.x Contribs => Topic started by: leonardocruz on October 17, 2013, 10:55:27 PM
-
-Install version 8.0
-install the updates available to the system
-install Dansguardian
LAN 192.168.50.1
wan X.X.X.X
in browser client pc set proxy to 192.168.50.1 port 8080
everything is fine up to this point, the internet is fine, but when setup the groupfilter , they cease to navigate and although he indicated that must apply authentication with PAM does not and the machines do not make it out to the internet.
and followed to the letter this tutorial: http://wiki.contribs.org/Dansguardian
can anyone help or enlighten?
- No answer for user
- No navigate to internet no dansguardian page showed
[root@cmailer ~]# db configuration show squid
squid=service
EnforceSafePorts=no
RequireAuth=pam
SafePorts=21,70,80,81,119,210,443,563,980,1024-65535
TCPPort=3128
TCPProxyPort=80:3128
Transparent=no
TransparentPort=8080
access=private
status=enabled
[root@cmailer ~]# db configuration show dansguardian
dansguardian=service
portblocking=yes
status=enabled
-
leonardocruz
Edit: Deleted my earlier post re
Transparent=yes
As you are using Filter Groups, then I suspect you have not configured the group memberships correctly.
IIRC the default filter group will block ALL access, & it is by giving additional rights based on filter group membership, that users can gain some or limited or more or even all access to the Internet.
I suggest you carefully review how you have set up filter groups & allocated membership to users.
-
hi, i check all configuration but, continue say in browsers "Connection closed by remote server" and don't answer for user, and this is configured to use auth pam in filtergroupslist i put two users for testing and nothing!,
Reinstall the server and config again and same problem.
Note: SME is 8.0 64bits!
*******************************dansguardian.conf
# Network Settings
#
# the IP that DansGuardian listens on. If left blank DansGuardian will
# listen on all IPs. That would include all NICs, loopback, modem, etc.
# Normally you would have your firewall protecting this, but if you want
# you can limit it to a certain IP. To bind to multiple interfaces,
# specify each IP on an individual filterip line.
filterip =
# the port that DansGuardian listens to.
filterport = 8080
# the ip of the proxy (default is the loopback - i.e. this server)
proxyip = 127.0.0.1
# the port DansGuardian connects to proxy on
proxyport = 3128
*******************************dansguardian F1
# Filter group mode
# This option determines whether members of this group have their web access
# unfiltered, filtered, or banned. This mechanism replaces the "banneduserlist"
# and "exceptionuserlist" files from previous versions.
#
# 0 = banned
# 1 = filtered
# 2 = unfiltered (exception)
#
# Only filter groups with a mode of 1 need to define phrase, URL, site, extension,
# mimetype and PICS lists; in other modes, these options are ignored to conserve
# memory.
#
# Defaults to 0 if unspecified.
# Unauthenticated users are treated as being in the first filter group.
groupmode = 0
# Filter group name
# Used to fill in the -FILTERGROUP- placeholder in the HTML template file, and to
# name the group in the access logs
# Defaults to empty string
groupname = 'Blocked Users'
********************************************dansguardianf2.conf
# Filter group mode
# This option determines whether members of this group have their web access
# unfiltered, filtered, or banned. This mechanism replaces the "banneduserlist"
# and "exceptionuserlist" files from previous versions.
#
# 0 = banned
# 1 = filtered
# 2 = unfiltered (exception)
#
# Only filter groups with a mode of 1 need to define phrase, URL, site, extension,
# mimetype and PICS lists; in other modes, these options are ignored to conserve
# memory.
#
# Defaults to 0 if unspecified.
# Unauthenticated users are treated as being in the first filter group.
groupmode = 1
# Filter group name
# Used to fill in the -FILTERGROUP- placeholder in the HTML template file, and to
# name the group in the access logs
# Defaults to empty string
groupname = 'Standard Users'
-
leonardocruz
Can you test without pam auth or any other auth enabled.
Please prove that dansguardian is blocking sites & so on, ie open a browser to sex.com or similar & you should get the dansguardian blocked site page message. Or try to download an exe file (assuming you have blocked those by default).
You will need to set Transparent=yes for this test
My idea here is that you just try to test & see that the basic configuration & functionality of dansguardian is working correctly (as expected).
If that is all OK then we can look further at specific filter group issues.
Also what versions are you running, show output of
rpm -q dansguardian
rpm -q smeserver-dansguardian
Also after making changes to dansguardian settings re users, your Windows workstation users should log off Windows & log back in again, so these user level changes take effect, have you been doing that ? Are your workstations running Windows or something else ?
-
Try all, at end download the NON 64 Bit Version of SME 8 and install, then Dansguardian put the command for answer PAM auth
At first time the browser answer for user and password and Dansguardian and function smooth.
My conclusion: Dansguardian not is compatible with SME8 64bits version!
-
leonardocruz
...... download the NON 64 Bit Version of SME 8 and install, then Dansguardian put the command for answer PAM auth. At first time the browser answer for user and password and Dansguardian and function smooth.
My conclusion: Dansguardian not is compatible with SME8 64bits version!
Please lodge a bug report so that the problem can be fixed.
Please advise the bug number back here, Thanks.
-
yes please fill a bug there :
http://bugs.contribs.org/enter_bug.cgi?product=SME%20Contribs&component=smeserver-dansguardian&cc=tests@pialasse.com&short_desc=x86_64%20incompatible%20PAM (http://bugs.contribs.org/enter_bug.cgi?product=SME%20Contribs&component=smeserver-dansguardian&cc=tests@pialasse.com&short_desc=x86_64%20incompatible%20PAM)
so we could fix this.
Usually these bugs are easy to fix ( most of the time wrong path to the libraries), but need to be reported and fully described