]> bbs.cooldavid.org Git - net-next-2.6.git/blame - net/ipv6/Kconfig
[NETNS][IPV6] route6 - dynamically allocate ip6_dst_ops
[net-next-2.6.git] / net / ipv6 / Kconfig
CommitLineData
1da177e4
LT
1#
2# IPv6 configuration
6a2e9b73
SR
3#
4
5# IPv6 as module will cause a CRASH if you try to unload it
6config 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 22config 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
41config 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
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
95c385b4
NH
60config IPV6_OPTIMISTIC_DAD
61 bool "IPv6: Enable RFC 4429 Optimistic DAD (EXPERIMENTAL)"
62 depends on IPV6 && 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
1da177e4
LT
70config INET6_AH
71 tristate "IPv6: AH transformation"
72 depends on IPV6
73 select XFRM
74 select CRYPTO
75 select CRYPTO_HMAC
76 select CRYPTO_MD5
77 select CRYPTO_SHA1
78 ---help---
79 Support for IPsec AH.
80
81 If unsure, say Y.
82
83config INET6_ESP
84 tristate "IPv6: ESP transformation"
85 depends on IPV6
86 select XFRM
87 select CRYPTO
38320c70 88 select CRYPTO_AEAD
1da177e4
LT
89 select CRYPTO_HMAC
90 select CRYPTO_MD5
6b7326c8 91 select CRYPTO_CBC
1da177e4
LT
92 select CRYPTO_SHA1
93 select CRYPTO_DES
94 ---help---
95 Support for IPsec ESP.
96
97 If unsure, say Y.
98
99config INET6_IPCOMP
100 tristate "IPv6: IPComp transformation"
101 depends on IPV6
102 select XFRM
d2acc347 103 select INET6_XFRM_TUNNEL
1da177e4
LT
104 select CRYPTO
105 select CRYPTO_DEFLATE
106 ---help---
107 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
108 typically needed for IPsec.
109
110 If unsure, say Y.
111
ee538268 112config IPV6_MIP6
59fbb3a6 113 tristate "IPv6: Mobility (EXPERIMENTAL)"
ee538268
MN
114 depends on IPV6 && EXPERIMENTAL
115 select XFRM
116 ---help---
117 Support for IPv6 Mobility described in RFC 3775.
118
119 If unsure, say N.
120
d2acc347
HX
121config INET6_XFRM_TUNNEL
122 tristate
123 select INET6_TUNNEL
124 default n
125
1da177e4 126config INET6_TUNNEL
d2acc347
HX
127 tristate
128 default n
1da177e4 129
b59f45d0
HX
130config INET6_XFRM_MODE_TRANSPORT
131 tristate "IPv6: IPsec transport mode"
132 depends on IPV6
133 default IPV6
134 select XFRM
135 ---help---
136 Support for IPsec transport mode.
137
138 If unsure, say Y.
139
140config INET6_XFRM_MODE_TUNNEL
141 tristate "IPv6: IPsec tunnel mode"
142 depends on IPV6
143 default IPV6
144 select XFRM
145 ---help---
146 Support for IPsec tunnel mode.
147
148 If unsure, say Y.
149
0a69452c
DB
150config INET6_XFRM_MODE_BEET
151 tristate "IPv6: IPsec BEET mode"
152 depends on IPV6
153 default IPV6
154 select XFRM
155 ---help---
156 Support for IPsec BEET mode.
157
158 If unsure, say Y.
159
1d71627d
MN
160config INET6_XFRM_MODE_ROUTEOPTIMIZATION
161 tristate "IPv6: MIPv6 route optimization mode (EXPERIMENTAL)"
162 depends on IPV6 && EXPERIMENTAL
163 select XFRM
164 ---help---
165 Support for MIPv6 route optimization mode.
166
989e5b96
JR
167config IPV6_SIT
168 tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
169 depends on IPV6
c73cb5a2 170 select INET_TUNNEL
989e5b96
JR
171 default y
172 ---help---
173 Tunneling means encapsulating data of one protocol type within
174 another protocol and sending it over a channel that understands the
175 encapsulating protocol. This driver implements encapsulation of IPv6
176 into IPv4 packets. This is useful if you want to connect two IPv6
177 networks over an IPv4-only path.
178
179 Saying M here will produce a module called sit.ko. If unsure, say Y.
180
1da177e4
LT
181config IPV6_TUNNEL
182 tristate "IPv6: IPv6-in-IPv6 tunnel"
d2acc347 183 select INET6_TUNNEL
1da177e4 184 depends on IPV6
1da177e4
LT
185 ---help---
186 Support for IPv6-in-IPv6 tunnels described in RFC 2473.
187
188 If unsure, say N.
189
264e91b6
VN
190config IPV6_MULTIPLE_TABLES
191 bool "IPv6: Multiple Routing Tables"
192 depends on IPV6 && EXPERIMENTAL
193 select FIB_RULES
194 ---help---
195 Support multiple routing tables.
196
4e96c2b4
YH
197config IPV6_SUBTREES
198 bool "IPv6: source address based routing"
264e91b6 199 depends on IPV6_MULTIPLE_TABLES
4e96c2b4
YH
200 ---help---
201 Enable routing by source address or prefix.
202
203 The destination address is still the primary routing key, so mixing
204 normal and source prefix specific routes in the same routing table
205 may sometimes lead to unintended routing behavior. This can be
206 avoided by defining different routing tables for the normal and
207 source prefix specific routes.
208
209 If unsure, say N.
210