5 # IPv6 as module will cause a CRASH if you try to unload it
7 tristate "The IPv6 protocol"
10 Support for IP version 6 (IPv6).
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/>
18 To compile this protocol support as a module, choose M here: the
19 module will be called ipv6.
23 config IPV6_ROUTER_PREF
24 bool "IPv6: Router Preference (RFC 4191) support"
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.
33 config IPV6_ROUTE_INFO
34 bool "IPv6: Route Information (RFC 4191) support"
35 depends on IPV6_ROUTER_PREF
37 This is experimental support of Route Information.
41 config IPV6_OPTIMISTIC_DAD
42 bool "IPv6: Enable RFC 4429 Optimistic DAD"
44 This is experimental support for optimistic Duplicate
45 Address Detection. It allows for autoconfigured addresses
46 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 tristate "IPv6: IPComp transformation"
93 select INET6_XFRM_TUNNEL
96 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
97 typically needed for IPsec.
102 tristate "IPv6: Mobility"
105 Support for IPv6 Mobility described in RFC 3775.
110 tristate "IPv6: Identifier Locator Addressing (ILA)"
114 Support for IPv6 Identifier Locator Addressing (ILA).
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
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.
129 config INET6_XFRM_TUNNEL
138 config INET6_XFRM_MODE_TRANSPORT
139 tristate "IPv6: IPsec transport mode"
143 Support for IPsec transport mode.
147 config INET6_XFRM_MODE_TUNNEL
148 tristate "IPv6: IPsec tunnel mode"
152 Support for IPsec tunnel mode.
156 config INET6_XFRM_MODE_BEET
157 tristate "IPv6: IPsec BEET mode"
161 Support for IPsec BEET mode.
165 config INET6_XFRM_MODE_ROUTEOPTIMIZATION
166 tristate "IPv6: MIPv6 route optimization mode"
169 Support for MIPv6 route optimization mode.
172 tristate "Virtual (secure) IPv6: tunneling"
175 depends on INET6_XFRM_MODE_TUNNEL
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
184 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
187 select IPV6_NDISC_NODETYPE
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
193 into IPv4 packets. This is useful if you want to connect two IPv6
194 networks over an IPv4-only path.
196 Saying M here will produce a module called sit. If unsure, say Y.
199 bool "IPv6: IPv6 Rapid Deployment (6RD)"
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.
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.
217 config IPV6_NDISC_NODETYPE
221 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)"
226 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in
232 tristate "IPv6: GRE tunnel"
235 depends on NET_IPGRE_DEMUX
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
247 Saying M here will produce a module called ip6_gre. If unsure, say N.
251 default NET_FOU && IPV6
253 config IPV6_FOU_TUNNEL
255 default NET_FOU_IP_TUNNELS && IPV6_FOU
258 config IPV6_MULTIPLE_TABLES
259 bool "IPv6: Multiple Routing Tables"
262 Support multiple routing tables.
265 bool "IPv6: source address based routing"
266 depends on IPV6_MULTIPLE_TABLES
268 Enable routing by source address or prefix.
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.
279 bool "IPv6: multicast routing"
282 Experimental support for IPv6 multicast forwarding.
285 config IPV6_MROUTE_MULTIPLE_TABLES
286 bool "IPv6: multicast policy routing"
287 depends on IPV6_MROUTE
290 Normally, a multicast router runs a userspace daemon and decides
291 what to do with a multicast packet based on the source and
292 destination addresses. If you say Y here, the multicast router
293 will also be able to take interfaces and packet marks into
294 account and run multiple instances of userspace daemons
295 simultaneously, each one handling a single table.
300 bool "IPv6: PIM-SM version 2 support"
301 depends on IPV6_MROUTE
303 Support for IPv6 PIM multicast routing protocol PIM-SMv2.
306 config IPV6_SEG6_LWTUNNEL
307 bool "IPv6: Segment Routing Header encapsulation support"
312 Support for encapsulation of packets within an outer IPv6
313 header and a Segment Routing Header using the lightweight
318 config IPV6_SEG6_INLINE
319 bool "IPv6: direct Segment Routing Header insertion "
320 depends on IPV6_SEG6_LWTUNNEL
322 Support for direct insertion of the Segment Routing Header,
323 also known as inline mode. Be aware that direct insertion of
324 extension headers (as opposed to encapsulation) may break
325 multiple mechanisms such as PMTUD or IPSec AH. Use this feature
326 only if you know exactly what you are doing.
330 config IPV6_SEG6_HMAC
331 bool "IPv6: Segment Routing HMAC support"
337 Support for HMAC signature generation and verification
338 of SR-enabled packets.