Re: RFH: curl, c-ares and ipv6
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: http://www.linux.it/~md/6to4 . -- ciao, Marco signature.asc Description: Digital signature
Re: RFH: curl, c-ares and ipv6
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 test the curl
packages (version 7.18.2-1e1) in experimental[1] and verify that the
test mentioned in #481189 works now? Does it fail on other ipv6
(or other NORMAL) operations?
Here it seems to work fine even with curl 7.18.2-1:
[EMAIL PROTECTED]: curl -v -o /dev/null http://linux-ipv6.org
* About to connect() to linux-ipv6.org port 80 (#0)
* Trying 2001:200:0:1c01:20f:1fff:fe67:32e9... connected
* Connected to linux-ipv6.org (2001:200:0:1c01:20f:1fff:fe67:32e9) port
80 (#0)
GET / HTTP/1.1
User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu) libcurl/7.18.2
OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18
Host: linux-ipv6.org
Accept: */*
HTTP/1.1 200 OK
Date: Thu, 26 Jun 2008 06:40:27 GMT
Server: Apache/2.2.3 (Debian) PHP/4.4.4-8+etch6 mod_ssl/2.2.3
OpenSSL/0.9.8c
Last-Modified: Wed, 19 Sep 2007 06:02:01 GMT
ETag: 108003c-1ba3-c6b2c840
Accept-Ranges: bytes
Content-Length: 7075
Content-Type: text/html
{ [data not shown]
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
100 7075 100 70750 0 2354 0 0:00:03 0:00:03 --:--:--
5537* Connection #0 to host linux-ipv6.org left intact
* Closing connection #0
Cheers,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
Re: RFH: curl, c-ares and ipv6
* 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 patch, too. Could someone with ipv6 connectivity please test the curl packages (version 7.18.2-1e1) in experimental[1] and verify that the test mentioned in #481189 works now? Does it fail on other ipv6 (or other NORMAL) operations? Here it seems to work fine even with curl 7.18.2-1: that is because curl 7.18.2-1 does not do asynchronous dns lookups as c-ares provides them (and are desireable for higher performance) but uses blocking dns lookups that libc offers. Because we took the save solution first (to do synchronous slow lookups in order to get the newest curl into lenny) the reportet bug is closed already (and curl is home free in testing). It would be nicer (and preferend by upstream) if curl was able to do asynchronous lookups AND do it right for ipv6, of course. That is (hopefully) the solution that is in experimental now. /andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFH: curl, c-ares and ipv6
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 port 80 (#0) * Trying 2001:1b10:100::1:1... connected * Connected to public.teleport-iabg.de (2001:1b10:100::1:1) port 80 (#0) GET /test100m.dat HTTP/1.1 User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 c-ares/1.5.2 libidn/1.8 libssh2/0.18 Host: public.teleport-iabg.de Accept: */* HTTP/1.1 200 OK Date: Thu, 26 Jun 2008 07:20:03 GMT Server: Apache/2.2.8 (Debian) DAV/2 SVN/1.4.6 PHP/5.2.5-3+lenny1 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 Last-Modified: Sat, 08 Oct 2005 22:52:07 GMT ETag: 5edfe-640-402a601ed53c0 Accept-Ranges: bytes Content-Length: 104857600 Content-Type: application/x-ns-proxy-autoconfig So it seems to work. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Re: RFH: curl, c-ares and ipv6
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 PROTECTED]:~$ curl -v -o /dev/null http://www.sixxs.net * About to connect() to www.sixxs.net port 80 (#0) * Trying 2001:838:1:1:210:dcff:fe20:7c7c... connected * Connected to www.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) port 80 (#0) GET / HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 c-ares/1.5.2 libidn/1.8 libssh2/0.18 [snip] with: ii curl 7.18.2-1e1 ii libcurl3 7.18.2-1e1 ii libcurl3-gnutls7.18.2-1e1 ii libc-ares2 1.5.2-2 I've also seen that -4 doesn't really force ipv4 resolution and connection: [EMAIL PROTECTED]:~$ curl -4 -v -o /dev/null http://www.sixxs.net * About to connect() to www.sixxs.net port 80 (#0) * Trying 2001:838:1:1:210:dcff:fe20:7c7c... connected * Connected to www.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) port 80 (#0) GET / HTTP/1.1 User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 c-ares/1.5.2 libidn/1.8 libssh2/0.18 is that normal? Cheers, Ciao, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer pgpNRMIXAa36E.pgp Description: PGP signature
Re: RFH: curl, c-ares and ipv6
* 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 that dont get checked yet, as c-ares together with curl are just in the early stages for ipv6. we will need to fix this. can you think of more funny things to test? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
