Prameet:
On Fri, 16 Mar 2007, Prameet Chhabra wrote:
when I run the sctpserv01 and sctpclient01 (downloaded the sample code from the book "UNIX Network Programming, Volume 1, Third edition" by W. Richard Stevens), the sctpserv01 failed at Sctp_sendmsg with error "Address Already in Use".
I don't have the book handy, but I think it is because the application is using sctp_sendmsg() on one-to-many for establishing the association and also after it has been established. sctp_sendmsg() doesn't take an assoc id, so it is not appropriate on a one to many (I think our man page was modified to state this). sctp_send() with the assoc. id is be the more appropriate none. (The "address already in use" error is because subsequent sctp_sendmsg() with the same address etc. tries to initiate another association).
Also, it was discovered that there is need to use bind before sctp_bindxvwhich, did not mentioned anywhere except the man page of sctp_bindx on Solaris 10, which seems not match with the book.
The earlier socket drafts specified sctp_bindx() to add address(es) to an already existing bound socket. Thus implying a previous bind(). I know there were discussions (in the SCTP working group) that sctp_bindx() should be allowed by itself, but I am not sure if there was an outcome as such. Kacheong, is this something that will be clarified in subsequent drafts (draft 14 seems to be similar to draft 11 in this regard?).
I really appreciate if you can help me to get some sample code for mulithoming sctp application. The Programming Interface Guide gives one example but it is one-to-one, not one-to-many style we need here.
The socket draft[1] has an example for one-to-many. I think what is is missing from your example is using sctp_send() with the association id (i.e after the assoc is established). If you send your example across, I can have a look and modify, if required, and send it back to you. -venu [1]http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-14.txt
please comment... _______________________________________________ networking-discuss mailing list [email protected]
_______________________________________________ networking-discuss mailing list [email protected]
