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 This is experimental 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 This is experimental support for optimistic Duplicate 45 Address Detection. It allows for autoconfigured addresses 46 to be used more quickly. 47 48 If unsure, say N. 49 50config INET6_AH 51 tristate "IPv6: AH transformation" 52 select XFRM_ALGO 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 62config INET6_ESP 63 tristate "IPv6: ESP transformation" 64 select XFRM_ALGO 65 select CRYPTO 66 select CRYPTO_AUTHENC 67 select CRYPTO_HMAC 68 select CRYPTO_MD5 69 select CRYPTO_CBC 70 select CRYPTO_SHA1 71 select CRYPTO_DES 72 select CRYPTO_ECHAINIV 73 ---help--- 74 Support for IPsec ESP. 75 76 If unsure, say Y. 77 78config 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 91config INET6_IPCOMP 92 tristate "IPv6: IPComp transformation" 93 select INET6_XFRM_TUNNEL 94 select XFRM_IPCOMP 95 ---help--- 96 Support for IP Payload Compression Protocol (IPComp) (RFC3173), 97 typically needed for IPsec. 98 99 If unsure, say Y. 100 101config IPV6_MIP6 102 tristate "IPv6: Mobility" 103 select XFRM 104 ---help--- 105 Support for IPv6 Mobility described in RFC 3775. 106 107 If unsure, say N. 108 109config IPV6_ILA 110 tristate "IPv6: Identifier Locator Addressing (ILA)" 111 depends on NETFILTER 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 INET6_XFRM_MODE_TRANSPORT 139 tristate "IPv6: IPsec transport mode" 140 default IPV6 141 select XFRM 142 ---help--- 143 Support for IPsec transport mode. 144 145 If unsure, say Y. 146 147config INET6_XFRM_MODE_TUNNEL 148 tristate "IPv6: IPsec tunnel mode" 149 default IPV6 150 select XFRM 151 ---help--- 152 Support for IPsec tunnel mode. 153 154 If unsure, say Y. 155 156config INET6_XFRM_MODE_BEET 157 tristate "IPv6: IPsec BEET mode" 158 default IPV6 159 select XFRM 160 ---help--- 161 Support for IPsec BEET mode. 162 163 If unsure, say Y. 164 165config INET6_XFRM_MODE_ROUTEOPTIMIZATION 166 tristate "IPv6: MIPv6 route optimization mode" 167 select XFRM 168 ---help--- 169 Support for MIPv6 route optimization mode. 170 171config IPV6_VTI 172tristate "Virtual (secure) IPv6: tunneling" 173 select IPV6_TUNNEL 174 select NET_IP_TUNNEL 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 183config IPV6_SIT 184 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" 185 select INET_TUNNEL 186 select NET_IP_TUNNEL 187 select IPV6_NDISC_NODETYPE 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 193 into IPv4 packets. This is useful if you want to connect two IPv6 194 networks over an IPv4-only path. 195 196 Saying M here will produce a module called sit. If unsure, say Y. 197 198config IPV6_SIT_6RD 199 bool "IPv6: IPv6 Rapid Deployment (6RD)" 200 depends on IPV6_SIT 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 217config IPV6_NDISC_NODETYPE 218 bool 219 220config IPV6_TUNNEL 221 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" 222 select INET6_TUNNEL 223 select DST_CACHE 224 select GRO_CELLS 225 ---help--- 226 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in 227 RFC 2473. 228 229 If unsure, say N. 230 231config IPV6_GRE 232 tristate "IPv6: GRE tunnel" 233 select IPV6_TUNNEL 234 select NET_IP_TUNNEL 235 depends on NET_IPGRE_DEMUX 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 249config IPV6_FOU 250 tristate 251 default NET_FOU && IPV6 252 253config IPV6_FOU_TUNNEL 254 tristate 255 default NET_FOU_IP_TUNNELS && IPV6_FOU 256 select IPV6_TUNNEL 257 258config IPV6_MULTIPLE_TABLES 259 bool "IPv6: Multiple Routing Tables" 260 select FIB_RULES 261 ---help--- 262 Support multiple routing tables. 263 264config IPV6_SUBTREES 265 bool "IPv6: source address based routing" 266 depends on IPV6_MULTIPLE_TABLES 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 278config IPV6_MROUTE 279 bool "IPv6: multicast routing" 280 depends on IPV6 281 ---help--- 282 Experimental support for IPv6 multicast forwarding. 283 If unsure, say N. 284 285config IPV6_MROUTE_MULTIPLE_TABLES 286 bool "IPv6: multicast policy routing" 287 depends on IPV6_MROUTE 288 select FIB_RULES 289 help 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. 296 297 If unsure, say N. 298 299config IPV6_PIMSM_V2 300 bool "IPv6: PIM-SM version 2 support" 301 depends on IPV6_MROUTE 302 ---help--- 303 Support for IPv6 PIM multicast routing protocol PIM-SMv2. 304 If unsure, say N. 305 306config IPV6_SEG6_LWTUNNEL 307 bool "IPv6: Segment Routing Header encapsulation support" 308 depends on IPV6 309 select LWTUNNEL 310 ---help--- 311 Support for encapsulation of packets within an outer IPv6 312 header and a Segment Routing Header using the lightweight 313 tunnels mechanism. 314 315 If unsure, say N. 316 317config IPV6_SEG6_INLINE 318 bool "IPv6: direct Segment Routing Header insertion " 319 depends on IPV6_SEG6_LWTUNNEL 320 ---help--- 321 Support for direct insertion of the Segment Routing Header, 322 also known as inline mode. Be aware that direct insertion of 323 extension headers (as opposed to encapsulation) may break 324 multiple mechanisms such as PMTUD or IPSec AH. Use this feature 325 only if you know exactly what you are doing. 326 327 If unsure, say N. 328 329config IPV6_SEG6_HMAC 330 bool "IPv6: Segment Routing HMAC support" 331 depends on IPV6 332 select CRYPTO_HMAC 333 select CRYPTO_SHA1 334 select CRYPTO_SHA256 335 ---help--- 336 Support for HMAC signature generation and verification 337 of SR-enabled packets. 338 339 If unsure, say N. 340 341endif # IPV6 342