similar to: Transparent http proxy

ive got a config thats client -> server ->Dansguardian->Squid -> onward adn I want to transparently redirect web traffic to DG/Squid Not sure where the problem lies - hoping you guys can help me and at least tell me that its NOT my shorewall config heres the configs When I point a browser straight at 3128 or 3129 I get web pages back and the appropriate stuff in the logs . I get a

Its in here : ( from your squid.conf ) "/etc/squid/listas/ad_block.lst" http_access deny ads #deny_info TCP_RESET ads affiliates.digitalriver.com it is in the ads list. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] Namens > erdosain9 > Verzonden: vrijdag 9 september 2016 15:55 > Aan:

Hello Everyone! I am using shorewall-3.0.5 on suse linux. Recently we have implemented dansguardian running on 8080 and squid on port 3128. Previously (before dans guardian) masquerading was working fine but after the implementation of dansguardian masquerading is not working. My rules file has entry Previous entry was ACCEPT loc:192.192.192.3 net REDIRECT loc 8080 tcp

Hello what is the essential difference between the default squid package and this squid34 package, as I have problems using this squid34 package for FTP connections; there are no shown icons, when going to e.g. ftp://ftp.adobe.com/ when I tell the browser to show the image then I get this squid generated message ... the same config /etc/squid/squid.conf works with the default squid package

Greetings, I installed a squid 3.1.10.i686 squid to a centos 6.2i686. The proxy is working fine with the default config. After I decided to use it as a transparent proxy, I added two lines to config: http_proxy 10.0.5.1:3128 transparent, always_direct allow all http_port 10.0.5.1:3128 transparent # # Recommended minimum configuration: # acl manager proto cache_object #acl localhost src

I remember to see something about that in shorewall.net some time ago, but I could not find it today ... The case : Debian Etch, Shorewall 3.2.6, squid3 and Apache 2 . The first 3 where already running fine for some time ... Now I need to setup an Apache server to allow some web mannagement, things like PHPsysinfo, phppgadmin, just for internal net, no web access . but port 80 is redirected to

Hello, I have a problem here with: [root at ablprx01 squid]# cat /etc/*release CentOS release 5.2 (Final) [root at ablprx01 squid]# rpm -qa|grep -i squid squid-2.6.STABLE6-5.el5_1.3 The web proxy process (used by 300-400 users) seems to run ok: [root at ablprx01 squid]# ps uawwwx|grep squid root 2304 0.0 0.0 7792 1268 ? Ss 08:45 0:00 squid -D squid 3082 27.7 0.9

Hello, I havn't gotten an answer over on the squid usergroup - so I'm hoping someone can help me here. SUSE - 9.1 SQUID - 2.5.STABLE5 SAMBA - 3.0.2a-SUSE (the one that came with SUSE Installer by YAST) I have set up squid, samba, got the winbind to work great Wbinfo -t, -u, -g all work great Squid also worked great until I tried to tie in NTLM_Auth If I authenticate using

Hi, I set up Squid 4.6 on Debian 10 and I'm having problems with browser authentication on a Windows station. I did the tests on the command line and apparently it's OK. root at proxy:/etc/squid/acls# /usr/bin/ntlm_auth --helper-protocol=squid-2.5-basic Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED lp_load_ex: refreshing parameters Initialising global

Hi all, I am trying to configure squid as a interception HTTPS proxy under CentOS 7. At every https request, I am receiving a certificate error. My current config for squid is: # My localnet acl localnet src 172.22.55.0/28 acl localnet src 172.22.58.0/29 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70

Hi, I recently migrated my office's server from Slackware64 14.1 to CentOS 7. Right now I'm in the process of configuring the Squid web proxy. I edited the default /etc/squid/squid.conf, and here's what I have so far: --8<-------------------------------------------------- # /etc/squid/squid.conf # Nom d'h?te du serveur Squid visible_hostname amandine.microlinux.lan #

Hi, I've setup a transparent HTTP+HTTPS proxy on my server running CentOS 7, using Squid. Here's my configuration file. --8<---------------------------------------------------------------- # /etc/squid/squid.conf # D?finitions acl localnet src 192.168.2.0/24 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port

hello, my name is Denny. I am new in this list. I am trying use multiple uplinks as describe in the lartc documentation (http://lartc.org/howto/lartc.rpdb.multiple-links.html) with squid transparent proxy in my gateway server. let me draw the configuration : /----------------- -----DSL1-----| \ |Transparent proxy |----Local network -----DSL2-----|

Hi. Samba-4.0.7 FreeBSD 10.0-CURRENT Besides serving files I'm using Samba to authenticate users in the Windows AD with squid. After having issues with samba 3.6.16 I decided to see if samba4 will fit me more. I was surprised, but I found that Samba 4 is fully functional in my environment and is nearly production-ready. After that I tried to setup squid to use samba for NTLM authentication.

Hi, I am running squid as a TRANSEPARENT PROXY WITH SQUID 2.5 on CENTOS 4.5. Pls see below for squid.con file. http_port 3128 cache_mem 64 MB cache_dir ufs /var/spool/squid 100 16 256 cache_access_log /var/log/squid/access.log cache_log /var/log/squid/cache.log cache_store_log /var/log/squid/store.log # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # Example rule

Hi all, I''ve just built Mandrake 10.1 on a Compaq Deskpro that I''ve built as a router/firewall and am redirecting port 80 outbound to force users through the Content Filter. I''ve run this setup on Mandrake 9.0 and 10.0 without any problems but this time the following happens. Squid is accessed through port 3128 and Dansguardian via 8080. If I set my browser on a

Hi, I try configure squid proxy transparent and shorewall In my squid.conf have this configuration: http_port 8000 acl all src 0.0.0.0/0.0.0.0 acl password REQUIRED http_access allow password http_access deny all authentica_program /usr/lib/squid/ncsa_auth /etc/squid/passwd In my rules have: REDIRECT loc 8000 tcp 80 - !MY_IP_EXTERNAL ACCEPT fw net tcp 80 I try

Authenticating Server: 2003 with Active Directory Enabled Squid Server: FreeBSD 5.1 Samba: 3.0.7,1 Other package info in package list at bottom. The DNS server is on the 2003 Server with the proper kerberos and ldap entries in the DNS server. (Passes Active Directory DNS utility tests) Responses are sent in LM, NTLM, &NTLM2 when negotiated. Signing requirements are not configured. (Choices:

Hi everybody. We are running Shorewall and Squid on Suse on the same box. Each is working fine independently, but we can''t get them to cooperate. The access log in squid shows no requests when Shorewall is on. Here are all the changes we made in the configuration files. Everything else is the same. We have read through the mailing list and the guide, but still haven''t figured it

Thanks to everyone for all the help getting this done. As promised, here are the detailed notes I put together. These step by step instructions should work starting with a raw RedHat Linux 9.0 system. - Greg Scott GregScott@InfraSupportEtc.com These are step by step instructions for how to install and configure the Squid proxy server with transparent authentication for users in a