On Fri, 6 Feb 2015 11:45:05 +0500 Roman Mamedov wrote: > > Hello, > > On some occasions I was using the directive "tcp_outgoing_address 0.0.0.0" to > force Squid on a dual-stack host to be IPv4-only. > > This works fine on 3.1.20-2.2+deb7u2 currently in Wheezy.
That behaviour was a bug. It caused Squid to use ::ffff:0.0.0.0 on the connections it made to IPv6 hosts. In dual-stack machines that is sometimes an alias-IP for localhost. The forwarding loop this sets up inside the TCP stack goes to a port which is probably closed on your machine. But not necesarily. > > However, this directive is ignored on the 3.4 version from backports. > > Even setting "tcp_outgoing_address [actual IPv4 address of the host]" does not > help, Squid still makes outgoing connections from IPv6 as well. The bug above was fixed in Squid-3.2. IPv4 outgoing addresses are only used for outgoing IPv4 connections. IPv6 outgoing addresses are only used for outgoing IPv6 connections. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
