Re: [squid-users] bandwith restriction
On 19/06/11 16:14, benjamin fernandis wrote: Hi Ragheb, Thanks for your quick response. == Take care banjo that for order for this to work all your client ips must hit the cache directly and not reach the cache through a nat rule otherwise your squid will see that all your web traffic is coming from one single ip and thus it will shape all your inner lan traffic as one ip and thus all your inner will be shaped to just 512kbps. = currently my squid 3.1 is running in transparent mode.and i used iptables rules to transfer port 80 traffic to port 3128(squid port).That is ok. Is there any change required with my existing setup to achieve delay pool facility. Should not be. I believe Ragheb's problem as described only occurs if your NAT is on a different box to Squid. That precise problem being one of the several reasons we say you MUST NOT have NAT on a separate box when doing interception with Squid. Same IP problem will occur if you have any other middleware (such as a content filter) between Squid and the clients. In this case you need it to send the X-Forwarded-For header and Squid to define trust of the relay software with follow_x_forwarded_for access controls. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.8 and 3.1.12.2
[squid-users] 3.2.0.9 Issues
Hello Squid Team, Thank you for much awaited 3.2.0.9 release. This one seem to have one major issue: 1) Peers are not honored. All connections going direct. I tried everything possible but of no use. Can someone verify? Others: 2) assertion failed: mem.cc:190: MemPools[type] == NULL 3) What does this mean? 2011/06/19 14:16:14 kid1| Failure Ratio at 1.008 2011/06/19 14:16:14 kid1| Going into hit-only-mode for 5 minutes... 4) --disable-ipv6 still not honored. need to use USE_IPV6 0 to disable. 5) forward.cc has Forwarding client request... line at debug 17,1 which seems to create a cache.log as big as the access.log! This is with a drop-in 3.2.0.8 config file at a cursory glance. I will go throught the options to see if anything changed and if these are my wrongdoings. Jenny
Re: [squid-users] bandwith restriction
Hi Amos, thanks your your response.Please share me any document for delay pool to understand it in exact manner as it works.I tried to find from internet but it is very confusing to me. As per squid document, there are class object in that they are using terms like aggregate , network and individual terms. What does that mean? What is the restore and max terms which used in delay_pool parameters? Please try to solve my doubts with any good practical example. Thanks, Benjamin
Re: [squid-users] 3.2.0.9 Issues
On 19/06/11 22:39, Jenny Lee wrote: Hello Squid Team, Thank you for much awaited 3.2.0.9 release. This one seem to have one major issue: 1) Peers are not honored. All connections going direct. I tried everything possible but of no use. Can someone verify? There was a major change in the peer selection algorithm to make it work with tcp_outgoing_address across multiple address families. I'm adding some debug now so we can view the selections and see what is going on a bit better. The patch is here: http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-11506.patch Others: 2) assertion failed: mem.cc:190: MemPools[type] == NULL 3) What does this mean? 2011/06/19 14:16:14 kid1| Failure Ratio at 1.008 2011/06/19 14:16:14 kid1| Going into hit-only-mode for 5 minutes... More DIRECT requests are failing due to TCP connect or DNS lookup errors than are succeeding. Probably a side effect of (1) above. 4) --disable-ipv6 still not honored. need to use USE_IPV6 0 to disable. Okay. Found this one. Sorry for being so dense earlier. I was looking at the logic rather than the variable name :( BTW: would you mind trialling with IPv6 enabled now? This version is supposed to resolve all the edge cases previous releases had. The only issues I'm expecting to be still relevant are: * servers not responding to IPv6 TCP packets (ECN and PMTUD issues). * DNS resolvers not responding to lookups. 5) forward.cc has Forwarding client request... line at debug 17,1 which seems to create a cache.log as big as the access.log! Thank you. That should have been 17,2. Just the debug tracer for when a request is about to be forwarded on somewhere. This is with a drop-in 3.2.0.8 config file at a cursory glance. I will go throught the options to see if anything changed and if these are my wrongdoings. Jenny Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.8 and 3.1.12.2
[squid-users] Problems compiling 3.1.12.3-RC with ICAP on RHEL
Hi all Is anyone else seeing problems with compiling the 3.1.12.3 RC on RHEL, with --enable-icap-client? It seems that patch 10313 (http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10313.patch) causes issues. This is the output I'm getting: snip ngs -Wcomments -Werror -D_REENTRANT -m64 -O2 -g -m64 -mtune=generic -c -o Initiate.lo Initiate.cc libtool: compile: g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../src -I../../include -I../../libltdl -I/usr/include/libxml2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Werror -D_REENTRANT -m64 -O2 -g -m64 -mtune=generic -c Initiate.cc -fPIC -DPIC -o .libs/Initiate.o /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../src -I../../include -I../../libltdl -I/usr/include/libxml2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Werror -D_REENTRANT -m64 -O2 -g -m64 -mtune=generic -c -o Initiator.lo Initiator.cc libtool: compile: g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../src -I../../include -I../../libltdl -I/usr/include/libxml2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Werror -D_REENTRANT -m64 -O2 -g -m64 -mtune=generic -c Initiator.cc -fPIC -DPIC -o .libs/Initiator.o Initiate.cc: In destructor 'virtual Adaptation::AnswerCall::~AnswerCall()': Initiate.cc:41: error: request for member 'message' in '((Adaptation::AnswerCall*)this)-Adaptation::AnswerCall::anonymous.AsyncCallTAdaptation::AnswerDialer::dialer.Adaptation::AnswerDialer::anonymous.UnaryMemFunTAdaptation::Initiator, HttpMsg*::arg1', which is of non-class type 'HttpMsg*' Initiate.cc:41: error: request for member 'message' in '((Adaptation::AnswerCall*)this)-Adaptation::AnswerCall::anonymous.AsyncCallTAdaptation::AnswerDialer::dialer.Adaptation::AnswerDialer::anonymous.UnaryMemFunTAdaptation::Initiator, HttpMsg*::arg1', which is of non-class type 'HttpMsg*' Initiate.cc:42: error: request for member 'message' in '((Adaptation::AnswerCall*)this)-Adaptation::AnswerCall::anonymous.AsyncCallTAdaptation::AnswerDialer::dialer.Adaptation::AnswerDialer::anonymous.UnaryMemFunTAdaptation::Initiator, HttpMsg*::arg1', which is of non-class type 'HttpMsg*' Initiate.cc: In member function 'void Adaptation::Initiate::sendAnswer(HttpMsg*)': Initiate.cc:94: error: 'answer' was not declared in this scope make[4]: *** [Initiate.lo] Error 1 make[4]: *** Waiting for unfinished jobs libtool: compile: g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../src -I../../include -I../../libltdl -I/usr/include/libxml2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Werror -D_REENTRANT -m64 -O2 -g -m64 -mtune=generic -c Initiator.cc -o Initiator.o /dev/null 21 make[4]: Leaving directory `/usr/src/redhat/BUILD/squid-3.1.12.3/src/adaptation' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/squid-3.1.12.3/src/adaptation' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/squid-3.1.12.3/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/squid-3.1.12.3/src' make: *** [all-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.34664 (%build) If I reverse that patch, Squid compiles OK. Thoughts? - Lindsay
