Re: delay required between configuring and binding to an IPv6 address?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 1 Nov 2006, Jeff Haran wrote:
> If I configure an IPv6 address via netlink sockets and then 
> immediately run an application that creates an AF_INET6, TCP socket 
> and tries to bind to that IPv6 address, bind() fails with 
> EADDRNOTAVAIL.
> 
> If I insert a 1 second delay between the configuration of the 
> address and the attempt to bind(), the same thing happens.
> 
> If I insert a 2 second delay, bind() succeeds.
> 
> The only difference is the period of the delay.
> 
> Is this supposed to be happening? If so, what is the required delay 
> period? And why should this be happening?

After you configure the address, it's in "tentative" state until 
duplicate address detection has finished (and should not be used yet).  
This is the likely source of this behaviour.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux