Bug#606273: libsoup2.4-1: libsoup prefers IPv4
Le mercredi 08 décembre 2010 à 00:05 +0100, Yves-Alexis Perez a écrit : it seems that libsoup prevents me from having correct IPv6 access. I have a working IPv6 setup, but none of my browser will use it because they are all webkit (and thus libsoup) based. A quick way to reproduce is to go to www.kame.net with midori, epiphany or chromium. The famous “dancing turtle” isn't dancing. I’m afraid I cannot reproduce that with my epiphany installation. I tried www.kame.net and the turtle is dancing. I tried my own website and looked at the logs, and epiphany definitely accessed it using IPv6. Cheers, -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Bug#606273: libsoup2.4-1: libsoup prefers IPv4
On mer., 2010-12-08 at 12:41 +0100, Yves-Alexis Perez wrote: On mer., 2010-12-08 at 09:17 +0100, Josselin Mouette wrote: Le mercredi 08 décembre 2010 à 00:05 +0100, Yves-Alexis Perez a écrit : it seems that libsoup prevents me from having correct IPv6 access. I have a working IPv6 setup, but none of my browser will use it because they are all webkit (and thus libsoup) based. A quick way to reproduce is to go to www.kame.net with midori, epiphany or chromium. The famous “dancing turtle” isn't dancing. I’m afraid I cannot reproduce that with my epiphany installation. I tried www.kame.net and the turtle is dancing. I tried my own website and looked at the logs, and epiphany definitely accessed it using IPv6. Ok, I guess I'm bitten by the fix applied for #468801. My IPv6 addresses are indeed 6to4 and so IPv4 is preferred. That quite sucks, but it's not really libsoup fault. I'm closing the bug for now and will try to tune my gai.conf to fix that, sorry for bothering. Fwiw, adding: scopev4 :::192.168.0.0/112 5 to /etc/gai.conf fixes the problem. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#606273: libsoup2.4-1: libsoup prefers IPv4
Package: libsoup2.4-1 Version: 2.30.2-1 Severity: important Tags: ipv6 Hey, it seems that libsoup prevents me from having correct IPv6 access. I have a working IPv6 setup, but none of my browser will use it because they are all webkit (and thus libsoup) based. A quick way to reproduce is to go to www.kame.net with midori, epiphany or chromium. The famous “dancing turtle” isn't dancing. I've tried the test programs in libsoup sources and it indeed seems that IPv4 is preferred: cor...@hidalgo: getent hosts www.kame.net 2001:200:dff:fff1:216:3eff:feb1:44d7 orange.kame.net www.kame.net cor...@hidalgo: ./dns www.kame.net Name:www.kame.net Address: 203.178.141.194 I think it's a fairly important issue, considering IPv6 is a release goal and IPv4 is likely to fade away during Squeeze life time. Regards, -- Yves-Alexis -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsoup2.4-1 depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr ii libglib2.0-02.27.3-1 The GLib library of C routines ii libgnutls26 2.10.2-1 the GNU TLS library - runtime libr ii libxml2 2.7.8.dfsg-1 GNOME XML library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libsoup2.4-1 recommends no packages. libsoup2.4-1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
