>>>>> On Fri, 22 Jun 2001 16:51:25 -0300,
>>>>> [EMAIL PROTECTED] said:
>> >> for example: on linux system, if you would like to turn IPV6_V6ONLY
>> >> option on, you can only accept IPv6 traffic with getaddrinfo(3) loop.
>> >If that changes were done, turning IPV6_V6ONLY on would not be frequently d=
>> >one.
>> if you want to see IPv4 traffic on AF_INET socket (so that we don't
>> get confused by bogus source address, and generating bogus traffic
>> when responding) you will want to do IPV6_V6ONLY.
> Yes, maybe a flag telling that the old behaviour should be used would be need
> to be added too.
Then we'll see unreadable conditionals or ifdef tricks. I'd rather
prefer just skipping possible errors against multiple calls of bind(2)
for each addrinfo element returned by getaddrinfo(3), as itojun
suggested. If we take this approach, though, then we'll need one
constraint of getaddrinfo(3); it should return the AF_INET6 wildcard
address before the AF_INET one on those stacks that do not allow
conflict of an AF_INET6 wildcard socket and an AF_INET one.
(Otherwise, the already bound AF_INET socket would reject binding the
AF_INET6 one, and we would not receive IPv6 packets.)
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
