Kconfig 3.23 KB
#
# SCTP configuration
#

menu "SCTP Configuration (EXPERIMENTAL)"
	depends on INET && EXPERIMENTAL

config IPV6_SCTP__
	tristate
	default y if IPV6=n
	default IPV6 if IPV6

config IP_SCTP
	tristate "The SCTP Protocol (EXPERIMENTAL)"
	depends on IPV6_SCTP__
	---help---
	  Stream Control Transmission Protocol

	  From RFC 2960 (http://www.ietf.org/rfc/rfc2960.txt)

	  "SCTP is a reliable transport protocol operating on top of a
	  connectionless packet network such as IP.  It offers the following
	  services to its users:

	  -- acknowledged error-free non-duplicated transfer of user data,
	  -- data fragmentation to conform to discovered path MTU size,
	  -- sequenced delivery of user messages within multiple streams,
	  with an option for order-of-arrival delivery of individual user
	  messages,
	  -- optional bundling of multiple user messages into a single SCTP
	  packet, and
	  -- network-level fault tolerance through supporting of multi-
	  homing at either or both ends of an association."

	  This protocol support is also available as a module ( = code which
	  can be inserted in and removed from the running kernel whenever you
	  want). The module will be called sctp. If you want to compile it
	  as a module, say M here and read <file:Documentation/modules.txt>.

	  If in doubt, say N.

config SCTP_ADLER32
	bool "SCTP: Use old checksum (Adler-32)"
	depends on IP_SCTP
	help
	  RFC2960 currently specifies the Adler-32 checksum algorithm for SCTP.
	  This has been deprecated and replaced by an algorithm now referred
	  to as crc32c.

	  If you say Y, this will use the Adler-32 algorithm, this might be 
	  useful for interoperation with downlevel peers. 

	  If unsure, say N.  

config SCTP_DBG_MSG
	bool "SCTP: Debug messages"
	depends on IP_SCTP
	help
	  If you say Y, this will enable verbose debugging messages. 

	  If unsure, say N.  However, if you are running into problems, use 
	  this option to gather detailed trace information

config SCTP_DBG_OBJCNT
	bool "SCTP: Debug object counts"
	depends on IP_SCTP
	help
	  If you say Y, this will enable debugging support for counting the 
	  type of objects that are currently allocated.  This is useful for 
	  identifying memory leaks.   If the /proc filesystem is enabled this 
	  debug information can be viewed by 
	  'cat /proc/net/sctp/sctp_dbg_objcnt'

	  If unsure, say N

choice
	prompt "SCTP: Cookie HMAC Algorithm"
	depends on IP_SCTP
	help
	  HMAC algorithm to be used during association initialization.  It
	  is strongly recommended to use HMAC-SHA1 or HMAC-MD5.  See 
	  configuration for Cryptographic API and enable those algorithms
          to make usable by SCTP. 

config SCTP_HMAC_NONE
	bool "None"
	help 
	  Choosing this disables the use of an HMAC during association 
	  establishment.  It is advised to use either HMAC-MD5 or HMAC-SHA1.

config SCTP_HMAC_SHA1
	bool "HMAC-SHA1" if CRYPTO_HMAC=y && CRYPTO_SHA1=y || CRYPTO_SHA1=m
	help 
	  Enable the use of HMAC-SHA1 during association establishment.  It 
	  is advised to use either HMAC-MD5 or HMAC-SHA1.

config SCTP_HMAC_MD5
	bool "HMAC-MD5" if CRYPTO_HMAC=y && CRYPTO_MD5=y || CRYPTO_MD5=m
	help
	  Enable the use of HMAC-MD5 during association establishment.  It is 
	  advised to use either HMAC-MD5 or HMAC-SHA1.

endchoice
endmenu