Re: [squid-users] many vms behind router to same proxy ips problems !

2015-02-20 Thread Amos Jeffries
On 21/02/2015 2:37 p.m., snakeeyes wrote: > Hi , > > > > I have squid with many ips already installed with and configured well with > tcp_outgoing directive. > You have two problems: 1) Your Squid version is too old. Squid-3.1 does not contain the IPv6 split-stack bug fixes that allow t

Re: [squid-users] One Squid proxy for multi-tenant environment

2015-02-20 Thread Amos Jeffries
On 21/02/2015 4:57 a.m., maxt wrote: > I'm just wondering if it is possible to do the following: > > Have one Squid proxy that covers multiple domains/tenants. Each tenant > would have their own specific whitelist and blacklist of sites. Each tenant > would have their own customized/branded bloc

Re: [squid-users] assertion failed: comm.cc:769: "Comm::IsConnOpen(conn)"

2015-02-20 Thread HackXBack
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.4434 GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. T

Re: [squid-users] many vms behind router to same proxy ips problems !

2015-02-20 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You want well-known thing in operating systems world. In Solaris it known as ip_strict_dst_multihoming. It divides in some levels: 1. On OS IP-stack's level must be specified strict dst respondes. I'e, when request comes from one NIC - respond must b

Re: [squid-users] assertion failed: comm.cc:769: "Comm::IsConnOpen(conn)"

2015-02-20 Thread HackXBack
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.3722 GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. T

Re: [squid-users] many vms behind router to same proxy ips problems !

2015-02-20 Thread snakeeyes
Not yet , I know ip routing :) Also I searched but didn’t fins a useful thing about my issue Can u guide more plz ? -Original Message- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Yuri Voinov Sent: Friday, February 20, 2015 7:41 AM To: squid-users@l

[squid-users] One Squid proxy for multi-tenant environment

2015-02-20 Thread maxt
I'm just wondering if it is possible to do the following: Have one Squid proxy that covers multiple domains/tenants. Each tenant would have their own specific whitelist and blacklist of sites. Each tenant would have their own customized/branded block page that would have instructions for request

Re: [squid-users] derive HTTP/HTTPS upload traffic to a secondary interface.

2015-02-20 Thread Josep Borrell
Hi Amos, I tried your suggestion and even if the acl is matched the outgoing IP is not changed. How to know why ? Working with squid 3.5.1. Original IP 192.168.111.10 must be changed for 192.168.111.20 Thanks Josep Squid.conf: debug_options ALL,1 33,2 28,9 11,3 #HTTPS (SSL) trafic interce

Re: [squid-users] many vms behind router to same proxy ips problems !

2015-02-20 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is not squid problem, man. Did you hear about TCP routing? This is the thing your need. 21.02.15 7:37, snakeeyes пишет: > Hi , > > > > I have squid with many ips already installed with and configured > well with tcp_outgoing directive. >

[squid-users] many vms behind router to same proxy ips problems !

2015-02-20 Thread snakeeyes
Hi , I have squid with many ips already installed with and configured well with tcp_outgoing directive. The provlem that I face is ; When many pc behind a router with same public ip use the proxy ips. Assume I have 2 pcs Pc1===> Using proxy ip 1.1.1.1 Pc2===>using proxy 1.1.1.2 N

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Odhiambo Washington
On 20 February 2015 at 17:29, Eliezer Croitoru wrote: > On 19/02/2015 11:49, Odhiambo Washington wrote: > >> I have been hoping that 3.5.2 would possibly help address my problems with >> ACLs, but alas! >> > > Sorry for hijacking the thread but the wiki freebsd buildfarm node install > page: > ht

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Eliezer Croitoru
On 19/02/2015 11:49, Odhiambo Washington wrote: I have been hoping that 3.5.2 would possibly help address my problems with ACLs, but alas! Sorry for hijacking the thread but the wiki freebsd buildfarm node install page: http://wiki.squid-cache.org/BuildFarm/FreeBsdInstall Doesn't include any

Re: [squid-users] "Valid document was not found in the cache" forwarded to clients

2015-02-20 Thread Corentin Delcourt
On 20/02/15 13:29, Amos Jeffries wrote: On 20/02/2015 10:55 p.m., Corentin Delcourt wrote: I run two squid servers, siblings with each other, let's call them A and B. When clients send requests to A, and A thinks B has the resource cached, but in reality B doesn't, Use HTCP protocol between th

Re: [squid-users] "Valid document was not found in the cache" forwarded to clients

2015-02-20 Thread Amos Jeffries
On 20/02/2015 10:55 p.m., Corentin Delcourt wrote: > Hello list. > > I described this issue a few days ago on IRC and no-one could help me, > so I am now turning to you. Here's my problem: > > I run two squid servers, siblings with each other, let's call them A and > B. When clients send requests

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Odhiambo Washington
When I configure the browser to manually use proxy, the pages fail to load and here is what I get: root@mail:/opt/squid-3.5.2/etc # tail -f /usr/local/squid/logs/access.log | grep 192.168.2.2 1424434499.542 1411 192.168.2.2 TAG_NONE/409 4306 CONNECT www.google.com:443 - HIER_NONE/- text/html 142

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Amos Jeffries
On 21/02/2015 12:35 a.m., Odhiambo Washington wrote: > On 20 February 2015 at 13:57, Amos Jeffries wrote: > >> On 20/02/2015 10:09 p.m., Odhiambo Washington wrote: >>> On 20 February 2015 at 04:15, Amos Jeffries >> wrote: >>> On 20/02/2015 5:15 a.m., Odhiambo Washington wrote: > On 19 F

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Amos Jeffries
On 21/02/2015 12:35 a.m., Odhiambo Washington wrote: > On 20 February 2015 at 13:57, Amos Jeffries wrote: > >> On 20/02/2015 10:09 p.m., Odhiambo Washington wrote: >>> On 20 February 2015 at 04:15, Amos Jeffries >> wrote: >>> On 20/02/2015 5:15 a.m., Odhiambo Washington wrote: > On 19 F

Re: [squid-users] Squid compatibility with Ubuntu Server 14.10

2015-02-20 Thread Amos Jeffries
On 20/02/2015 10:52 p.m., BennoBright.MariaEphrem wrote: > Hi, > > We got a requirement as setting up a squid proxy in the Linux OS. Squid > proxy is new for me. It will be helpful if I got clarification for the > below questions. > > > 1) Is it Squid proxy compatible with Ubuntu Serv

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Odhiambo Washington
On 20 February 2015 at 13:57, Amos Jeffries wrote: > On 20/02/2015 10:09 p.m., Odhiambo Washington wrote: > > On 20 February 2015 at 04:15, Amos Jeffries > wrote: > > > >> On 20/02/2015 5:15 a.m., Odhiambo Washington wrote: > >>> On 19 February 2015 at 15:12, Odhiambo Washington > >>> wrote: >

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Amos Jeffries
On 20/02/2015 10:09 p.m., Odhiambo Washington wrote: > On 20 February 2015 at 04:15, Amos Jeffries wrote: > >> On 20/02/2015 5:15 a.m., Odhiambo Washington wrote: >>> On 19 February 2015 at 15:12, Odhiambo Washington >>> wrote: >>> Hi Amos, I did see that thread. However, the disc

[squid-users] Squid compatibility with Ubuntu Server 14.10

2015-02-20 Thread BennoBright.MariaEphrem
Hi, We got a requirement as setting up a squid proxy in the Linux OS. Squid proxy is new for me. It will be helpful if I got clarification for the below questions. 1) Is it Squid proxy compatible with Ubuntu Server 14.10. 2) Which Squid proxy version fit in more appropriate with

[squid-users] "Valid document was not found in the cache" forwarded to clients

2015-02-20 Thread Corentin Delcourt
Hello list. I described this issue a few days ago on IRC and no-one could help me, so I am now turning to you. Here's my problem: I run two squid servers, siblings with each other, let's call them A and B. When clients send requests to A, and A thinks B has the resource cached, but in realit

Re: [squid-users] Mutual authentication managed by Squid

2015-02-20 Thread Yuri Voinov
20.02.15 15:34, Ilya Karpov пишет: I’m not sure that using transparent sslbump squid will understand how to use client certificate for mutual authentication. As you configure it. At least without transparent ssl bump it doesn’t. Sure. Did you try to use trspr-sslbump for client auth? How does

Re: [squid-users] Mutual authentication managed by Squid

2015-02-20 Thread Ilya Karpov
I’m not sure that using transparent sslbump squid will understand how to use client certificate for mutual authentication. At least without transparent ssl bump it doesn’t. Did you try to use trspr-sslbump for client auth? How does squid pick right client certificate for certain host? Best regar

Re: [squid-users] Mutual authentication managed by Squid

2015-02-20 Thread Yuri Voinov
Transparent SSL Bump interception, eh? 20.02.15 15:14, Ilya Karpov пишет: Hi guys, can anyone suggest solution to make following scenario work using squid: step1. Client(actually server application) calls HTTP://example .org squid via proxy. | V step2. Proxy(Squid) understand

[squid-users] Mutual authentication managed by Squid

2015-02-20 Thread Ilya Karpov
Hi guys, can anyone suggest solution to make following scenario work using squid: step1. Client(actually server application) calls HTTP://example .org squid via proxy. | V step2. Proxy(Squid) understands that all calls to HTTP://example.org should be ch

Re: [squid-users] Squid-3.5.2 and FreeBSD 10.1

2015-02-20 Thread Odhiambo Washington
On 20 February 2015 at 04:15, Amos Jeffries wrote: > On 20/02/2015 5:15 a.m., Odhiambo Washington wrote: > > On 19 February 2015 at 15:12, Odhiambo Washington > > wrote: > > > >> Hi Amos, > >> > >> I did see that thread. However, the discussion was still continuing > then. > >> > >> > >> I will