xref: /openbmc/linux/net/ipv6/Kconfig (revision 3fc41476)
1#
2# IPv6 configuration
3#
4
5#   IPv6 as module will cause a CRASH if you try to unload it
6menuconfig IPV6
7	tristate "The IPv6 protocol"
8	default y
9	---help---
10	  Support for IP version 6 (IPv6).
11
12	  For general information about IPv6, see
13	  <https://en.wikipedia.org/wiki/IPv6>.
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/>
17
18	  To compile this protocol support as a module, choose M here: the
19	  module will be called ipv6.
20
21if IPV6
22
23config IPV6_ROUTER_PREF
24	bool "IPv6: Router Preference (RFC 4191) support"
25	---help---
26	  Router Preference is an optional extension to the Router
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.
30
31	  If unsure, say N.
32
33config IPV6_ROUTE_INFO
34	bool "IPv6: Route Information (RFC 4191) support"
35	depends on IPV6_ROUTER_PREF
36	---help---
37	  Support of Route Information.
38
39	  If unsure, say N.
40
41config IPV6_OPTIMISTIC_DAD
42	bool "IPv6: Enable RFC 4429 Optimistic DAD"
43	---help---
44	  Support for optimistic Duplicate Address Detection. It allows for
45	  autoconfigured addresses to be used more quickly.
46
47	  If unsure, say N.
48
49config INET6_AH
50	tristate "IPv6: AH transformation"
51	select XFRM_ALGO
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
61config INET6_ESP
62	tristate "IPv6: ESP transformation"
63	select XFRM_ALGO
64	select CRYPTO
65	select CRYPTO_AUTHENC
66	select CRYPTO_HMAC
67	select CRYPTO_MD5
68	select CRYPTO_CBC
69	select CRYPTO_SHA1
70	select CRYPTO_DES
71	select CRYPTO_ECHAINIV
72	---help---
73	  Support for IPsec ESP.
74
75	  If unsure, say Y.
76
77config 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
90config INET6_IPCOMP
91	tristate "IPv6: IPComp transformation"
92	select INET6_XFRM_TUNNEL
93	select XFRM_IPCOMP
94	---help---
95	  Support for IP Payload Compression Protocol (IPComp) (RFC3173),
96	  typically needed for IPsec.
97
98	  If unsure, say Y.
99
100config IPV6_MIP6
101	tristate "IPv6: Mobility"
102	select XFRM
103	---help---
104	  Support for IPv6 Mobility described in RFC 3775.
105
106	  If unsure, say N.
107
108config IPV6_ILA
109	tristate "IPv6: Identifier Locator Addressing (ILA)"
110	depends on NETFILTER
111	select DST_CACHE
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
129config INET6_XFRM_TUNNEL
130	tristate
131	select INET6_TUNNEL
132	default n
133
134config INET6_TUNNEL
135	tristate
136	default n
137
138config IPV6_VTI
139tristate "Virtual (secure) IPv6: tunneling"
140	select IPV6_TUNNEL
141	select NET_IP_TUNNEL
142	select XFRM
143	---help---
144	Tunneling means encapsulating data of one protocol type within
145	another protocol and sending it over a channel that understands the
146	encapsulating protocol. This can be used with xfrm mode tunnel to give
147	the notion of a secure tunnel for IPSEC and then use routing protocol
148	on top.
149
150config IPV6_SIT
151	tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
152	select INET_TUNNEL
153	select NET_IP_TUNNEL
154	select IPV6_NDISC_NODETYPE
155	default y
156	---help---
157	  Tunneling means encapsulating data of one protocol type within
158	  another protocol and sending it over a channel that understands the
159	  encapsulating protocol. This driver implements encapsulation of IPv6
160	  into IPv4 packets. This is useful if you want to connect two IPv6
161	  networks over an IPv4-only path.
162
163	  Saying M here will produce a module called sit. If unsure, say Y.
164
165config IPV6_SIT_6RD
166	bool "IPv6: IPv6 Rapid Deployment (6RD)"
167	depends on IPV6_SIT
168	default n
169	---help---
170	  IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon
171	  mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly
172	  deploy IPv6 unicast service to IPv4 sites to which it provides
173	  customer premise equipment.  Like 6to4, it utilizes stateless IPv6 in
174	  IPv4 encapsulation in order to transit IPv4-only network
175	  infrastructure.  Unlike 6to4, a 6rd service provider uses an IPv6
176	  prefix of its own in place of the fixed 6to4 prefix.
177
178	  With this option enabled, the SIT driver offers 6rd functionality by
179	  providing additional ioctl API to configure the IPv6 Prefix for in
180	  stead of static 2002::/16 for 6to4.
181
182	  If unsure, say N.
183
184config IPV6_NDISC_NODETYPE
185	bool
186
187config IPV6_TUNNEL
188	tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
189	select INET6_TUNNEL
190	select DST_CACHE
191	select GRO_CELLS
192	---help---
193	  Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
194	  RFC 2473.
195
196	  If unsure, say N.
197
198config IPV6_GRE
199	tristate "IPv6: GRE tunnel"
200	select IPV6_TUNNEL
201	select NET_IP_TUNNEL
202	depends on NET_IPGRE_DEMUX
203	---help---
204	  Tunneling means encapsulating data of one protocol type within
205	  another protocol and sending it over a channel that understands the
206	  encapsulating protocol. This particular tunneling driver implements
207	  GRE (Generic Routing Encapsulation) and at this time allows
208	  encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure.
209	  This driver is useful if the other endpoint is a Cisco router: Cisco
210	  likes GRE much better than the other Linux tunneling driver ("IP
211	  tunneling" above). In addition, GRE allows multicast redistribution
212	  through the tunnel.
213
214	  Saying M here will produce a module called ip6_gre. If unsure, say N.
215
216config IPV6_FOU
217	tristate
218	default NET_FOU && IPV6
219
220config IPV6_FOU_TUNNEL
221	tristate
222	default NET_FOU_IP_TUNNELS && IPV6_FOU
223	select IPV6_TUNNEL
224
225config IPV6_MULTIPLE_TABLES
226	bool "IPv6: Multiple Routing Tables"
227	select FIB_RULES
228	---help---
229	  Support multiple routing tables.
230
231config IPV6_SUBTREES
232	bool "IPv6: source address based routing"
233	depends on IPV6_MULTIPLE_TABLES
234	---help---
235	  Enable routing by source address or prefix.
236
237	  The destination address is still the primary routing key, so mixing
238	  normal and source prefix specific routes in the same routing table
239	  may sometimes lead to unintended routing behavior.  This can be
240	  avoided by defining different routing tables for the normal and
241	  source prefix specific routes.
242
243	  If unsure, say N.
244
245config IPV6_MROUTE
246	bool "IPv6: multicast routing"
247	depends on IPV6
248	select IP_MROUTE_COMMON
249	---help---
250	  Support for IPv6 multicast forwarding.
251	  If unsure, say N.
252
253config IPV6_MROUTE_MULTIPLE_TABLES
254	bool "IPv6: multicast policy routing"
255	depends on IPV6_MROUTE
256	select FIB_RULES
257	help
258	  Normally, a multicast router runs a userspace daemon and decides
259	  what to do with a multicast packet based on the source and
260	  destination addresses. If you say Y here, the multicast router
261	  will also be able to take interfaces and packet marks into
262	  account and run multiple instances of userspace daemons
263	  simultaneously, each one handling a single table.
264
265	  If unsure, say N.
266
267config IPV6_PIMSM_V2
268	bool "IPv6: PIM-SM version 2 support"
269	depends on IPV6_MROUTE
270	---help---
271	  Support for IPv6 PIM multicast routing protocol PIM-SMv2.
272	  If unsure, say N.
273
274config IPV6_SEG6_LWTUNNEL
275	bool "IPv6: Segment Routing Header encapsulation support"
276	depends on IPV6
277	select LWTUNNEL
278	select DST_CACHE
279	select IPV6_MULTIPLE_TABLES
280	---help---
281	  Support for encapsulation of packets within an outer IPv6
282	  header and a Segment Routing Header using the lightweight
283	  tunnels mechanism. Also enable support for advanced local
284	  processing of SRv6 packets based on their active segment.
285
286	  If unsure, say N.
287
288config IPV6_SEG6_HMAC
289	bool "IPv6: Segment Routing HMAC support"
290	depends on IPV6
291	select CRYPTO_HMAC
292	select CRYPTO_SHA1
293	select CRYPTO_SHA256
294	---help---
295	  Support for HMAC signature generation and verification
296	  of SR-enabled packets.
297
298	  If unsure, say N.
299
300config IPV6_SEG6_BPF
301	def_bool y
302	depends on IPV6_SEG6_LWTUNNEL
303	depends on IPV6 = y
304
305endif # IPV6
306