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 m 9 ---help--- 10 This is complemental support for the IP version 6. 11 You will still be able to do traditional IPv4 networking as well. 12 13 For general information about IPv6, see 14 <https://en.wikipedia.org/wiki/IPv6>. 15 For Linux IPv6 development information, see <http://www.linux-ipv6.org>. 16 For specific information about IPv6 under Linux, read the HOWTO at 17 <http://www.bieringer.de/linux/IPv6/>. 18 19 To compile this protocol support as a module, choose M here: the 20 module will be called ipv6. 21 22if IPV6 23 24config IPV6_PRIVACY 25 bool "IPv6: Privacy Extensions (RFC 3041) support" 26 ---help--- 27 Privacy Extensions for Stateless Address Autoconfiguration in IPv6 28 support. With this option, additional periodically-altered 29 pseudo-random global-scope unicast address(es) will be assigned to 30 your interface(s). 31 32 We use our standard pseudo-random algorithm to generate the 33 randomized interface identifier, instead of one described in RFC 3041. 34 35 By default the kernel does not generate temporary addresses. 36 To use temporary addresses, do 37 38 echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr 39 40 See <file:Documentation/networking/ip-sysctl.txt> for details. 41 42config IPV6_ROUTER_PREF 43 bool "IPv6: Router Preference (RFC 4191) support" 44 ---help--- 45 Router Preference is an optional extension to the Router 46 Advertisement message which improves the ability of hosts 47 to pick an appropriate router, especially when the hosts 48 are placed in a multi-homed network. 49 50 If unsure, say N. 51 52config IPV6_ROUTE_INFO 53 bool "IPv6: Route Information (RFC 4191) support" 54 depends on IPV6_ROUTER_PREF 55 ---help--- 56 This is experimental support of Route Information. 57 58 If unsure, say N. 59 60config IPV6_OPTIMISTIC_DAD 61 bool "IPv6: Enable RFC 4429 Optimistic DAD" 62 ---help--- 63 This is experimental support for optimistic Duplicate 64 Address Detection. It allows for autoconfigured addresses 65 to be used more quickly. 66 67 If unsure, say N. 68 69config INET6_AH 70 tristate "IPv6: AH transformation" 71 select XFRM_ALGO 72 select CRYPTO 73 select CRYPTO_HMAC 74 select CRYPTO_MD5 75 select CRYPTO_SHA1 76 ---help--- 77 Support for IPsec AH. 78 79 If unsure, say Y. 80 81config INET6_ESP 82 tristate "IPv6: ESP transformation" 83 select XFRM_ALGO 84 select CRYPTO 85 select CRYPTO_AUTHENC 86 select CRYPTO_HMAC 87 select CRYPTO_MD5 88 select CRYPTO_CBC 89 select CRYPTO_SHA1 90 select CRYPTO_DES 91 ---help--- 92 Support for IPsec ESP. 93 94 If unsure, say Y. 95 96config INET6_IPCOMP 97 tristate "IPv6: IPComp transformation" 98 select INET6_XFRM_TUNNEL 99 select XFRM_IPCOMP 100 ---help--- 101 Support for IP Payload Compression Protocol (IPComp) (RFC3173), 102 typically needed for IPsec. 103 104 If unsure, say Y. 105 106config IPV6_MIP6 107 tristate "IPv6: Mobility" 108 select XFRM 109 ---help--- 110 Support for IPv6 Mobility described in RFC 3775. 111 112 If unsure, say N. 113 114config INET6_XFRM_TUNNEL 115 tristate 116 select INET6_TUNNEL 117 default n 118 119config INET6_TUNNEL 120 tristate 121 default n 122 123config INET6_XFRM_MODE_TRANSPORT 124 tristate "IPv6: IPsec transport mode" 125 default IPV6 126 select XFRM 127 ---help--- 128 Support for IPsec transport mode. 129 130 If unsure, say Y. 131 132config INET6_XFRM_MODE_TUNNEL 133 tristate "IPv6: IPsec tunnel mode" 134 default IPV6 135 select XFRM 136 ---help--- 137 Support for IPsec tunnel mode. 138 139 If unsure, say Y. 140 141config INET6_XFRM_MODE_BEET 142 tristate "IPv6: IPsec BEET mode" 143 default IPV6 144 select XFRM 145 ---help--- 146 Support for IPsec BEET mode. 147 148 If unsure, say Y. 149 150config INET6_XFRM_MODE_ROUTEOPTIMIZATION 151 tristate "IPv6: MIPv6 route optimization mode" 152 select XFRM 153 ---help--- 154 Support for MIPv6 route optimization mode. 155 156config IPV6_SIT 157 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" 158 select INET_TUNNEL 159 select NET_IP_TUNNEL 160 select IPV6_NDISC_NODETYPE 161 default y 162 ---help--- 163 Tunneling means encapsulating data of one protocol type within 164 another protocol and sending it over a channel that understands the 165 encapsulating protocol. This driver implements encapsulation of IPv6 166 into IPv4 packets. This is useful if you want to connect two IPv6 167 networks over an IPv4-only path. 168 169 Saying M here will produce a module called sit. If unsure, say Y. 170 171config IPV6_SIT_6RD 172 bool "IPv6: IPv6 Rapid Deployment (6RD)" 173 depends on IPV6_SIT 174 default n 175 ---help--- 176 IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon 177 mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly 178 deploy IPv6 unicast service to IPv4 sites to which it provides 179 customer premise equipment. Like 6to4, it utilizes stateless IPv6 in 180 IPv4 encapsulation in order to transit IPv4-only network 181 infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 182 prefix of its own in place of the fixed 6to4 prefix. 183 184 With this option enabled, the SIT driver offers 6rd functionality by 185 providing additional ioctl API to configure the IPv6 Prefix for in 186 stead of static 2002::/16 for 6to4. 187 188 If unsure, say N. 189 190config IPV6_NDISC_NODETYPE 191 bool 192 193config IPV6_TUNNEL 194 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" 195 select INET6_TUNNEL 196 ---help--- 197 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in 198 RFC 2473. 199 200 If unsure, say N. 201 202config IPV6_GRE 203 tristate "IPv6: GRE tunnel" 204 select IPV6_TUNNEL 205 select NET_IP_TUNNEL 206 ---help--- 207 Tunneling means encapsulating data of one protocol type within 208 another protocol and sending it over a channel that understands the 209 encapsulating protocol. This particular tunneling driver implements 210 GRE (Generic Routing Encapsulation) and at this time allows 211 encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure. 212 This driver is useful if the other endpoint is a Cisco router: Cisco 213 likes GRE much better than the other Linux tunneling driver ("IP 214 tunneling" above). In addition, GRE allows multicast redistribution 215 through the tunnel. 216 217 Saying M here will produce a module called ip6_gre. If unsure, say N. 218 219config IPV6_MULTIPLE_TABLES 220 bool "IPv6: Multiple Routing Tables" 221 select FIB_RULES 222 ---help--- 223 Support multiple routing tables. 224 225config IPV6_SUBTREES 226 bool "IPv6: source address based routing" 227 depends on IPV6_MULTIPLE_TABLES 228 ---help--- 229 Enable routing by source address or prefix. 230 231 The destination address is still the primary routing key, so mixing 232 normal and source prefix specific routes in the same routing table 233 may sometimes lead to unintended routing behavior. This can be 234 avoided by defining different routing tables for the normal and 235 source prefix specific routes. 236 237 If unsure, say N. 238 239config IPV6_MROUTE 240 bool "IPv6: multicast routing" 241 depends on IPV6 242 ---help--- 243 Experimental support for IPv6 multicast forwarding. 244 If unsure, say N. 245 246config IPV6_MROUTE_MULTIPLE_TABLES 247 bool "IPv6: multicast policy routing" 248 depends on IPV6_MROUTE 249 select FIB_RULES 250 help 251 Normally, a multicast router runs a userspace daemon and decides 252 what to do with a multicast packet based on the source and 253 destination addresses. If you say Y here, the multicast router 254 will also be able to take interfaces and packet marks into 255 account and run multiple instances of userspace daemons 256 simultaneously, each one handling a single table. 257 258 If unsure, say N. 259 260config IPV6_PIMSM_V2 261 bool "IPv6: PIM-SM version 2 support" 262 depends on IPV6_MROUTE 263 ---help--- 264 Support for IPv6 PIM multicast routing protocol PIM-SMv2. 265 If unsure, say N. 266 267endif # IPV6 268