Home › Comunidade Brasileira Endian Firewall › Endian Firewall › Endian Firewall – Suporte › Serviços do Firewall Parado
- Este tópico contém 15 respostas, 4 vozes e foi atualizado pela última vez 10 anos, 8 meses atrás por Douglas Santos.
-
AutorPosts
-
-
abril 20, 2010 às 2:39 pm #195jerfeson santosParticipante
Pessoal,
Uso dansguardian no endian e não consigo restartar o mesmo, alguns servi~ps meu está com status de parado. Como resolver??
Wireguard_webadmin
Sistema gratuito (Open Source) para gestão de VPN's WireGuard com uma Web interface intuitiva e fácil de usar.
Principais funcionalidades:
- Sistema de Firewall completo e flexível.
- Encaminhamento de portas
- Suporte a multi usuário com níveis diferentes de acesso
- Múltiplas instâncias do Wireguard
- Crypto key routing para configuração de VPN site-to-site
O projeto é Open Source, fácil de instalar e está disponível em wireguard_webadmin
-
abril 20, 2010 às 2:52 pm #4211Albaney BaylãoParticipante
O Squid está ativo? Existe alguma access policy ativa usando algum content filter? O Dansguardian só “starta” se o endian considerar necessário, ou seja se houver pelo menos uma policy ativa usando filtro de conteúdo.
-
abril 20, 2010 às 4:31 pm #4212jerfeson santosParticipante
O squid está ativo. E uso o filtro de conteúdo. Estava funcionando tudo normalmente até que o pessoal se queixou que a internet não estava funcionando ao verifica qual a mensagem o browser retorna era a seguinte: “Cache incapaz de encaminhar esta requisito neste momento” acessei pelo modo gráfico o serviço HTTP e parei voltou a funcionar só sem levar em considerações os filtros definidos. Abaixo serviços em ativa no firewall.
Antivírus PARADO
Antivírus FTP PARADO
Antivírus para HTTP (havp) PARADO
DHCP server PARADO
Email scanner (POP3) RODANDO
Filtro de conteúdo PARADO
NTP server RODANDO
OpenVPN server PARADO
Proxy Web RODANDO
Pyzor spam filter RODANDO
SIproxy PARADO
Secure Shell server RODANDO
Servidor CRON RODANDO
Servidor DNS proxy RODANDO
Servidor Web RODANDO
Servidor de histórico RODANDO
Sistema de Detecção de Intrusos PARADO
Spam filter for POP3 (spamd) RODANDO
Spam filter for SMTP (amavis) PARADO
VPN (IPsec)
-
abril 20, 2010 às 5:05 pm #4213Albaney BaylãoParticipante
Faça um acesso ssh no endian. Execute o comando restartsquid.py. Quais as mensagens que ele dá?
Depois disso vá ao diretório /var/log e dê o comando “grep dans *.log”. O que ele mostra?
-
abril 20, 2010 às 5:24 pm #4214jerfeson santosParticipante
No primeiro comando retorna :
2010-04-20 14:24:55,818 – endian.logger – DEBUG – sync from old
/usr/lib/python2.4/site-packages/Cheetah/Compiler.py:1577: UserWarning: You supplied an empty string for the source!
Starting squid: . [OK]
Segundo comando:
boot.log:Apr 20 10:36:10 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:22:10 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:22:18 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:22:42 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:22:51 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:23:16 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:23:26 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:23:34 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:25:29 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:25:29 fwceapeba dansguardian: dansguardian shutdown succeeded
boot.log:Apr 20 11:25:37 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:25:39 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:25:48 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:27:05 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:36:10 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:36:18 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:48:47 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 11:48:55 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 11:51:39 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:01:07 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 12:01:16 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:02:28 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 12:02:37 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:02:51 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:12:29 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:12:56 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 12:13:00 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 12:13:08 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 13:41:07 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 13:41:15 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:01:28 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 14:01:36 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:02:22 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:07:00 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 14:07:09 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:09:46 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 14:09:54 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:16:12 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:20:25 fwceapeba dansguardian: dansguardian shutdown failed
boot.log:Apr 20 14:20:33 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:20:57 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:21:19 fwceapeba dansguardian: dansguardian startup failed
boot.log:Apr 20 14:25:13 fwceapeba dansguardian: dansguardian startup failed
-
abril 20, 2010 às 5:54 pm #4215jerfeson santosParticipante
Ao tentar acessar a internet em uma estação dar essa mensagem “Cache incapaz de encaminhar esta requisio neste momento” isso com proxy http ativo…
-
abril 20, 2010 às 6:03 pm #4216Albaney BaylãoParticipante
Há algum arquivo de log além dos “access.log” no diretório /var/log/dansguardian? Se sim o que tem neles?
-
abril 20, 2010 às 6:26 pm #4217jerfeson santosParticipante
Estou observando pelo WinSCP e tem outras pasta além do dansguardian. Tem um arquivo boot.log em txt que tem:
Apr 19 23:57:02 fwceapeba syslog-ng: syslog-ng -HUP succeeded
Apr 19 23:57:02 fwceapeba syslog-ng: syslog-ng -HUP succeeded
Apr 19 23:57:02 fwceapeba syslog-ng: syslog-ng -HUP succeeded
Apr 20 08:06:07 fwceapeba havp: havp shutdown failed
Apr 20 08:06:07 fwceapeba havp: havp shutdown failed
Apr 20 10:36:01 fwceapeba havp: havp startup failed
Apr 20 10:36:10 fwceapeba dansguardian: dansguardian startup failed
Apr 20 10:37:36 fwceapeba pyzord: pyzord shutdown failed
Apr 20 10:37:53 fwceapeba dnsmasq: dnsmasq shutdown succeeded
Apr 20 10:37:53 fwceapeba dnsmasq: dnsmasq startup succeeded
Apr 20 11:22:10 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:22:18 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:22:42 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:22:51 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:23:08 fwceapeba havp: havp startup failed
Apr 20 11:23:16 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:23:26 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:23:34 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:25:28 fwceapeba havp: havp startup failed
Apr 20 11:25:29 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:25:29 fwceapeba dansguardian: dansguardian shutdown succeeded
Apr 20 11:25:37 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:25:39 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:25:48 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:26:56 fwceapeba havp: havp startup failed
Apr 20 11:27:05 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:36:10 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:36:18 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:48:47 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 11:48:55 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:50:52 fwceapeba syslog-ng: syslog-ng startup succeeded
Apr 20 11:50:53 fwceapeba ulogd: ulogd startup succeeded
Apr 20 11:51:00 fwceapeba capi: capiinit startup failed
Apr 20 11:51:12 fwceapeba dnsmasq: dnsmasq startup succeeded
Apr 20 11:51:13 fwceapeba httpd: httpd startup succeeded
Apr 20 11:51:13 fwceapeba sshd: succeeded
Apr 20 11:51:17 fwceapeba pyzord: pyzord shutdown failed
Apr 20 11:51:17 fwceapeba ntpd: ntpd startup succeeded
Apr 20 11:51:17 fwceapeba dnsmasq: dnsmasq -HUP succeeded
Apr 20 11:51:18 fwceapeba pyzord: pyzord shutdown failed
Apr 20 11:51:19 fwceapeba p3scan: p3scan startup succeeded
Apr 20 11:51:21 fwceapeba postfix: succeeded
Apr 20 11:51:21 fwceapeba ntpd: ntpd shutdown succeeded
Apr 20 11:51:21 fwceapeba mailgraph: mailgraph startup succeeded
Apr 20 11:51:21 fwceapeba ntpd: ntpd startup succeeded
Apr 20 11:51:24 fwceapeba snort: snort startup failed
Apr 20 11:51:24 fwceapeba snort: snort startup failed
Apr 20 11:51:28 fwceapeba havp: havp startup failed
Apr 20 11:51:30 fwceapeba fcron: fcron startup succeeded
Apr 20 11:51:30 fwceapeba ntop: ntop startup succeeded
Apr 20 11:51:39 fwceapeba dansguardian: dansguardian startup failed
Apr 20 11:52:48 fwceapeba pyzord: pyzord shutdown failed
Apr 20 11:52:48 fwceapeba pyzord: pyzord startup succeeded
Apr 20 11:52:49 fwceapeba spamassassin: spamd startup succeeded
Apr 20 11:52:49 fwceapeba p3scan: p3scan shutdown succeeded
Apr 20 11:52:49 fwceapeba p3scan: p3scan startup succeeded
Apr 20 12:01:07 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 12:01:16 fwceapeba dansguardian: dansguardian startup failed
Apr 20 12:02:28 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 12:02:37 fwceapeba dansguardian: dansguardian startup failed
Apr 20 12:02:51 fwceapeba dansguardian: dansguardian startup failed
Apr 20 12:03:09 fwceapeba havp: havp shutdown failed
Apr 20 12:03:09 fwceapeba havp: havp shutdown failed
Apr 20 12:12:29 fwceapeba dansguardian: dansguardian startup failed
Apr 20 12:12:56 fwceapeba dansguardian: dansguardian startup failed
Apr 20 12:13:00 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 12:13:08 fwceapeba dansguardian: dansguardian startup failed
Apr 20 13:41:07 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 13:41:15 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:01:28 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 14:01:36 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:02:13 fwceapeba havp: havp startup failed
Apr 20 14:02:22 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:07:00 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 14:07:09 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:09:46 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 14:09:54 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:15:38 fwceapeba pyzord: pyzord shutdown succeeded
Apr 20 14:15:38 fwceapeba pyzord: pyzord startup succeeded
Apr 20 14:15:39 fwceapeba spamassassin: spamd shutdown succeeded
Apr 20 14:15:39 fwceapeba spamassassin: spamd startup succeeded
Apr 20 14:16:04 fwceapeba havp: havp startup failed
Apr 20 14:16:12 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:20:25 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 14:20:33 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:20:49 fwceapeba havp: havp startup failed
Apr 20 14:20:57 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:21:10 fwceapeba havp: havp startup failed
Apr 20 14:21:19 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:25:04 fwceapeba havp: havp startup failed
Apr 20 14:25:13 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:28:52 fwceapeba havp: havp startup failed
Apr 20 14:29:00 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:29:39 fwceapeba dansguardian: dansguardian shutdown failed
Apr 20 14:29:48 fwceapeba dansguardian: dansguardian startup failed
Apr 20 14:32:31 fwceapeba pyzord: pyzord shutdown succeeded
Apr 20 14:32:31 fwceapeba pyzord: pyzord startup succeeded
Apr 20 14:32:34 fwceapeba postfix: succeeded
Apr 20 14:32:34 fwceapeba mailgraph: mailgraph shutdown succeeded
Apr 20 14:32:35 fwceapeba postfix: succeeded
Apr 20 14:32:35 fwceapeba mailgraph: mailgraph startup succeeded
Os logs estão localizados nesta pasta loglocation = ‘/var/log/fifo/dansguardian’. Verifiquei isso no dansguardian.conf
-
abril 20, 2010 às 7:37 pm #4218jerfeson santosParticipante
Pode ser cache cheia pra está dando esse problema e não permitindo startar o dansguardian????
-
abril 20, 2010 às 7:51 pm #4219Albaney BaylãoParticipante
Sinceramente não tenho mais dicas pra colocar a não ser procurar novas informações em outros logs….
Se não funcionar, talvez seja o caso de reinstalar. O Endian instala tão rápido que nem sei se não vale mais a pena reinstalar do que ficar tentando advinhar qual o problema….
Só lembre de salvar a configuração antes, se for reinstalar.
-
abril 22, 2010 às 12:52 pm #4220jerfeson santosParticipante
quando ativo o proxy http dar isso nas estações ao acessar a internet:
ERRO
A URL solicitada no pode ser recuperada
Na tentativa de recuperar a URL: http://webmail.ceapeba.org.br/
O seguinte erro foi encontrado:
Cache incapaz de encaminhar esta requisio neste momento.
Esta requisio no pode ser encaminhada para o servidor ou para qualquer outro cache. A causa mais provvel para este erro :
O administrador do cache no permite que este cache faa conexes diretas para servidores, e
Todos os caches configurados no esto disponveis.
Generated Thu, 22 Apr 2010 12:52:41 GMT by fwceapeba (squid/2.6.STABLE18)
-
abril 22, 2010 às 2:45 pm #4221jerfeson santosParticipante
Segue a configuração de meu squid:
shutdown_lifetime 1 seconds
icp_port 0
http_port 0.0.0.0:8080 transparent
cache_effective_user squid
cache_effective_group squid
pid_filename /var/run/squid.pid
cache_mem 100 MB
cache_dir aufs /var/spool/squid 5000 16 256
error_directory /usr/share/squid/errors/Portuguese
max_filedesc 12513
server_persistent_connections off
half_closed_clients off
buffered_logs on
# START LOG
cache_log /var/log/squid/cache.log
cache_access_log syslog:local6.info
cache_store_log none
useragent_log /var/log/squid/useragent.log
strip_query_terms off
log_mime_hdrs off
# END LOG
# FORWARD IP ADDRESS
forwarded_for on
# START PROFILE ACLS
acl default_safe_ports port “/var/efw/proxy/profiles/defaultprofile/acls/safeports.acl”
acl default_ssl_ports port “/var/efw/proxy/profiles/defaultprofile/acls/safesslports.acl”
acl default_blocked_mimetypes rep_mime_type “/var/efw/proxy/profiles/defaultprofile/mimetypes”
acl default_0_timeframe time MTWHFAS 00:00-24:00
# END PROFILE ACLS
acl all src 0.0.0.0/0.0.0.0
acl localhost src 127.0.0.1/255.255.255.255
acl CONNECT method CONNECT
acl EFW_http port 80
acl EFW_https port 10443
acl EFW_ips dst 192.168.10.253
acl EFW_networks src “/var/efw/proxy/acls/src_subnets.acl”
acl EFW_dst_networks dst “/var/efw/proxy/acls/src_subnets.acl”
acl HAVP_ALLOWED_PROTOS proto HTTP
acl HAVP_ALLOWED_PROTOS proto SSL
acl QUERY urlpath_regex cgi-bin ?
cache deny QUERY
cache deny localhost
cache deny CONNECT
cache allow all
# GREEN
acl EFW_src_green src 192.168.10.0/255.255.255.0
acl EFW_dst_green dst 192.168.10.0/255.255.255.0
# Only allow cachemgr access from localhost
acl manager proto cache_object
http_access allow manager EFW_ips
http_access deny manager
#Only allow snmp access from localhost
acl snmppublic snmp_community public
snmp_access allow EFW_ips
snmp_access allow localhost
snmp_access deny all
header_access Via deny all
# EFW PROXY INTERFACE
# ACCESS TO SQUID
# local machine, no restriction
http_access allow localhost
# GUI admin if local machine connects
http_access allow EFW_ips EFW_networks EFW_http
http_access allow CONNECT EFW_ips EFW_networks EFW_https
# Deny not web services
http_access deny !default_safe_ports !default_ssl_ports
http_access deny CONNECT !default_ssl_ports
http_access allow EFW_networks default_0_timeframe
http_access deny all
http_reply_access allow localhost
http_reply_access allow EFW_networks !default_blocked_mimetypes
http_reply_access deny all
maximum_object_size 1024 KB
minimum_object_size 0 KB
request_body_max_size 0 KB
reply_body_max_size 0 allow all
cache_mgr Informatica@ceapeba.org.br
visible_hostname fwceapeba
# begin custom.tmpl
# end custom.tmpl
# cache peers for dansguardian
cache_peer 127.0.0.1 parent 9999 0 no-query no-digest no-netdb-exchange name=dg_profile1 login=*:password
cache_peer_access dg_profile1 deny localhost
cache_peer_access dg_profile1 deny !HAVP_ALLOWED_PROTOS
cache_peer_access dg_profile1 allow EFW_networks default_0_timeframe
cache_peer_access dg_profile1 deny EFW_networks
never_direct deny localhost
never_direct deny !HAVP_ALLOWED_PROTOS all default_0_timeframe
never_direct allow all default_0_timeframe
never_direct allow all
-
abril 22, 2010 às 2:46 pm #4222jerfeson santosParticipante
do dansguardian:
# DansGuardian config file for version 2.9.x
reportinglevel = 3
languagedir = ‘/usr/share/dansguardian/languages’
language = ‘en’
loglevel = 1
logexceptionhits = on
logfileformat = 1 # maybe we should change this?
#maxlogitemlength = 400
#anonymizelogs = on
#syslog = on
#statlocation = ‘/var/log/dansguardian/stats’
loglocation = ‘/var/log/fifo/dansguardian’
filterip = 127.0.0.1
filterport = 9999
proxyip = 127.0.0.1
proxyport = 9998
accessdeniedaddress = ‘http://YOURSERVER.YOURDOMAIN/cgi-bin/dansguardian.pl’
nonstandarddelimiter = on
usecustombannedimage = 1
custombannedimagefile = ‘/usr/share/dansguardian/transparent1x1.gif’
# Filter groups options
filtergroups = 1
filtergroupslist = ‘/etc/dansguardian/filtergroupslist’
# Authentication files location
bannediplist = ‘/etc/dansguardian/lists/bannediplist’
exceptioniplist = ‘/etc/dansguardian/lists/exceptioniplist’
banneduserlist = ‘/etc/dansguardian/dansguardian/lists/banneduserlist’
exceptionuserlist = ‘/etc/dansguardian/lists/exceptionuserlist’
showweightedfound = on
weightedphrasemode = 2
urlcachenumber = 1000 # maybe we should set this higher?
urlcacheage = 900
scancleancache = on
phrasefiltermode = 2
preservecase = 0
hexdecodecontent = off
forcequicksearch = off
reverseaddresslookups = off
reverseclientiplookups = off
logclienthostnames = off # maybe this should be an option?
createlistcachefiles = on
maxuploadsize = -1
maxcontentfiltersize = 256
maxcontentramcachescansize = 2000
maxcontentfilecachescansize = 20000
filecachedir = ‘/tmp’
deletedownloadedtempfiles = on
# download manager stuff
initialtrickledelay = 20
trickledelay = 10
downloadmanager = ‘/etc/dansguardian/downloadmanagers/default.conf’
# antivirus
#contentscanner = ‘/etc/dansguardian/contentscanners/clamav.conf’
contentscannertimeout = 60
contentscanexceptions = off
# auth plugins
#authplugin = ‘/etc/dansguardian/authplugins/proxy-basic.conf’
#authplugin = ‘/etc/dansguardian/authplugins/proxy-digest.conf’
#authplugin = ‘/etc/dansguardian/authplugins/proxy-ntlm.conf’
#authplugin = ‘/etc/dansguardian/authplugins/ident.conf’
authplugin = ‘/etc/dansguardian/authplugins/ip.conf’
recheckreplacedurls = off
forwardedfor = on
usexforwardedfor = on
logconnectionhandlingerrors = on
logchildprocesshandling = off
maxchildren = 60
minchildren = 8
minsparechildren = 4
preforkchildren = 6
maxsparechildren = 32
maxagechildren = 500
# maximum number of concurrent ips
maxips = 0
ipcfilename = ‘/tmp/.dguardianipc’
urlipcfilename = ‘/tmp/.dguardianurlipc’
pidfilename = ‘/var/run/dansguardian.pid’
nodaemon = off
nologger = off
# Enable logging of “ADs” category blocks
logadblocks = off
loguseragent = off
# daemonuser = ‘nobody’
# daemongroup = ‘nobody’
softrestart = off
mailer = ‘/usr/sbin/sendmail -t’
-
agosto 18, 2013 às 1:07 am #4223Douglas SantosParticipante
Meu Status de filtro de conteúdo esta parado , mais meu squid Esta rodando tranquilo , ja resetei ele no SSH e ele me da a resposta dizendo q esta tudo ok , ja pegui uma vez uma falha onde um usuário mesmo na regra de CONTROLADOS conseguia acessar tpw facebook . Refiz o usuario dele novamente e botei ele no CONTROLADOS e ai sim ele volto ao normal , mais a pergunta e , pq o status na aba esta como parado se o squid n me mostra nenhuma linha de erro .
-
agosto 19, 2013 às 7:11 pm #4224neophspParticipante
Douglas,
Eu estava com esse problema. Rode o comando no console do endian # dansguardian
O que retorna?
-
agosto 23, 2013 às 10:51 pm #4225Douglas SantosParticipante
Vlw , dei um reset do dansguardian ele voltou
-
-
AutorPosts
- O tópico ‘Serviços do Firewall Parado’ está fechado para novas respostas.