On 18/05/2013 12:30 a.m., jimmah6786 wrote:
Is there anything else I could check to see why this still doesn't work?
Does anyone have a working example of Squid 3.3 with this type of topology?
Routing on a stick.
The wiki is pretty much the exact config I'm happily using on my own
network
On 20/05/2013 9:37 a.m., Alex Domoradov wrote:
Hello all, I have encountered with strange issue in selection of
tcp_outgoing_address. I have linux box with CentOS-6.4 x64. Is default
getaway for a few vlans. On the router is installed squid
# squid -v
Squid Cache: Version 3.1.10
Squid
So I need to upgrade at least to squid 3.2? 3.1.23 wouldn't be enough?
On Mon, May 20, 2013 at 10:16 AM, Amos Jeffries squ...@treenet.co.nz wrote:
On 20/05/2013 9:37 a.m., Alex Domoradov wrote:
Hello all, I have encountered with strange issue in selection of
tcp_outgoing_address. I have linux
hi Amos ,
thanks fro reply ,
sorry for late ,
i dont think that its hardware issue .
i mean that i dont think that my hardware router cant bear two squid . it
can do it and perfectly .
i returned to its refernece manual and find it has a specific enhancement
featured implemented fro wccp and
here is some verification from router , :
Gateway7600#sh ip wccp capabilities
WCCP Platform Capability Settings
Capability Setting
Supported forwarding methodsGRE L2
Supported return methodsGRE L2
Supported
On 20/05/2013 8:34 p.m., Alex Domoradov wrote:
So I need to upgrade at least to squid 3.2? 3.1.23 wouldn't be enough?
Probably not. Most of the issues with tcp_outgoing_address required a
major overhaul of the TCP handling. Which we don't do to stable release
series.
Amos
Firstly, thank you for bringing this to everyones attention.
On 20/05/2013 12:54 p.m., Daniel Streefkerk wrote:
Symantec provide a version of Squid to their Symantec.Cloud customers
that they call the Client Site Proxy. They've modified the source to
add two encrypted headers (X-TEACUP and
ok, I will try 3.2
On Mon, May 20, 2013 at 1:48 PM, Amos Jeffries squ...@treenet.co.nz wrote:
On 20/05/2013 8:34 p.m., Alex Domoradov wrote:
So I need to upgrade at least to squid 3.2? 3.1.23 wouldn't be enough?
Probably not. Most of the issues with tcp_outgoing_address required a major
Hallo, Amos,
Du meintest am 18.05.13:
I have enabled squidGuard within a huge network.
[...]
What are you using squidGuard for anyway?
There are 2 different options/decisions:
a) using redirect/rewrite (as squidGuard and ufdbguard do) or
using the squid options acl and http_access (as
On 5/20/2013 12:17 PM, Ahmad wrote:
hi Amos ,
thanks fro reply ,
sorry for late ,
i dont think that its hardware issue .
i mean that i dont think that my hardware router cant bear two squid . it
can do it and perfectly .
i returned to its refernece manual and find it has a specific
On 5/20/2013 11:34 AM, Alex Domoradov wrote:
older than 3.2
newer then 3.2 beta so 3.2 stable.
but now there is 3.3 stable then if you can use it it's better.
Eliezer
The problem was --cond 'enabled=1'. Without it worked.
Thanks!
Em 18/05/2013 00:38, Amos Jeffries escreveu:
On 18/05/2013 6:49 a.m., Delton wrote:
Dear guys,
I'm testing in MySql authentication via 'basic_db_auth'.
I ran the test and it worked:
/lib/squid3/basic_db_auth --user squid
Thanks for the reply Amos. I'm pretty sure they're using Squid to
provide their services, but they are distributing the binaries in the
product they call the Client Site Proxy. It's a packaged install of
Squid for Windows that's preconfigured to point to their cloud-based
upstream proxies.
As for
On 20/05/2013 11:54 p.m., Delton wrote:
The problem was --cond 'enabled=1'. Without it worked.
??? then your test which used it should have failed as well.
Amos
Thanks!
Em 18/05/2013 00:38, Amos Jeffries escreveu:
On 18/05/2013 6:49 a.m., Delton wrote:
Dear guys,
I'm testing in MySql
Ok, apparently the problem with squidGuard was related to corrupted
databases, causing unpredictably behaviour. I recompiled everything
and now is working fine.
I'll think about the suggestions (ufdbguard and raw squid), and maybe
write down a comparison.
thanks guys!
On Mon, May 20, 2013 at
On 05/18/2013 04:32 PM, Guy Helmer wrote:
further testing indicates that building with --enable_kqueue causes
squid not to read the remainder of the body
Yes, if my interpretation of the sources is correct, Squid kqueue code
does not fully support SSL yet :-(. There is no kqueue code to resume
On 05/18/2013 04:32 PM, Guy Helmer wrote:
Any thoughts on appropriate timeouts for the ICAP protocol? I have
not seen recommendations for timeouts in RFC 3507 or the ICAP
Errata.
Let the ICAP client determine them? :-)
Cheers,
Alex.
17 matches
Mail list logo
