Re: broken IPv6 code (attached exampled app)
>> option a: kernel forbids bind(0.0.0.0) after bind(::), but
>> bind(::) after bind(0.0.0.0) is okay
>> option b: kernel forbids bind(::) after bind(0.0.0.0)
>> bind(0.0.0.0) after bind(::) is okay
>> option c: only one of them is allowed
>> option d: kernel works okay with any order
>That's what I am doing now, but I am just ignoring this specific case: IPv4 bind
>causing error 98 ("Address already in use"). Should it be ignored for other
>cases too ? Is there any system that does (a) or (b) ? At the moment, my
>handling seems to be OK for Linux (seems to do 1 + c according to YOSHIFUJI
>Hideaki) and KAME, which seems to do 1 + d. Are there other combinations
>implemented ?
if i remember correctly, BSD/OS 4.2 (and possibly 4.1) does (a).
itojun
Reply to: