[squid-users] squid ipv6 tcp_outgoing limitation ??

Amos Jeffries squid3 at treenet.co.nz
Tue Oct 28 00:29:49 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25/10/2014 11:11 a.m., Ahmed Allzaeem wrote:
> Hi ,
> 
> Recently I used squid 3.4.3 for ipv6 for tcp_outgoing for many
> ipv6 addresses based on the username.
> 
> 
> 
> 
> 
> I added about 1000 users with 1000 tcp_outgoing address but it
> didn't work ..it always uses the last line in squid.conf with
> tcp_outgoing directive !!
> 
> 
> 
> Does squid has limitation in ipv6 ?
> 

Not in this regard.

The only IPv4/IPv6 related limitation in 3.4 is that IPv6 address
cannot be used to contact server IPv4 address and similarly no IPv4
use to contact server IPv6 address.
eg the problem which earlier versions needed to use the special
"ipv6"/"ipv4" ACL matches for is fixed.

More likely the credentials are not available at the time the tests
are being run.


> The question is
> 
> 
> 
> Is it squid issue ?
> 
> Networking issue ?
> 
> Kernel issue ?
> 

Unknown, unknown, unknown. More info is required to diagnose what the
problem is. In particular:

 what does squid.conf contain?

 what server domain *and* IP(s) are being contacted?
  (all of the IPs)

 what does adding "debug_options 28,4 " produce in cache.log?
  (be aware this may have large amount of output, we only need one or
two requests details)

Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUTuN5AAoJELJo5wb/XPRjfngIAIviCYmqTOo5uzoyVAdMkvLv
VDcZ2u8TDy9A86J6OL1thxwpGwUxO0QmkSEuJeVawxBzM9lfy8w0iGT5DICrYfgQ
Gm2YWKxl2MYUIx8NEBOdJGMVk2Yfrs8WZPCDoQaTaK8zcKr8NKiUrEKwLXtw6PZq
xQG5lwTlw3n4j+1vZUzEp8qV2eRenP8tbAKzYNxfOgD7e5kq0pSanFE/y+CwAgwR
4JWqGyUCKJrP3UZKog2H4VqwMw+B0eahDjM+gJ4HZ5XfooHQfY2te+TawXnvazoL
PG+ISeRP7Vf1nyVZd1W3YlHCQ1aBo9J6SWj1VKiucKypSjwVAS9oNJmJsA2gsJA=
=8Yol
-----END PGP SIGNATURE-----


More information about the squid-users mailing list