For anyone still following along, I’ve since discovered the resolv.conf option
“single-request-reopen” which seems to fix the slowness in every situation
except my squidclient tests e.g. curl and dig +trace.
Currently waiting to get access to an actual proxy client to see if it’s any
better fro
dig +trace results against ISP+other dns services shows 65000+ ms
response time which means that there is something wrong outside of squid.
Eliezer
On 07/03/2016 06:50, Dan Charlesworth wrote:
Alright, we’re getting somewhere.
A plain curl is about as slow as a default squid config curl:
P.S
Alright, we’re getting somewhere.
A plain curl is about as slow as a default squid config curl:
P.S. I sent you a Skype request
---
# time curl http://httpbin.org/ip
{
"origin": "59.167.202.249"
}
real0m5.513s
user0m0.002s
sys 0m0.001s
# time curl http://httpbin.org/ip --proxy h
If you want to somehow use a skype\irc session to see what can be done
without all the hassle of emails back and forth let me know.
Eliezer
On 06/03/2016 13:55, Dan Charlesworth wrote:
For what it's worth, I've now tried disabling IPv6 via sysctl and it
didn't make any difference.
Appreciate
For what it's worth, I've now tried disabling IPv6 via sysctl and it didn't
make any difference.
Appreciate the advice so far. More from me tomorrow.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squ
Yes but!!
We know nothing about the box.
This is not a perfect script at all:
http://ngtech.co.il/squid/ipv6_test.sh
but it verifies if there is a basic ICMP ipv6 access to a publicly
allowed ipv6 icmp host.
And it also sets the dns_v4_first to on automatically.
As I mentioned the first thing
> I've seen the dns issue when IPv6 is not being handled properly. One way to
> test ( ya ya ) is to disable IPv6 via sysctl and see if you still see the
> delays.
Tory___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-c
Hey Amos,
Yeah 30 other happy sites which also have basically identical squid boxes, and
very similar networks.
They did also mention to me that that they had IPv6 going on this network for
quite a while, but switched it off recently (around when this problem started)
due to nothing related to
On 4/03/2016 3:04 p.m., Dan Charlesworth wrote:
> Eliezer,
>
> I haven’t had time to put together a current squid.conf and make it readable,
> remove sensitive stuff. But we don’t have any DNS-related directives set,
> it’s all just defaults for that stuff.
>
FYI:
(squid -k parse 2>&1 ) | g
On 4/03/2016 11:42 a.m., Dan Charlesworth wrote:
> Thanks for your input Eliezer.
>
> I've tested against various public DNS servers at this point so I'm ruling
> out any DNS-server-side problems. The only time there's any timeouts or
> slowness is when the request is going through squid. Doesn't
Eliezer,
I haven’t had time to put together a current squid.conf and make it readable,
remove sensitive stuff. But we don’t have any DNS-related directives set, it’s
all just defaults for that stuff.
As for the other things you asked about:
1. The current resolv.conf looks like this:
```
searc
This is where you need to share your squid.conf..
Also what was the result of the query I mentioned?
Another one to try is:
http://www.squid-cache.org/Doc/config/dns_v4_first/
try adding to the end of squid.conf
dns_v4_first on
All The Bests,
Eliezer
On 04/03/2016 00:42, Dan Charlesworth wrote
Thanks for your input Eliezer.
I've tested against various public DNS servers at this point so I'm ruling
out any DNS-server-side problems. The only time there's any timeouts or
slowness is when the request is going through squid. Doesn't seem to matter
which HTTP server I'm requesting, whether it
Well what I can see is that there are couple queries ID and the issues are:
0x8528: timeout
0x69c2 - timeout
but I am pretty sure that the DNS server that the query is against is:
192.231.203.132:53
So the first thing is to findout what dns servers are defined inside
squid.conf
if you don't ha
14 matches
Mail list logo
