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 <http://playground.sun.com/pub/ipng/html/ipng-main.html>. 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 (EXPERIMENTAL)" 54 depends on IPV6_ROUTER_PREF && EXPERIMENTAL 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 (EXPERIMENTAL)" 62 depends on EXPERIMENTAL 63 ---help--- 64 This is experimental support for optimistic Duplicate 65 Address Detection. It allows for autoconfigured addresses 66 to be used more quickly. 67 68 If unsure, say N. 69 70config INET6_AH 71 tristate "IPv6: AH transformation" 72 select XFRM_ALGO 73 select CRYPTO 74 select CRYPTO_HMAC 75 select CRYPTO_MD5 76 select CRYPTO_SHA1 77 ---help--- 78 Support for IPsec AH. 79 80 If unsure, say Y. 81 82config INET6_ESP 83 tristate "IPv6: ESP transformation" 84 select XFRM_ALGO 85 select CRYPTO 86 select CRYPTO_AUTHENC 87 select CRYPTO_HMAC 88 select CRYPTO_MD5 89 select CRYPTO_CBC 90 select CRYPTO_SHA1 91 select CRYPTO_DES 92 ---help--- 93 Support for IPsec ESP. 94 95 If unsure, say Y. 96 97config INET6_IPCOMP 98 tristate "IPv6: IPComp transformation" 99 select INET6_XFRM_TUNNEL 100 select XFRM_IPCOMP 101 ---help--- 102 Support for IP Payload Compression Protocol (IPComp) (RFC3173), 103 typically needed for IPsec. 104 105 If unsure, say Y. 106 107config IPV6_MIP6 108 tristate "IPv6: Mobility (EXPERIMENTAL)" 109 depends on EXPERIMENTAL 110 select XFRM 111 ---help--- 112 Support for IPv6 Mobility described in RFC 3775. 113 114 If unsure, say N. 115 116config INET6_XFRM_TUNNEL 117 tristate 118 select INET6_TUNNEL 119 default n 120 121config INET6_TUNNEL 122 tristate 123 default n 124 125config INET6_XFRM_MODE_TRANSPORT 126 tristate "IPv6: IPsec transport mode" 127 default IPV6 128 select XFRM 129 ---help--- 130 Support for IPsec transport mode. 131 132 If unsure, say Y. 133 134config INET6_XFRM_MODE_TUNNEL 135 tristate "IPv6: IPsec tunnel mode" 136 default IPV6 137 select XFRM 138 ---help--- 139 Support for IPsec tunnel mode. 140 141 If unsure, say Y. 142 143config INET6_XFRM_MODE_BEET 144 tristate "IPv6: IPsec BEET mode" 145 default IPV6 146 select XFRM 147 ---help--- 148 Support for IPsec BEET mode. 149 150 If unsure, say Y. 151 152config INET6_XFRM_MODE_ROUTEOPTIMIZATION 153 tristate "IPv6: MIPv6 route optimization mode (EXPERIMENTAL)" 154 depends on EXPERIMENTAL 155 select XFRM 156 ---help--- 157 Support for MIPv6 route optimization mode. 158 159config IPV6_SIT 160 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" 161 select INET_TUNNEL 162 select IPV6_NDISC_NODETYPE 163 default y 164 ---help--- 165 Tunneling means encapsulating data of one protocol type within 166 another protocol and sending it over a channel that understands the 167 encapsulating protocol. This driver implements encapsulation of IPv6 168 into IPv4 packets. This is useful if you want to connect two IPv6 169 networks over an IPv4-only path. 170 171 Saying M here will produce a module called sit. If unsure, say Y. 172 173config IPV6_SIT_6RD 174 bool "IPv6: IPv6 Rapid Deployment (6RD) (EXPERIMENTAL)" 175 depends on IPV6_SIT && EXPERIMENTAL 176 default n 177 ---help--- 178 IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon 179 mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly 180 deploy IPv6 unicast service to IPv4 sites to which it provides 181 customer premise equipment. Like 6to4, it utilizes stateless IPv6 in 182 IPv4 encapsulation in order to transit IPv4-only network 183 infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 184 prefix of its own in place of the fixed 6to4 prefix. 185 186 With this option enabled, the SIT driver offers 6rd functionality by 187 providing additional ioctl API to configure the IPv6 Prefix for in 188 stead of static 2002::/16 for 6to4. 189 190 If unsure, say N. 191 192config IPV6_NDISC_NODETYPE 193 bool 194 195config IPV6_TUNNEL 196 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" 197 select INET6_TUNNEL 198 ---help--- 199 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in 200 RFC 2473. 201 202 If unsure, say N. 203 204config IPV6_MULTIPLE_TABLES 205 bool "IPv6: Multiple Routing Tables" 206 depends on EXPERIMENTAL 207 select FIB_RULES 208 ---help--- 209 Support multiple routing tables. 210 211config IPV6_SUBTREES 212 bool "IPv6: source address based routing" 213 depends on IPV6_MULTIPLE_TABLES 214 ---help--- 215 Enable routing by source address or prefix. 216 217 The destination address is still the primary routing key, so mixing 218 normal and source prefix specific routes in the same routing table 219 may sometimes lead to unintended routing behavior. This can be 220 avoided by defining different routing tables for the normal and 221 source prefix specific routes. 222 223 If unsure, say N. 224 225config IPV6_MROUTE 226 bool "IPv6: multicast routing (EXPERIMENTAL)" 227 depends on IPV6 && EXPERIMENTAL 228 ---help--- 229 Experimental support for IPv6 multicast forwarding. 230 If unsure, say N. 231 232config IPV6_MROUTE_MULTIPLE_TABLES 233 bool "IPv6: multicast policy routing" 234 depends on IPV6_MROUTE 235 select FIB_RULES 236 help 237 Normally, a multicast router runs a userspace daemon and decides 238 what to do with a multicast packet based on the source and 239 destination addresses. If you say Y here, the multicast router 240 will also be able to take interfaces and packet marks into 241 account and run multiple instances of userspace daemons 242 simultaneously, each one handling a single table. 243 244 If unsure, say N. 245 246config IPV6_PIMSM_V2 247 bool "IPv6: PIM-SM version 2 support (EXPERIMENTAL)" 248 depends on IPV6_MROUTE 249 ---help--- 250 Support for IPv6 PIM multicast routing protocol PIM-SMv2. 251 If unsure, say N. 252 253endif # IPV6 254