Hi, On Thu, Jun 11, 2009 at 12:07:18PM +0200, Roland Rosenfeld wrote: > > IPv6 patched privoxy does not have option to disable IPv6 support > > and does not fall back to IPv4 if IPv6 network is unreachable. > > > > My ISP does not correctly route IPv6... > > Wouldn't it be a better solution to fix your IPv6 problems generally > instead of modifying privoxy? Did you think about removing the IPv6 > default route, if your ISP doesn't support IPv6? This should solve > your IPv6 problems for all programs.
http://www.ipv6style.jp/en/news/20070226/ntteast.html > "FLET'S .NET", an IPv6 closed network service currently offered by NTT East, > will continue operation as well. It is closed IPv6 network for own service. Definitely, I disable IPv6 and needless to modify privoxy. > I don't think that an option to disable IPv6 in privoxy would be the > right way trough IPv6 (and we have to migration to IPv6 in the near > future, since we run out of IPv4 addresses). It is true. But we use IPv4 now and for a while. > I'm not sure whether it would be possible to fall back to IPv4 after > some timeout if the IPv6 address doesn't answer. But on the otherhand > the broken AAAA of www.apache.org just showed, that it is necessary to > bring IPv6 into the minds of all administrators. Without someone > running into trouble with broken IPv6, the IPv6 setup will never been > fixed and the migration will take forever... Iceweasel, wget, w3m and so on, has disabling IPv6 (IPv4 only) option. So, it is better that privoxy also has it, I think. -- Regards, dai -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
