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 IPV6_NDISC_NODETYPE 160 default y 161 ---help--- 162 Tunneling means encapsulating data of one protocol type within 163 another protocol and sending it over a channel that understands the 164 encapsulating protocol. This driver implements encapsulation of IPv6 165 into IPv4 packets. This is useful if you want to connect two IPv6 166 networks over an IPv4-only path. 167 168 Saying M here will produce a module called sit. If unsure, say Y. 169 170config IPV6_SIT_6RD 171 bool "IPv6: IPv6 Rapid Deployment (6RD)" 172 depends on IPV6_SIT 173 default n 174 ---help--- 175 IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon 176 mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly 177 deploy IPv6 unicast service to IPv4 sites to which it provides 178 customer premise equipment. Like 6to4, it utilizes stateless IPv6 in 179 IPv4 encapsulation in order to transit IPv4-only network 180 infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 181 prefix of its own in place of the fixed 6to4 prefix. 182 183 With this option enabled, the SIT driver offers 6rd functionality by 184 providing additional ioctl API to configure the IPv6 Prefix for in 185 stead of static 2002::/16 for 6to4. 186 187 If unsure, say N. 188 189config IPV6_NDISC_NODETYPE 190 bool 191 192config IPV6_TUNNEL 193 tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" 194 select INET6_TUNNEL 195 ---help--- 196 Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in 197 RFC 2473. 198 199 If unsure, say N. 200 201config IPV6_GRE 202 tristate "IPv6: GRE tunnel" 203 select IPV6_TUNNEL 204 ---help--- 205 Tunneling means encapsulating data of one protocol type within 206 another protocol and sending it over a channel that understands the 207 encapsulating protocol. This particular tunneling driver implements 208 GRE (Generic Routing Encapsulation) and at this time allows 209 encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure. 210 This driver is useful if the other endpoint is a Cisco router: Cisco 211 likes GRE much better than the other Linux tunneling driver ("IP 212 tunneling" above). In addition, GRE allows multicast redistribution 213 through the tunnel. 214 215 Saying M here will produce a module called ip6_gre. If unsure, say N. 216 217config IPV6_MULTIPLE_TABLES 218 bool "IPv6: Multiple Routing Tables" 219 select FIB_RULES 220 ---help--- 221 Support multiple routing tables. 222 223config IPV6_SUBTREES 224 bool "IPv6: source address based routing" 225 depends on IPV6_MULTIPLE_TABLES 226 ---help--- 227 Enable routing by source address or prefix. 228 229 The destination address is still the primary routing key, so mixing 230 normal and source prefix specific routes in the same routing table 231 may sometimes lead to unintended routing behavior. This can be 232 avoided by defining different routing tables for the normal and 233 source prefix specific routes. 234 235 If unsure, say N. 236 237config IPV6_MROUTE 238 bool "IPv6: multicast routing" 239 depends on IPV6 240 ---help--- 241 Experimental support for IPv6 multicast forwarding. 242 If unsure, say N. 243 244config IPV6_MROUTE_MULTIPLE_TABLES 245 bool "IPv6: multicast policy routing" 246 depends on IPV6_MROUTE 247 select FIB_RULES 248 help 249 Normally, a multicast router runs a userspace daemon and decides 250 what to do with a multicast packet based on the source and 251 destination addresses. If you say Y here, the multicast router 252 will also be able to take interfaces and packet marks into 253 account and run multiple instances of userspace daemons 254 simultaneously, each one handling a single table. 255 256 If unsure, say N. 257 258config IPV6_PIMSM_V2 259 bool "IPv6: PIM-SM version 2 support" 260 depends on IPV6_MROUTE 261 ---help--- 262 Support for IPv6 PIM multicast routing protocol PIM-SMv2. 263 If unsure, say N. 264 265endif # IPV6 266