blob: 24e2b7294bf89e46874cd7dd7dd30f2d08c15c5f [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# IP configuration
3#
Linus Torvalds1da177e2005-04-16 15:20:36 -07004config IP_MULTICAST
5 bool "IP: multicasting"
Linus Torvalds1da177e2005-04-16 15:20:36 -07006 help
7 This is code for addressing several networked computers at once,
8 enlarging your kernel by about 2 KB. You need multicasting if you
9 intend to participate in the MBONE, a high bandwidth network on top
10 of the Internet which carries audio and video broadcasts. More
11 information about the MBONE is on the WWW at
Adrian Bunk936bb142007-02-17 19:49:13 +010012 <http://www.savetz.com/mbone/>. Information about the multicast
Linus Torvalds1da177e2005-04-16 15:20:36 -070013 capabilities of the various network cards is contained in
14 <file:Documentation/networking/multicast.txt>. For most people, it's
15 safe to say N.
16
17config IP_ADVANCED_ROUTER
18 bool "IP: advanced router"
Linus Torvalds1da177e2005-04-16 15:20:36 -070019 ---help---
20 If you intend to run your Linux box mostly as a router, i.e. as a
21 computer that forwards and redistributes network packets, say Y; you
22 will then be presented with several options that allow more precise
23 control about the routing process.
24
25 The answer to this question won't directly affect the kernel:
26 answering N will just cause the configurator to skip all the
27 questions about advanced routing.
28
29 Note that your box can only act as a router if you enable IP
30 forwarding in your kernel; you can do that by saying Y to "/proc
31 file system support" and "Sysctl support" below and executing the
32 line
33
34 echo "1" > /proc/sys/net/ipv4/ip_forward
35
36 at boot time after the /proc file system has been mounted.
37
38 If you turn on IP forwarding, you will also get the rp_filter, which
39 automatically rejects incoming packets if the routing table entry
40 for their source address doesn't match the network interface they're
41 arriving on. This has security advantages because it prevents the
42 so-called IP spoofing, however it can pose problems if you use
43 asymmetric routing (packets from you to a host take a different path
44 than packets from that host to you) or if you operate a non-routing
45 host which has several IP addresses on different interfaces. To turn
Dave Jonesd7394372007-05-17 15:02:21 -070046 rp_filter on use:
Linus Torvalds1da177e2005-04-16 15:20:36 -070047
Dave Jonesd7394372007-05-17 15:02:21 -070048 echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
Linus Torvalds1da177e2005-04-16 15:20:36 -070049 or
Dave Jonesd7394372007-05-17 15:02:21 -070050 echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
Linus Torvalds1da177e2005-04-16 15:20:36 -070051
52 If unsure, say N here.
53
David S. Millerbb298ca2005-06-24 17:50:53 -070054choice
55 prompt "Choose IP: FIB lookup algorithm (choose FIB_HASH if unsure)"
56 depends on IP_ADVANCED_ROUTER
Adrian Bunk6876f952005-07-18 13:55:19 -070057 default ASK_IP_FIB_HASH
David S. Millerbb298ca2005-06-24 17:50:53 -070058
Adrian Bunk6876f952005-07-18 13:55:19 -070059config ASK_IP_FIB_HASH
David S. Millerbb298ca2005-06-24 17:50:53 -070060 bool "FIB_HASH"
61 ---help---
62 Current FIB is very proven and good enough for most users.
63
64config IP_FIB_TRIE
65 bool "FIB_TRIE"
66 ---help---
Matt LaPlante44c09202006-10-03 22:34:14 +020067 Use new experimental LC-trie as FIB lookup algorithm.
David S. Millerbb298ca2005-06-24 17:50:53 -070068 This improves lookup performance if you have a large
69 number of routes.
70
71 LC-trie is a longest matching prefix lookup algorithm which
72 performs better than FIB_HASH for large routing tables.
73 But, it consumes more memory and is more complex.
74
75 LC-trie is described in:
76
77 IP-address lookup using LC-tries. Stefan Nilsson and Gunnar Karlsson
78 IEEE Journal on Selected Areas in Communications, 17(6):1083-1092, June 1999
79 An experimental study of compression methods for dynamic tries
80 Stefan Nilsson and Matti Tikkanen. Algorithmica, 33(1):19-33, 2002.
81 http://www.nada.kth.se/~snilsson/public/papers/dyntrie2/
82
83endchoice
84
David S. Millerbb298ca2005-06-24 17:50:53 -070085config IP_FIB_HASH
Adrian Bunk6876f952005-07-18 13:55:19 -070086 def_bool ASK_IP_FIB_HASH || !IP_ADVANCED_ROUTER
David S. Millerbb298ca2005-06-24 17:50:53 -070087
Stephen Hemminger66a2f7f2008-01-12 21:23:17 -080088config IP_FIB_TRIE_STATS
89 bool "FIB TRIE statistics"
90 depends on IP_FIB_TRIE
91 ---help---
92 Keep track of statistics on structure of FIB TRIE table.
93 Useful for testing and measuring TRIE performance.
94
Linus Torvalds1da177e2005-04-16 15:20:36 -070095config IP_MULTIPLE_TABLES
96 bool "IP: policy routing"
97 depends on IP_ADVANCED_ROUTER
Thomas Grafe1ef4bf2006-08-04 03:39:22 -070098 select FIB_RULES
Linus Torvalds1da177e2005-04-16 15:20:36 -070099 ---help---
100 Normally, a router decides what to do with a received packet based
101 solely on the packet's final destination address. If you say Y here,
102 the Linux router will also be able to take the packet's source
103 address into account. Furthermore, the TOS (Type-Of-Service) field
104 of the packet can be used for routing decisions as well.
105
106 If you are interested in this, please see the preliminary
107 documentation at <http://www.compendium.com.ar/policy-routing.txt>
108 and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
109 You will need supporting software from
110 <ftp://ftp.tux.org/pub/net/ip-routing/>.
111
112 If unsure, say N.
113
Linus Torvalds1da177e2005-04-16 15:20:36 -0700114config IP_ROUTE_MULTIPATH
115 bool "IP: equal cost multipath"
116 depends on IP_ADVANCED_ROUTER
117 help
118 Normally, the routing tables specify a single action to be taken in
119 a deterministic manner for a given packet. If you say Y here
120 however, it becomes possible to attach several actions to a packet
121 pattern, in effect specifying several alternative paths to travel
122 for those packets. The router considers all these paths to be of
123 equal "cost" and chooses one of them in a non-deterministic fashion
124 if a matching packet arrives.
125
Linus Torvalds1da177e2005-04-16 15:20:36 -0700126config IP_ROUTE_VERBOSE
127 bool "IP: verbose route monitoring"
128 depends on IP_ADVANCED_ROUTER
129 help
130 If you say Y here, which is recommended, then the kernel will print
131 verbose messages regarding the routing, for example warnings about
132 received packets which look strange and could be evidence of an
133 attack or a misconfigured system somewhere. The information is
134 handled by the klogd daemon which is responsible for kernel messages
135 ("man klogd").
136
137config IP_PNP
138 bool "IP: kernel level autoconfiguration"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700139 help
140 This enables automatic configuration of IP addresses of devices and
141 of the routing table during kernel boot, based on either information
142 supplied on the kernel command line or by BOOTP or RARP protocols.
143 You need to say Y only for diskless machines requiring network
144 access to boot (in which case you want to say Y to "Root file system
145 on NFS" as well), because all other machines configure the network
146 in their startup scripts.
147
148config IP_PNP_DHCP
149 bool "IP: DHCP support"
150 depends on IP_PNP
151 ---help---
152 If you want your Linux box to mount its whole root file system (the
153 one containing the directory /) from some other computer over the
154 net via NFS and you want the IP address of your computer to be
155 discovered automatically at boot time using the DHCP protocol (a
156 special protocol designed for doing this job), say Y here. In case
157 the boot ROM of your network card was designed for booting Linux and
158 does DHCP itself, providing all necessary information on the kernel
159 command line, you can say N here.
160
161 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
162 must be operating on your network. Read
163 <file:Documentation/nfsroot.txt> for details.
164
165config IP_PNP_BOOTP
166 bool "IP: BOOTP support"
167 depends on IP_PNP
168 ---help---
169 If you want your Linux box to mount its whole root file system (the
170 one containing the directory /) from some other computer over the
171 net via NFS and you want the IP address of your computer to be
172 discovered automatically at boot time using the BOOTP protocol (a
173 special protocol designed for doing this job), say Y here. In case
174 the boot ROM of your network card was designed for booting Linux and
175 does BOOTP itself, providing all necessary information on the kernel
176 command line, you can say N here. If unsure, say Y. Note that if you
177 want to use BOOTP, a BOOTP server must be operating on your network.
178 Read <file:Documentation/nfsroot.txt> for details.
179
180config IP_PNP_RARP
181 bool "IP: RARP support"
182 depends on IP_PNP
183 help
184 If you want your Linux box to mount its whole root file system (the
185 one containing the directory /) from some other computer over the
186 net via NFS and you want the IP address of your computer to be
187 discovered automatically at boot time using the RARP protocol (an
188 older protocol which is being obsoleted by BOOTP and DHCP), say Y
189 here. Note that if you want to use RARP, a RARP server must be
190 operating on your network. Read <file:Documentation/nfsroot.txt> for
191 details.
192
193# not yet ready..
194# bool ' IP: ARP support' CONFIG_IP_PNP_ARP
195config NET_IPIP
196 tristate "IP: tunneling"
Herbert Xud2acc342006-03-28 01:12:13 -0800197 select INET_TUNNEL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198 ---help---
199 Tunneling means encapsulating data of one protocol type within
200 another protocol and sending it over a channel that understands the
201 encapsulating protocol. This particular tunneling driver implements
202 encapsulation of IP within IP, which sounds kind of pointless, but
203 can be useful if you want to make your (or some other) machine
204 appear on a different network than it physically is, or to use
205 mobile-IP facilities (allowing laptops to seamlessly move between
206 networks without changing their IP addresses).
207
208 Saying Y to this option will produce two modules ( = code which can
209 be inserted in and removed from the running kernel whenever you
210 want). Most people won't need this and can say N.
211
212config NET_IPGRE
213 tristate "IP: GRE tunnels over IP"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700214 help
215 Tunneling means encapsulating data of one protocol type within
216 another protocol and sending it over a channel that understands the
217 encapsulating protocol. This particular tunneling driver implements
218 GRE (Generic Routing Encapsulation) and at this time allows
219 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
220 This driver is useful if the other endpoint is a Cisco router: Cisco
221 likes GRE much better than the other Linux tunneling driver ("IP
222 tunneling" above). In addition, GRE allows multicast redistribution
223 through the tunnel.
224
225config NET_IPGRE_BROADCAST
226 bool "IP: broadcast GRE over IP"
227 depends on IP_MULTICAST && NET_IPGRE
228 help
229 One application of GRE/IP is to construct a broadcast WAN (Wide Area
230 Network), which looks like a normal Ethernet LAN (Local Area
231 Network), but can be distributed all over the Internet. If you want
232 to do that, say Y here and to "IP multicast routing" below.
233
234config IP_MROUTE
235 bool "IP: multicast routing"
236 depends on IP_MULTICAST
237 help
238 This is used if you want your machine to act as a router for IP
239 packets that have several destination addresses. It is needed on the
240 MBONE, a high bandwidth network on top of the Internet which carries
241 audio and video broadcasts. In order to do that, you would most
242 likely run the program mrouted. Information about the multicast
243 capabilities of the various network cards is contained in
244 <file:Documentation/networking/multicast.txt>. If you haven't heard
245 about it, you don't need it.
246
247config IP_PIMSM_V1
248 bool "IP: PIM-SM version 1 support"
249 depends on IP_MROUTE
250 help
251 Kernel side support for Sparse Mode PIM (Protocol Independent
252 Multicast) version 1. This multicast routing protocol is used widely
253 because Cisco supports it. You need special software to use it
254 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
255 information about PIM.
256
257 Say Y if you want to use PIM-SM v1. Note that you can say N here if
258 you just want to use Dense Mode PIM.
259
260config IP_PIMSM_V2
261 bool "IP: PIM-SM version 2 support"
262 depends on IP_MROUTE
263 help
264 Kernel side support for Sparse Mode PIM version 2. In order to use
265 this, you need an experimental routing daemon supporting it (pimd or
266 gated-5). This routing protocol is not used widely, so say N unless
267 you want to play with it.
268
269config ARPD
270 bool "IP: ARP daemon support (EXPERIMENTAL)"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700271 depends on EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700272 ---help---
273 Normally, the kernel maintains an internal cache which maps IP
274 addresses to hardware addresses on the local network, so that
275 Ethernet/Token Ring/ etc. frames are sent to the proper address on
276 the physical networking layer. For small networks having a few
277 hundred directly connected hosts or less, keeping this address
278 resolution (ARP) cache inside the kernel works well. However,
279 maintaining an internal ARP cache does not work well for very large
280 switched networks, and will use a lot of kernel memory if TCP/IP
281 connections are made to many machines on the network.
282
283 If you say Y here, the kernel's internal ARP cache will never grow
284 to more than 256 entries (the oldest entries are expired in a LIFO
285 manner) and communication will be attempted with the user space ARP
286 daemon arpd. Arpd then answers the address resolution request either
287 from its own cache or by asking the net.
288
289 This code is experimental and also obsolete. If you want to use it,
290 you need to find a version of the daemon arpd on the net somewhere,
291 and you should also say Y to "Kernel/User network link driver",
292 below. If unsure, say N.
293
294config SYN_COOKIES
295 bool "IP: TCP syncookie support (disabled per default)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700296 ---help---
297 Normal TCP/IP networking is open to an attack known as "SYN
298 flooding". This denial-of-service attack prevents legitimate remote
299 users from being able to connect to your computer during an ongoing
300 attack and requires very little work from the attacker, who can
301 operate from anywhere on the Internet.
302
303 SYN cookies provide protection against this type of attack. If you
304 say Y here, the TCP/IP stack will use a cryptographic challenge
305 protocol known as "SYN cookies" to enable legitimate users to
306 continue to connect, even when your machine is under attack. There
307 is no need for the legitimate users to change their TCP/IP software;
308 SYN cookies work transparently to them. For technical information
309 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
310
311 If you are SYN flooded, the source address reported by the kernel is
312 likely to have been forged by the attacker; it is only reported as
313 an aid in tracing the packets to their actual source and should not
314 be taken as absolute truth.
315
316 SYN cookies may prevent correct error reporting on clients when the
317 server is really overloaded. If this happens frequently better turn
318 them off.
319
320 If you say Y here, note that SYN cookies aren't enabled by default;
321 you can enable them by saying Y to "/proc file system support" and
322 "Sysctl support" below and executing the command
323
324 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
325
326 at boot time after the /proc file system has been mounted.
327
328 If unsure, say N.
329
330config INET_AH
331 tristate "IP: AH transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700332 select XFRM
333 select CRYPTO
334 select CRYPTO_HMAC
335 select CRYPTO_MD5
336 select CRYPTO_SHA1
337 ---help---
338 Support for IPsec AH.
339
340 If unsure, say Y.
341
342config INET_ESP
343 tristate "IP: ESP transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700344 select XFRM
345 select CRYPTO
346 select CRYPTO_HMAC
347 select CRYPTO_MD5
Herbert Xu6b7326c2006-07-30 15:41:01 +1000348 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700349 select CRYPTO_SHA1
350 select CRYPTO_DES
351 ---help---
352 Support for IPsec ESP.
353
354 If unsure, say Y.
355
356config INET_IPCOMP
357 tristate "IP: IPComp transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700358 select XFRM
Herbert Xud2acc342006-03-28 01:12:13 -0800359 select INET_XFRM_TUNNEL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700360 select CRYPTO
361 select CRYPTO_DEFLATE
362 ---help---
363 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
364 typically needed for IPsec.
365
366 If unsure, say Y.
367
Herbert Xud2acc342006-03-28 01:12:13 -0800368config INET_XFRM_TUNNEL
369 tristate
370 select INET_TUNNEL
371 default n
372
Linus Torvalds1da177e2005-04-16 15:20:36 -0700373config INET_TUNNEL
Herbert Xud2acc342006-03-28 01:12:13 -0800374 tristate
375 default n
Linus Torvalds1da177e2005-04-16 15:20:36 -0700376
Herbert Xub59f45d2006-05-27 23:05:54 -0700377config INET_XFRM_MODE_TRANSPORT
378 tristate "IP: IPsec transport mode"
379 default y
380 select XFRM
381 ---help---
382 Support for IPsec transport mode.
383
384 If unsure, say Y.
385
386config INET_XFRM_MODE_TUNNEL
387 tristate "IP: IPsec tunnel mode"
388 default y
389 select XFRM
390 ---help---
391 Support for IPsec tunnel mode.
392
393 If unsure, say Y.
394
Diego Beltrami0a694522006-10-03 23:47:05 -0700395config INET_XFRM_MODE_BEET
396 tristate "IP: IPsec BEET mode"
397 default y
398 select XFRM
399 ---help---
400 Support for IPsec BEET mode.
401
402 If unsure, say Y.
403
Jan-Bernd Themann71c87e02007-08-08 22:38:05 -0700404config INET_LRO
405 tristate "Large Receive Offload (ipv4/tcp)"
406
407 ---help---
408 Support for Large Receive Offload (ipv4/tcp).
409
410 If unsure, say Y.
411
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300412config INET_DIAG
413 tristate "INET: socket monitoring interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700414 default y
415 ---help---
Arnaldo Carvalho de Melo73c1f4a2005-08-12 12:51:49 -0300416 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
417 native Linux tools such as ss. ss is included in iproute2, currently
Baruch Evenf4b94792007-02-21 19:32:37 -0800418 downloadable at <http://linux-net.osdl.org/index.php/Iproute2>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700419
420 If unsure, say Y.
421
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300422config INET_TCP_DIAG
423 depends on INET_DIAG
424 def_tristate INET_DIAG
425
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700426menuconfig TCP_CONG_ADVANCED
David S. Millera6484042005-06-24 18:07:51 -0700427 bool "TCP: advanced congestion control"
David S. Millera6484042005-06-24 18:07:51 -0700428 ---help---
429 Support for selection of various TCP congestion control
430 modules.
431
432 Nearly all users can safely say no here, and a safe default
Stephen Hemminger597811e2006-09-24 20:13:03 -0700433 selection will be made (CUBIC with new Reno as a fallback).
David S. Millera6484042005-06-24 18:07:51 -0700434
435 If unsure, say N.
436
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700437if TCP_CONG_ADVANCED
Stephen Hemminger83803032005-06-23 12:23:25 -0700438
439config TCP_CONG_BIC
440 tristate "Binary Increase Congestion (BIC) control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700441 default m
Stephen Hemminger83803032005-06-23 12:23:25 -0700442 ---help---
443 BIC-TCP is a sender-side only change that ensures a linear RTT
444 fairness under large windows while offering both scalability and
445 bounded TCP-friendliness. The protocol combines two schemes
446 called additive increase and binary search increase. When the
447 congestion window is large, additive increase with a large
448 increment ensures linear RTT fairness as well as good
449 scalability. Under small congestion windows, binary search
450 increase provides TCP friendliness.
451 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
452
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800453config TCP_CONG_CUBIC
454 tristate "CUBIC TCP"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700455 default y
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800456 ---help---
457 This is version 2.0 of BIC-TCP which uses a cubic growth function
458 among other techniques.
459 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
460
Stephen Hemminger87270762005-06-23 12:24:09 -0700461config TCP_CONG_WESTWOOD
462 tristate "TCP Westwood+"
Stephen Hemminger87270762005-06-23 12:24:09 -0700463 default m
464 ---help---
465 TCP Westwood+ is a sender-side only modification of the TCP Reno
466 protocol stack that optimizes the performance of TCP congestion
467 control. It is based on end-to-end bandwidth estimation to set
468 congestion window and slow start threshold after a congestion
469 episode. Using this estimation, TCP Westwood+ adaptively sets a
470 slow start threshold and a congestion window which takes into
471 account the bandwidth used at the time congestion is experienced.
472 TCP Westwood+ significantly increases fairness wrt TCP Reno in
473 wired networks and throughput over wireless links.
474
Baruch Evena7868ea2005-06-23 12:28:11 -0700475config TCP_CONG_HTCP
476 tristate "H-TCP"
Baruch Evena7868ea2005-06-23 12:28:11 -0700477 default m
478 ---help---
479 H-TCP is a send-side only modifications of the TCP Reno
480 protocol stack that optimizes the performance of TCP
481 congestion control for high speed network links. It uses a
482 modeswitch to change the alpha and beta parameters of TCP Reno
483 based on network conditions and in a way so as to be fair with
484 other Reno and H-TCP flows.
485
John Heffnera628d292005-06-23 12:24:58 -0700486config TCP_CONG_HSTCP
487 tristate "High Speed TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700488 depends on EXPERIMENTAL
John Heffnera628d292005-06-23 12:24:58 -0700489 default n
490 ---help---
491 Sally Floyd's High Speed TCP (RFC 3649) congestion control.
492 A modification to TCP's congestion control mechanism for use
493 with large congestion windows. A table indicates how much to
494 increase the congestion window by when an ACK is received.
495 For more detail see http://www.icir.org/floyd/hstcp.html
496
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700497config TCP_CONG_HYBLA
498 tristate "TCP-Hybla congestion control algorithm"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700499 depends on EXPERIMENTAL
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700500 default n
501 ---help---
502 TCP-Hybla is a sender-side only change that eliminates penalization of
503 long-RTT, large-bandwidth connections, like when satellite legs are
Matt LaPlante44c09202006-10-03 22:34:14 +0200504 involved, especially when sharing a common bottleneck with normal
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700505 terrestrial connections.
506
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700507config TCP_CONG_VEGAS
508 tristate "TCP Vegas"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700509 depends on EXPERIMENTAL
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700510 default n
511 ---help---
512 TCP Vegas is a sender-side only change to TCP that anticipates
513 the onset of congestion by estimating the bandwidth. TCP Vegas
514 adjusts the sending rate by modifying the congestion
515 window. TCP Vegas should provide less packet loss, but it is
516 not as aggressive as TCP Reno.
517
John Heffner0e579762005-06-23 12:29:07 -0700518config TCP_CONG_SCALABLE
519 tristate "Scalable TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700520 depends on EXPERIMENTAL
John Heffner0e579762005-06-23 12:29:07 -0700521 default n
522 ---help---
523 Scalable TCP is a sender-side only change to TCP which uses a
524 MIMD congestion control algorithm which has some nice scaling
525 properties, though is known to have fairness issues.
Baruch Evenf4b94792007-02-21 19:32:37 -0800526 See http://www.deneholme.net/tom/scalable/
Baruch Evena7868ea2005-06-23 12:28:11 -0700527
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700528config TCP_CONG_LP
529 tristate "TCP Low Priority"
530 depends on EXPERIMENTAL
531 default n
532 ---help---
533 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
Matt LaPlantecab00892006-10-03 22:36:44 +0200534 to utilize only the excess network bandwidth as compared to the
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700535 ``fair share`` of bandwidth as targeted by TCP.
536 See http://www-ece.rice.edu/networks/TCP-LP/
537
Bin Zhou76f10172006-06-05 17:28:30 -0700538config TCP_CONG_VENO
539 tristate "TCP Veno"
540 depends on EXPERIMENTAL
541 default n
542 ---help---
543 TCP Veno is a sender-side only enhancement of TCP to obtain better
544 throughput over wireless networks. TCP Veno makes use of state
545 distinguishing to circumvent the difficult judgment of the packet loss
546 type. TCP Veno cuts down less congestion window in response to random
547 loss packets.
548 See http://www.ntu.edu.sg/home5/ZHOU0022/papers/CPFu03a.pdf
549
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800550config TCP_CONG_YEAH
551 tristate "YeAH TCP"
552 depends on EXPERIMENTAL
David S. Miller2ff011e2007-05-17 00:07:47 -0700553 select TCP_CONG_VEGAS
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800554 default n
555 ---help---
556 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
557 algorithm, which uses a mixed loss/delay approach to compute the
558 congestion window. It's design goals target high efficiency,
559 internal, RTT and Reno fairness, resilience to link loss while
560 keeping network elements load as low as possible.
561
562 For further details look here:
563 http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
564
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700565config TCP_CONG_ILLINOIS
566 tristate "TCP Illinois"
567 depends on EXPERIMENTAL
568 default n
569 ---help---
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200570 TCP-Illinois is a sender-side modification of TCP Reno for
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700571 high speed long delay links. It uses round-trip-time to
572 adjust the alpha and beta parameters to achieve a higher average
573 throughput and maintain fairness.
574
575 For further details see:
576 http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
577
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700578choice
579 prompt "Default TCP congestion control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700580 default DEFAULT_CUBIC
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700581 help
582 Select the TCP congestion control that will be used by default
583 for all connections.
584
585 config DEFAULT_BIC
586 bool "Bic" if TCP_CONG_BIC=y
587
588 config DEFAULT_CUBIC
589 bool "Cubic" if TCP_CONG_CUBIC=y
590
591 config DEFAULT_HTCP
592 bool "Htcp" if TCP_CONG_HTCP=y
593
594 config DEFAULT_VEGAS
595 bool "Vegas" if TCP_CONG_VEGAS=y
596
597 config DEFAULT_WESTWOOD
598 bool "Westwood" if TCP_CONG_WESTWOOD=y
599
600 config DEFAULT_RENO
601 bool "Reno"
602
603endchoice
604
605endif
Stephen Hemminger83803032005-06-23 12:23:25 -0700606
Stephen Hemminger597811e2006-09-24 20:13:03 -0700607config TCP_CONG_CUBIC
David S. Miller6c360762005-06-26 15:20:20 -0700608 tristate
David S. Millera6484042005-06-24 18:07:51 -0700609 depends on !TCP_CONG_ADVANCED
610 default y
611
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700612config DEFAULT_TCP_CONG
613 string
614 default "bic" if DEFAULT_BIC
615 default "cubic" if DEFAULT_CUBIC
616 default "htcp" if DEFAULT_HTCP
617 default "vegas" if DEFAULT_VEGAS
618 default "westwood" if DEFAULT_WESTWOOD
619 default "reno" if DEFAULT_RENO
Stephen Hemminger597811e2006-09-24 20:13:03 -0700620 default "cubic"
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700621
YOSHIFUJI Hideakicfb6eeb2006-11-14 19:07:45 -0800622config TCP_MD5SIG
623 bool "TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL)"
624 depends on EXPERIMENTAL
625 select CRYPTO
626 select CRYPTO_MD5
627 ---help---
David Sterba3dde6ad2007-05-09 07:12:20 +0200628 RFC2385 specifies a method of giving MD5 protection to TCP sessions.
YOSHIFUJI Hideakicfb6eeb2006-11-14 19:07:45 -0800629 Its main (only?) use is to protect BGP sessions between core routers
630 on the Internet.
631
632 If unsure, say N.
633
Linus Torvalds1da177e2005-04-16 15:20:36 -0700634source "net/ipv4/ipvs/Kconfig"
635