Nothing wrong with any of this, afaict. On your apache system, perhaps try retrieving URLs with wget and see what happens. On my 13.2 systems, wget will choose ipv4 when there's no ipv6.
If you have the default gai.conf, and you have ipv4 connectivity, there is no reason for apache to attempt to use ipv6. OK. I had to change the router firmware because of issues with the OpenWRT 10.03.1 firmware. So probably, the IPv6 issue goes away with
Per Jessen wrote: the OpenWRT 10.03.1 firmware. Probably the issue was, that dnsmasq from OpenWRT 10.03.1 changed the sorting of A (IPv4) and AAAA (IPv6) DNS replies. And if Apache gets the AAAA first and then A, it will probably try to connect the AAAA address first. If my Linux box answers this immediately with "Network is unreachable" (see routing table with no IPv6 default route), Apache continues with IPv4 milliseconds later. If both A and AAAA addresses can't connect, Apache will log one or both of the addresses. And IPv6 addresses in logs confuse the users, if there is no IPv6 connectivity. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org