Mauro Tortonesi [EMAIL PROTECTED] writes:
there is another possible solution. reordering the addresses
returned by getaddrinfo so that IPv4 addresses are at the beginning
of the list.
[...]
i think that the best think we can do right now is reordering the
addresses returned by getaddrinfo.
Mauro Tortonesi [EMAIL PROTECTED] writes:
there is another possible solution. reordering the addresses returned by
getaddrinfo so that IPv4 addresses are at the beginning of the list.
Will that cause problems in some setups? I thought there was an RFC
that mandated that the order of records
On Wednesday 20 April 2005 04:47 am, you wrote:
Mauro Tortonesi [EMAIL PROTECTED] writes:
there is another possible solution. reordering the addresses returned by
getaddrinfo so that IPv4 addresses are at the beginning of the list.
Will that cause problems in some setups?
on IPv6-only
::1|:80... failed: No route
to host. Connecting to www.deepspace6.net|192.167.219.83|:80... connected.
HTTP request sent, awaiting response... 200 OK
...
Why does getaddrinfo return records, when Wget specifies
AI_ADDRCONFIG?
that's because your host has a configured IPv6 address (most
of
AI_ADDRCONFIG:
http://dict.regex.info/ipv6/v6ops/2003-10.mail/0146.html
i agree with itojun when he says that AI_ADDRCONFIG semantics is too
vague.
He does make a good point. But, from an application's perspective,
AI_ADDRCONFIG represents an honest effort to spare IPv4-only users
the practical usefulness of
AI_ADDRCONFIG:
http://dict.regex.info/ipv6/v6ops/2003-10.mail/0146.html
i agree with itojun when he says that AI_ADDRCONFIG semantics is too
vague.
He does make a good point. But, from an application's perspective,
AI_ADDRCONFIG represents an honest effort
to www.deepspace6.net|192.167.219.83|:80... connected.
HTTP request sent, awaiting response... 200 OK
...
Why does getaddrinfo return records, when Wget specifies
AI_ADDRCONFIG? It is not a problem in practice, as Wget correctly
handles inability to connect to the first address, but seeing the
error
On Wed, 12 Nov 2003, Hrvoje Niksic wrote:
Mauro Tortonesi [EMAIL PROTECTED] writes:
Wget works well, but it looks ugly because my machine is not
configured for IPv6.
According to OpenGroup's web site, AI_ADDRCONFIG flag should be of use
here. Should I be worried that the getaddrinfo
Hrvoje Niksic wrote:
According to OpenGroup's web site, AI_ADDRCONFIG flag should be of use
here. Should I be worried that the getaddrinfo man page on my (RHL 9)
system doesn't mention AI_ADDRCONFIG?
Yes. The end of OpenGroup's man page says:
IEEE Std 1003.1-2001/Cor 1-2002, item XSH
On Wed, 12 Nov 2003, [iso-8859-2] Dra¾en Kaèar wrote:
Hrvoje Niksic wrote:
According to OpenGroup's web site, AI_ADDRCONFIG flag should be of use
here. Should I be worried that the getaddrinfo man page on my (RHL 9)
system doesn't mention AI_ADDRCONFIG?
Yes. The end of OpenGroup's man
Mauro Tortonesi [EMAIL PROTECTED] writes:
I suppose I can work around the problem by specifying `inet4_only=yes'
in .wgetrc...
Better yet, maybe we should make -4 the default on machines that don't
support AI_ADDRCONFIG and on which creating an AF_INET6 socket fails?
IMHO, no. we should
On Wed, 12 Nov 2003, Hrvoje Niksic wrote:
Mauro Tortonesi [EMAIL PROTECTED] writes:
I suppose I can work around the problem by specifying `inet4_only=yes'
in .wgetrc...
Better yet, maybe we should make -4 the default on machines that don't
support AI_ADDRCONFIG and on which creating
in theory, the user could use --no-inet4 to undo the problem.
However, I agree that this is still suboptimal. So let's add the
socket creation check in main(). The check will only occur on systems
*with* IPv6 in libc, but *without* AI_ADDRCONFIG. The number of those
will dwindle as IPv6 gets
to ftp.deepspace6.net|192.167.215.13|:21... connected.
[...]
Wget works well, but it looks ugly because my machine is not
configured for IPv6.
According to OpenGroup's web site, AI_ADDRCONFIG flag should be of use
here. Should I be worried that the getaddrinfo man page on my (RHL 9)
system doesn't
14 matches
Mail list logo
