Hi,
Can you test the attached patch? It fixes the problrem for me. Without
this patch, I need to set tcp_outgoing_address to force IPv4 for some
sites.
diff -uNrp squid3-3.1.18.orig/src/comm.cc squid3-3.1.18/src/comm.cc
--- squid3-3.1.18.orig/src/comm.cc 2011-12-03 06:18:46.0 +
++
Hi,
remove the route entrie do the trick.
However, it seems better to pass bindv6only to 0.
With this version of squid, and full ipv6, we experiment some timeout
problems.
With only a local ipv6 address, we experiment this bug.
Do an echo 0 > /proc/sys/net/ipv6/bindv6only, or adjust
/etc/sys
We have just had some problem solving on the squid-users mailing list
for what appears to be this same problem.
The solution found there was to check "ip -6 route" and remove the route
entries (default route is automatic when IPv6 is enabled).
Amos Jeffries
--
To UNSUBSCRIBE, email to debi
Le 02/03/2011 18:17, Luigi Gangitano a écrit :
Hi Jean-Philippe,
can you please report on the status of the dns_v4_fallback in your setup? This
should be set 'on' by default.
Regards,
L
Il giorno 02/mar/2011, alle ore 17.49, Jean-Philippe Menil ha scritto:
Hi,
Experiencing the same proble
Hi Jean-Philippe,
can you please report on the status of the dns_v4_fallback in your setup? This
should be set 'on' by default.
Regards,
L
Il giorno 02/mar/2011, alle ore 17.49, Jean-Philippe Menil ha scritto:
> Hi,
>
> Experiencing the same problem with squid 3.1.11-1 packaged in sid.
> Rec
Hi,
Experiencing the same problem with squid 3.1.11-1 packaged in sid.
Recompile with the option "--disable_ipv6" solve the the problem.
Regards.
--
Jean-Philippe Menil - Pôle réseau Service IRTS
DSI Université de Nantes
jean-philippe.me...@univ-nantes.fr
Tel : 02.53.48.49.27 - Fax : 02.53.48.4
Experiencing the same problem (hosts with more than one record do not
work) with stock install of squid3 3.1.6-1.1 on multiple computers.
NB. bugs.debian.org today has just one address (and works) but
packages.debian.org still has two and security.debian.org also fails with three.
-
Hi,
Sorry for the lack of response, bug submitters don't get email sent to
the bug by default and I hadn't subscribed to the bug!
I tried the patch at
http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-10841.patch
and it doesn't fix things for me.
Regards,
Stephen
--
To UNSUBS
Strange. It's cycling before completing all IPs.
Does this upstream patch related to IP counts help?
http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-10841.patch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
The fact that other sites are working properly with the same access
types indicates a problem outside of Squid which affects it.
ServFail DNS result, PMTU or routing issues come to mind. If one
particular remote IP is inaccessible and the link hanging it can prevent
Squid having time to do fai
Package: squid3
Version: 3.1.6-1
Severity: normal
Tags: ipv6
Hi,
This may of course be due to misconfiguration on my end, in which case
I'm sorry to bother you.
Since the upgrade from squid3 3.1.3-2 to 3.1.6-1,
http://bugs.debian.org is inaccessible; Squid always reports that the
network is ina
11 matches
Mail list logo
