1 .\" Copyright (c) 1983, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd connect an SCTP socket with multiple destination addresses
41 .Fn sctp_connectx "int sd" "struct sockaddr *addrs" "int addrcnt" "sctp_assoc_t *id"
45 call attempts to initiate an association to a peer SCTP
47 The call operates similarly to
49 but it also provides the ability to specify multiple destination
50 addresses for the peer.
51 This allows a fault tolerant method
52 of initiating an association.
53 When one of the peers addresses
54 is unreachable, the subsequent listed addresses will also be used
55 to set up the association with the peer.
57 The user also needs to consider that any address listed in an
59 call is also considered "confirmed".
60 A confirmed address is one in
61 which the SCTP transport will trust is a part of the association
62 and it will not send a confirmation heartbeat to it with
65 If the peer SCTP stack does not list one or more of
66 the provided addresses in its response message then
67 the extra addresses sent in the
69 call will be silently discarded from the association.
71 successful completion the provided
74 filled in with the association identification of the newly
77 The call returns 0 on success and -1 upon failure.
81 function can return the following errors:
84 An address listed has an invalid family or no
85 addresses were provided.
87 The size of the address list exceeds the amount of
92 is not a valid descriptor.