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