projects / linux-2.6 / blame
| Commit | Line | Data |
|---|---|---|
| 1da177e4 LT |
1 | # |
| 2 | # IPv6 configuration | |
| 6a2e9b73 SR |
3 | # |
| 4 | ||
| 5 | # IPv6 as module will cause a CRASH if you try to unload it | |
| 6 | config IPV6 | |
| 7 | tristate "The IPv6 protocol" | |
| 8 | default m | |
| 6a2e9b73 SR |
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 | ||
| 1da177e4 | 22 | config IPV6_PRIVACY |
| 955189ef | 23 | bool "IPv6: Privacy Extensions support" |
| 1da177e4 LT |
24 | depends on IPV6 |
| 25 | ---help--- | |
| 26 | Privacy Extensions for Stateless Address Autoconfiguration in IPv6 | |
| 27 | support. With this option, additional periodically-alter | |
| 28 | pseudo-random global-scope unicast address(es) will assigned to | |
| 29 | your interface(s). | |
| 30 | ||
| 955189ef YH |
31 | We use our standard pseudo random algorithm to generate randomized |
| 32 | interface identifier, instead of one described in RFC 3041. | |
| 33 | ||
| 1da177e4 LT |
34 | By default, kernel do not generate temporary addresses. |
| 35 | To use temporary addresses, do | |
| 36 | ||
| 37 | echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr | |
| 38 | ||
| 39 | See <file:Documentation/networking/ip-sysctl.txt> for details. | |
| 40 | ||
| ebacaaa0 YH |
41 | config IPV6_ROUTER_PREF |
| 42 | bool "IPv6: Router Preference (RFC 4191) support" | |
| 43 | depends on IPV6 | |
| 44 | ---help--- | |
| 45 | Router Preference is an optional extension to the Router | |
| 46 | Advertisement message to improve the ability of hosts | |
| 47 | to pick more appropriate router, especially when the hosts | |
| 48 | is placed in a multi-homed network. | |
| 49 | ||
| 50 | If unsure, say N. | |
| 51 | ||
| 70ceb4f5 YH |
52 | config 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 | ||
| 1da177e4 LT |
60 | config INET6_AH |
| 61 | tristate "IPv6: AH transformation" | |
| 62 | depends on IPV6 | |
| 63 | select XFRM | |
| 64 | select CRYPTO | |
| 65 | select CRYPTO_HMAC | |
| 66 | select CRYPTO_MD5 | |
| 67 | select CRYPTO_SHA1 | |
| 68 | ---help--- | |
| 69 | Support for IPsec AH. | |
| 70 | ||
| 71 | If unsure, say Y. | |
| 72 | ||
| 73 | config INET6_ESP | |
| 74 | tristate "IPv6: ESP transformation" | |
| 75 | depends on IPV6 | |
| 76 | select XFRM | |
| 77 | select CRYPTO | |
| 78 | select CRYPTO_HMAC | |
| 79 | select CRYPTO_MD5 | |
| 6b7326c8 | 80 | select CRYPTO_CBC |
| 1da177e4 LT |
81 | select CRYPTO_SHA1 |
| 82 | select CRYPTO_DES | |
| 83 | ---help--- | |
| 84 | Support for IPsec ESP. | |
| 85 | ||
| 86 | If unsure, say Y. | |
| 87 | ||
| 88 | config INET6_IPCOMP | |
| 89 | tristate "IPv6: IPComp transformation" | |
| 90 | depends on IPV6 | |
| 91 | select XFRM | |
| d2acc347 | 92 | select INET6_XFRM_TUNNEL |
| 1da177e4 LT |
93 | select CRYPTO |
| 94 | select CRYPTO_DEFLATE | |
| 95 | ---help--- | |
| 96 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), | |
| 97 | typically needed for IPsec. | |
| 98 | ||
| 99 | If unsure, say Y. | |
| 100 | ||
| ee538268 MN |
101 | config IPV6_MIP6 |
| 102 | bool "IPv6: Mobility (EXPERIMENTAL)" | |
| 103 | depends on IPV6 && EXPERIMENTAL | |
| 104 | select XFRM | |
| 105 | ---help--- | |
| 106 | Support for IPv6 Mobility described in RFC 3775. | |
| 107 | ||
| 108 | If unsure, say N. | |
| 109 | ||
| d2acc347 HX |
110 | config INET6_XFRM_TUNNEL |
| 111 | tristate | |
| 112 | select INET6_TUNNEL | |
| 113 | default n | |
| 114 | ||
| 1da177e4 | 115 | config INET6_TUNNEL |
| d2acc347 HX |
116 | tristate |
| 117 | default n | |
| 1da177e4 | 118 | |
| b59f45d0 HX |
119 | config INET6_XFRM_MODE_TRANSPORT |
| 120 | tristate "IPv6: IPsec transport mode" | |
| 121 | depends on IPV6 | |
| 122 | default IPV6 | |
| 123 | select XFRM | |
| 124 | ---help--- | |
| 125 | Support for IPsec transport mode. | |
| 126 | ||
| 127 | If unsure, say Y. | |
| 128 | ||
| 129 | config INET6_XFRM_MODE_TUNNEL | |
| 130 | tristate "IPv6: IPsec tunnel mode" | |
| 131 | depends on IPV6 | |
| 132 | default IPV6 | |
| 133 | select XFRM | |
| 134 | ---help--- | |
| 135 | Support for IPsec tunnel mode. | |
| 136 | ||
| 137 | If unsure, say Y. | |
| 138 | ||
| 0a69452c DB |
139 | config INET6_XFRM_MODE_BEET |
| 140 | tristate "IPv6: IPsec BEET mode" | |
| 141 | depends on IPV6 | |
| 142 | default IPV6 | |
| 143 | select XFRM | |
| 144 | ---help--- | |
| 145 | Support for IPsec BEET mode. | |
| 146 | ||
| 147 | If unsure, say Y. | |
| 148 | ||
| 1d71627d MN |
149 | config INET6_XFRM_MODE_ROUTEOPTIMIZATION |
| 150 | tristate "IPv6: MIPv6 route optimization mode (EXPERIMENTAL)" | |
| 151 | depends on IPV6 && EXPERIMENTAL | |
| 152 | select XFRM | |
| 153 | ---help--- | |
| 154 | Support for MIPv6 route optimization mode. | |
| 155 | ||
| 989e5b96 JR |
156 | config IPV6_SIT |
| 157 | tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" | |
| 158 | depends on IPV6 | |
| 159 | default y | |
| 160 | ---help--- | |
| 161 | Tunneling means encapsulating data of one protocol type within | |
| 162 | another protocol and sending it over a channel that understands the | |
| 163 | encapsulating protocol. This driver implements encapsulation of IPv6 | |
| 164 | into IPv4 packets. This is useful if you want to connect two IPv6 | |
| 165 | networks over an IPv4-only path. | |
| 166 | ||
| 167 | Saying M here will produce a module called sit.ko. If unsure, say Y. | |
| 168 | ||
| 1da177e4 LT |
169 | config IPV6_TUNNEL |
| 170 | tristate "IPv6: IPv6-in-IPv6 tunnel" | |
| d2acc347 | 171 | select INET6_TUNNEL |
| 1da177e4 | 172 | depends on IPV6 |
| 1da177e4 LT |
173 | ---help--- |
| 174 | Support for IPv6-in-IPv6 tunnels described in RFC 2473. | |
| 175 | ||
| 176 | If unsure, say N. | |
| 177 | ||
| 264e91b6 VN |
178 | config IPV6_MULTIPLE_TABLES |
| 179 | bool "IPv6: Multiple Routing Tables" | |
| 180 | depends on IPV6 && EXPERIMENTAL | |
| 181 | select FIB_RULES | |
| 182 | ---help--- | |
| 183 | Support multiple routing tables. | |
| 184 | ||
| 4e96c2b4 YH |
185 | config IPV6_SUBTREES |
| 186 | bool "IPv6: source address based routing" | |
| 264e91b6 | 187 | depends on IPV6_MULTIPLE_TABLES |
| 4e96c2b4 YH |
188 | ---help--- |
| 189 | Enable routing by source address or prefix. | |
| 190 | ||
| 191 | The destination address is still the primary routing key, so mixing | |
| 192 | normal and source prefix specific routes in the same routing table | |
| 193 | may sometimes lead to unintended routing behavior. This can be | |
| 194 | avoided by defining different routing tables for the normal and | |
| 195 | source prefix specific routes. | |
| 196 | ||
| 197 | If unsure, say N. | |
| 198 |