Hallo,
I wrote am 29.12.11:
The Squid HTTP Proxy team is very pleased to announce the
availability of the Squid-3.2.0.14 beta release!
I had to re-install the former version; 3.2.0.14 had stopped working.
Seems to be (have been) a false alarm - sorry.
The same breakdown just happened with
Hallo, Amos,
Du meintest am 13.12.11:
The Squid HTTP Proxy team is very pleased to announce the
availability of the Squid-3.2.0.14 beta release!
I had to re-install the former version; 3.2.0.14 had stopped working.
Messages in /var/log/warn:
Dec 29 07:05:51 Arktur squid[4479]: Starting
3.2.0.14 with a couple of custom patches is working 9 days without
any single assert or segfault, doing steady 200 reqs/sec. It took
almost a year to get to this point for me.
I have very simple configuration: no caching, no workers, no ipv6, no
SSL, no icap, almost any possible
Date: Sat, 24 Dec 2011 13:16:45 +1300
From: squ...@treenet.co.nz
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Squid 3.2.0.14 beta is available
On 24/12/2011 12:15 p.m., Jenny Lee wrote:
Date: Sat, 24 Dec 2011 10:38:58 +1300
From: squ...@treenet.co.nz
To: squid-users
Hi Amos,
After I set the memory_cache_shared off in the config file of the squid
, after I disable the memory_cache_shared , squid not crash, but we need
shared memory caching, any fix for this problem.
Best Regards,
Saleh Madi
On 15/12/2011 11:42 p.m., Saleh Madi wrote:
why squid 3.2.0.14
On 24/12/2011 9:25 a.m., Saleh Madi wrote:
Hi Amos,
After I set the memory_cache_shared off in the config file of the squid
, after I disable the memory_cache_shared , squid not crash, but we need
shared memory caching, any fix for this problem.
Okay, did you find any other details about it?
Date: Sat, 24 Dec 2011 10:38:58 +1300
From: squ...@treenet.co.nz
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Squid 3.2.0.14 beta is available
On 24/12/2011 9:25 a.m., Saleh Madi wrote:
Hi Amos,
After I set the memory_cache_shared off in the config file of the squid
On 24/12/2011 12:15 p.m., Jenny Lee wrote:
Date: Sat, 24 Dec 2011 10:38:58 +1300
From: squ...@treenet.co.nz
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Squid 3.2.0.14 beta is available
On 24/12/2011 9:25 a.m., Saleh Madi wrote:
Hi Amos,
After I set the memory_cache_shared off
Hallo, Amos,
Du meintest am 13.12.11:
The Squid HTTP Proxy team is very pleased to announce the
availability of the Squid-3.2.0.14 beta release!
Slackware binary:
http://helmut.hullen.de/filebox/Linux/slackware/n/squid-3.2.0.14-i486-1hln.tgz
Viele Gruesse!
Helmut
On Dec 15, 2011, at 12:04 AM, Amos Jeffries wrote:
On 15/12/2011 4:28 a.m., Guy Helmer wrote:
undefined reference to `__sync_fetch_and_sub_4
Thank you.
Apparently that is related to GCC version. Which gcc version are you building
with?
Amos
The stock compiler on FreeBSD 8.x is
On 15/12/2011 11:42 p.m., Saleh Madi wrote:
why squid 3.2.0.14 exited/restarted every 2 or 3 or 4 ... hours and
why squid crashing with segfault.
Question: why squid 3.2.0.14 exited/restarted ?
Answer: because of crashing with segfault.
Squid auto-restarts after any unexpected crash from
Below is all information for kid3
config for kid3
if ${process_number} = 3
cache_dir diskd /cache1/cache3 6 32 256
cache_dir diskd /cache2/cache3 6 32 256
cache_dir diskd /cache3/cache3 6 32 256
redirect_program /usr/bin/squidGuard -c /etc/squid/squidGuard.conf
redirect_children 8
Dears all,
The www.facebook.com not work in the TPROXY mode because the problem of
the Host header forgery detected, the TPROXY is nice feature and we
needed it for the spoofing the client IP address. I think the squid
developers need to Think about this problem, I hope we can fix this
On Dec 13, 2011, at 1:20 AM, Amos Jeffries wrote:
The Squid HTTP Proxy team is very pleased to announce the
availability of the Squid-3.2.0.14 beta release!
FYI, I had to add -march=i486 to CFLAGS on FreeBSD 8 i386 (32-bit) to fix
issues like these with the link stage of the build:
On 14/12/2011 10:02 p.m., Saleh Madi wrote:
Dears all,
The www.facebook.com not work in the TPROXY mode because the problem of
the Host header forgery detected, the TPROXY is nice feature and we
needed it for the spoofing the client IP address. I think the squid
developers need to Think about
On 15/12/2011 4:28 a.m., Guy Helmer wrote:
undefined reference to `__sync_fetch_and_sub_4
Thank you.
Apparently that is related to GCC version. Which gcc version are you
building with?
Amos
On 13/12/2011 8:48 p.m., Saleh Madi wrote:
Thanks Amos for your good work, from squid-3.2.0.13 and squid-3.2.0.14
version we facing a big problem with SECURITY ALERT: By user agent and
SECURITY ALERT: on URL the squid box and the clients using the same DNS
servers, what mean flags=33 and
I use linux policy based routing.
Example: linux pppoe server have tow interfaces one interface connected
with the main linux router the other interface connected with squid box
and I redirect all http traffic form the pppoe server via policy based
routing to the squid box.
Note: the pppoe server
tis 2011-12-13 klockan 22:59 +1300 skrev Amos Jeffries:
Squid has resolved the domain name (www.facebook.com) the client
(10.0.2.45) was supposedly contacting and determined that the IP
(66.220.147.33) the packet was going to does not belong to that domain name.
Details about the alert
tis 2011-12-13 klockan 12:59 +0200 skrev Saleh Madi:
Dos the policy based routing make the Host header forgery detected problem.
All forms of interception runs into this.
The best cure is to get the browser configured to use the proxy. This
avoids the issue entirely.
See WPAD for one way to
Thanks Henrik for your reply, but when you have 1000 clients , its
difficult to lit all clients to configure there browser with proxy, I
think the redirect rule via policy based routing or other redirect method
is easy than the configuration of the client bowser , have you any idea
what the best
Il 13/12/2011 13:14, Saleh Madi ha scritto:
Thanks Henrik for your reply, but when you have 1000 clients , its
difficult to lit all clients to configure there browser with proxy, I
think the redirect rule via policy based routing or other redirect method
is easy than the configuration of the
Thanks Marcello for your reply, we have linux pppoe server work for 1000
clients , how I can use the WPAD (web proxy autodiscovery protocol) for
them.
Thanks and Best Regards,
Saleh
Il 13/12/2011 13:14, Saleh Madi ha scritto:
Thanks Henrik for your reply, but when you have 1000 clients , its
Il 13/12/2011 13:53, Saleh Madi ha scritto:
Thanks Marcello for your reply, we have linux pppoe server work for 1000
clients , how I can use the WPAD (web proxy autodiscovery protocol) for
them.
Thanks and Best Regards,
Saleh
Il 13/12/2011 13:14, Saleh Madi ha scritto:
Thanks Henrik for
why dont you use the interception\transparent mode instead of TPROXY?
for your setup it seems just the perfect idea.
i'm using a range setup like this:
-A PREROUTING -p tcp -m tcp -m iprange ! -d 192.168.0.0/16 -i eth1
--dport 80 -j REDIRECT --to-ports 3128 --src-range
On Tue, 13 Dec 2011 16:20:57 +0200, Eliezer Croitoru wrote:
why dont you use the interception\transparent mode instead of TPROXY?
for your setup it seems just the perfect idea.
i'm using a range setup like this:
-A PREROUTING -p tcp -m tcp -m iprange ! -d 192.168.0.0/16 -i eth1
--dport 80 -j
Thanks Amos for your good work, from squid-3.2.0.13 and squid-3.2.0.14
version we facing a big problem with SECURITY ALERT: By user agent and
SECURITY ALERT: on URL the squid box and the clients using the same DNS
servers, what mean flags=33 and flags=17 in the cache log file and how I
can disable
27 matches
Mail list logo
