Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
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 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.
Yes I think that's correct. With "wget", the order of the addresses for "www.heise.de" does change depending on whether the client system has ipv6 or not. This raises the question how exactly an application detects weather a Linux system "has ipv6 or not".
Yes, I was thinking about that too. I don't think it's up to the application though, I'm sure it's in the name resolution, i.e. getaddrinfo() and therefore controlled by gai.conf. An IPv6-aware application would use getaddrinfo() with AF_UNSPEC to get both addresses, but the ordering is determined by getaddrinfo().
I think, standard openSUSE installations activate IPv4 and IPv6 on all interfaces.
Yes that is the default.
Network cards need to find a RADVD or DHCPv6 server in order to get a valid IPv6 configuration.
Or have a static config.
Having a running RADVD or DHCPv6 server on the router or somewhere else in the LAN does not necessary mean, that the Internet provider offers IPv6 connectivity.
Definitely correct.
Also a temporary situation may change from time to time.
Absolutely - it's easily done with RADVD. Add/remove a client link-local address to/from the clients{} section of radvd.conf, then the client will be with or without IPv6. -- Per Jessen, Zürich (16.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org