blob: aa2a2c79776f897e31456c27acd81896c7607ced [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
Stephen Hemminger66a2f7f2008-01-12 21:23:17 -080058config IP_FIB_TRIE_STATS
59 bool "FIB TRIE statistics"
David S. Miller3630b7c2011-02-01 15:15:39 -080060 depends on IP_ADVANCED_ROUTER
Stephen Hemminger66a2f7f2008-01-12 21:23:17 -080061 ---help---
62 Keep track of statistics on structure of FIB TRIE table.
63 Useful for testing and measuring TRIE performance.
64
Linus Torvalds1da177e2005-04-16 15:20:36 -070065config IP_MULTIPLE_TABLES
66 bool "IP: policy routing"
67 depends on IP_ADVANCED_ROUTER
Thomas Grafe1ef4bf2006-08-04 03:39:22 -070068 select FIB_RULES
Linus Torvalds1da177e2005-04-16 15:20:36 -070069 ---help---
70 Normally, a router decides what to do with a received packet based
71 solely on the packet's final destination address. If you say Y here,
72 the Linux router will also be able to take the packet's source
73 address into account. Furthermore, the TOS (Type-Of-Service) field
74 of the packet can be used for routing decisions as well.
75
76 If you are interested in this, please see the preliminary
77 documentation at <http://www.compendium.com.ar/policy-routing.txt>
78 and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
79 You will need supporting software from
80 <ftp://ftp.tux.org/pub/net/ip-routing/>.
81
82 If unsure, say N.
83
Linus Torvalds1da177e2005-04-16 15:20:36 -070084config IP_ROUTE_MULTIPATH
85 bool "IP: equal cost multipath"
86 depends on IP_ADVANCED_ROUTER
87 help
88 Normally, the routing tables specify a single action to be taken in
89 a deterministic manner for a given packet. If you say Y here
90 however, it becomes possible to attach several actions to a packet
91 pattern, in effect specifying several alternative paths to travel
92 for those packets. The router considers all these paths to be of
93 equal "cost" and chooses one of them in a non-deterministic fashion
94 if a matching packet arrives.
95
Linus Torvalds1da177e2005-04-16 15:20:36 -070096config IP_ROUTE_VERBOSE
97 bool "IP: verbose route monitoring"
98 depends on IP_ADVANCED_ROUTER
99 help
100 If you say Y here, which is recommended, then the kernel will print
101 verbose messages regarding the routing, for example warnings about
102 received packets which look strange and could be evidence of an
103 attack or a misconfigured system somewhere. The information is
104 handled by the klogd daemon which is responsible for kernel messages
105 ("man klogd").
106
Patrick McHardyc7066f72011-01-14 13:36:42 +0100107config IP_ROUTE_CLASSID
108 bool
109
Linus Torvalds1da177e2005-04-16 15:20:36 -0700110config IP_PNP
111 bool "IP: kernel level autoconfiguration"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700112 help
113 This enables automatic configuration of IP addresses of devices and
114 of the routing table during kernel boot, based on either information
115 supplied on the kernel command line or by BOOTP or RARP protocols.
116 You need to say Y only for diskless machines requiring network
117 access to boot (in which case you want to say Y to "Root file system
118 on NFS" as well), because all other machines configure the network
119 in their startup scripts.
120
121config IP_PNP_DHCP
122 bool "IP: DHCP support"
123 depends on IP_PNP
124 ---help---
125 If you want your Linux box to mount its whole root file system (the
126 one containing the directory /) from some other computer over the
127 net via NFS and you want the IP address of your computer to be
128 discovered automatically at boot time using the DHCP protocol (a
129 special protocol designed for doing this job), say Y here. In case
130 the boot ROM of your network card was designed for booting Linux and
131 does DHCP itself, providing all necessary information on the kernel
132 command line, you can say N here.
133
134 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
135 must be operating on your network. Read
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400136 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700137
138config IP_PNP_BOOTP
139 bool "IP: BOOTP support"
140 depends on IP_PNP
141 ---help---
142 If you want your Linux box to mount its whole root file system (the
143 one containing the directory /) from some other computer over the
144 net via NFS and you want the IP address of your computer to be
145 discovered automatically at boot time using the BOOTP protocol (a
146 special protocol designed for doing this job), say Y here. In case
147 the boot ROM of your network card was designed for booting Linux and
148 does BOOTP itself, providing all necessary information on the kernel
149 command line, you can say N here. If unsure, say Y. Note that if you
150 want to use BOOTP, a BOOTP server must be operating on your network.
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400151 Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152
153config IP_PNP_RARP
154 bool "IP: RARP support"
155 depends on IP_PNP
156 help
157 If you want your Linux box to mount its whole root file system (the
158 one containing the directory /) from some other computer over the
159 net via NFS and you want the IP address of your computer to be
160 discovered automatically at boot time using the RARP protocol (an
161 older protocol which is being obsoleted by BOOTP and DHCP), say Y
162 here. Note that if you want to use RARP, a RARP server must be
J. Bruce Fields6ded55d2008-04-07 15:59:03 -0400163 operating on your network. Read
J. Bruce Fieldsdc7a0812009-10-27 14:41:35 -0400164 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165
Linus Torvalds1da177e2005-04-16 15:20:36 -0700166config NET_IPIP
167 tristate "IP: tunneling"
Herbert Xud2acc342006-03-28 01:12:13 -0800168 select INET_TUNNEL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700169 ---help---
170 Tunneling means encapsulating data of one protocol type within
171 another protocol and sending it over a channel that understands the
172 encapsulating protocol. This particular tunneling driver implements
173 encapsulation of IP within IP, which sounds kind of pointless, but
174 can be useful if you want to make your (or some other) machine
175 appear on a different network than it physically is, or to use
176 mobile-IP facilities (allowing laptops to seamlessly move between
177 networks without changing their IP addresses).
178
179 Saying Y to this option will produce two modules ( = code which can
180 be inserted in and removed from the running kernel whenever you
181 want). Most people won't need this and can say N.
182
Dmitry Kozlov00959ad2010-08-21 23:05:39 -0700183config NET_IPGRE_DEMUX
184 tristate "IP: GRE demultiplexer"
185 help
186 This is helper module to demultiplex GRE packets on GRE version field criteria.
187 Required by ip_gre and pptp modules.
188
Linus Torvalds1da177e2005-04-16 15:20:36 -0700189config NET_IPGRE
190 tristate "IP: GRE tunnels over IP"
David S. Miller21a180c2010-10-04 11:56:38 -0700191 depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700192 help
193 Tunneling means encapsulating data of one protocol type within
194 another protocol and sending it over a channel that understands the
195 encapsulating protocol. This particular tunneling driver implements
196 GRE (Generic Routing Encapsulation) and at this time allows
197 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
198 This driver is useful if the other endpoint is a Cisco router: Cisco
199 likes GRE much better than the other Linux tunneling driver ("IP
200 tunneling" above). In addition, GRE allows multicast redistribution
201 through the tunnel.
202
203config NET_IPGRE_BROADCAST
204 bool "IP: broadcast GRE over IP"
205 depends on IP_MULTICAST && NET_IPGRE
206 help
207 One application of GRE/IP is to construct a broadcast WAN (Wide Area
208 Network), which looks like a normal Ethernet LAN (Local Area
209 Network), but can be distributed all over the Internet. If you want
210 to do that, say Y here and to "IP multicast routing" below.
211
212config IP_MROUTE
213 bool "IP: multicast routing"
214 depends on IP_MULTICAST
215 help
216 This is used if you want your machine to act as a router for IP
217 packets that have several destination addresses. It is needed on the
218 MBONE, a high bandwidth network on top of the Internet which carries
219 audio and video broadcasts. In order to do that, you would most
220 likely run the program mrouted. Information about the multicast
221 capabilities of the various network cards is contained in
222 <file:Documentation/networking/multicast.txt>. If you haven't heard
223 about it, you don't need it.
224
Patrick McHardyf0ad0862010-04-13 05:03:23 +0000225config IP_MROUTE_MULTIPLE_TABLES
226 bool "IP: multicast policy routing"
Patrick McHardy66496d42010-04-15 13:29:27 +0200227 depends on IP_MROUTE && IP_ADVANCED_ROUTER
Patrick McHardyf0ad0862010-04-13 05:03:23 +0000228 select FIB_RULES
229 help
230 Normally, a multicast router runs a userspace daemon and decides
231 what to do with a multicast packet based on the source and
232 destination addresses. If you say Y here, the multicast router
233 will also be able to take interfaces and packet marks into
234 account and run multiple instances of userspace daemons
235 simultaneously, each one handling a single table.
236
237 If unsure, say N.
238
Linus Torvalds1da177e2005-04-16 15:20:36 -0700239config IP_PIMSM_V1
240 bool "IP: PIM-SM version 1 support"
241 depends on IP_MROUTE
242 help
243 Kernel side support for Sparse Mode PIM (Protocol Independent
244 Multicast) version 1. This multicast routing protocol is used widely
245 because Cisco supports it. You need special software to use it
246 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
247 information about PIM.
248
249 Say Y if you want to use PIM-SM v1. Note that you can say N here if
250 you just want to use Dense Mode PIM.
251
252config IP_PIMSM_V2
253 bool "IP: PIM-SM version 2 support"
254 depends on IP_MROUTE
255 help
256 Kernel side support for Sparse Mode PIM version 2. In order to use
257 this, you need an experimental routing daemon supporting it (pimd or
258 gated-5). This routing protocol is not used widely, so say N unless
259 you want to play with it.
260
261config ARPD
Timo Teräse61a4b62009-06-11 19:38:02 +0000262 bool "IP: ARP daemon support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700263 ---help---
Timo Teräse61a4b62009-06-11 19:38:02 +0000264 The kernel maintains an internal cache which maps IP addresses to
265 hardware addresses on the local network, so that Ethernet/Token Ring/
266 etc. frames are sent to the proper address on the physical networking
267 layer. Normally, kernel uses the ARP protocol to resolve these
268 mappings.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700269
Timo Teräse61a4b62009-06-11 19:38:02 +0000270 Saying Y here adds support to have an user space daemon to do this
271 resolution instead. This is useful for implementing an alternate
272 address resolution protocol (e.g. NHRP on mGRE tunnels) and also for
273 testing purposes.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700274
Timo Teräse61a4b62009-06-11 19:38:02 +0000275 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276
277config SYN_COOKIES
Florian Westphal57f15532010-06-03 00:42:30 +0000278 bool "IP: TCP syncookie support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700279 ---help---
280 Normal TCP/IP networking is open to an attack known as "SYN
281 flooding". This denial-of-service attack prevents legitimate remote
282 users from being able to connect to your computer during an ongoing
283 attack and requires very little work from the attacker, who can
284 operate from anywhere on the Internet.
285
286 SYN cookies provide protection against this type of attack. If you
287 say Y here, the TCP/IP stack will use a cryptographic challenge
288 protocol known as "SYN cookies" to enable legitimate users to
289 continue to connect, even when your machine is under attack. There
290 is no need for the legitimate users to change their TCP/IP software;
291 SYN cookies work transparently to them. For technical information
292 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
293
294 If you are SYN flooded, the source address reported by the kernel is
295 likely to have been forged by the attacker; it is only reported as
296 an aid in tracing the packets to their actual source and should not
297 be taken as absolute truth.
298
299 SYN cookies may prevent correct error reporting on clients when the
300 server is really overloaded. If this happens frequently better turn
301 them off.
302
Florian Westphal57f15532010-06-03 00:42:30 +0000303 If you say Y here, you can disable SYN cookies at run time by
304 saying Y to "/proc file system support" and
Linus Torvalds1da177e2005-04-16 15:20:36 -0700305 "Sysctl support" below and executing the command
306
Florian Westphal57f15532010-06-03 00:42:30 +0000307 echo 0 > /proc/sys/net/ipv4/tcp_syncookies
Linus Torvalds1da177e2005-04-16 15:20:36 -0700308
Florian Westphal57f15532010-06-03 00:42:30 +0000309 after the /proc file system has been mounted.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700310
311 If unsure, say N.
312
313config INET_AH
314 tristate "IP: AH transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700315 select XFRM
316 select CRYPTO
317 select CRYPTO_HMAC
318 select CRYPTO_MD5
319 select CRYPTO_SHA1
320 ---help---
321 Support for IPsec AH.
322
323 If unsure, say Y.
324
325config INET_ESP
326 tristate "IP: ESP transformation"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700327 select XFRM
328 select CRYPTO
Herbert Xued58dd42008-03-04 14:29:21 -0800329 select CRYPTO_AUTHENC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700330 select CRYPTO_HMAC
331 select CRYPTO_MD5
Herbert Xu6b7326c2006-07-30 15:41:01 +1000332 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700333 select CRYPTO_SHA1
334 select CRYPTO_DES
335 ---help---
336 Support for IPsec ESP.
337
338 If unsure, say Y.
339
340config INET_IPCOMP
341 tristate "IP: IPComp transformation"
Herbert Xud2acc342006-03-28 01:12:13 -0800342 select INET_XFRM_TUNNEL
Herbert Xu6fccab62008-07-25 02:54:40 -0700343 select XFRM_IPCOMP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700344 ---help---
345 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
346 typically needed for IPsec.
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -0800347
Linus Torvalds1da177e2005-04-16 15:20:36 -0700348 If unsure, say Y.
349
Herbert Xud2acc342006-03-28 01:12:13 -0800350config INET_XFRM_TUNNEL
351 tristate
352 select INET_TUNNEL
353 default n
354
Linus Torvalds1da177e2005-04-16 15:20:36 -0700355config INET_TUNNEL
Herbert Xud2acc342006-03-28 01:12:13 -0800356 tristate
357 default n
Linus Torvalds1da177e2005-04-16 15:20:36 -0700358
Herbert Xub59f45d2006-05-27 23:05:54 -0700359config INET_XFRM_MODE_TRANSPORT
360 tristate "IP: IPsec transport mode"
361 default y
362 select XFRM
363 ---help---
364 Support for IPsec transport mode.
365
366 If unsure, say Y.
367
368config INET_XFRM_MODE_TUNNEL
369 tristate "IP: IPsec tunnel mode"
370 default y
371 select XFRM
372 ---help---
373 Support for IPsec tunnel mode.
374
375 If unsure, say Y.
376
Diego Beltrami0a694522006-10-03 23:47:05 -0700377config INET_XFRM_MODE_BEET
378 tristate "IP: IPsec BEET mode"
379 default y
380 select XFRM
381 ---help---
382 Support for IPsec BEET mode.
383
384 If unsure, say Y.
385
Jan-Bernd Themann71c87e02007-08-08 22:38:05 -0700386config INET_LRO
Ben Hutchingsc5d35572010-10-03 15:37:42 +0000387 tristate "Large Receive Offload (ipv4/tcp)"
Frans Popbc8a5392009-05-18 21:48:38 -0700388 default y
Jan-Bernd Themann71c87e02007-08-08 22:38:05 -0700389 ---help---
390 Support for Large Receive Offload (ipv4/tcp).
391
392 If unsure, say Y.
393
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300394config INET_DIAG
395 tristate "INET: socket monitoring interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700396 default y
397 ---help---
Arnaldo Carvalho de Melo73c1f4a2005-08-12 12:51:49 -0300398 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
399 native Linux tools such as ss. ss is included in iproute2, currently
Michael Wittenc996d8b2010-11-15 19:55:34 +0000400 downloadable at:
401
402 http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
Jesper Dangaard Brouera6e8f272009-02-22 00:07:13 -0800403
Linus Torvalds1da177e2005-04-16 15:20:36 -0700404 If unsure, say Y.
405
Arnaldo Carvalho de Melo17b085e2005-08-12 12:59:17 -0300406config INET_TCP_DIAG
407 depends on INET_DIAG
408 def_tristate INET_DIAG
409
Pavel Emelyanov507dd792011-12-09 06:24:36 +0000410config INET_UDP_DIAG
David S. Miller6d62a662012-01-07 12:13:06 -0800411 tristate "UDP: socket monitoring interface"
Pavel Emelyanov507dd792011-12-09 06:24:36 +0000412 depends on INET_DIAG
David S. Miller6d62a662012-01-07 12:13:06 -0800413 default n
414 ---help---
415 Support for UDP socket monitoring interface used by the ss tool.
416 If unsure, say Y.
Pavel Emelyanov507dd792011-12-09 06:24:36 +0000417
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700418menuconfig TCP_CONG_ADVANCED
David S. Millera6484042005-06-24 18:07:51 -0700419 bool "TCP: advanced congestion control"
David S. Millera6484042005-06-24 18:07:51 -0700420 ---help---
421 Support for selection of various TCP congestion control
422 modules.
423
424 Nearly all users can safely say no here, and a safe default
Stephen Hemminger597811e2006-09-24 20:13:03 -0700425 selection will be made (CUBIC with new Reno as a fallback).
David S. Millera6484042005-06-24 18:07:51 -0700426
427 If unsure, say N.
428
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700429if TCP_CONG_ADVANCED
Stephen Hemminger83803032005-06-23 12:23:25 -0700430
431config TCP_CONG_BIC
432 tristate "Binary Increase Congestion (BIC) control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700433 default m
Stephen Hemminger83803032005-06-23 12:23:25 -0700434 ---help---
435 BIC-TCP is a sender-side only change that ensures a linear RTT
436 fairness under large windows while offering both scalability and
437 bounded TCP-friendliness. The protocol combines two schemes
438 called additive increase and binary search increase. When the
439 congestion window is large, additive increase with a large
440 increment ensures linear RTT fairness as well as good
441 scalability. Under small congestion windows, binary search
442 increase provides TCP friendliness.
443 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
444
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800445config TCP_CONG_CUBIC
446 tristate "CUBIC TCP"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700447 default y
Stephen Hemmingerdf3271f2005-12-13 23:13:28 -0800448 ---help---
449 This is version 2.0 of BIC-TCP which uses a cubic growth function
450 among other techniques.
451 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
452
Stephen Hemminger87270762005-06-23 12:24:09 -0700453config TCP_CONG_WESTWOOD
454 tristate "TCP Westwood+"
Stephen Hemminger87270762005-06-23 12:24:09 -0700455 default m
456 ---help---
457 TCP Westwood+ is a sender-side only modification of the TCP Reno
458 protocol stack that optimizes the performance of TCP congestion
459 control. It is based on end-to-end bandwidth estimation to set
460 congestion window and slow start threshold after a congestion
461 episode. Using this estimation, TCP Westwood+ adaptively sets a
462 slow start threshold and a congestion window which takes into
463 account the bandwidth used at the time congestion is experienced.
464 TCP Westwood+ significantly increases fairness wrt TCP Reno in
465 wired networks and throughput over wireless links.
466
Baruch Evena7868ea2005-06-23 12:28:11 -0700467config TCP_CONG_HTCP
468 tristate "H-TCP"
Baruch Evena7868ea2005-06-23 12:28:11 -0700469 default m
470 ---help---
471 H-TCP is a send-side only modifications of the TCP Reno
472 protocol stack that optimizes the performance of TCP
473 congestion control for high speed network links. It uses a
474 modeswitch to change the alpha and beta parameters of TCP Reno
475 based on network conditions and in a way so as to be fair with
476 other Reno and H-TCP flows.
477
John Heffnera628d292005-06-23 12:24:58 -0700478config TCP_CONG_HSTCP
479 tristate "High Speed TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700480 depends on EXPERIMENTAL
John Heffnera628d292005-06-23 12:24:58 -0700481 default n
482 ---help---
483 Sally Floyd's High Speed TCP (RFC 3649) congestion control.
484 A modification to TCP's congestion control mechanism for use
485 with large congestion windows. A table indicates how much to
486 increase the congestion window by when an ACK is received.
487 For more detail see http://www.icir.org/floyd/hstcp.html
488
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700489config TCP_CONG_HYBLA
490 tristate "TCP-Hybla congestion control algorithm"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700491 depends on EXPERIMENTAL
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700492 default n
493 ---help---
494 TCP-Hybla is a sender-side only change that eliminates penalization of
495 long-RTT, large-bandwidth connections, like when satellite legs are
Matt LaPlante44c09202006-10-03 22:34:14 +0200496 involved, especially when sharing a common bottleneck with normal
Daniele Lacamera835b3f02005-06-23 12:26:34 -0700497 terrestrial connections.
498
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700499config TCP_CONG_VEGAS
500 tristate "TCP Vegas"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700501 depends on EXPERIMENTAL
Stephen Hemmingerb87d8562005-06-23 12:27:19 -0700502 default n
503 ---help---
504 TCP Vegas is a sender-side only change to TCP that anticipates
505 the onset of congestion by estimating the bandwidth. TCP Vegas
506 adjusts the sending rate by modifying the congestion
507 window. TCP Vegas should provide less packet loss, but it is
508 not as aggressive as TCP Reno.
509
John Heffner0e579762005-06-23 12:29:07 -0700510config TCP_CONG_SCALABLE
511 tristate "Scalable TCP"
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -0700512 depends on EXPERIMENTAL
John Heffner0e579762005-06-23 12:29:07 -0700513 default n
514 ---help---
515 Scalable TCP is a sender-side only change to TCP which uses a
516 MIMD congestion control algorithm which has some nice scaling
517 properties, though is known to have fairness issues.
Baruch Evenf4b94792007-02-21 19:32:37 -0800518 See http://www.deneholme.net/tom/scalable/
Baruch Evena7868ea2005-06-23 12:28:11 -0700519
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700520config TCP_CONG_LP
521 tristate "TCP Low Priority"
522 depends on EXPERIMENTAL
523 default n
524 ---help---
525 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
Matt LaPlantecab00892006-10-03 22:36:44 +0200526 to utilize only the excess network bandwidth as compared to the
Wong Hoi Sing Edison7c106d72006-06-05 17:27:58 -0700527 ``fair share`` of bandwidth as targeted by TCP.
528 See http://www-ece.rice.edu/networks/TCP-LP/
529
Bin Zhou76f10172006-06-05 17:28:30 -0700530config TCP_CONG_VENO
531 tristate "TCP Veno"
532 depends on EXPERIMENTAL
533 default n
534 ---help---
535 TCP Veno is a sender-side only enhancement of TCP to obtain better
536 throughput over wireless networks. TCP Veno makes use of state
537 distinguishing to circumvent the difficult judgment of the packet loss
538 type. TCP Veno cuts down less congestion window in response to random
539 loss packets.
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200540 See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
Bin Zhou76f10172006-06-05 17:28:30 -0700541
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800542config TCP_CONG_YEAH
543 tristate "YeAH TCP"
544 depends on EXPERIMENTAL
David S. Miller2ff011e2007-05-17 00:07:47 -0700545 select TCP_CONG_VEGAS
Angelo P. Castellani5ef81472007-02-22 00:23:05 -0800546 default n
547 ---help---
548 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
549 algorithm, which uses a mixed loss/delay approach to compute the
550 congestion window. It's design goals target high efficiency,
551 internal, RTT and Reno fairness, resilience to link loss while
552 keeping network elements load as low as possible.
553
554 For further details look here:
555 http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
556
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700557config TCP_CONG_ILLINOIS
558 tristate "TCP Illinois"
559 depends on EXPERIMENTAL
560 default n
561 ---help---
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200562 TCP-Illinois is a sender-side modification of TCP Reno for
Stephen Hemmingerc4622382007-04-20 17:07:51 -0700563 high speed long delay links. It uses round-trip-time to
564 adjust the alpha and beta parameters to achieve a higher average
565 throughput and maintain fairness.
566
567 For further details see:
568 http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
569
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700570choice
571 prompt "Default TCP congestion control"
Stephen Hemminger597811e2006-09-24 20:13:03 -0700572 default DEFAULT_CUBIC
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700573 help
574 Select the TCP congestion control that will be used by default
575 for all connections.
576
577 config DEFAULT_BIC
578 bool "Bic" if TCP_CONG_BIC=y
579
580 config DEFAULT_CUBIC
581 bool "Cubic" if TCP_CONG_CUBIC=y
582
583 config DEFAULT_HTCP
584 bool "Htcp" if TCP_CONG_HTCP=y
585
Jan Engelhardtdd2acaa2010-03-11 09:57:27 +0000586 config DEFAULT_HYBLA
587 bool "Hybla" if TCP_CONG_HYBLA=y
588
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700589 config DEFAULT_VEGAS
590 bool "Vegas" if TCP_CONG_VEGAS=y
591
Jan Engelhardt6ce1a6d2010-03-11 09:57:28 +0000592 config DEFAULT_VENO
593 bool "Veno" if TCP_CONG_VENO=y
594
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700595 config DEFAULT_WESTWOOD
596 bool "Westwood" if TCP_CONG_WESTWOOD=y
597
598 config DEFAULT_RENO
599 bool "Reno"
600
601endchoice
602
603endif
Stephen Hemminger83803032005-06-23 12:23:25 -0700604
Stephen Hemminger597811e2006-09-24 20:13:03 -0700605config TCP_CONG_CUBIC
David S. Miller6c360762005-06-26 15:20:20 -0700606 tristate
David S. Millera6484042005-06-24 18:07:51 -0700607 depends on !TCP_CONG_ADVANCED
608 default y
609
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700610config DEFAULT_TCP_CONG
611 string
612 default "bic" if DEFAULT_BIC
613 default "cubic" if DEFAULT_CUBIC
614 default "htcp" if DEFAULT_HTCP
Jan Engelhardtdd2acaa2010-03-11 09:57:27 +0000615 default "hybla" if DEFAULT_HYBLA
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700616 default "vegas" if DEFAULT_VEGAS
617 default "westwood" if DEFAULT_WESTWOOD
Jan Engelhardt6ce1a6d2010-03-11 09:57:28 +0000618 default "veno" if DEFAULT_VENO
Stephen Hemminger3d2573f2006-09-24 20:11:58 -0700619 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.