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 getaddri
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-o
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 recor
rom 2003 seems to question 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
scussion from 2003 seems to question 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
ting to www.deepspace6.net|2001:1418:13:3::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 AAAA records, when Wget specifies
> AI_ADDRCONFIG?
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? It is not a problem in practice, as Wget correctly
handles inability to connect to the first address, but seeing
they can be reverted with --no-inet4-only. So
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.
On Wed, 12 Nov 2003, Hrvoje Niksic wrote:
> Mauro Tortonesi <[EMAIL PROTECTED]> writes:
>
> > perhaps we can perform a check like this in main: if AI_ADDRCONFIG
> > is not supported AND ipv6 is not supported (e.g. creation of
> > PF_INET6 sockets fails or we do
Mauro Tortonesi <[EMAIL PROTECTED]> writes:
> perhaps we can perform a check like this in main: if AI_ADDRCONFIG
> is not supported AND ipv6 is not supported (e.g. creation of
> PF_INET6 sockets fails or we don't have a global ipv6 address
> configured on one of the i
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
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 c
Mauro Tortonesi <[EMAIL PROTECTED]> writes:
> 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.
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
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
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_A
cting 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)
s
17 matches
Mail list logo
