Kconfig 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293
  1. #
  2. # IPv6 configuration
  3. #
  4. # IPv6 as module will cause a CRASH if you try to unload it
  5. menuconfig IPV6
  6. tristate "The IPv6 protocol"
  7. default y
  8. ---help---
  9. Support for IP version 6 (IPv6).
  10. For general information about IPv6, see
  11. <https://en.wikipedia.org/wiki/IPv6>.
  12. For specific information about IPv6 under Linux, see
  13. Documentation/networking/ipv6.txt and read the HOWTO at
  14. <http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/>
  15. To compile this protocol support as a module, choose M here: the
  16. module will be called ipv6.
  17. if IPV6
  18. config IPV6_ROUTER_PREF
  19. bool "IPv6: Router Preference (RFC 4191) support"
  20. ---help---
  21. Router Preference is an optional extension to the Router
  22. Advertisement message which improves the ability of hosts
  23. to pick an appropriate router, especially when the hosts
  24. are placed in a multi-homed network.
  25. If unsure, say N.
  26. config IPV6_ROUTE_INFO
  27. bool "IPv6: Route Information (RFC 4191) support"
  28. depends on IPV6_ROUTER_PREF
  29. ---help---
  30. This is experimental support of Route Information.
  31. If unsure, say N.
  32. config IPV6_OPTIMISTIC_DAD
  33. bool "IPv6: Enable RFC 4429 Optimistic DAD"
  34. ---help---
  35. This is experimental support for optimistic Duplicate
  36. Address Detection. It allows for autoconfigured addresses
  37. to be used more quickly.
  38. If unsure, say N.
  39. config INET6_AH
  40. tristate "IPv6: AH transformation"
  41. select XFRM_ALGO
  42. select CRYPTO
  43. select CRYPTO_HMAC
  44. select CRYPTO_MD5
  45. select CRYPTO_SHA1
  46. ---help---
  47. Support for IPsec AH.
  48. If unsure, say Y.
  49. config INET6_ESP
  50. tristate "IPv6: ESP transformation"
  51. select XFRM_ALGO
  52. select CRYPTO
  53. select CRYPTO_AUTHENC
  54. select CRYPTO_HMAC
  55. select CRYPTO_MD5
  56. select CRYPTO_CBC
  57. select CRYPTO_SHA1
  58. select CRYPTO_DES
  59. select CRYPTO_ECHAINIV
  60. ---help---
  61. Support for IPsec ESP.
  62. If unsure, say Y.
  63. config INET6_IPCOMP
  64. tristate "IPv6: IPComp transformation"
  65. select INET6_XFRM_TUNNEL
  66. select XFRM_IPCOMP
  67. ---help---
  68. Support for IP Payload Compression Protocol (IPComp) (RFC3173),
  69. typically needed for IPsec.
  70. If unsure, say Y.
  71. config IPV6_MIP6
  72. tristate "IPv6: Mobility"
  73. select XFRM
  74. ---help---
  75. Support for IPv6 Mobility described in RFC 3775.
  76. If unsure, say N.
  77. config IPV6_ILA
  78. tristate "IPv6: Identifier Locator Addressing (ILA)"
  79. depends on NETFILTER
  80. select LWTUNNEL
  81. ---help---
  82. Support for IPv6 Identifier Locator Addressing (ILA).
  83. ILA is a mechanism to do network virtualization without
  84. encapsulation. The basic concept of ILA is that we split an
  85. IPv6 address into a 64 bit locator and 64 bit identifier. The
  86. identifier is the identity of an entity in communication
  87. ("who") and the locator expresses the location of the
  88. entity ("where").
  89. ILA can be configured using the "encap ila" option with
  90. "ip -6 route" command. ILA is described in
  91. https://tools.ietf.org/html/draft-herbert-nvo3-ila-00.
  92. If unsure, say N.
  93. config INET6_XFRM_TUNNEL
  94. tristate
  95. select INET6_TUNNEL
  96. default n
  97. config INET6_TUNNEL
  98. tristate
  99. default n
  100. config INET6_XFRM_MODE_TRANSPORT
  101. tristate "IPv6: IPsec transport mode"
  102. default IPV6
  103. select XFRM
  104. ---help---
  105. Support for IPsec transport mode.
  106. If unsure, say Y.
  107. config INET6_XFRM_MODE_TUNNEL
  108. tristate "IPv6: IPsec tunnel mode"
  109. default IPV6
  110. select XFRM
  111. ---help---
  112. Support for IPsec tunnel mode.
  113. If unsure, say Y.
  114. config INET6_XFRM_MODE_BEET
  115. tristate "IPv6: IPsec BEET mode"
  116. default IPV6
  117. select XFRM
  118. ---help---
  119. Support for IPsec BEET mode.
  120. If unsure, say Y.
  121. config INET6_XFRM_MODE_ROUTEOPTIMIZATION
  122. tristate "IPv6: MIPv6 route optimization mode"
  123. select XFRM
  124. ---help---
  125. Support for MIPv6 route optimization mode.
  126. config IPV6_VTI
  127. tristate "Virtual (secure) IPv6: tunneling"
  128. select IPV6_TUNNEL
  129. select NET_IP_TUNNEL
  130. depends on INET6_XFRM_MODE_TUNNEL
  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 can be used with xfrm mode tunnel to give
  135. the notion of a secure tunnel for IPSEC and then use routing protocol
  136. on top.
  137. config IPV6_SIT
  138. tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
  139. select INET_TUNNEL
  140. select NET_IP_TUNNEL
  141. select IPV6_NDISC_NODETYPE
  142. default y
  143. ---help---
  144. Tunneling means encapsulating data of one protocol type within
  145. another protocol and sending it over a channel that understands the
  146. encapsulating protocol. This driver implements encapsulation of IPv6
  147. into IPv4 packets. This is useful if you want to connect two IPv6
  148. networks over an IPv4-only path.
  149. Saying M here will produce a module called sit. If unsure, say Y.
  150. config IPV6_SIT_6RD
  151. bool "IPv6: IPv6 Rapid Deployment (6RD)"
  152. depends on IPV6_SIT
  153. default n
  154. ---help---
  155. IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon
  156. mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly
  157. deploy IPv6 unicast service to IPv4 sites to which it provides
  158. customer premise equipment. Like 6to4, it utilizes stateless IPv6 in
  159. IPv4 encapsulation in order to transit IPv4-only network
  160. infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6
  161. prefix of its own in place of the fixed 6to4 prefix.
  162. With this option enabled, the SIT driver offers 6rd functionality by
  163. providing additional ioctl API to configure the IPv6 Prefix for in
  164. stead of static 2002::/16 for 6to4.
  165. If unsure, say N.
  166. config IPV6_NDISC_NODETYPE
  167. bool
  168. config IPV6_TUNNEL
  169. tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
  170. select INET6_TUNNEL
  171. select DST_CACHE
  172. ---help---
  173. Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
  174. RFC 2473.
  175. If unsure, say N.
  176. config IPV6_GRE
  177. tristate "IPv6: GRE tunnel"
  178. select IPV6_TUNNEL
  179. select NET_IP_TUNNEL
  180. depends on NET_IPGRE_DEMUX
  181. ---help---
  182. Tunneling means encapsulating data of one protocol type within
  183. another protocol and sending it over a channel that understands the
  184. encapsulating protocol. This particular tunneling driver implements
  185. GRE (Generic Routing Encapsulation) and at this time allows
  186. encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure.
  187. This driver is useful if the other endpoint is a Cisco router: Cisco
  188. likes GRE much better than the other Linux tunneling driver ("IP
  189. tunneling" above). In addition, GRE allows multicast redistribution
  190. through the tunnel.
  191. Saying M here will produce a module called ip6_gre. If unsure, say N.
  192. config IPV6_FOU
  193. tristate
  194. default NET_FOU && IPV6
  195. config IPV6_FOU_TUNNEL
  196. tristate
  197. default NET_FOU_IP_TUNNELS && IPV6_FOU
  198. select IPV6_TUNNEL
  199. config IPV6_MULTIPLE_TABLES
  200. bool "IPv6: Multiple Routing Tables"
  201. select FIB_RULES
  202. ---help---
  203. Support multiple routing tables.
  204. config IPV6_SUBTREES
  205. bool "IPv6: source address based routing"
  206. depends on IPV6_MULTIPLE_TABLES
  207. ---help---
  208. Enable routing by source address or prefix.
  209. The destination address is still the primary routing key, so mixing
  210. normal and source prefix specific routes in the same routing table
  211. may sometimes lead to unintended routing behavior. This can be
  212. avoided by defining different routing tables for the normal and
  213. source prefix specific routes.
  214. If unsure, say N.
  215. config IPV6_MROUTE
  216. bool "IPv6: multicast routing"
  217. depends on IPV6
  218. ---help---
  219. Experimental support for IPv6 multicast forwarding.
  220. If unsure, say N.
  221. config IPV6_MROUTE_MULTIPLE_TABLES
  222. bool "IPv6: multicast policy routing"
  223. depends on IPV6_MROUTE
  224. select FIB_RULES
  225. help
  226. Normally, a multicast router runs a userspace daemon and decides
  227. what to do with a multicast packet based on the source and
  228. destination addresses. If you say Y here, the multicast router
  229. will also be able to take interfaces and packet marks into
  230. account and run multiple instances of userspace daemons
  231. simultaneously, each one handling a single table.
  232. If unsure, say N.
  233. config IPV6_PIMSM_V2
  234. bool "IPv6: PIM-SM version 2 support"
  235. depends on IPV6_MROUTE
  236. ---help---
  237. Support for IPv6 PIM multicast routing protocol PIM-SMv2.
  238. If unsure, say N.
  239. endif # IPV6