Re: SO_REUSEADDR setsockopt() and SCTP

From: Brian F. G. Bidulock <bidulock@openss7.org>
Date: Fri Feb 11 2005 - 17:03:38 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Anatoly,

SO_REUSEADDR is described by POSIX and is protocol independent.

--brian

On Fri, 11 Feb 2005, 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"
>
>
> 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"?
>
> Thanks,
>
> Anatoly Khusid

-- 
Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org    ¦ world; the unreasonable one persists in  ¦
http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
                        ¦ Therefore  all  progress  depends on the ¦
                        ¦ unreasonable man. -- George Bernard Shaw ¦

Received on Fri Feb 11 17:09:54 2005