Commit | Line | Data |
---|---|---|
ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
1da177e4 LT |
2 | # |
3 | # IPv6 configuration | |
6a2e9b73 SR |
4 | # |
5 | ||
6 | # IPv6 as module will cause a CRASH if you try to unload it | |
0b18542b | 7 | menuconfig IPV6 |
6a2e9b73 | 8 | tristate "The IPv6 protocol" |
de551f2e | 9 | default y |
ec8f7f48 | 10 | select CRYPTO_LIB_SHA1 |
a7f7f624 | 11 | help |
de551f2e | 12 | Support for IP version 6 (IPv6). |
6a2e9b73 SR |
13 | |
14 | For general information about IPv6, see | |
242260fb | 15 | <https://en.wikipedia.org/wiki/IPv6>. |
de551f2e | 16 | For specific information about IPv6 under Linux, see |
19093313 | 17 | Documentation/networking/ipv6.rst and read the HOWTO at |
7a6498eb | 18 | <https://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/> |
6a2e9b73 | 19 | |
e446a276 | 20 | To compile this protocol support as a module, choose M here: the |
6a2e9b73 SR |
21 | module will be called ipv6. |
22 | ||
0b18542b JE |
23 | if IPV6 |
24 | ||
ebacaaa0 YH |
25 | config IPV6_ROUTER_PREF |
26 | bool "IPv6: Router Preference (RFC 4191) support" | |
a7f7f624 | 27 | help |
ebacaaa0 | 28 | Router Preference is an optional extension to the Router |
692105b8 ML |
29 | Advertisement message which improves the ability of hosts |
30 | to pick an appropriate router, especially when the hosts | |
31 | are placed in a multi-homed network. | |
ebacaaa0 YH |
32 | |
33 | If unsure, say N. | |
34 | ||
70ceb4f5 | 35 | config IPV6_ROUTE_INFO |
f9ceb16e KC |
36 | bool "IPv6: Route Information (RFC 4191) support" |
37 | depends on IPV6_ROUTER_PREF | |
a7f7f624 | 38 | help |
a9f71d0d | 39 | Support of Route Information. |
70ceb4f5 YH |
40 | |
41 | If unsure, say N. | |
42 | ||
95c385b4 | 43 | config IPV6_OPTIMISTIC_DAD |
f9ceb16e | 44 | bool "IPv6: Enable RFC 4429 Optimistic DAD" |
a7f7f624 | 45 | help |
a9f71d0d GH |
46 | Support for optimistic Duplicate Address Detection. It allows for |
47 | autoconfigured addresses to be used more quickly. | |
95c385b4 NH |
48 | |
49 | If unsure, say N. | |
50 | ||
1da177e4 LT |
51 | config INET6_AH |
52 | tristate "IPv6: AH transformation" | |
7d4e3919 | 53 | select XFRM_AH |
a7f7f624 | 54 | help |
be013698 EB |
55 | Support for IPsec AH (Authentication Header). |
56 | ||
57 | AH can be used with various authentication algorithms. Besides | |
58 | enabling AH support itself, this option enables the generic | |
59 | implementations of the algorithms that RFC 8221 lists as MUST be | |
60 | implemented. If you need any other algorithms, you'll need to enable | |
61 | them in the crypto API. You should also enable accelerated | |
62 | implementations of any needed algorithms when available. | |
1da177e4 LT |
63 | |
64 | If unsure, say Y. | |
65 | ||
66 | config INET6_ESP | |
67 | tristate "IPv6: ESP transformation" | |
7d4e3919 | 68 | select XFRM_ESP |
a7f7f624 | 69 | help |
be013698 EB |
70 | Support for IPsec ESP (Encapsulating Security Payload). |
71 | ||
72 | ESP can be used with various encryption and authentication algorithms. | |
73 | Besides enabling ESP support itself, this option enables the generic | |
74 | implementations of the algorithms that RFC 8221 lists as MUST be | |
75 | implemented. If you need any other algorithms, you'll need to enable | |
76 | them in the crypto API. You should also enable accelerated | |
77 | implementations of any needed algorithms when available. | |
1da177e4 LT |
78 | |
79 | If unsure, say Y. | |
80 | ||
7785bba2 SK |
81 | config INET6_ESP_OFFLOAD |
82 | tristate "IPv6: ESP transformation offload" | |
83 | depends on INET6_ESP | |
84 | select XFRM_OFFLOAD | |
85 | default n | |
a7f7f624 | 86 | help |
7785bba2 SK |
87 | Support for ESP transformation offload. This makes sense |
88 | only if this system really does IPsec and want to do it | |
89 | with high throughput. A typical desktop system does not | |
90 | need it, even if it does IPsec. | |
91 | ||
92 | If unsure, say N. | |
93 | ||
26333c37 SD |
94 | config INET6_ESPINTCP |
95 | bool "IPv6: ESP in TCP encapsulation (RFC 8229)" | |
96 | depends on XFRM && INET6_ESP | |
97 | select STREAM_PARSER | |
98 | select NET_SOCK_MSG | |
99 | select XFRM_ESPINTCP | |
100 | help | |
101 | Support for RFC 8229 encapsulation of ESP and IKE over | |
102 | TCP/IPv6 sockets. | |
103 | ||
104 | If unsure, say N. | |
105 | ||
1da177e4 LT |
106 | config INET6_IPCOMP |
107 | tristate "IPv6: IPComp transformation" | |
d2acc347 | 108 | select INET6_XFRM_TUNNEL |
6fccab67 | 109 | select XFRM_IPCOMP |
a7f7f624 | 110 | help |
1da177e4 LT |
111 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), |
112 | typically needed for IPsec. | |
113 | ||
114 | If unsure, say Y. | |
115 | ||
ee538268 | 116 | config IPV6_MIP6 |
f9ceb16e | 117 | tristate "IPv6: Mobility" |
ee538268 | 118 | select XFRM |
a7f7f624 | 119 | help |
ee538268 MN |
120 | Support for IPv6 Mobility described in RFC 3775. |
121 | ||
122 | If unsure, say N. | |
123 | ||
65d7ab8d TH |
124 | config IPV6_ILA |
125 | tristate "IPv6: Identifier Locator Addressing (ILA)" | |
8cb964da | 126 | depends on NETFILTER |
83ed7d1f | 127 | select DST_CACHE |
65d7ab8d | 128 | select LWTUNNEL |
a7f7f624 | 129 | help |
65d7ab8d TH |
130 | Support for IPv6 Identifier Locator Addressing (ILA). |
131 | ||
132 | ILA is a mechanism to do network virtualization without | |
133 | encapsulation. The basic concept of ILA is that we split an | |
134 | IPv6 address into a 64 bit locator and 64 bit identifier. The | |
135 | identifier is the identity of an entity in communication | |
136 | ("who") and the locator expresses the location of the | |
137 | entity ("where"). | |
138 | ||
139 | ILA can be configured using the "encap ila" option with | |
140 | "ip -6 route" command. ILA is described in | |
141 | https://tools.ietf.org/html/draft-herbert-nvo3-ila-00. | |
142 | ||
143 | If unsure, say N. | |
144 | ||
d2acc347 HX |
145 | config INET6_XFRM_TUNNEL |
146 | tristate | |
147 | select INET6_TUNNEL | |
148 | default n | |
149 | ||
1da177e4 | 150 | config INET6_TUNNEL |
d2acc347 HX |
151 | tristate |
152 | default n | |
1da177e4 | 153 | |
ed1efb2a SK |
154 | config IPV6_VTI |
155 | tristate "Virtual (secure) IPv6: tunneling" | |
156 | select IPV6_TUNNEL | |
876fc03a | 157 | select NET_IP_TUNNEL |
4c145dce | 158 | select XFRM |
a7f7f624 | 159 | help |
ed1efb2a SK |
160 | Tunneling means encapsulating data of one protocol type within |
161 | another protocol and sending it over a channel that understands the | |
162 | encapsulating protocol. This can be used with xfrm mode tunnel to give | |
163 | the notion of a secure tunnel for IPSEC and then use routing protocol | |
164 | on top. | |
165 | ||
989e5b96 JR |
166 | config IPV6_SIT |
167 | tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" | |
c73cb5a2 | 168 | select INET_TUNNEL |
f61dd388 | 169 | select NET_IP_TUNNEL |
de357cc0 | 170 | select IPV6_NDISC_NODETYPE |
989e5b96 | 171 | default y |
a7f7f624 | 172 | help |
989e5b96 JR |
173 | Tunneling means encapsulating data of one protocol type within |
174 | another protocol and sending it over a channel that understands the | |
175 | encapsulating protocol. This driver implements encapsulation of IPv6 | |
5c5d6dab | 176 | into IPv4 packets. This is useful if you want to connect two IPv6 |
989e5b96 JR |
177 | networks over an IPv4-only path. |
178 | ||
4737f097 | 179 | Saying M here will produce a module called sit. If unsure, say Y. |
989e5b96 | 180 | |
fa857afc | 181 | config IPV6_SIT_6RD |
f9ceb16e KC |
182 | bool "IPv6: IPv6 Rapid Deployment (6RD)" |
183 | depends on IPV6_SIT | |
fa857afc | 184 | default n |
a7f7f624 | 185 | help |
fa857afc YH |
186 | IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon |
187 | mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly | |
188 | deploy IPv6 unicast service to IPv4 sites to which it provides | |
189 | customer premise equipment. Like 6to4, it utilizes stateless IPv6 in | |
190 | IPv4 encapsulation in order to transit IPv4-only network | |
191 | infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 | |
192 | prefix of its own in place of the fixed 6to4 prefix. | |
193 | ||
194 | With this option enabled, the SIT driver offers 6rd functionality by | |
195 | providing additional ioctl API to configure the IPv6 Prefix for in | |
196 | stead of static 2002::/16 for 6to4. | |
197 | ||
198 | If unsure, say N. | |
199 | ||
de357cc0 YH |
200 | config IPV6_NDISC_NODETYPE |
201 | bool | |
202 | ||
1da177e4 | 203 | config IPV6_TUNNEL |
38fe999e | 204 | tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" |
d2acc347 | 205 | select INET6_TUNNEL |
607f725f | 206 | select DST_CACHE |
97e219b7 | 207 | select GRO_CELLS |
a7f7f624 | 208 | help |
38fe999e YH |
209 | Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in |
210 | RFC 2473. | |
1da177e4 LT |
211 | |
212 | If unsure, say N. | |
213 | ||
c12b395a | 214 | config IPV6_GRE |
215 | tristate "IPv6: GRE tunnel" | |
216 | select IPV6_TUNNEL | |
f61dd388 | 217 | select NET_IP_TUNNEL |
8bf42e9e | 218 | depends on NET_IPGRE_DEMUX |
a7f7f624 | 219 | help |
c12b395a | 220 | Tunneling means encapsulating data of one protocol type within |
221 | another protocol and sending it over a channel that understands the | |
222 | encapsulating protocol. This particular tunneling driver implements | |
223 | GRE (Generic Routing Encapsulation) and at this time allows | |
224 | encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure. | |
225 | This driver is useful if the other endpoint is a Cisco router: Cisco | |
226 | likes GRE much better than the other Linux tunneling driver ("IP | |
227 | tunneling" above). In addition, GRE allows multicast redistribution | |
228 | through the tunnel. | |
229 | ||
230 | Saying M here will produce a module called ip6_gre. If unsure, say N. | |
231 | ||
fabb13db AB |
232 | config IPV6_FOU |
233 | tristate | |
234 | default NET_FOU && IPV6 | |
235 | ||
236 | config IPV6_FOU_TUNNEL | |
237 | tristate | |
238 | default NET_FOU_IP_TUNNELS && IPV6_FOU | |
95e4daa8 | 239 | select IPV6_TUNNEL |
fabb13db | 240 | |
264e91b6 VN |
241 | config IPV6_MULTIPLE_TABLES |
242 | bool "IPv6: Multiple Routing Tables" | |
264e91b6 | 243 | select FIB_RULES |
a7f7f624 | 244 | help |
264e91b6 VN |
245 | Support multiple routing tables. |
246 | ||
4e96c2b4 YH |
247 | config IPV6_SUBTREES |
248 | bool "IPv6: source address based routing" | |
264e91b6 | 249 | depends on IPV6_MULTIPLE_TABLES |
a7f7f624 | 250 | help |
4e96c2b4 YH |
251 | Enable routing by source address or prefix. |
252 | ||
253 | The destination address is still the primary routing key, so mixing | |
254 | normal and source prefix specific routes in the same routing table | |
255 | may sometimes lead to unintended routing behavior. This can be | |
256 | avoided by defining different routing tables for the normal and | |
257 | source prefix specific routes. | |
258 | ||
259 | If unsure, say N. | |
260 | ||
7bc570c8 | 261 | config IPV6_MROUTE |
f9ceb16e KC |
262 | bool "IPv6: multicast routing" |
263 | depends on IPV6 | |
6853f21f | 264 | select IP_MROUTE_COMMON |
a7f7f624 | 265 | help |
a9f71d0d | 266 | Support for IPv6 multicast forwarding. |
7bc570c8 YH |
267 | If unsure, say N. |
268 | ||
d1db275d PM |
269 | config IPV6_MROUTE_MULTIPLE_TABLES |
270 | bool "IPv6: multicast policy routing" | |
271 | depends on IPV6_MROUTE | |
272 | select FIB_RULES | |
273 | help | |
274 | Normally, a multicast router runs a userspace daemon and decides | |
275 | what to do with a multicast packet based on the source and | |
276 | destination addresses. If you say Y here, the multicast router | |
277 | will also be able to take interfaces and packet marks into | |
278 | account and run multiple instances of userspace daemons | |
279 | simultaneously, each one handling a single table. | |
280 | ||
281 | If unsure, say N. | |
282 | ||
14fb64e1 | 283 | config IPV6_PIMSM_V2 |
f9ceb16e | 284 | bool "IPv6: PIM-SM version 2 support" |
14fb64e1 | 285 | depends on IPV6_MROUTE |
a7f7f624 | 286 | help |
14fb64e1 YH |
287 | Support for IPv6 PIM multicast routing protocol PIM-SMv2. |
288 | If unsure, say N. | |
289 | ||
46738b13 DL |
290 | config IPV6_SEG6_LWTUNNEL |
291 | bool "IPv6: Segment Routing Header encapsulation support" | |
292 | depends on IPV6 | |
293 | select LWTUNNEL | |
402a5bc4 | 294 | select DST_CACHE |
d7a669dd | 295 | select IPV6_MULTIPLE_TABLES |
a7f7f624 | 296 | help |
46738b13 DL |
297 | Support for encapsulation of packets within an outer IPv6 |
298 | header and a Segment Routing Header using the lightweight | |
d1df6fd8 DL |
299 | tunnels mechanism. Also enable support for advanced local |
300 | processing of SRv6 packets based on their active segment. | |
46738b13 DL |
301 | |
302 | If unsure, say N. | |
303 | ||
bf355b8d DL |
304 | config IPV6_SEG6_HMAC |
305 | bool "IPv6: Segment Routing HMAC support" | |
306 | depends on IPV6 | |
db7cd91a | 307 | select CRYPTO |
bf355b8d DL |
308 | select CRYPTO_HMAC |
309 | select CRYPTO_SHA1 | |
310 | select CRYPTO_SHA256 | |
a7f7f624 | 311 | help |
bf355b8d DL |
312 | Support for HMAC signature generation and verification |
313 | of SR-enabled packets. | |
314 | ||
315 | If unsure, say N. | |
316 | ||
fe94cc29 MX |
317 | config IPV6_SEG6_BPF |
318 | def_bool y | |
319 | depends on IPV6_SEG6_LWTUNNEL | |
320 | depends on IPV6 = y | |
321 | ||
a7a29f9c AA |
322 | config IPV6_RPL_LWTUNNEL |
323 | bool "IPv6: RPL Source Routing Header support" | |
324 | depends on IPV6 | |
325 | select LWTUNNEL | |
a7f7f624 | 326 | help |
a7a29f9c AA |
327 | Support for RFC6554 RPL Source Routing Header using the lightweight |
328 | tunnels mechanism. | |
329 | ||
330 | If unsure, say N. | |
331 | ||
3edede08 JI |
332 | config IPV6_IOAM6_LWTUNNEL |
333 | bool "IPv6: IOAM Pre-allocated Trace insertion support" | |
334 | depends on IPV6 | |
335 | select LWTUNNEL | |
8cb3bf8b | 336 | select DST_CACHE |
3edede08 | 337 | help |
8cb3bf8b JI |
338 | Support for the insertion of IOAM Pre-allocated Trace |
339 | Header using the lightweight tunnels mechanism. | |
3edede08 JI |
340 | |
341 | If unsure, say N. | |
342 | ||
0b18542b | 343 | endif # IPV6 |