Home › Comunidade Brasileira Endian Firewall › Endian Firewall › Endian Firewall – Suporte › Proxy Transparente
Marcado: proxy transparente
- Este tópico contém 4 respostas, 4 vozes e foi atualizado pela última vez 13 anos, 2 meses atrás por jabinha.
-
AutorPosts
-
-
fevereiro 11, 2011 às 2:21 pm #854leizenParticipante
Boa tarde.
Hoje cheguei na empresa e minha internet estava da seguinte forma:
– Conseguia baixar emails sem problemas
– Skype Conectava normalmente
Mas não estava conseguindo acessar nenhuma pagina de internet: http://www.google.com.br, http://www.uol.com.br, http://www.yahoo.com.br não conseguia entrar em absolutamente nenhuma pagina de internet.
Reiniciei o PC e nada, Reiniciei o modem da telefonica e nada, Reiniciei o Endian e nada! Simplesmente não consigo acessar paginas na internet.
Depois de fuçar muito no Endian fiz o seguinte teste:
Meu proxy estava configurado como transparente e tentei colocar como Não Transparente.
Como não transparente a internet voltou porém minha black list não está sendo aplicada. Esta sendo possível visitar qualquer site.
Como transparente não vai e como Não Transparente acessa mas acessa sem respeitar minha black list.
Esse problema ocorreu do nada. Ontem quando eu fui embora estava tudo normal e hoje quando eu cheguei enctontrei esse problema.
Uso o Endian 2.4 alguem sabe me dizer o que pode estar ocorrendo?
Segue log:
Sistema2011-02-11 10:47:06
dnsmasq (18381) using nameserver 8.8.8.8#53Intrusio..2011-02-11 08:24:16
snort[5836]: [122:3:0] (portscan) TCP Portsweep[Priority: 3]: {PROTO:255} 192.168.1.34 -> 217.111.199.65Sistema2011-02-11 10:47:06
dnsmasq (18381) exiting on receipt of SIGTERMSistema2011-02-11 10:47:06
dnsmasq (18450) started, version 2.47 cachesize 2048Sistema2011-02-11 10:47:06
dnsmasq (18450) IPv6 GNU-getopt no-DBus no-I18N TFTPSistema2011-02-11 10:47:06
dnsmasq (18450) reading /etc/dnsmasq/resolv.confSistema2011-02-11 10:47:06
dnsmasq (18450) using nameserver 200.204.0.138#53Sistema2011-02-11 10:47:06
dnsmasq (18450) using nameserver 8.8.8.8#53Sistema2011-02-11 10:47:06
dnsmasq (18450) read /etc/hosts – 3 addressesSistema2011-02-11 10:47:06
dnsmasq (18450) No such file or directorySistema2011-02-11 10:47:09
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartdnsmasq.py –forceSistema2011-02-11 10:47:09
dnsmasq (18450) reading /etc/dnsmasq/resolv.confSistema2011-02-11 10:47:09
dnsmasq (18450) using nameserver 200.204.0.138#53Sistema2011-02-11 10:47:09
dnsmasq (18450) using nameserver 8.8.8.8#53Sistema2011-02-11 10:47:09
dnsmasq (18450) exiting on receipt of SIGTERMSistema2011-02-11 10:47:09
dnsmasq (18512) started, version 2.47 cachesize 2048Sistema2011-02-11 10:47:09
dnsmasq (18512) IPv6 GNU-getopt no-DBus no-I18N TFTPSistema2011-02-11 10:47:09
dnsmasq (18512) reading /etc/dnsmasq/resolv.confSistema2011-02-11 10:47:09
dnsmasq (18512) using nameserver 200.204.0.138#53Sistema2011-02-11 10:47:09
dnsmasq (18512) using nameserver 8.8.8.8#53Sistema2011-02-11 10:47:09
dnsmasq (18512) read /etc/hosts – 3 addressesSistema2011-02-11 10:47:09
dnsmasq (18512) No such file or directorySistema2011-02-11 10:47:33
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.pySistema2011-02-11 10:48:12
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.py –forceSistema2011-02-11 10:48:22
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/sbin/ifplugstatusSistema2011-02-11 10:48:22
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/bin/openvpn-user listSistema2011-02-11 10:49:06
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.py –forceSistema2011-02-11 10:49:13
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.pySistema2011-02-11 10:49:30
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.pySistema2011-02-11 10:49:46
dnsmasq (18512) reading /etc/dnsmasq/resolv.confSistema2011-02-11 10:49:46
dnsmasq (18512) using nameserver 200.204.0.138#53Sistema2011-02-11 10:49:46
dnsmasq (18512) using nameserver 8.8.8.8#53Filtro d..2011-02-11 10:50:08
127.0.0.1 192.168.1.54 http://www.orkut.com *DENIED* Banned site: http://www.orkut.com GET 0 0 1 403 – Default Profile (content1) -Sistema2011-02-11 10:50:12
fetchipac (19805) segfault at 1 ip b76b6e16 sp bfdc1608 error 4 in libc-2.3.4.so[b7663000+114000]Anti-ví..2011-02-11 10:50:40
clamd (19820) Not loading PUA signatures. Intrusio..2011-02-11 08:22:29
snort[5836]: [1:2002330:4] ET POLICY Google Talk TLS Client Traffic [Classification: Potential Corporate Privacy Violation] [Priority: 1]: {TCP} 192.168.1.25:60376 -> 209.85.157.125:443Anti-ví..2011-02-11 10:50:40
clamd (19820) Malformed database Intrusio..2011-02-11 08:23:38
snort[5836]: [122:3:0] (portscan) TCP Portsweep[Priority: 3]: {PROTO:255} 192.168.1.34 -> 173.99.236.37Anti-ví..2011-02-11 10:51:12
clamd (19849) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:51:12
clamd (19849) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:51:12
clamd (19849) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:51:12
clamd (19849) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:51:12
clamd (19849) Not loading PUA signatures. Anti-ví..2011-02-11 10:51:12
clamd (19849) Malformed database Sistema2011-02-11 10:52:15
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.py –reloadAnti-ví..2011-02-11 10:52:18
clamd (19977) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:52:18
clamd (19977) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:52:18
clamd (19977) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:52:18
clamd (19977) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:52:18
clamd (19977) Not loading PUA signatures. Anti-ví..2011-02-11 10:52:18
clamd (19977) Malformed database Anti-ví..2011-02-11 10:52:22
clamd (20061) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:52:22
clamd (20061) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:52:22
clamd (20061) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:52:22
clamd (20061) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:52:22
clamd (20061) Not loading PUA signatures. Anti-ví..2011-02-11 10:52:22
clamd (20061) Malformed database Sistema2011-02-11 10:52:38
sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsquid.pyAnti-ví..2011-02-11 10:52:41
clamd (20141) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:52:41
clamd (20141) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:52:41
clamd (20141) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:52:41
clamd (20141) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:52:41
clamd (20141) Not loading PUA signatures. Anti-ví..2011-02-11 10:52:41
clamd (20141) Malformed database Anti-ví..2011-02-11 10:52:45
clamd (20221) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:52:45
clamd (20221) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:52:45
clamd (20221) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:52:45
clamd (20221) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:52:45
clamd (20221) Not loading PUA signatures. Anti-ví..2011-02-11 10:52:45
clamd (20221) Malformed database Sistema2011-02-11 10:52:55
kernel: [ 4301.510619] eth0 link down.Sistema2011-02-11 10:52:55
kernel: [ 4301.510877] br0 port 1(eth0) entering disabled stateAnti-ví..2011-02-11 10:53:17
clamd (20240) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:53:17
clamd (20240) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:53:17
clamd (20240) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:53:17
clamd (20240) Reading databases from /usr/share/clamav Anti-ví..2011-02-11 10:53:17
clamd (20240) Not loading PUA signatures. Anti-ví..2011-02-11 10:53:17
clamd (20240) Malformed database Sistema2011-02-11 10:53:43
kernel: [ 4349.862505] eth0 link up.Sistema2011-02-11 10:53:43
kernel: [ 4349.862678] br0 port 1(eth0) entering learning stateSistema2011-02-11 10:53:47
kernel: [ 4353.862024] br0 topology change detected, propagatingSistema2011-02-11 10:53:47
kernel: [ 4353.862028] br0 port 1(eth0) entering forwarding stateAnti-ví..2011-02-11 10:53:49
clamd (20256) clamd daemon 0.95.2 (OS: linux-gnu, ARCH: i386, CPU: i586) Anti-ví..2011-02-11 10:53:49
clamd (20256) Running as user clamav (UID 1000, GID 107) Anti-ví..2011-02-11 10:53:49
clamd (20256) Log file size limited to 2097152 bytes. Anti-ví..2011-02-11 10:53:49
clamd (20256) Reading databases from /usr/share/clamav Anti-ví..
Obrigado.
Carlos Messias.
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
-
fevereiro 11, 2011 às 2:59 pm #7193thiagomespbParticipante
veja este post com as dicas que resolve.
-
fevereiro 11, 2011 às 5:20 pm #7194Jefferson FernandesParticipante
problema ja foi resolvido ?
-
fevereiro 11, 2011 às 6:06 pm #7195thiagomespbParticipante
Aqui o meu problema foi resolvido .. segui a dica do colega do post.
-
fevereiro 11, 2011 às 6:22 pm #7196jabinhaParticipante
Today’s Topics:
1. Re: Sudden issues with Transparent Proxy/Squid (John Marotta)
2. Re: 2.4.1 Port forwarding on RED multi-IP broken (Daniel Moree)
If it doesn’t:
1. Delete or rename the daily.cvd file located in the /usr/share/clamav folder.
2. Then run a freshclam -v to get the latested update.
3. Restart your HTTP Proxy and you should be OK.
4. Check the Status tab to ensure that the following are in a Running state:
a. Content Filter
b. HTTP Antivirus (havp)
c. WEB Proxy
=John=
-
-
AutorPosts
- O tópico ‘Proxy Transparente’ está fechado para novas respostas.