1 # SPDX-License-Identifier: GPL-2.0-only
6 # IPv6 as module will cause a CRASH if you try to unload it
8 tristate "The IPv6 protocol"
11 Support for IP version 6 (IPv6).
13 For general information about IPv6, see
14 <https://en.wikipedia.org/wiki/IPv6>.
15 For specific information about IPv6 under Linux, see
16 Documentation/networking/ipv6.rst and read the HOWTO at
17 <http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/>
19 To compile this protocol support as a module, choose M here: the
20 module will be called ipv6.
24 config IPV6_ROUTER_PREF
25 bool "IPv6: Router Preference (RFC 4191) support"
27 Router Preference is an optional extension to the Router
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.
34 config IPV6_ROUTE_INFO
35 bool "IPv6: Route Information (RFC 4191) support"
36 depends on IPV6_ROUTER_PREF
38 Support of Route Information.
42 config IPV6_OPTIMISTIC_DAD
43 bool "IPv6: Enable RFC 4429 Optimistic DAD"
45 Support for optimistic Duplicate Address Detection. It allows for
46 autoconfigured addresses to be used more quickly.
51 tristate "IPv6: AH transformation"
63 tristate "IPv6: ESP transformation"
72 select CRYPTO_ECHAINIV
74 Support for IPsec ESP.
78 config INET6_ESP_OFFLOAD
79 tristate "IPv6: ESP transformation offload"
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.
92 bool "IPv6: ESP in TCP encapsulation (RFC 8229)"
93 depends on XFRM && INET6_ESP
98 Support for RFC 8229 encapsulation of ESP and IKE over
104 tristate "IPv6: IPComp transformation"
105 select INET6_XFRM_TUNNEL
108 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
109 typically needed for IPsec.
114 tristate "IPv6: Mobility"
117 Support for IPv6 Mobility described in RFC 3775.
122 tristate "IPv6: Identifier Locator Addressing (ILA)"
127 Support for IPv6 Identifier Locator Addressing (ILA).
129 ILA is a mechanism to do network virtualization without
130 encapsulation. The basic concept of ILA is that we split an
131 IPv6 address into a 64 bit locator and 64 bit identifier. The
132 identifier is the identity of an entity in communication
133 ("who") and the locator expresses the location of the
136 ILA can be configured using the "encap ila" option with
137 "ip -6 route" command. ILA is described in
138 https://tools.ietf.org/html/draft-herbert-nvo3-ila-00.
142 config INET6_XFRM_TUNNEL
152 tristate "Virtual (secure) IPv6: tunneling"
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 can be used with xfrm mode tunnel to give
160 the notion of a secure tunnel for IPSEC and then use routing protocol
164 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
167 select IPV6_NDISC_NODETYPE
170 Tunneling means encapsulating data of one protocol type within
171 another protocol and sending it over a channel that understands the
172 encapsulating protocol. This driver implements encapsulation of IPv6
173 into IPv4 packets. This is useful if you want to connect two IPv6
174 networks over an IPv4-only path.
176 Saying M here will produce a module called sit. If unsure, say Y.
179 bool "IPv6: IPv6 Rapid Deployment (6RD)"
183 IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon
184 mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly
185 deploy IPv6 unicast service to IPv4 sites to which it provides
186 customer premise equipment. Like 6to4, it utilizes stateless IPv6 in
187 IPv4 encapsulation in order to transit IPv4-only network
188 infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6
189 prefix of its own in place of the fixed 6to4 prefix.
191 With this option enabled, the SIT driver offers 6rd functionality by
192 providing additional ioctl API to configure the IPv6 Prefix for in
193 stead of static 2002::/16 for 6to4.
197 config IPV6_NDISC_NODETYPE
201 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
206 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
212 tristate "IPv6: GRE tunnel"
215 depends on NET_IPGRE_DEMUX
217 Tunneling means encapsulating data of one protocol type within
218 another protocol and sending it over a channel that understands the
219 encapsulating protocol. This particular tunneling driver implements
220 GRE (Generic Routing Encapsulation) and at this time allows
221 encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure.
222 This driver is useful if the other endpoint is a Cisco router: Cisco
223 likes GRE much better than the other Linux tunneling driver ("IP
224 tunneling" above). In addition, GRE allows multicast redistribution
227 Saying M here will produce a module called ip6_gre. If unsure, say N.
231 default NET_FOU && IPV6
233 config IPV6_FOU_TUNNEL
235 default NET_FOU_IP_TUNNELS && IPV6_FOU
238 config IPV6_MULTIPLE_TABLES
239 bool "IPv6: Multiple Routing Tables"
242 Support multiple routing tables.
245 bool "IPv6: source address based routing"
246 depends on IPV6_MULTIPLE_TABLES
248 Enable routing by source address or prefix.
250 The destination address is still the primary routing key, so mixing
251 normal and source prefix specific routes in the same routing table
252 may sometimes lead to unintended routing behavior. This can be
253 avoided by defining different routing tables for the normal and
254 source prefix specific routes.
259 bool "IPv6: multicast routing"
261 select IP_MROUTE_COMMON
263 Support for IPv6 multicast forwarding.
266 config IPV6_MROUTE_MULTIPLE_TABLES
267 bool "IPv6: multicast policy routing"
268 depends on IPV6_MROUTE
271 Normally, a multicast router runs a userspace daemon and decides
272 what to do with a multicast packet based on the source and
273 destination addresses. If you say Y here, the multicast router
274 will also be able to take interfaces and packet marks into
275 account and run multiple instances of userspace daemons
276 simultaneously, each one handling a single table.
281 bool "IPv6: PIM-SM version 2 support"
282 depends on IPV6_MROUTE
284 Support for IPv6 PIM multicast routing protocol PIM-SMv2.
287 config IPV6_SEG6_LWTUNNEL
288 bool "IPv6: Segment Routing Header encapsulation support"
292 select IPV6_MULTIPLE_TABLES
294 Support for encapsulation of packets within an outer IPv6
295 header and a Segment Routing Header using the lightweight
296 tunnels mechanism. Also enable support for advanced local
297 processing of SRv6 packets based on their active segment.
301 config IPV6_SEG6_HMAC
302 bool "IPv6: Segment Routing HMAC support"
308 Support for HMAC signature generation and verification
309 of SR-enabled packets.
315 depends on IPV6_SEG6_LWTUNNEL
318 config IPV6_RPL_LWTUNNEL
319 bool "IPv6: RPL Source Routing Header support"
323 Support for RFC6554 RPL Source Routing Header using the lightweight