]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # SCTP configuration | |
3 | # | |
4 | ||
29e32ccd | 5 | menuconfig IP_SCTP |
1da177e4 | 6 | tristate "The SCTP Protocol (EXPERIMENTAL)" |
29e32ccd | 7 | depends on INET && EXPERIMENTAL |
1da177e4 | 8 | depends on IPV6 || IPV6=n |
b7e0fe9f VY |
9 | select CRYPTO |
10 | select CRYPTO_HMAC | |
11 | select CRYPTO_SHA1 | |
1da177e4 | 12 | select CRYPTO_MD5 if SCTP_HMAC_MD5 |
9ad0977f | 13 | select LIBCRC32C |
1da177e4 LT |
14 | ---help--- |
15 | Stream Control Transmission Protocol | |
16 | ||
17 | From RFC 2960 <http://www.ietf.org/rfc/rfc2960.txt>. | |
18 | ||
19 | "SCTP is a reliable transport protocol operating on top of a | |
20 | connectionless packet network such as IP. It offers the following | |
21 | services to its users: | |
22 | ||
23 | -- acknowledged error-free non-duplicated transfer of user data, | |
24 | -- data fragmentation to conform to discovered path MTU size, | |
25 | -- sequenced delivery of user messages within multiple streams, | |
26 | with an option for order-of-arrival delivery of individual user | |
27 | messages, | |
28 | -- optional bundling of multiple user messages into a single SCTP | |
29 | packet, and | |
30 | -- network-level fault tolerance through supporting of multi- | |
31 | homing at either or both ends of an association." | |
32 | ||
33 | To compile this protocol support as a module, choose M here: the | |
34 | module will be called sctp. | |
35 | ||
36 | If in doubt, say N. | |
37 | ||
29e32ccd JE |
38 | if IP_SCTP |
39 | ||
787a51a0 WY |
40 | config NET_SCTPPROBE |
41 | tristate "SCTP: Association probing" | |
42 | depends on PROC_FS && KPROBES | |
43 | ---help--- | |
44 | This module allows for capturing the changes to SCTP association | |
45 | state in response to incoming packets. It is used for debugging | |
46 | SCTP congestion control algorithms. If you don't understand | |
47 | what was just said, you don't need it: say N. | |
48 | ||
49 | To compile this code as a module, choose M here: the | |
50 | module will be called sctp_probe. | |
51 | ||
1da177e4 LT |
52 | config SCTP_DBG_MSG |
53 | bool "SCTP: Debug messages" | |
1da177e4 LT |
54 | help |
55 | If you say Y, this will enable verbose debugging messages. | |
56 | ||
57 | If unsure, say N. However, if you are running into problems, use | |
58 | this option to gather detailed trace information | |
59 | ||
60 | config SCTP_DBG_OBJCNT | |
61 | bool "SCTP: Debug object counts" | |
c4e85f82 | 62 | depends on PROC_FS |
1da177e4 LT |
63 | help |
64 | If you say Y, this will enable debugging support for counting the | |
65 | type of objects that are currently allocated. This is useful for | |
c4e85f82 | 66 | identifying memory leaks. This debug information can be viewed by |
1da177e4 LT |
67 | 'cat /proc/net/sctp/sctp_dbg_objcnt' |
68 | ||
69 | If unsure, say N | |
70 | ||
71 | choice | |
72 | prompt "SCTP: Cookie HMAC Algorithm" | |
1da177e4 LT |
73 | default SCTP_HMAC_MD5 |
74 | help | |
75 | HMAC algorithm to be used during association initialization. It | |
76 | is strongly recommended to use HMAC-SHA1 or HMAC-MD5. See | |
77 | configuration for Cryptographic API and enable those algorithms | |
78 | to make usable by SCTP. | |
79 | ||
80 | config SCTP_HMAC_NONE | |
81 | bool "None" | |
82 | help | |
83 | Choosing this disables the use of an HMAC during association | |
84 | establishment. It is advised to use either HMAC-MD5 or HMAC-SHA1. | |
85 | ||
86 | config SCTP_HMAC_SHA1 | |
87 | bool "HMAC-SHA1" | |
88 | help | |
89 | Enable the use of HMAC-SHA1 during association establishment. It | |
90 | is advised to use either HMAC-MD5 or HMAC-SHA1. | |
91 | ||
92 | config SCTP_HMAC_MD5 | |
93 | bool "HMAC-MD5" | |
94 | help | |
95 | Enable the use of HMAC-MD5 during association establishment. It is | |
96 | advised to use either HMAC-MD5 or HMAC-SHA1. | |
97 | ||
98 | endchoice | |
29e32ccd JE |
99 | |
100 | endif # IP_SCTP |