Re: SO_REUSEADDR setsockopt() and SCTP

From: Kacheong Poon <kacheong.poon@sun.com>
Date: Fri Feb 11 2005 - 20:29:40 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Anatoly Khusid wrote:
> This question deals more with "SCTP Sockets API" draft. I have not seen any
> explanation in this document regarding the usage of SO_REUSEADDR on SCTP
> sockets.
> The following code fails on Solaris 10:
>
>
> ADDR = Some valid address to bind
> fd1 = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP);
> setsockopt(fd1, SOL_SOCKET, SO_REUSEADDR)
> bind(fd1, ADDR)
> fd2 = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP);
> setsockopt(fd2, SOL_SOCKET, SO_REUSEADDR)
> bind(fd2, ADDR) <=== Fails with errno="Address in use"

The second bind() fails because the first socket is still in bound
state. If the first socket is in, say, established state, the
second bind() will succeed. This is the same behavior as a TCP socket.

> However, the above code works fine on Linux SLES9. Does it mean that Linux
> has a bug, or this is something implementation dependent?
> What is the right behavior for SO_REUSEADDR on SCTP sockets?
> Do you think this should be explained/documented in "SCTP Sockets API"?

-- 
						K. Poon.
						kacheong.poon@sun.com

Received on Fri Feb 11 20:33:46 2005