blob: a5a1050595d1866c6cc4ce3df0ade8c94cc183b3 [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
Jesper Dangaard Brouerb2cc46a2009-02-22 00:06:20 -080038 If you turn on IP forwarding, you should consider the rp_filter, which
Linus Torvalds1da177e2005-04-16 15:20:36 -070039 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
Nicolas Dichtel750e9fa2010-08-31 05:50:43 +000049 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
Jesper Dangaard Brouerb2cc46a2009-02-22 00:06:20 -080052 Note that some distributions enable it in startup scripts.
Jesper Dangaard Brouerd18921a2009-02-23 04:40:43 +000053 For details about rp_filter strict and loose mode read
54 <file:Documentation/networking/ip-sysctl.txt>.
Jesper Dangaard Brouerb2cc46a2009-02-22 00:06:20 -080055
Linus Torvalds1da177e2005-04-16 15:20:36 -070056 If unsure, say N here.
57
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -080058choice
David S. Millerbb298ca2005-06-24 17:50:53 -070059 prompt "Choose IP: FIB lookup algorithm (choose FIB_HASH if unsure)"
60 depends on IP_ADVANCED_ROUTER
Adrian Bunk6876f952005-07-18 13:55:19 -070061 default ASK_IP_FIB_HASH
David S. Millerbb298ca2005-06-24 17:50:53 -070062
Adrian Bunk6876f952005-07-18 13:55:19 -070063config ASK_IP_FIB_HASH
David S. Millerbb298ca2005-06-24 17:50:53 -070064 bool "FIB_HASH"
65 ---help---
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -080066 Current FIB is very proven and good enough for most users.
David S. Millerbb298ca2005-06-24 17:50:53 -070067
68config IP_FIB_TRIE
69 bool "FIB_TRIE"
70 ---help---
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -080071 Use new experimental LC-trie as FIB lookup algorithm.
72 This improves lookup performance if you have a large
73 number of routes.
David S. Millerbb298ca2005-06-24 17:50:53 -070074
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -080075 LC-trie is a longest matching prefix lookup algorithm which
76 performs better than FIB_HASH for large routing tables.
77 But, it consumes more memory and is more complex.
78
79 LC-trie is described in:
80
81 IP-address lookup using LC-tries. Stefan Nilsson and Gunnar Karlsson
82 IEEE Journal on Selected Areas in Communications, 17(6):1083-1092,
83 June 1999
84
85 An experimental study of compression methods for dynamic tries
86 Stefan Nilsson and Matti Tikkanen. Algorithmica, 33(1):19-33, 2002.
Justin P. Mattock631dd1a2010-10-18 11:03:14 +020087 <http://www.csc.kth.se/~snilsson/software/dyntrie2/>
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -080088
David S. Millerbb298ca2005-06-24 17:50:53 -070089endchoice
90
David S. Millerbb298ca2005-06-24 17:50:53 -070091config IP_FIB_HASH
Adrian Bunk6876f952005-07-18 13:55:19 -070092 def_bool ASK_IP_FIB_HASH || !IP_ADVANCED_ROUTER
David S. Millerbb298ca2005-06-24 17:50:53 -070093
Stephen Hemminger66a2f7f2008-01-12 21:23:17 -080094config IP_FIB_TRIE_STATS
95 bool "FIB TRIE statistics"
96 depends on IP_FIB_TRIE
97 ---help---
98 Keep track of statistics on structure of FIB TRIE table.
99 Useful for testing and measuring TRIE performance.
100
Linus Torvalds1da177e2005-04-16 15:20:36 -0700101config IP_MULTIPLE_TABLES
102 bool "IP: policy routing"
103 depends on IP_ADVANCED_ROUTER
Thomas Grafe1ef4bf2006-08-04 03:39:22 -0700104 select FIB_RULES
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105 ---help---
106 Normally, a router decides what to do with a received packet based
107 solely on the packet's final destination address. If you say Y here,
108 the Linux router will also be able to take the packet's source
109 address into account. Furthermore, the TOS (Type-Of-Service) field
110 of the packet can be used for routing decisions as well.
111
112 If you are interested in this, please see the preliminary
113 documentation at <http://www.compendium.com.ar/policy-routing.txt>
114 and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
115 You will need supporting software from
116 <ftp://ftp.tux.org/pub/net/ip-routing/>.
117
118 If unsure, say N.
119
Linus Torvalds1da177e2005-04-16 15:20:36 -0700120config IP_ROUTE_MULTIPATH
121 bool "IP: equal cost multipath"
122 depends on IP_ADVANCED_ROUTER
123 help
124 Normally, the routing tables specify a single action to be taken in
125 a deterministic manner for a given packet. If you say Y here
126 however, it becomes possible to attach several actions to a packet
127 pattern, in effect specifying several alternative paths to travel
128 for those packets. The router considers all these paths to be of
129 equal "cost" and chooses one of them in a non-deterministic fashion
130 if a matching packet arrives.
131
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132config IP_ROUTE_VERBOSE
133 bool "IP: verbose route monitoring"
134 depends on IP_ADVANCED_ROUTER
135 help
136 If you say Y here, which is recommended, then the kernel will print
137 verbose messages regarding the routing, for example warnings about
138 received packets which look strange and could be evidence of an
139 attack or a misconfigured system somewhere. The information is
140 handled by the klogd daemon which is responsible for kernel messages
141 ("man klogd").
142
143config IP_PNP
144 bool "IP: kernel level autoconfiguration"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145 help
146 This enables automatic configuration of IP addresses of devices and
147 of the routing table during kernel boot, based on either information
148 supplied on the kernel command line or by BOOTP or RARP protocols.
149 You need to say Y only for diskless machines requiring network
150 access to boot (in which case you want to say Y to "Root file system
151 on NFS" as well), because all other machines configure the network
152 in their startup scripts.
153
154config IP_PNP_DHCP
155 bool "IP: DHCP support"
156 depends on IP_PNP
157 ---help---
158 If you want your Linux box to mount its whole root file system (the
159 one containing the directory /) from some other computer over the
160 net via NFS and you want the IP address of your computer to be
161 discovered automatically at boot time using the DHCP protocol (a
162 special protocol designed for doing this job), say Y here. In case
163 the boot ROM of your network card was designed for booting Linux and
164 does DHCP itself, providing all necessary information on the kernel
165 command line, you can say N here.
166
167 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
168 must be operating on your network. Read
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400169 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700170
171config IP_PNP_BOOTP
172 bool "IP: BOOTP support"
173 depends on IP_PNP
174 ---help---
175 If you want your Linux box to mount its whole root file system (the
176 one containing the directory /) from some other computer over the
177 net via NFS and you want the IP address of your computer to be
178 discovered automatically at boot time using the BOOTP protocol (a
179 special protocol designed for doing this job), say Y here. In case
180 the boot ROM of your network card was designed for booting Linux and
181 does BOOTP itself, providing all necessary information on the kernel
182 command line, you can say N here. If unsure, say Y. Note that if you
183 want to use BOOTP, a BOOTP server must be operating on your network.
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400184 Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700185
186config IP_PNP_RARP
187 bool "IP: RARP support"
188 depends on IP_PNP
189 help
190 If you want your Linux box to mount its whole root file system (the
191 one containing the directory /) from some other computer over the
192 net via NFS and you want the IP address of your computer to be
193 discovered automatically at boot time using the RARP protocol (an
194 older protocol which is being obsoleted by BOOTP and DHCP), say Y
195 here. Note that if you want to use RARP, a RARP server must be
J. Bruce Fields6ded55d2008-04-07 15:59:03 -0400196 operating on your network. Read
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400197 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198
199# not yet ready..
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -0800200# bool ' IP: ARP support' CONFIG_IP_PNP_ARP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700201config NET_IPIP
202 tristate "IP: tunneling"
Herbert Xud2acc342006-03-28 01:12:13 -0800203 select INET_TUNNEL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700204 ---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 encapsulation of IP within IP, which sounds kind of pointless, but
209 can be useful if you want to make your (or some other) machine
210 appear on a different network than it physically is, or to use
211 mobile-IP facilities (allowing laptops to seamlessly move between
212 networks without changing their IP addresses).
213
214 Saying Y to this option will produce two modules ( = code which can
215 be inserted in and removed from the running kernel whenever you
216 want). Most people won't need this and can say N.
217
Dmitry Kozlov00959ad2010-08-21 23:05:39 -0700218config NET_IPGRE_DEMUX
219 tristate "IP: GRE demultiplexer"
220 help
221 This is helper module to demultiplex GRE packets on GRE version field criteria.
222 Required by ip_gre and pptp modules.
223
Linus Torvalds1da177e2005-04-16 15:20:36 -0700224config NET_IPGRE
225 tristate "IP: GRE tunnels over IP"
David S. Miller21a180c2010-10-04 11:56:38 -0700226 depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700227 help
228 Tunneling means encapsulating data of one protocol type within
229 another protocol and sending it over a channel that understands the
230 encapsulating protocol. This particular tunneling driver implements
231 GRE (Generic Routing Encapsulation) and at this time allows
232 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
233 This driver is useful if the other endpoint is a Cisco router: Cisco
234 likes GRE much better than the other Linux tunneling driver ("IP
235 tunneling" above). In addition, GRE allows multicast redistribution
236 through the tunnel.
237
238config NET_IPGRE_BROADCAST
239 bool "IP: broadcast GRE over IP"
240 depends on IP_MULTICAST && NET_IPGRE
241 help
242 One application of GRE/IP is to construct a broadcast WAN (Wide Area
243 Network), which looks like a normal Ethernet LAN (Local Area
244 Network), but can be distributed all over the Internet. If you want
245 to do that, say Y here and to "IP multicast routing" below.
246
247config IP_MROUTE
248 bool "IP: multicast routing"
249 depends on IP_MULTICAST
250 help
251 This is used if you want your machine to act as a router for IP
252 packets that have several destination addresses. It is needed on the
253 MBONE, a high bandwidth network on top of the Internet which carries
254 audio and video broadcasts. In order to do that, you would most
255 likely run the program mrouted. Information about the multicast
256 capabilities of the various network cards is contained in
257 <file:Documentation/networking/multicast.txt>. If you haven't heard
258 about it, you don't need it.
259
Patrick McHardyf0ad0862010-04-13 05:03:23 +0000260config IP_MROUTE_MULTIPLE_TABLES
261 bool "IP: multicast policy routing"
Patrick McHardy66496d42010-04-15 13:29:27 +0200262 depends on IP_MROUTE && IP_ADVANCED_ROUTER
Patrick McHardyf0ad0862010-04-13 05:03:23 +0000263 select FIB_RULES
264 help
265 Normally, a multicast router runs a userspace daemon and decides
266 what to do with a multicast packet based on the source and
267 destination addresses. If you say Y here, the multicast router
268 will also be able to take interfaces and packet marks into
269 account and run multiple instances of userspace daemons
270 simultaneously, each one handling a single table.
271
272 If unsure, say N.
273
Linus Torvalds1da177e2005-04-16 15:20:36 -0700274config IP_PIMSM_V1
275 bool "IP: PIM-SM version 1 support"
276 depends on IP_MROUTE
277 help
278 Kernel side support for Sparse Mode PIM (Protocol Independent
279 Multicast) version 1. This multicast routing protocol is used widely
280 because Cisco supports it. You need special software to use it
281 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
282 information about PIM.
283
284 Say Y if you want to use PIM-SM v1. Note that you can say N here if
285 you just want to use Dense Mode PIM.
286
287config IP_PIMSM_V2
288 bool "IP: PIM-SM version 2 support"
289 depends on IP_MROUTE
290 help
291 Kernel side support for Sparse Mode PIM version 2. In order to use
292 this, you need an experimental routing daemon supporting it (pimd or
293 gated-5). This routing protocol is not used widely, so say N unless
294 you want to play with it.
295
296config ARPD
Timo Teräse61a4b62009-06-11 19:38:02 +0000297 bool "IP: ARP daemon support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700298 ---help---
Timo Teräse61a4b62009-06-11 19:38:02 +0000299 The kernel maintains an internal cache which maps IP addresses to
300 hardware addresses on the local network, so that Ethernet/Token Ring/
301 etc. frames are sent to the proper address on the physical networking
302 layer. Normally, kernel uses the ARP protocol to resolve these
303 mappings.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700304
Timo Teräse61a4b62009-06-11 19:38:02 +0000305 Saying Y here adds support to have an user space daemon to do this
306 resolution instead. This is useful for implementing an alternate
307 address resolution protocol (e.g. NHRP on mGRE tunnels) and also for
308 testing purposes.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700309
Timo Teräse61a4b62009-06-11 19:38:02 +0000310 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700311
312config SYN_COOKIES
Florian Westphal57f15532010-06-03 00:42:30 +0000313 bool "IP: TCP syncookie support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700314 ---help---
315 Normal TCP/IP networking is open to an attack known as "SYN
316 flooding". This denial-of-service attack prevents legitimate remote
317 users from being able to connect to your computer during an ongoing
318 attack and requires very little work from the attacker, who can
319 operate from anywhere on the Internet.
320
321 SYN cookies provide protection against this type of attack. If you
322 say Y here, the TCP/IP stack will use a cryptographic challenge
323 protocol known as "SYN cookies" to enable legitimate users to
324 continue to connect, even when your machine is under attack. There
325 is no need for the legitimate users to change their TCP/IP software;
326 SYN cookies work transparently to them. For technical information
327 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
328
329 If you are SYN flooded, the source address reported by the kernel is
330 likely to have been forged by the attacker; it is only reported as
331 an aid in tracing the packets to their actual source and should not
332 be taken as absolute truth.
333
334 SYN cookies may prevent correct error reporting on clients when the
335 server is really overloaded. If this happens frequently better turn
336 them off.
337
Florian Westphal57f15532010-06-03 00:42:30 +0000338 If you say Y here, you can disable SYN cookies at run time by
339 saying Y to "/proc file system support" and
Linus Torvalds1da177e2005-04-16 15:20:36 -0700340 "Sysctl support" below and executing the command
341
Florian Westphal57f15532010-06-03 00:42:30 +0000342 echo 0 > /proc/sys/net/ipv4/tcp_syncookies
Linus Torvalds1da177e2005-04-16 15:20:36 -0700343
Florian Westphal57f15532010-06-03 00:42:30 +0000344 after the /proc file system has been mounted.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345
346 If unsure, say N.
347
348config INET_AH
349 tristate "IP: AH transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700350 select XFRM
351 select CRYPTO
352 select CRYPTO_HMAC
353 select CRYPTO_MD5
354 select CRYPTO_SHA1
355 ---help---
356 Support for IPsec AH.
357
358 If unsure, say Y.
359
360config INET_ESP
361 tristate "IP: ESP transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700362 select XFRM
363 select CRYPTO
Herbert Xued58dd42008-03-04 14:29:21 -0800364 select CRYPTO_AUTHENC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700365 select CRYPTO_HMAC
366 select CRYPTO_MD5
Herbert Xu6b7326c2006-07-30 15:41:01 +1000367 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700368 select CRYPTO_SHA1
369 select CRYPTO_DES
370 ---help---
371 Support for IPsec ESP.
372
373 If unsure, say Y.
374
375config INET_IPCOMP
376 tristate "IP: IPComp transformation"
Herbert Xud2acc342006-03-28 01:12:13 -0800377 select INET_XFRM_TUNNEL
Herbert Xu6fccab62008-07-25 02:54:40 -0700378 select XFRM_IPCOMP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700379 ---help---
380 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
381 typically needed for IPsec.
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -0800382
Linus Torvalds1da177e2005-04-16 15:20:36 -0700383 If unsure, say Y.
384
Herbert Xud2acc342006-03-28 01:12:13 -0800385config INET_XFRM_TUNNEL
386 tristate
387 select INET_TUNNEL
388 default n
389
Linus Torvalds1da177e2005-04-16 15:20:36 -0700390config INET_TUNNEL
Herbert Xud2acc342006-03-28 01:12:13 -0800391 tristate
392 default n
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393
Herbert Xub59f45d2006-05-27 23:05:54 -0700394config INET_XFRM_MODE_TRANSPORT
395 tristate "IP: IPsec transport mode"
396 default y
397 select XFRM
398 ---help---
399 Support for IPsec transport mode.
400
401 If unsure, say Y.
402
403config INET_XFRM_MODE_TUNNEL
404 tristate "IP: IPsec tunnel mode"
405 default y
406 select XFRM
407 ---help---
408 Support for IPsec tunnel mode.
409
410 If unsure, say Y.
411
Diego Beltrami0a694522006-10-03 23:47:05 -0700412config INET_XFRM_MODE_BEET
413 tristate "IP: IPsec BEET mode"
414 default y
415 select XFRM
416 ---help---
417 Support for IPsec BEET mode.
418
419 If unsure, say Y.
420
Jan-Bernd Themann71c87e02007-08-08 22:38:05 -0700421config INET_LRO
Ben Hutchingsc5d35572010-10-03 15:37:42 +0000422 tristate "Large Receive Offload (ipv4/tcp)"
Frans Popbc8a5392009-05-18 21:48:38 -0700423 default y
Jan-Bernd Themann71c87e02007-08-08 22:38:05 -0700424 ---help---
425 Support for Large Receive Offload (ipv4/tcp).
426
427 If unsure, say Y.
428
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300429config INET_DIAG
430 tristate "INET: socket monitoring interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700431 default y
432 ---help---
Arnaldo Carvalho de Melo73c1f4a2005-08-12 12:51:49 -0300433 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
434 native Linux tools such as ss. ss is included in iproute2, currently
Michael Wittenc996d8b2010-11-15 19:55:34 +0000435 downloadable at:
436
437 http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -0800438
Linus Torvalds1da177e2005-04-16 15:20:36 -0700439 If unsure, say Y.
440
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300441config INET_TCP_DIAG
442 depends on INET_DIAG
443 def_tristate INET_DIAG
444
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700445menuconfig TCP_CONG_ADVANCED
David S. Millera6484042005-06-24 18:07:51 -0700446 bool "TCP: advanced congestion control"
David S. Millera6484042005-06-24 18:07:51 -0700447 ---help---
448 Support for selection of various TCP congestion control
449 modules.
450
451 Nearly all users can safely say no here, and a safe default
Stephen Hemminger597811e2006-09-24 20:13:03 -0700452 selection will be made (CUBIC with new Reno as a fallback).
David S. Millera6484042005-06-24 18:07:51 -0700453
454 If unsure, say N.
455
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700456if TCP_CONG_ADVANCED
Stephen Hemminger83803032005-06-23 12:23:25 -0700457
458config TCP_CONG_BIC
459 tristate "Binary Increase Congestion (BIC) control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700460 default m
Stephen Hemminger83803032005-06-23 12:23:25 -0700461 ---help---
462 BIC-TCP is a sender-side only change that ensures a linear RTT
463 fairness under large windows while offering both scalability and
464 bounded TCP-friendliness. The protocol combines two schemes
465 called additive increase and binary search increase. When the
466 congestion window is large, additive increase with a large
467 increment ensures linear RTT fairness as well as good
468 scalability. Under small congestion windows, binary search
469 increase provides TCP friendliness.
470 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
471
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800472config TCP_CONG_CUBIC
473 tristate "CUBIC TCP"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700474 default y
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800475 ---help---
476 This is version 2.0 of BIC-TCP which uses a cubic growth function
477 among other techniques.
478 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
479
Stephen Hemminger87270762005-06-23 12:24:09 -0700480config TCP_CONG_WESTWOOD
481 tristate "TCP Westwood+"
Stephen Hemminger87270762005-06-23 12:24:09 -0700482 default m
483 ---help---
484 TCP Westwood+ is a sender-side only modification of the TCP Reno
485 protocol stack that optimizes the performance of TCP congestion
486 control. It is based on end-to-end bandwidth estimation to set
487 congestion window and slow start threshold after a congestion
488 episode. Using this estimation, TCP Westwood+ adaptively sets a
489 slow start threshold and a congestion window which takes into
490 account the bandwidth used at the time congestion is experienced.
491 TCP Westwood+ significantly increases fairness wrt TCP Reno in
492 wired networks and throughput over wireless links.
493
Baruch Evena7868ea2005-06-23 12:28:11 -0700494config TCP_CONG_HTCP
495 tristate "H-TCP"
Baruch Evena7868ea2005-06-23 12:28:11 -0700496 default m
497 ---help---
498 H-TCP is a send-side only modifications of the TCP Reno
499 protocol stack that optimizes the performance of TCP
500 congestion control for high speed network links. It uses a
501 modeswitch to change the alpha and beta parameters of TCP Reno
502 based on network conditions and in a way so as to be fair with
503 other Reno and H-TCP flows.
504
John Heffnera628d292005-06-23 12:24:58 -0700505config TCP_CONG_HSTCP
506 tristate "High Speed TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700507 depends on EXPERIMENTAL
John Heffnera628d292005-06-23 12:24:58 -0700508 default n
509 ---help---
510 Sally Floyd's High Speed TCP (RFC 3649) congestion control.
511 A modification to TCP's congestion control mechanism for use
512 with large congestion windows. A table indicates how much to
513 increase the congestion window by when an ACK is received.
514 For more detail see http://www.icir.org/floyd/hstcp.html
515
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700516config TCP_CONG_HYBLA
517 tristate "TCP-Hybla congestion control algorithm"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700518 depends on EXPERIMENTAL
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700519 default n
520 ---help---
521 TCP-Hybla is a sender-side only change that eliminates penalization of
522 long-RTT, large-bandwidth connections, like when satellite legs are
Matt LaPlante44c09202006-10-03 22:34:14 +0200523 involved, especially when sharing a common bottleneck with normal
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700524 terrestrial connections.
525
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700526config TCP_CONG_VEGAS
527 tristate "TCP Vegas"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700528 depends on EXPERIMENTAL
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700529 default n
530 ---help---
531 TCP Vegas is a sender-side only change to TCP that anticipates
532 the onset of congestion by estimating the bandwidth. TCP Vegas
533 adjusts the sending rate by modifying the congestion
534 window. TCP Vegas should provide less packet loss, but it is
535 not as aggressive as TCP Reno.
536
John Heffner0e579762005-06-23 12:29:07 -0700537config TCP_CONG_SCALABLE
538 tristate "Scalable TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700539 depends on EXPERIMENTAL
John Heffner0e579762005-06-23 12:29:07 -0700540 default n
541 ---help---
542 Scalable TCP is a sender-side only change to TCP which uses a
543 MIMD congestion control algorithm which has some nice scaling
544 properties, though is known to have fairness issues.
Baruch Evenf4b94792007-02-21 19:32:37 -0800545 See http://www.deneholme.net/tom/scalable/
Baruch Evena7868ea2005-06-23 12:28:11 -0700546
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700547config TCP_CONG_LP
548 tristate "TCP Low Priority"
549 depends on EXPERIMENTAL
550 default n
551 ---help---
552 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
Matt LaPlantecab00892006-10-03 22:36:44 +0200553 to utilize only the excess network bandwidth as compared to the
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700554 ``fair share`` of bandwidth as targeted by TCP.
555 See http://www-ece.rice.edu/networks/TCP-LP/
556
Bin Zhou76f10172006-06-05 17:28:30 -0700557config TCP_CONG_VENO
558 tristate "TCP Veno"
559 depends on EXPERIMENTAL
560 default n
561 ---help---
562 TCP Veno is a sender-side only enhancement of TCP to obtain better
563 throughput over wireless networks. TCP Veno makes use of state
564 distinguishing to circumvent the difficult judgment of the packet loss
565 type. TCP Veno cuts down less congestion window in response to random
566 loss packets.
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200567 See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
Bin Zhou76f10172006-06-05 17:28:30 -0700568
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800569config TCP_CONG_YEAH
570 tristate "YeAH TCP"
571 depends on EXPERIMENTAL
David S. Miller2ff011e2007-05-17 00:07:47 -0700572 select TCP_CONG_VEGAS
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800573 default n
574 ---help---
575 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
576 algorithm, which uses a mixed loss/delay approach to compute the
577 congestion window. It's design goals target high efficiency,
578 internal, RTT and Reno fairness, resilience to link loss while
579 keeping network elements load as low as possible.
580
581 For further details look here:
582 http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
583
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700584config TCP_CONG_ILLINOIS
585 tristate "TCP Illinois"
586 depends on EXPERIMENTAL
587 default n
588 ---help---
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200589 TCP-Illinois is a sender-side modification of TCP Reno for
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700590 high speed long delay links. It uses round-trip-time to
591 adjust the alpha and beta parameters to achieve a higher average
592 throughput and maintain fairness.
593
594 For further details see:
595 http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
596
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700597choice
598 prompt "Default TCP congestion control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700599 default DEFAULT_CUBIC
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700600 help
601 Select the TCP congestion control that will be used by default
602 for all connections.
603
604 config DEFAULT_BIC
605 bool "Bic" if TCP_CONG_BIC=y
606
607 config DEFAULT_CUBIC
608 bool "Cubic" if TCP_CONG_CUBIC=y
609
610 config DEFAULT_HTCP
611 bool "Htcp" if TCP_CONG_HTCP=y
612
Jan Engelhardtdd2acaa2010-03-11 09:57:27 +0000613 config DEFAULT_HYBLA
614 bool "Hybla" if TCP_CONG_HYBLA=y
615
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700616 config DEFAULT_VEGAS
617 bool "Vegas" if TCP_CONG_VEGAS=y
618
Jan Engelhardt6ce1a6d2010-03-11 09:57:28 +0000619 config DEFAULT_VENO
620 bool "Veno" if TCP_CONG_VENO=y
621
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700622 config DEFAULT_WESTWOOD
623 bool "Westwood" if TCP_CONG_WESTWOOD=y
624
625 config DEFAULT_RENO
626 bool "Reno"
627
628endchoice
629
630endif
Stephen Hemminger83803032005-06-23 12:23:25 -0700631
Stephen Hemminger597811e2006-09-24 20:13:03 -0700632config TCP_CONG_CUBIC
David S. Miller6c360762005-06-26 15:20:20 -0700633 tristate
David S. Millera6484042005-06-24 18:07:51 -0700634 depends on !TCP_CONG_ADVANCED
635 default y
636
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700637config DEFAULT_TCP_CONG
638 string
639 default "bic" if DEFAULT_BIC
640 default "cubic" if DEFAULT_CUBIC
641 default "htcp" if DEFAULT_HTCP
Jan Engelhardtdd2acaa2010-03-11 09:57:27 +0000642 default "hybla" if DEFAULT_HYBLA
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700643 default "vegas" if DEFAULT_VEGAS
644 default "westwood" if DEFAULT_WESTWOOD
Jan Engelhardt6ce1a6d2010-03-11 09:57:28 +0000645 default "veno" if DEFAULT_VENO
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700646 default "reno" if DEFAULT_RENO
Stephen Hemminger597811e2006-09-24 20:13:03 -0700647 default "cubic"
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700648
YOSHIFUJI Hideakicfb6eeb2006-11-14 19:07:45 -0800649config TCP_MD5SIG
650 bool "TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL)"
651 depends on EXPERIMENTAL
652 select CRYPTO
653 select CRYPTO_MD5
654 ---help---
David Sterba3dde6ad2007-05-09 07:12:20 +0200655 RFC2385 specifies a method of giving MD5 protection to TCP sessions.
YOSHIFUJI Hideakicfb6eeb2006-11-14 19:07:45 -0800656 Its main (only?) use is to protect BGP sessions between core routers
657 on the Internet.
658
659 If unsure, say N.
660