Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-10-09 08:57, Per Jessen wrote:
Bjoern Voigt wrote:
Carlos E. R. wrote:
Sorry, why would gai.conf need to be changed? :-? A laptop use may connect the laptop in Network1 with IPv6 and IPv4 enabled and later in Network2, where only IPv4 is available. For instance, the German Telekom offers IPv4/IPv6 connectivity for business and home users and some other providers currently only offer IPv4. A laptop user expects, that the laptop network configuration will be automatically adapted by DHCP when he switches the network. Changing gai.conf is AFAIK not a standard feature of the Linux DHCP clients.
I see.
But surely changing gai.conf would only be necessary in those faulty environments where IPv6 addresses are handed out, but where the IPv6 network otherwise doesn't work ?
Well... I don't know what gai.conf is normally intended for, for I suppose that handling missing IPv6 is not the main one :-?
gai.conf controls the behaviour of the getaddrinfo() call. From the man page: A call to getaddrinfo(3) might return multiple answers. According to RFC 3484 these answers must be sorted so that the answer with the highest success rate is first in the list. The RFC provides an algorithm for the sorting. The static rules are not always adequate, though. For this reason, the RFC also requires that system administrators should have the possibility to dynamically change the sorting. For the glibc implementation, this can be achieved with the /etc/gai.conf file. For me, the default gai.conf (empty) has always worked, but I've never been in the situation of a partially crippled ipv6 network. -- Per Jessen, Zürich (11.7°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