Kconfig 9.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342
  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_ESP_OFFLOAD
  64. tristate "IPv6: ESP transformation offload"
  65. depends on INET6_ESP
  66. select XFRM_OFFLOAD
  67. default n
  68. ---help---
  69. Support for ESP transformation offload. This makes sense
  70. only if this system really does IPsec and want to do it
  71. with high throughput. A typical desktop system does not
  72. need it, even if it does IPsec.
  73. If unsure, say N.
  74. config INET6_IPCOMP
  75. tristate "IPv6: IPComp transformation"
  76. select INET6_XFRM_TUNNEL
  77. select XFRM_IPCOMP
  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. tristate "IPv6: Mobility"
  84. select XFRM
  85. ---help---
  86. Support for IPv6 Mobility described in RFC 3775.
  87. If unsure, say N.
  88. config IPV6_ILA
  89. tristate "IPv6: Identifier Locator Addressing (ILA)"
  90. depends on NETFILTER
  91. select LWTUNNEL
  92. ---help---
  93. Support for IPv6 Identifier Locator Addressing (ILA).
  94. ILA is a mechanism to do network virtualization without
  95. encapsulation. The basic concept of ILA is that we split an
  96. IPv6 address into a 64 bit locator and 64 bit identifier. The
  97. identifier is the identity of an entity in communication
  98. ("who") and the locator expresses the location of the
  99. entity ("where").
  100. ILA can be configured using the "encap ila" option with
  101. "ip -6 route" command. ILA is described in
  102. https://tools.ietf.org/html/draft-herbert-nvo3-ila-00.
  103. If unsure, say N.
  104. config INET6_XFRM_TUNNEL
  105. tristate
  106. select INET6_TUNNEL
  107. default n
  108. config INET6_TUNNEL
  109. tristate
  110. default n
  111. config INET6_XFRM_MODE_TRANSPORT
  112. tristate "IPv6: IPsec transport mode"
  113. default IPV6
  114. select XFRM
  115. ---help---
  116. Support for IPsec transport mode.
  117. If unsure, say Y.
  118. config INET6_XFRM_MODE_TUNNEL
  119. tristate "IPv6: IPsec tunnel mode"
  120. default IPV6
  121. select XFRM
  122. ---help---
  123. Support for IPsec tunnel mode.
  124. If unsure, say Y.
  125. config INET6_XFRM_MODE_BEET
  126. tristate "IPv6: IPsec BEET mode"
  127. default IPV6
  128. select XFRM
  129. ---help---
  130. Support for IPsec BEET mode.
  131. If unsure, say Y.
  132. config INET6_XFRM_MODE_ROUTEOPTIMIZATION
  133. tristate "IPv6: MIPv6 route optimization mode"
  134. select XFRM
  135. ---help---
  136. Support for MIPv6 route optimization mode.
  137. config IPV6_VTI
  138. tristate "Virtual (secure) IPv6: tunneling"
  139. select IPV6_TUNNEL
  140. select NET_IP_TUNNEL
  141. depends on INET6_XFRM_MODE_TUNNEL
  142. ---help---
  143. Tunneling means encapsulating data of one protocol type within
  144. another protocol and sending it over a channel that understands the
  145. encapsulating protocol. This can be used with xfrm mode tunnel to give
  146. the notion of a secure tunnel for IPSEC and then use routing protocol
  147. on top.
  148. config IPV6_SIT
  149. tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
  150. select INET_TUNNEL
  151. select NET_IP_TUNNEL
  152. select IPV6_NDISC_NODETYPE
  153. default y
  154. ---help---
  155. Tunneling means encapsulating data of one protocol type within
  156. another protocol and sending it over a channel that understands the
  157. encapsulating protocol. This driver implements encapsulation of IPv6
  158. into IPv4 packets. This is useful if you want to connect two IPv6
  159. networks over an IPv4-only path.
  160. Saying M here will produce a module called sit. If unsure, say Y.
  161. config IPV6_SIT_6RD
  162. bool "IPv6: IPv6 Rapid Deployment (6RD)"
  163. depends on IPV6_SIT
  164. default n
  165. ---help---
  166. IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon
  167. mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly
  168. deploy IPv6 unicast service to IPv4 sites to which it provides
  169. customer premise equipment. Like 6to4, it utilizes stateless IPv6 in
  170. IPv4 encapsulation in order to transit IPv4-only network
  171. infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6
  172. prefix of its own in place of the fixed 6to4 prefix.
  173. With this option enabled, the SIT driver offers 6rd functionality by
  174. providing additional ioctl API to configure the IPv6 Prefix for in
  175. stead of static 2002::/16 for 6to4.
  176. If unsure, say N.
  177. config IPV6_NDISC_NODETYPE
  178. bool
  179. config IPV6_TUNNEL
  180. tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
  181. select INET6_TUNNEL
  182. select DST_CACHE
  183. select GRO_CELLS
  184. ---help---
  185. Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
  186. RFC 2473.
  187. If unsure, say N.
  188. config IPV6_GRE
  189. tristate "IPv6: GRE tunnel"
  190. select IPV6_TUNNEL
  191. select NET_IP_TUNNEL
  192. depends on NET_IPGRE_DEMUX
  193. ---help---
  194. Tunneling means encapsulating data of one protocol type within
  195. another protocol and sending it over a channel that understands the
  196. encapsulating protocol. This particular tunneling driver implements
  197. GRE (Generic Routing Encapsulation) and at this time allows
  198. encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure.
  199. This driver is useful if the other endpoint is a Cisco router: Cisco
  200. likes GRE much better than the other Linux tunneling driver ("IP
  201. tunneling" above). In addition, GRE allows multicast redistribution
  202. through the tunnel.
  203. Saying M here will produce a module called ip6_gre. If unsure, say N.
  204. config IPV6_FOU
  205. tristate
  206. default NET_FOU && IPV6
  207. config IPV6_FOU_TUNNEL
  208. tristate
  209. default NET_FOU_IP_TUNNELS && IPV6_FOU
  210. select IPV6_TUNNEL
  211. config IPV6_MULTIPLE_TABLES
  212. bool "IPv6: Multiple Routing Tables"
  213. select FIB_RULES
  214. ---help---
  215. Support multiple routing tables.
  216. config IPV6_SUBTREES
  217. bool "IPv6: source address based routing"
  218. depends on IPV6_MULTIPLE_TABLES
  219. ---help---
  220. Enable routing by source address or prefix.
  221. The destination address is still the primary routing key, so mixing
  222. normal and source prefix specific routes in the same routing table
  223. may sometimes lead to unintended routing behavior. This can be
  224. avoided by defining different routing tables for the normal and
  225. source prefix specific routes.
  226. If unsure, say N.
  227. config IPV6_MROUTE
  228. bool "IPv6: multicast routing"
  229. depends on IPV6
  230. ---help---
  231. Experimental support for IPv6 multicast forwarding.
  232. If unsure, say N.
  233. config IPV6_MROUTE_MULTIPLE_TABLES
  234. bool "IPv6: multicast policy routing"
  235. depends on IPV6_MROUTE
  236. select FIB_RULES
  237. help
  238. Normally, a multicast router runs a userspace daemon and decides
  239. what to do with a multicast packet based on the source and
  240. destination addresses. If you say Y here, the multicast router
  241. will also be able to take interfaces and packet marks into
  242. account and run multiple instances of userspace daemons
  243. simultaneously, each one handling a single table.
  244. If unsure, say N.
  245. config IPV6_PIMSM_V2
  246. bool "IPv6: PIM-SM version 2 support"
  247. depends on IPV6_MROUTE
  248. ---help---
  249. Support for IPv6 PIM multicast routing protocol PIM-SMv2.
  250. If unsure, say N.
  251. config IPV6_SEG6_LWTUNNEL
  252. bool "IPv6: Segment Routing Header encapsulation support"
  253. depends on IPV6
  254. select LWTUNNEL
  255. select DST_CACHE
  256. ---help---
  257. Support for encapsulation of packets within an outer IPv6
  258. header and a Segment Routing Header using the lightweight
  259. tunnels mechanism.
  260. If unsure, say N.
  261. config IPV6_SEG6_INLINE
  262. bool "IPv6: direct Segment Routing Header insertion "
  263. depends on IPV6_SEG6_LWTUNNEL
  264. ---help---
  265. Support for direct insertion of the Segment Routing Header,
  266. also known as inline mode. Be aware that direct insertion of
  267. extension headers (as opposed to encapsulation) may break
  268. multiple mechanisms such as PMTUD or IPSec AH. Use this feature
  269. only if you know exactly what you are doing.
  270. If unsure, say N.
  271. config IPV6_SEG6_HMAC
  272. bool "IPv6: Segment Routing HMAC support"
  273. depends on IPV6
  274. select CRYPTO_HMAC
  275. select CRYPTO_SHA1
  276. select CRYPTO_SHA256
  277. ---help---
  278. Support for HMAC signature generation and verification
  279. of SR-enabled packets.
  280. If unsure, say N.
  281. endif # IPV6