I did some research and found bug #555210 which changed to the behaviour
reported here. Here's a workaround:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/555210/comments/10
--
IPv4 addresses come sorted before IPv6 ones if you ask libc in teredo
environment.
https://bugs.launchpad.net/
I got the authoritative answer from glibc team and unfortunately we have
to treat such a behavior as "feature" rather than a "bug".
--
IPv4 addresses come sorted before IPv6 ones if you ask libc in teredo
environment.
https://bugs.launchpad.net/bugs/584243
You received this bug notification beca
It's the same issue with 6to4 tunnel as well. I was wondering why my
applications don't use ipv6 and I also found that getaddinfo() is
returning ipv4 addresses before ipv6. So my 6to4 tunnel is useless
because applications don't use ipv6 unless I explicitly instruct them to
do so (eg. use ssh -6 or
Yes, this is intentional behaviour, teredo addresses have lower
reliability than native v6 mechanisms and in general lower than ipv4, so
it makes sense to give them lower priority too.
** Changed in: eglibc (Ubuntu)
Status: New => Invalid
--
IPv4 addresses come sorted before IPv6 ones if
** Attachment added: "getaddr_binary.zip"
http://launchpadlibrarian.net/48926075/getaddr_binary.zip
--
IPv4 addresses come sorted before IPv6 ones if you ask libc in teredo
environment.
https://bugs.launchpad.net/bugs/584243
You received this bug notification because you are a member of Ubun
** Attachment added: "getaddr_source.zip"
http://launchpadlibrarian.net/48926053/getaddr_source.zip
--
IPv4 addresses come sorted before IPv6 ones if you ask libc in teredo
environment.
https://bugs.launchpad.net/bugs/584243
You received this bug notification because you are a member of Ubun
