SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] Non-blocking connect call for TCP-style socket


Chronological Thread 
  • From: Thomas Dreibholz <dreibh AT iem.uni-due.de>
  • To: sctp-discussion AT sctp.de
  • Cc: Bipin Chandrapal <mmcbipin AT yahoo.com>
  • Subject: Re: [SCTP-Discussion] Non-blocking connect call for TCP-style socket
  • Date: Fri, 11 Apr 2008 11:28:58 +0100
  • List-archive: <http://lists.franken.de/pipermail/sctp-discussion>
  • List-id: SCTP Discussions <sctp-discussion.sctp.de>
  • Organization: University of Duisburg-Essen

On Mittwoch 09 April 2008, Bipin Chandrapal wrote:
> Hi All,
>
> I am working on both solaris-10 and SUSE-10 operating systems.
> I am trying to write a client program using SCTP sockets of TCP-style.
>
> 1.socket(AF_INET,SOCK_STREAM,IPPROTO_SCTP)
> 2.bind
> 3. Setting the socket to non-block mode using fcntl()
> 4. connect()
> 5. polling on the socket.
>
> On success/failure of the connection, pollout event will come on the
> socket. Then I am getting the SO_ERROR socket option. If it is zero, then
> connection is success. Otherwise connection failed.
>
> This approach is working fine with TCP sockets.
>
> In case of SCTP sockets, on success pollout event is received. But there
> is no event received if the peer does not exist.

This should also work fine with SCTP, too. Using the sctplib/socketapi
implementation, this will work (see the rsplib RSerPool package for example
code: http://tdrwww.iem.uni-due.de/dreibholz/rserpool/). If you are using
Solaris kernel SCTP, this seems to be a bug and you should write to the
Solaris mailing list.


Best regards
--
=======================================================================
Dr. Thomas Dreibholz

University of Duisburg-Essen, Room ES210
Inst. for Experimental Mathematics Ellernstraße 29
Computer Networking Technology Group D-45326 Essen/Germany
-----------------------------------------------------------------------
E-Mail:
dreibh AT iem.uni-due.de
Homepage: http://www.iem.uni-due.de/~dreibh
=======================================================================

Attachment: signature.asc
Description: This is a digitally signed message part.




Archive powered by MHonArc 2.6.19+.

Top of page