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