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. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
39 .Nd connect an sctp socket with multiple destination addresses.
47 .Fn sctp_connectx "int s" "struct sockaddr *" "int addrcnt"
51 call attempts to initiate an association to a peer SCTP
52 endpoint. The call operates similarly to
54 but it also provides the ability to specify multiple destination
55 addresses for the peer. This allows a fault tolerant method
56 of initiating an association. When one of the peers addresses
57 is unreachable, the subsequent listed addresses will also be used
58 to setup the association with the peer.
60 The user also needs to consider that any address listed in an
62 call is also consider "confirmed".
63 A confirmed address is one in
64 which the SCTP transport will trust is a part of the association
65 and it will not send a confirmation heartbeat to it with
68 If the peer SCTP stack does not list one or more of
69 the provided addresses in its response message then
70 the extra addresses sent in the
72 call will be silently discarded from the association.
74 The call returns 0 on success and -1 upon failure.
78 can return the following errors.
81 An address listed has an invalid family or no
82 addresses were provided.
84 The size of the address list exceeds the amount of
89 is not a valid descriptor.