Root/
1 | # |
2 | # IPv6 configuration |
3 | # |
4 | |
5 | # IPv6 as module will cause a CRASH if you try to unload it |
6 | menuconfig 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 | |
22 | if IPV6 |
23 | |
24 | config IPV6_ROUTER_PREF |
25 | bool "IPv6: Router Preference (RFC 4191) support" |
26 | ---help--- |
27 | Router Preference is an optional extension to the Router |
28 | Advertisement message which improves the ability of hosts |
29 | to pick an appropriate router, especially when the hosts |
30 | are placed in a multi-homed network. |
31 | |
32 | If unsure, say N. |
33 | |
34 | config IPV6_ROUTE_INFO |
35 | bool "IPv6: Route Information (RFC 4191) support" |
36 | depends on IPV6_ROUTER_PREF |
37 | ---help--- |
38 | This is experimental support of Route Information. |
39 | |
40 | If unsure, say N. |
41 | |
42 | config IPV6_OPTIMISTIC_DAD |
43 | bool "IPv6: Enable RFC 4429 Optimistic DAD" |
44 | ---help--- |
45 | This is experimental support for optimistic Duplicate |
46 | Address Detection. It allows for autoconfigured addresses |
47 | to be used more quickly. |
48 | |
49 | If unsure, say N. |
50 | |
51 | config INET6_AH |
52 | tristate "IPv6: AH transformation" |
53 | select XFRM_ALGO |
54 | select CRYPTO |
55 | select CRYPTO_HMAC |
56 | select CRYPTO_MD5 |
57 | select CRYPTO_SHA1 |
58 | ---help--- |
59 | Support for IPsec AH. |
60 | |
61 | If unsure, say Y. |
62 | |
63 | config INET6_ESP |
64 | tristate "IPv6: ESP transformation" |
65 | select XFRM_ALGO |
66 | select CRYPTO |
67 | select CRYPTO_AUTHENC |
68 | select CRYPTO_HMAC |
69 | select CRYPTO_MD5 |
70 | select CRYPTO_CBC |
71 | select CRYPTO_SHA1 |
72 | select CRYPTO_DES |
73 | ---help--- |
74 | Support for IPsec ESP. |
75 | |
76 | If unsure, say Y. |
77 | |
78 | config INET6_IPCOMP |
79 | tristate "IPv6: IPComp transformation" |
80 | select INET6_XFRM_TUNNEL |
81 | select XFRM_IPCOMP |
82 | ---help--- |
83 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), |
84 | typically needed for IPsec. |
85 | |
86 | If unsure, say Y. |
87 | |
88 | config IPV6_MIP6 |
89 | tristate "IPv6: Mobility" |
90 | select XFRM |
91 | ---help--- |
92 | Support for IPv6 Mobility described in RFC 3775. |
93 | |
94 | If unsure, say N. |
95 | |
96 | config INET6_XFRM_TUNNEL |
97 | tristate |
98 | select INET6_TUNNEL |
99 | default n |
100 | |
101 | config INET6_TUNNEL |
102 | tristate |
103 | default n |
104 | |
105 | config INET6_XFRM_MODE_TRANSPORT |
106 | tristate "IPv6: IPsec transport mode" |
107 | default IPV6 |
108 | select XFRM |
109 | ---help--- |
110 | Support for IPsec transport mode. |
111 | |
112 | If unsure, say Y. |
113 | |
114 | config INET6_XFRM_MODE_TUNNEL |
115 | tristate "IPv6: IPsec tunnel mode" |
116 | default IPV6 |
117 | select XFRM |
118 | ---help--- |
119 | Support for IPsec tunnel mode. |
120 | |
121 | If unsure, say Y. |
122 | |
123 | config INET6_XFRM_MODE_BEET |
124 | tristate "IPv6: IPsec BEET mode" |
125 | default IPV6 |
126 | select XFRM |
127 | ---help--- |
128 | Support for IPsec BEET mode. |
129 | |
130 | If unsure, say Y. |
131 | |
132 | config INET6_XFRM_MODE_ROUTEOPTIMIZATION |
133 | tristate "IPv6: MIPv6 route optimization mode" |
134 | select XFRM |
135 | ---help--- |
136 | Support for MIPv6 route optimization mode. |
137 | |
138 | config IPV6_VTI |
139 | tristate "Virtual (secure) IPv6: tunneling" |
140 | select IPV6_TUNNEL |
141 | depends on INET6_XFRM_MODE_TUNNEL |
142 | ---help--- |
143 | Tunneling means encapsulating data of one protocol type within |
144 | another protocol and sending it over a channel that understands the |
145 | encapsulating protocol. This can be used with xfrm mode tunnel to give |
146 | the notion of a secure tunnel for IPSEC and then use routing protocol |
147 | on top. |
148 | |
149 | config IPV6_SIT |
150 | tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)" |
151 | select INET_TUNNEL |
152 | select NET_IP_TUNNEL |
153 | select IPV6_NDISC_NODETYPE |
154 | default y |
155 | ---help--- |
156 | Tunneling means encapsulating data of one protocol type within |
157 | another protocol and sending it over a channel that understands the |
158 | encapsulating protocol. This driver implements encapsulation of IPv6 |
159 | into IPv4 packets. This is useful if you want to connect two IPv6 |
160 | networks over an IPv4-only path. |
161 | |
162 | Saying M here will produce a module called sit. If unsure, say Y. |
163 | |
164 | config IPV6_SIT_6RD |
165 | bool "IPv6: IPv6 Rapid Deployment (6RD)" |
166 | depends on IPV6_SIT |
167 | default n |
168 | ---help--- |
169 | IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon |
170 | mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly |
171 | deploy IPv6 unicast service to IPv4 sites to which it provides |
172 | customer premise equipment. Like 6to4, it utilizes stateless IPv6 in |
173 | IPv4 encapsulation in order to transit IPv4-only network |
174 | infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 |
175 | prefix of its own in place of the fixed 6to4 prefix. |
176 | |
177 | With this option enabled, the SIT driver offers 6rd functionality by |
178 | providing additional ioctl API to configure the IPv6 Prefix for in |
179 | stead of static 2002::/16 for 6to4. |
180 | |
181 | If unsure, say N. |
182 | |
183 | config IPV6_NDISC_NODETYPE |
184 | bool |
185 | |
186 | config IPV6_TUNNEL |
187 | tristate "IPv6: IP-in-IPv6 tunnel (RFC2473)" |
188 | select INET6_TUNNEL |
189 | ---help--- |
190 | Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in |
191 | RFC 2473. |
192 | |
193 | If unsure, say N. |
194 | |
195 | config IPV6_GRE |
196 | tristate "IPv6: GRE tunnel" |
197 | select IPV6_TUNNEL |
198 | select NET_IP_TUNNEL |
199 | ---help--- |
200 | Tunneling means encapsulating data of one protocol type within |
201 | another protocol and sending it over a channel that understands the |
202 | encapsulating protocol. This particular tunneling driver implements |
203 | GRE (Generic Routing Encapsulation) and at this time allows |
204 | encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure. |
205 | This driver is useful if the other endpoint is a Cisco router: Cisco |
206 | likes GRE much better than the other Linux tunneling driver ("IP |
207 | tunneling" above). In addition, GRE allows multicast redistribution |
208 | through the tunnel. |
209 | |
210 | Saying M here will produce a module called ip6_gre. If unsure, say N. |
211 | |
212 | config IPV6_MULTIPLE_TABLES |
213 | bool "IPv6: Multiple Routing Tables" |
214 | select FIB_RULES |
215 | ---help--- |
216 | Support multiple routing tables. |
217 | |
218 | config IPV6_SUBTREES |
219 | bool "IPv6: source address based routing" |
220 | depends on IPV6_MULTIPLE_TABLES |
221 | ---help--- |
222 | Enable routing by source address or prefix. |
223 | |
224 | The destination address is still the primary routing key, so mixing |
225 | normal and source prefix specific routes in the same routing table |
226 | may sometimes lead to unintended routing behavior. This can be |
227 | avoided by defining different routing tables for the normal and |
228 | source prefix specific routes. |
229 | |
230 | If unsure, say N. |
231 | |
232 | config IPV6_MROUTE |
233 | bool "IPv6: multicast routing" |
234 | depends on IPV6 |
235 | ---help--- |
236 | Experimental support for IPv6 multicast forwarding. |
237 | If unsure, say N. |
238 | |
239 | config IPV6_MROUTE_MULTIPLE_TABLES |
240 | bool "IPv6: multicast policy routing" |
241 | depends on IPV6_MROUTE |
242 | select FIB_RULES |
243 | help |
244 | Normally, a multicast router runs a userspace daemon and decides |
245 | what to do with a multicast packet based on the source and |
246 | destination addresses. If you say Y here, the multicast router |
247 | will also be able to take interfaces and packet marks into |
248 | account and run multiple instances of userspace daemons |
249 | simultaneously, each one handling a single table. |
250 | |
251 | If unsure, say N. |
252 | |
253 | config IPV6_PIMSM_V2 |
254 | bool "IPv6: PIM-SM version 2 support" |
255 | depends on IPV6_MROUTE |
256 | ---help--- |
257 | Support for IPv6 PIM multicast routing protocol PIM-SMv2. |
258 | If unsure, say N. |
259 | |
260 | endif # IPV6 |
261 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9