Kconfig 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199
  1. #
  2. # IPv6 configuration
  3. #
  4. # IPv6 as module will cause a CRASH if you try to unload it
  5. config IPV6
  6. tristate "The IPv6 protocol"
  7. default m
  8. ---help---
  9. This is complemental support for the IP version 6.
  10. You will still be able to do traditional IPv4 networking as well.
  11. For general information about IPv6, see
  12. <http://playground.sun.com/pub/ipng/html/ipng-main.html>.
  13. For Linux IPv6 development information, see <http://www.linux-ipv6.org>.
  14. For specific information about IPv6 under Linux, read the HOWTO at
  15. <http://www.bieringer.de/linux/IPv6/>.
  16. To compile this protocol support as a module, choose M here: the
  17. module will be called ipv6.
  18. config IPV6_PRIVACY
  19. bool "IPv6: Privacy Extensions support"
  20. depends on IPV6
  21. ---help---
  22. Privacy Extensions for Stateless Address Autoconfiguration in IPv6
  23. support. With this option, additional periodically-alter
  24. pseudo-random global-scope unicast address(es) will assigned to
  25. your interface(s).
  26. We use our standard pseudo random algorithm to generate randomized
  27. interface identifier, instead of one described in RFC 3041.
  28. By default, kernel do not generate temporary addresses.
  29. To use temporary addresses, do
  30. echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr
  31. See <file:Documentation/networking/ip-sysctl.txt> for details.
  32. config IPV6_ROUTER_PREF
  33. bool "IPv6: Router Preference (RFC 4191) support"
  34. depends on IPV6
  35. ---help---
  36. Router Preference is an optional extension to the Router
  37. Advertisement message to improve the ability of hosts
  38. to pick more appropriate router, especially when the hosts
  39. is placed in a multi-homed network.
  40. If unsure, say N.
  41. config IPV6_ROUTE_INFO
  42. bool "IPv6: Route Information (RFC 4191) support (EXPERIMENTAL)"
  43. depends on IPV6_ROUTER_PREF && EXPERIMENTAL
  44. ---help---
  45. This is experimental support of Route Information.
  46. If unsure, say N.
  47. config INET6_AH
  48. tristate "IPv6: AH transformation"
  49. depends on IPV6
  50. select XFRM
  51. select CRYPTO
  52. select CRYPTO_HMAC
  53. select CRYPTO_MD5
  54. select CRYPTO_SHA1
  55. ---help---
  56. Support for IPsec AH.
  57. If unsure, say Y.
  58. config INET6_ESP
  59. tristate "IPv6: ESP transformation"
  60. depends on IPV6
  61. select XFRM
  62. select CRYPTO
  63. select CRYPTO_HMAC
  64. select CRYPTO_MD5
  65. select CRYPTO_CBC
  66. select CRYPTO_SHA1
  67. select CRYPTO_DES
  68. ---help---
  69. Support for IPsec ESP.
  70. If unsure, say Y.
  71. config INET6_IPCOMP
  72. tristate "IPv6: IPComp transformation"
  73. depends on IPV6
  74. select XFRM
  75. select INET6_XFRM_TUNNEL
  76. select CRYPTO
  77. select CRYPTO_DEFLATE
  78. ---help---
  79. Support for IP Payload Compression Protocol (IPComp) (RFC3173),
  80. typically needed for IPsec.
  81. If unsure, say Y.
  82. config IPV6_MIP6
  83. bool "IPv6: Mobility (EXPERIMENTAL)"
  84. depends on IPV6 && EXPERIMENTAL
  85. select XFRM
  86. ---help---
  87. Support for IPv6 Mobility described in RFC 3775.
  88. If unsure, say N.
  89. config INET6_XFRM_TUNNEL
  90. tristate
  91. select INET6_TUNNEL
  92. default n
  93. config INET6_TUNNEL
  94. tristate
  95. default n
  96. config INET6_XFRM_MODE_TRANSPORT
  97. tristate "IPv6: IPsec transport mode"
  98. depends on IPV6
  99. default IPV6
  100. select XFRM
  101. ---help---
  102. Support for IPsec transport mode.
  103. If unsure, say Y.
  104. config INET6_XFRM_MODE_TUNNEL
  105. tristate "IPv6: IPsec tunnel mode"
  106. depends on IPV6
  107. default IPV6
  108. select XFRM
  109. ---help---
  110. Support for IPsec tunnel mode.
  111. If unsure, say Y.
  112. config INET6_XFRM_MODE_BEET
  113. tristate "IPv6: IPsec BEET mode"
  114. depends on IPV6
  115. default IPV6
  116. select XFRM
  117. ---help---
  118. Support for IPsec BEET mode.
  119. If unsure, say Y.
  120. config INET6_XFRM_MODE_ROUTEOPTIMIZATION
  121. tristate "IPv6: MIPv6 route optimization mode (EXPERIMENTAL)"
  122. depends on IPV6 && EXPERIMENTAL
  123. select XFRM
  124. ---help---
  125. Support for MIPv6 route optimization mode.
  126. config IPV6_SIT
  127. tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
  128. depends on IPV6
  129. select INET_TUNNEL
  130. default y
  131. ---help---
  132. Tunneling means encapsulating data of one protocol type within
  133. another protocol and sending it over a channel that understands the
  134. encapsulating protocol. This driver implements encapsulation of IPv6
  135. into IPv4 packets. This is useful if you want to connect two IPv6
  136. networks over an IPv4-only path.
  137. Saying M here will produce a module called sit.ko. If unsure, say Y.
  138. config IPV6_TUNNEL
  139. tristate "IPv6: IPv6-in-IPv6 tunnel"
  140. select INET6_TUNNEL
  141. depends on IPV6
  142. ---help---
  143. Support for IPv6-in-IPv6 tunnels described in RFC 2473.
  144. If unsure, say N.
  145. config IPV6_MULTIPLE_TABLES
  146. bool "IPv6: Multiple Routing Tables"
  147. depends on IPV6 && EXPERIMENTAL
  148. select FIB_RULES
  149. ---help---
  150. Support multiple routing tables.
  151. config IPV6_SUBTREES
  152. bool "IPv6: source address based routing"
  153. depends on IPV6_MULTIPLE_TABLES
  154. ---help---
  155. Enable routing by source address or prefix.
  156. The destination address is still the primary routing key, so mixing
  157. normal and source prefix specific routes in the same routing table
  158. may sometimes lead to unintended routing behavior. This can be
  159. avoided by defining different routing tables for the normal and
  160. source prefix specific routes.
  161. If unsure, say N.