Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # IPv6 configuration |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 3 | # |
| 4 | |
| 5 | # IPv6 as module will cause a CRASH if you try to unload it |
Jan Engelhardt | 0b18542 | 2008-04-13 23:30:47 -0700 | [diff] [blame] | 6 | menuconfig IPV6 |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 7 | tristate "The IPv6 protocol" |
Tom Herbert | de551f2 | 2015-07-13 08:48:00 -0700 | [diff] [blame] | 8 | default y |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 9 | ---help--- |
Tom Herbert | de551f2 | 2015-07-13 08:48:00 -0700 | [diff] [blame] | 10 | Support for IP version 6 (IPv6). |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 11 | |
| 12 | For general information about IPv6, see |
Christian Kujau | 242260f | 2013-02-21 16:43:05 -0800 | [diff] [blame] | 13 | <https://en.wikipedia.org/wiki/IPv6>. |
Tom Herbert | de551f2 | 2015-07-13 08:48:00 -0700 | [diff] [blame] | 14 | For specific information about IPv6 under Linux, see |
| 15 | Documentation/networking/ipv6.txt and read the HOWTO at |
| 16 | <http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/> |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 17 | |
| 18 | To compile this protocol support as a module, choose M here: the |
| 19 | module will be called ipv6. |
| 20 | |
Jan Engelhardt | 0b18542 | 2008-04-13 23:30:47 -0700 | [diff] [blame] | 21 | if IPV6 |
| 22 | |
YOSHIFUJI Hideaki | ebacaaa | 2006-03-20 17:04:53 -0800 | [diff] [blame] | 23 | config IPV6_ROUTER_PREF |
| 24 | bool "IPv6: Router Preference (RFC 4191) support" |
YOSHIFUJI Hideaki | ebacaaa | 2006-03-20 17:04:53 -0800 | [diff] [blame] | 25 | ---help--- |
| 26 | Router Preference is an optional extension to the Router |
Matt LaPlante | 692105b | 2009-01-26 11:12:25 +0100 | [diff] [blame] | 27 | Advertisement message which improves the ability of hosts |
| 28 | to pick an appropriate router, especially when the hosts |
| 29 | are placed in a multi-homed network. |
YOSHIFUJI Hideaki | ebacaaa | 2006-03-20 17:04:53 -0800 | [diff] [blame] | 30 | |
| 31 | If unsure, say N. |
| 32 | |
YOSHIFUJI Hideaki | 70ceb4f | 2006-03-20 17:06:24 -0800 | [diff] [blame] | 33 | config IPV6_ROUTE_INFO |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 34 | bool "IPv6: Route Information (RFC 4191) support" |
| 35 | depends on IPV6_ROUTER_PREF |
YOSHIFUJI Hideaki | 70ceb4f | 2006-03-20 17:06:24 -0800 | [diff] [blame] | 36 | ---help--- |
| 37 | This is experimental support of Route Information. |
| 38 | |
| 39 | If unsure, say N. |
| 40 | |
Neil Horman | 95c385b | 2007-04-25 17:08:10 -0700 | [diff] [blame] | 41 | config IPV6_OPTIMISTIC_DAD |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 42 | bool "IPv6: Enable RFC 4429 Optimistic DAD" |
Neil Horman | 95c385b | 2007-04-25 17:08:10 -0700 | [diff] [blame] | 43 | ---help--- |
| 44 | This is experimental support for optimistic Duplicate |
| 45 | Address Detection. It allows for autoconfigured addresses |
| 46 | to be used more quickly. |
| 47 | |
| 48 | If unsure, say N. |
| 49 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 50 | config INET6_AH |
| 51 | tristate "IPv6: AH transformation" |
Jan Beulich | 7e15252 | 2012-05-15 01:57:44 +0000 | [diff] [blame] | 52 | select XFRM_ALGO |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 53 | select CRYPTO |
| 54 | select CRYPTO_HMAC |
| 55 | select CRYPTO_MD5 |
| 56 | select CRYPTO_SHA1 |
| 57 | ---help--- |
| 58 | Support for IPsec AH. |
| 59 | |
| 60 | If unsure, say Y. |
| 61 | |
| 62 | config INET6_ESP |
| 63 | tristate "IPv6: ESP transformation" |
Jan Beulich | 7e15252 | 2012-05-15 01:57:44 +0000 | [diff] [blame] | 64 | select XFRM_ALGO |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 65 | select CRYPTO |
Herbert Xu | ed58dd4 | 2008-03-04 14:29:21 -0800 | [diff] [blame] | 66 | select CRYPTO_AUTHENC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 67 | select CRYPTO_HMAC |
| 68 | select CRYPTO_MD5 |
Herbert Xu | 6b7326c | 2006-07-30 15:41:01 +1000 | [diff] [blame] | 69 | select CRYPTO_CBC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 70 | select CRYPTO_SHA1 |
| 71 | select CRYPTO_DES |
Thomas Egerer | 32b6170c | 2016-01-25 12:58:44 +0100 | [diff] [blame] | 72 | select CRYPTO_ECHAINIV |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 73 | ---help--- |
| 74 | Support for IPsec ESP. |
| 75 | |
| 76 | If unsure, say Y. |
| 77 | |
| 78 | config INET6_IPCOMP |
| 79 | tristate "IPv6: IPComp transformation" |
Herbert Xu | d2acc34 | 2006-03-28 01:12:13 -0800 | [diff] [blame] | 80 | select INET6_XFRM_TUNNEL |
Herbert Xu | 6fccab6 | 2008-07-25 02:54:40 -0700 | [diff] [blame] | 81 | select XFRM_IPCOMP |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 82 | ---help--- |
| 83 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), |
| 84 | typically needed for IPsec. |
| 85 | |
| 86 | If unsure, say Y. |
| 87 | |
Masahide NAKAMURA | ee53826 | 2006-08-23 19:13:46 -0700 | [diff] [blame] | 88 | config IPV6_MIP6 |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 89 | tristate "IPv6: Mobility" |
Masahide NAKAMURA | ee53826 | 2006-08-23 19:13:46 -0700 | [diff] [blame] | 90 | select XFRM |
| 91 | ---help--- |
| 92 | Support for IPv6 Mobility described in RFC 3775. |
| 93 | |
| 94 | If unsure, say N. |
| 95 | |
Tom Herbert | 65d7ab8 | 2015-08-17 13:42:27 -0700 | [diff] [blame] | 96 | config IPV6_ILA |
| 97 | tristate "IPv6: Identifier Locator Addressing (ILA)" |
Arnd Bergmann | 8cb964d | 2015-12-18 15:37:37 +0100 | [diff] [blame] | 98 | depends on NETFILTER |
Tom Herbert | 65d7ab8 | 2015-08-17 13:42:27 -0700 | [diff] [blame] | 99 | select LWTUNNEL |
| 100 | ---help--- |
| 101 | Support for IPv6 Identifier Locator Addressing (ILA). |
| 102 | |
| 103 | ILA is a mechanism to do network virtualization without |
| 104 | encapsulation. The basic concept of ILA is that we split an |
| 105 | IPv6 address into a 64 bit locator and 64 bit identifier. The |
| 106 | identifier is the identity of an entity in communication |
| 107 | ("who") and the locator expresses the location of the |
| 108 | entity ("where"). |
| 109 | |
| 110 | ILA can be configured using the "encap ila" option with |
| 111 | "ip -6 route" command. ILA is described in |
| 112 | https://tools.ietf.org/html/draft-herbert-nvo3-ila-00. |
| 113 | |
| 114 | If unsure, say N. |
| 115 | |
Herbert Xu | d2acc34 | 2006-03-28 01:12:13 -0800 | [diff] [blame] | 116 | config INET6_XFRM_TUNNEL |
| 117 | tristate |
| 118 | select INET6_TUNNEL |
| 119 | default n |
| 120 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 121 | config INET6_TUNNEL |
Herbert Xu | d2acc34 | 2006-03-28 01:12:13 -0800 | [diff] [blame] | 122 | tristate |
| 123 | default n |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 124 | |
Herbert Xu | b59f45d | 2006-05-27 23:05:54 -0700 | [diff] [blame] | 125 | config INET6_XFRM_MODE_TRANSPORT |
| 126 | tristate "IPv6: IPsec transport mode" |
Herbert Xu | b59f45d | 2006-05-27 23:05:54 -0700 | [diff] [blame] | 127 | default IPV6 |
| 128 | select XFRM |
| 129 | ---help--- |
| 130 | Support for IPsec transport mode. |
| 131 | |
| 132 | If unsure, say Y. |
| 133 | |
| 134 | config INET6_XFRM_MODE_TUNNEL |
| 135 | tristate "IPv6: IPsec tunnel mode" |
Herbert Xu | b59f45d | 2006-05-27 23:05:54 -0700 | [diff] [blame] | 136 | default IPV6 |
| 137 | select XFRM |
| 138 | ---help--- |
| 139 | Support for IPsec tunnel mode. |
| 140 | |
| 141 | If unsure, say Y. |
| 142 | |
Diego Beltrami | 0a69452 | 2006-10-03 23:47:05 -0700 | [diff] [blame] | 143 | config INET6_XFRM_MODE_BEET |
| 144 | tristate "IPv6: IPsec BEET mode" |
Diego Beltrami | 0a69452 | 2006-10-03 23:47:05 -0700 | [diff] [blame] | 145 | default IPV6 |
| 146 | select XFRM |
| 147 | ---help--- |
| 148 | Support for IPsec BEET mode. |
| 149 | |
| 150 | If unsure, say Y. |
| 151 | |
Masahide NAKAMURA | 1d71627 | 2006-08-23 17:59:44 -0700 | [diff] [blame] | 152 | config INET6_XFRM_MODE_ROUTEOPTIMIZATION |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 153 | tristate "IPv6: MIPv6 route optimization mode" |
Masahide NAKAMURA | 1d71627 | 2006-08-23 17:59:44 -0700 | [diff] [blame] | 154 | select XFRM |
| 155 | ---help--- |
| 156 | Support for MIPv6 route optimization mode. |
| 157 | |
Steffen Klassert | ed1efb2 | 2013-08-19 08:07:34 +0200 | [diff] [blame] | 158 | config IPV6_VTI |
| 159 | tristate "Virtual (secure) IPv6: tunneling" |
| 160 | select IPV6_TUNNEL |
Steffen Klassert | 876fc03 | 2014-02-19 13:33:23 +0100 | [diff] [blame] | 161 | select NET_IP_TUNNEL |
Steffen Klassert | ed1efb2 | 2013-08-19 08:07:34 +0200 | [diff] [blame] | 162 | depends on INET6_XFRM_MODE_TUNNEL |
| 163 | ---help--- |
| 164 | Tunneling means encapsulating data of one protocol type within |
| 165 | another protocol and sending it over a channel that understands the |
| 166 | encapsulating protocol. This can be used with xfrm mode tunnel to give |
| 167 | the notion of a secure tunnel for IPSEC and then use routing protocol |
| 168 | on top. |
| 169 | |
Joerg Roedel | 989e5b9 | 2006-10-10 14:47:44 -0700 | [diff] [blame] | 170 | config IPV6_SIT |
| 171 | tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" |
Kazunori MIYAZAWA | c73cb5a | 2007-02-13 12:55:25 -0800 | [diff] [blame] | 172 | select INET_TUNNEL |
Pravin B Shelar | f61dd38 | 2013-03-25 14:50:00 +0000 | [diff] [blame] | 173 | select NET_IP_TUNNEL |
YOSHIFUJI Hideaki | de357cc | 2008-03-15 23:59:18 -0400 | [diff] [blame] | 174 | select IPV6_NDISC_NODETYPE |
Joerg Roedel | 989e5b9 | 2006-10-10 14:47:44 -0700 | [diff] [blame] | 175 | default y |
| 176 | ---help--- |
| 177 | Tunneling means encapsulating data of one protocol type within |
| 178 | another protocol and sending it over a channel that understands the |
| 179 | encapsulating protocol. This driver implements encapsulation of IPv6 |
David S. Miller | 5c5d6da | 2008-04-26 22:50:57 -0700 | [diff] [blame] | 180 | into IPv4 packets. This is useful if you want to connect two IPv6 |
Joerg Roedel | 989e5b9 | 2006-10-10 14:47:44 -0700 | [diff] [blame] | 181 | networks over an IPv4-only path. |
| 182 | |
Pavel Machek | 4737f09 | 2009-06-05 00:44:53 +0200 | [diff] [blame] | 183 | Saying M here will produce a module called sit. If unsure, say Y. |
Joerg Roedel | 989e5b9 | 2006-10-10 14:47:44 -0700 | [diff] [blame] | 184 | |
YOSHIFUJI Hideaki / 吉藤英明 | fa857af | 2009-09-22 23:43:14 +0000 | [diff] [blame] | 185 | config IPV6_SIT_6RD |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 186 | bool "IPv6: IPv6 Rapid Deployment (6RD)" |
| 187 | depends on IPV6_SIT |
YOSHIFUJI Hideaki / 吉藤英明 | fa857af | 2009-09-22 23:43:14 +0000 | [diff] [blame] | 188 | default n |
| 189 | ---help--- |
| 190 | IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon |
| 191 | mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly |
| 192 | deploy IPv6 unicast service to IPv4 sites to which it provides |
| 193 | customer premise equipment. Like 6to4, it utilizes stateless IPv6 in |
| 194 | IPv4 encapsulation in order to transit IPv4-only network |
| 195 | infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 |
| 196 | prefix of its own in place of the fixed 6to4 prefix. |
| 197 | |
| 198 | With this option enabled, the SIT driver offers 6rd functionality by |
| 199 | providing additional ioctl API to configure the IPv6 Prefix for in |
| 200 | stead of static 2002::/16 for 6to4. |
| 201 | |
| 202 | If unsure, say N. |
| 203 | |
YOSHIFUJI Hideaki | de357cc | 2008-03-15 23:59:18 -0400 | [diff] [blame] | 204 | config IPV6_NDISC_NODETYPE |
| 205 | bool |
| 206 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 207 | config IPV6_TUNNEL |
YOSHIFUJI Hideaki | 38fe999 | 2008-03-20 16:13:58 -0700 | [diff] [blame] | 208 | tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" |
Herbert Xu | d2acc34 | 2006-03-28 01:12:13 -0800 | [diff] [blame] | 209 | select INET6_TUNNEL |
Paolo Abeni | 607f725 | 2016-02-12 15:43:54 +0100 | [diff] [blame] | 210 | select DST_CACHE |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 211 | ---help--- |
YOSHIFUJI Hideaki | 38fe999 | 2008-03-20 16:13:58 -0700 | [diff] [blame] | 212 | Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in |
| 213 | RFC 2473. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 214 | |
| 215 | If unsure, say N. |
| 216 | |
xeb@mail.ru | c12b395 | 2012-08-10 00:51:50 +0000 | [diff] [blame] | 217 | config IPV6_GRE |
| 218 | tristate "IPv6: GRE tunnel" |
| 219 | select IPV6_TUNNEL |
Pravin B Shelar | f61dd38 | 2013-03-25 14:50:00 +0000 | [diff] [blame] | 220 | select NET_IP_TUNNEL |
Arnd Bergmann | 8bf42e9 | 2016-05-03 17:19:57 +0200 | [diff] [blame] | 221 | depends on NET_IPGRE_DEMUX |
xeb@mail.ru | c12b395 | 2012-08-10 00:51:50 +0000 | [diff] [blame] | 222 | ---help--- |
| 223 | Tunneling means encapsulating data of one protocol type within |
| 224 | another protocol and sending it over a channel that understands the |
| 225 | encapsulating protocol. This particular tunneling driver implements |
| 226 | GRE (Generic Routing Encapsulation) and at this time allows |
| 227 | encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure. |
| 228 | This driver is useful if the other endpoint is a Cisco router: Cisco |
| 229 | likes GRE much better than the other Linux tunneling driver ("IP |
| 230 | tunneling" above). In addition, GRE allows multicast redistribution |
| 231 | through the tunnel. |
| 232 | |
| 233 | Saying M here will produce a module called ip6_gre. If unsure, say N. |
| 234 | |
Arnd Bergmann | fabb13d | 2016-05-25 16:50:46 +0200 | [diff] [blame] | 235 | config IPV6_FOU |
| 236 | tristate |
| 237 | default NET_FOU && IPV6 |
| 238 | |
| 239 | config IPV6_FOU_TUNNEL |
| 240 | tristate |
| 241 | default NET_FOU_IP_TUNNELS && IPV6_FOU |
Arnd Bergmann | 95e4daa | 2016-05-31 22:42:11 +0200 | [diff] [blame] | 242 | select IPV6_TUNNEL |
Arnd Bergmann | fabb13d | 2016-05-25 16:50:46 +0200 | [diff] [blame] | 243 | |
Ville Nuorvala | 264e91b | 2006-10-16 22:12:21 -0700 | [diff] [blame] | 244 | config IPV6_MULTIPLE_TABLES |
| 245 | bool "IPv6: Multiple Routing Tables" |
Ville Nuorvala | 264e91b | 2006-10-16 22:12:21 -0700 | [diff] [blame] | 246 | select FIB_RULES |
| 247 | ---help--- |
| 248 | Support multiple routing tables. |
| 249 | |
YOSHIFUJI Hideaki | 4e96c2b | 2006-08-23 17:23:39 -0700 | [diff] [blame] | 250 | config IPV6_SUBTREES |
| 251 | bool "IPv6: source address based routing" |
Ville Nuorvala | 264e91b | 2006-10-16 22:12:21 -0700 | [diff] [blame] | 252 | depends on IPV6_MULTIPLE_TABLES |
YOSHIFUJI Hideaki | 4e96c2b | 2006-08-23 17:23:39 -0700 | [diff] [blame] | 253 | ---help--- |
| 254 | Enable routing by source address or prefix. |
| 255 | |
| 256 | The destination address is still the primary routing key, so mixing |
| 257 | normal and source prefix specific routes in the same routing table |
| 258 | may sometimes lead to unintended routing behavior. This can be |
| 259 | avoided by defining different routing tables for the normal and |
| 260 | source prefix specific routes. |
| 261 | |
| 262 | If unsure, say N. |
| 263 | |
YOSHIFUJI Hideaki | 7bc570c | 2008-04-03 09:22:53 +0900 | [diff] [blame] | 264 | config IPV6_MROUTE |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 265 | bool "IPv6: multicast routing" |
| 266 | depends on IPV6 |
YOSHIFUJI Hideaki | 7bc570c | 2008-04-03 09:22:53 +0900 | [diff] [blame] | 267 | ---help--- |
| 268 | Experimental support for IPv6 multicast forwarding. |
| 269 | If unsure, say N. |
| 270 | |
Patrick McHardy | d1db275 | 2010-05-11 14:40:55 +0200 | [diff] [blame] | 271 | config IPV6_MROUTE_MULTIPLE_TABLES |
| 272 | bool "IPv6: multicast policy routing" |
| 273 | depends on IPV6_MROUTE |
| 274 | select FIB_RULES |
| 275 | help |
| 276 | Normally, a multicast router runs a userspace daemon and decides |
| 277 | what to do with a multicast packet based on the source and |
| 278 | destination addresses. If you say Y here, the multicast router |
| 279 | will also be able to take interfaces and packet marks into |
| 280 | account and run multiple instances of userspace daemons |
| 281 | simultaneously, each one handling a single table. |
| 282 | |
| 283 | If unsure, say N. |
| 284 | |
YOSHIFUJI Hideaki | 14fb64e | 2008-04-03 09:22:54 +0900 | [diff] [blame] | 285 | config IPV6_PIMSM_V2 |
Kees Cook | f9ceb16 | 2012-10-02 11:19:49 -0700 | [diff] [blame] | 286 | bool "IPv6: PIM-SM version 2 support" |
YOSHIFUJI Hideaki | 14fb64e | 2008-04-03 09:22:54 +0900 | [diff] [blame] | 287 | depends on IPV6_MROUTE |
| 288 | ---help--- |
| 289 | Support for IPv6 PIM multicast routing protocol PIM-SMv2. |
| 290 | If unsure, say N. |
| 291 | |
David Lebrun | 6c8702c | 2016-11-08 14:57:41 +0100 | [diff] [blame] | 292 | config IPV6_SEG6_INLINE |
| 293 | bool "IPv6: direct Segment Routing Header insertion " |
| 294 | depends on IPV6 |
| 295 | ---help--- |
| 296 | Support for direct insertion of the Segment Routing Header, |
| 297 | also known as inline mode. Be aware that direct insertion of |
| 298 | extension headers (as opposed to encapsulation) may break |
| 299 | multiple mechanisms such as PMTUD or IPSec AH. Use this feature |
| 300 | only if you know exactly what you are doing. |
| 301 | |
| 302 | If unsure, say N. |
| 303 | |
David Lebrun | bf355b8 | 2016-11-08 14:57:42 +0100 | [diff] [blame] | 304 | config IPV6_SEG6_HMAC |
| 305 | bool "IPv6: Segment Routing HMAC support" |
| 306 | depends on IPV6 |
| 307 | select CRYPTO_HMAC |
| 308 | select CRYPTO_SHA1 |
| 309 | select CRYPTO_SHA256 |
| 310 | ---help--- |
| 311 | Support for HMAC signature generation and verification |
| 312 | of SR-enabled packets. |
| 313 | |
| 314 | If unsure, say N. |
| 315 | |
Jan Engelhardt | 0b18542 | 2008-04-13 23:30:47 -0700 | [diff] [blame] | 316 | endif # IPV6 |