he reply/info.
Nick
--
Nick Fennell
n...@tbfh.org
On 12 Feb 2013, at 10:08, Amos Jeffries wrote:
> On 12/02/2013 10:31 p.m., Nick Fennell wrote:
>> Hey Amos.
>>
>> I was waiting for that!
>>
>> We have a few requirements not yet satisfied in Squid 3.x, storeurl_r
ou aware of any bugs that may cause sibling_hit
to be ineffective. I saw on the Lusca project that their code had an issue
preventing the mark from ever being applied. I wonder if Squid suffers with a
similar fault.
Nick
--
Nick Fennell
n...@tbfh.org
On 12 Feb 2013, at 02:05, Amos Jeffries wro
zph_local 0x30
zph_sibling 0x31
}}}
I can see traffic tagged as 0x30 from both units however, I see no traffic
marked with 0x31. Nothing at all.
The closest reference to my issue is here,
http://www.squid-cache.org/mail-archive/squid-users/201201/0364.html
Any suggestions appreciated.
Many Thanks,
Hi Mustafa,
Is it only a single site you are having issues with? All other sites working OK?
What type of WCCP deployment have you gone for? Web-Cache or TPROXY with WCCP
service groups?
Nick
--
Nick Fennell
n...@tbfh.org
On 13 Dec 2012, at 20:28, Mustafa Raji wrote:
> hi
> i have a p
other.
My suggestion: Bypass TPROXY for LAN traffic.
Nick
--
Nick Fennell
n...@tbfh.org
On 28 Nov 2012, at 16:12, Steve Hill wrote:
> On 28.11.12 13:30, Nick Fennell wrote:
>
>> The route needs to be Symmetric.
>>
>> The way I work round this behaviour is to have the Sq
at 15:53, Bruno de Oliveira Bastos
wrote:
> Yes, my adsl is 192.168.1.1 and my network lan is 192.168.1.2.
>
> 2012/11/27 Nick Fennell :
>> What is your default route address?
>>
>> Are your LAN and ADSL links sharing the same subnet?
>>
>> Can you pro
What is your default route address?
Are your LAN and ADSL links sharing the same subnet?
Can you provide more information on interface names and subnet addressing?
Thanks.
Nick
--
On 27 Nov 2012, at 10:52, Bruno de Oliveira Bastos
wrote:
> Hi, i am using the squid 3.1.10, and i have 3 links
A rule set like the below may help;
iptables -I INPUT -p tcp --dport 3128 -m state --state NEW -m recent --set
iptables -I INPUT -p tcp --dport 3128 -m state --state NEW -m recent --update
--seconds 60 --hitcount 30 -j DROP
This should new requests being dropped when more than 30 connections hav
