On Jun 26, Andreas Schuldei [EMAIL PROTECTED] wrote:
Could someone with ipv6 connectivity please test the curl
packages (version 7.18.2-1e1) in experimental[1] and verify that the
Everybody can have IPv6 connectivity, just download and run (on a
non-NAT'ed host) this script:
On jeu, 2008-06-26 at 00:28 +0200, Andreas Schuldei wrote:
Hi!
As a solution for #481189 curl: cannot connect to IPv6 hosts
anymore I added a patch to hook curl to c-ares even for ipv6
lookups. Upstream is very interested in this patch, too.
Could someone with ipv6 connectivity please
* Yves-Alexis Perez ([EMAIL PROTECTED]) [080626 08:42]:
On jeu, 2008-06-26 at 00:28 +0200, Andreas Schuldei wrote:
Hi!
As a solution for #481189 curl: cannot connect to IPv6 hosts
anymore I added a patch to hook curl to c-ares even for ipv6
lookups. Upstream is very interested in this
On jeu, 2008-06-26 at 08:41 +0200, Yves-Alexis Perez wrote:
Here it seems to work fine even with curl 7.18.2-1:
Hmhm well. Ok. With curl 7.8.12-1e1 and libcares:
[EMAIL PROTECTED]: curl -v -o /dev/null
http://public.teleport-iabg.de/test100m.dat
* About to connect() to public.teleport-iabg.de
Yves-Alexis Perez scrisse:
On jeu, 2008-06-26 at 08:41 +0200, Yves-Alexis Perez wrote:
Here it seems to work fine even with curl 7.18.2-1:
Hmhm well. Ok. With curl 7.8.12-1e1 and libcares:
So it seems to work.
Rebuilt from incoming for i386, it seems to work here too:
[EMAIL
* Luca Bruno ([EMAIL PROTECTED]) [080626 09:57]:
Rebuilt from incoming for i386, it seems to work here too:
good. thanks!
I've also seen that -4 doesn't really force ipv4 resolution and connection:
great that you thought of testing that, too. It is entirely
possible that there are more cases
Hi!
As a solution for #481189 curl: cannot connect to IPv6 hosts
anymore I added a patch to hook curl to c-ares even for ipv6
lookups. Upstream is very interested in this patch, too.
Could someone with ipv6 connectivity please test the curl
packages (version 7.18.2-1e1) in experimental[1] and
7 matches
Mail list logo
