Kconfig 25.6 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7 8 9 10 11
#
# IP configuration
#
config IP_MULTICAST
	bool "IP: multicasting"
	help
	  This is code for addressing several networked computers at once,
	  enlarging your kernel by about 2 KB. You need multicasting if you
	  intend to participate in the MBONE, a high bandwidth network on top
	  of the Internet which carries audio and video broadcasts. More
	  information about the MBONE is on the WWW at
12
	  <http://www.savetz.com/mbone/>. For most people, it's safe to say N.
L
Linus Torvalds 已提交
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

config IP_ADVANCED_ROUTER
	bool "IP: advanced router"
	---help---
	  If you intend to run your Linux box mostly as a router, i.e. as a
	  computer that forwards and redistributes network packets, say Y; you
	  will then be presented with several options that allow more precise
	  control about the routing process.

	  The answer to this question won't directly affect the kernel:
	  answering N will just cause the configurator to skip all the
	  questions about advanced routing.

	  Note that your box can only act as a router if you enable IP
	  forwarding in your kernel; you can do that by saying Y to "/proc
	  file system support" and "Sysctl support" below and executing the
	  line

	  echo "1" > /proc/sys/net/ipv4/ip_forward

	  at boot time after the /proc file system has been mounted.

35
	  If you turn on IP forwarding, you should consider the rp_filter, which
L
Linus Torvalds 已提交
36 37 38 39 40 41 42
	  automatically rejects incoming packets if the routing table entry
	  for their source address doesn't match the network interface they're
	  arriving on. This has security advantages because it prevents the
	  so-called IP spoofing, however it can pose problems if you use
	  asymmetric routing (packets from you to a host take a different path
	  than packets from that host to you) or if you operate a non-routing
	  host which has several IP addresses on different interfaces. To turn
43
	  rp_filter on use:
L
Linus Torvalds 已提交
44

45
	  echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
46
	   or
47
	  echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
L
Linus Torvalds 已提交
48

49
	  Note that some distributions enable it in startup scripts.
50 51
	  For details about rp_filter strict and loose mode read
	  <file:Documentation/networking/ip-sysctl.txt>.
52

L
Linus Torvalds 已提交
53 54
	  If unsure, say N here.

55 56
config IP_FIB_TRIE_STATS
	bool "FIB TRIE statistics"
D
David S. Miller 已提交
57
	depends on IP_ADVANCED_ROUTER
58 59 60 61
	---help---
	  Keep track of statistics on structure of FIB TRIE table.
	  Useful for testing and measuring TRIE performance.

L
Linus Torvalds 已提交
62 63 64
config IP_MULTIPLE_TABLES
	bool "IP: policy routing"
	depends on IP_ADVANCED_ROUTER
65
	select FIB_RULES
L
Linus Torvalds 已提交
66 67 68 69 70 71 72
	---help---
	  Normally, a router decides what to do with a received packet based
	  solely on the packet's final destination address. If you say Y here,
	  the Linux router will also be able to take the packet's source
	  address into account. Furthermore, the TOS (Type-Of-Service) field
	  of the packet can be used for routing decisions as well.

73 74 75
	  If you need more information, see the Linux Advanced
	  Routing and Traffic Control documentation at
	  <http://lartc.org/howto/lartc.rpdb.html>
L
Linus Torvalds 已提交
76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101

	  If unsure, say N.

config IP_ROUTE_MULTIPATH
	bool "IP: equal cost multipath"
	depends on IP_ADVANCED_ROUTER
	help
	  Normally, the routing tables specify a single action to be taken in
	  a deterministic manner for a given packet. If you say Y here
	  however, it becomes possible to attach several actions to a packet
	  pattern, in effect specifying several alternative paths to travel
	  for those packets. The router considers all these paths to be of
	  equal "cost" and chooses one of them in a non-deterministic fashion
	  if a matching packet arrives.

config IP_ROUTE_VERBOSE
	bool "IP: verbose route monitoring"
	depends on IP_ADVANCED_ROUTER
	help
	  If you say Y here, which is recommended, then the kernel will print
	  verbose messages regarding the routing, for example warnings about
	  received packets which look strange and could be evidence of an
	  attack or a misconfigured system somewhere. The information is
	  handled by the klogd daemon which is responsible for kernel messages
	  ("man klogd").

102 103 104
config IP_ROUTE_CLASSID
	bool

L
Linus Torvalds 已提交
105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130
config IP_PNP
	bool "IP: kernel level autoconfiguration"
	help
	  This enables automatic configuration of IP addresses of devices and
	  of the routing table during kernel boot, based on either information
	  supplied on the kernel command line or by BOOTP or RARP protocols.
	  You need to say Y only for diskless machines requiring network
	  access to boot (in which case you want to say Y to "Root file system
	  on NFS" as well), because all other machines configure the network
	  in their startup scripts.

config IP_PNP_DHCP
	bool "IP: DHCP support"
	depends on IP_PNP
	---help---
	  If you want your Linux box to mount its whole root file system (the
	  one containing the directory /) from some other computer over the
	  net via NFS and you want the IP address of your computer to be
	  discovered automatically at boot time using the DHCP protocol (a
	  special protocol designed for doing this job), say Y here. In case
	  the boot ROM of your network card was designed for booting Linux and
	  does DHCP itself, providing all necessary information on the kernel
	  command line, you can say N here.

	  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
	  must be operating on your network.  Read
131
	  <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
L
Linus Torvalds 已提交
132 133 134 135 136 137 138 139 140 141 142 143 144 145

config IP_PNP_BOOTP
	bool "IP: BOOTP support"
	depends on IP_PNP
	---help---
	  If you want your Linux box to mount its whole root file system (the
	  one containing the directory /) from some other computer over the
	  net via NFS and you want the IP address of your computer to be
	  discovered automatically at boot time using the BOOTP protocol (a
	  special protocol designed for doing this job), say Y here. In case
	  the boot ROM of your network card was designed for booting Linux and
	  does BOOTP itself, providing all necessary information on the kernel
	  command line, you can say N here. If unsure, say Y. Note that if you
	  want to use BOOTP, a BOOTP server must be operating on your network.
146
	  Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
L
Linus Torvalds 已提交
147 148 149 150 151 152 153 154 155 156 157

config IP_PNP_RARP
	bool "IP: RARP support"
	depends on IP_PNP
	help
	  If you want your Linux box to mount its whole root file system (the
	  one containing the directory /) from some other computer over the
	  net via NFS and you want the IP address of your computer to be
	  discovered automatically at boot time using the RARP protocol (an
	  older protocol which is being obsoleted by BOOTP and DHCP), say Y
	  here. Note that if you want to use RARP, a RARP server must be
158
	  operating on your network. Read
159
	  <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
L
Linus Torvalds 已提交
160 161 162

config NET_IPIP
	tristate "IP: tunneling"
H
Herbert Xu 已提交
163
	select INET_TUNNEL
P
Pravin B Shelar 已提交
164
	select NET_IP_TUNNEL
L
Linus Torvalds 已提交
165 166 167 168 169 170 171 172 173 174 175 176 177 178
	---help---
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This particular tunneling driver implements
	  encapsulation of IP within IP, which sounds kind of pointless, but
	  can be useful if you want to make your (or some other) machine
	  appear on a different network than it physically is, or to use
	  mobile-IP facilities (allowing laptops to seamlessly move between
	  networks without changing their IP addresses).

	  Saying Y to this option will produce two modules ( = code which can
	  be inserted in and removed from the running kernel whenever you
	  want). Most people won't need this and can say N.

179 180 181 182 183 184
config NET_IPGRE_DEMUX
	tristate "IP: GRE demultiplexer"
	help
	 This is helper module to demultiplex GRE packets on GRE version field criteria.
	 Required by ip_gre and pptp modules.

185 186
config NET_IP_TUNNEL
	tristate
187
	select DST_CACHE
188
	select GRO_CELLS
189 190
	default n

L
Linus Torvalds 已提交
191 192
config NET_IPGRE
	tristate "IP: GRE tunnels over IP"
193
	depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
194
	select NET_IP_TUNNEL
L
Linus Torvalds 已提交
195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214
	help
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This particular tunneling driver implements
	  GRE (Generic Routing Encapsulation) and at this time allows
	  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
	  This driver is useful if the other endpoint is a Cisco router: Cisco
	  likes GRE much better than the other Linux tunneling driver ("IP
	  tunneling" above). In addition, GRE allows multicast redistribution
	  through the tunnel.

config NET_IPGRE_BROADCAST
	bool "IP: broadcast GRE over IP"
	depends on IP_MULTICAST && NET_IPGRE
	help
	  One application of GRE/IP is to construct a broadcast WAN (Wide Area
	  Network), which looks like a normal Ethernet LAN (Local Area
	  Network), but can be distributed all over the Internet. If you want
	  to do that, say Y here and to "IP multicast routing" below.

215 216 217 218
config IP_MROUTE_COMMON
	bool
	depends on IP_MROUTE || IPV6_MROUTE

L
Linus Torvalds 已提交
219 220 221
config IP_MROUTE
	bool "IP: multicast routing"
	depends on IP_MULTICAST
222
	select IP_MROUTE_COMMON
L
Linus Torvalds 已提交
223 224 225 226 227
	help
	  This is used if you want your machine to act as a router for IP
	  packets that have several destination addresses. It is needed on the
	  MBONE, a high bandwidth network on top of the Internet which carries
	  audio and video broadcasts. In order to do that, you would most
228 229
	  likely run the program mrouted. If you haven't heard about it, you
	  don't need it.
L
Linus Torvalds 已提交
230

231 232
config IP_MROUTE_MULTIPLE_TABLES
	bool "IP: multicast policy routing"
233
	depends on IP_MROUTE && IP_ADVANCED_ROUTER
234 235 236 237 238 239 240 241 242 243 244
	select FIB_RULES
	help
	  Normally, a multicast router runs a userspace daemon and decides
	  what to do with a multicast packet based on the source and
	  destination addresses. If you say Y here, the multicast router
	  will also be able to take interfaces and packet marks into
	  account and run multiple instances of userspace daemons
	  simultaneously, each one handling a single table.

	  If unsure, say N.

L
Linus Torvalds 已提交
245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267
config IP_PIMSM_V1
	bool "IP: PIM-SM version 1 support"
	depends on IP_MROUTE
	help
	  Kernel side support for Sparse Mode PIM (Protocol Independent
	  Multicast) version 1. This multicast routing protocol is used widely
	  because Cisco supports it. You need special software to use it
	  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
	  information about PIM.

	  Say Y if you want to use PIM-SM v1. Note that you can say N here if
	  you just want to use Dense Mode PIM.

config IP_PIMSM_V2
	bool "IP: PIM-SM version 2 support"
	depends on IP_MROUTE
	help
	  Kernel side support for Sparse Mode PIM version 2. In order to use
	  this, you need an experimental routing daemon supporting it (pimd or
	  gated-5). This routing protocol is not used widely, so say N unless
	  you want to play with it.

config SYN_COOKIES
268
	bool "IP: TCP syncookie support"
L
Linus Torvalds 已提交
269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292
	---help---
	  Normal TCP/IP networking is open to an attack known as "SYN
	  flooding". This denial-of-service attack prevents legitimate remote
	  users from being able to connect to your computer during an ongoing
	  attack and requires very little work from the attacker, who can
	  operate from anywhere on the Internet.

	  SYN cookies provide protection against this type of attack. If you
	  say Y here, the TCP/IP stack will use a cryptographic challenge
	  protocol known as "SYN cookies" to enable legitimate users to
	  continue to connect, even when your machine is under attack. There
	  is no need for the legitimate users to change their TCP/IP software;
	  SYN cookies work transparently to them. For technical information
	  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.

	  If you are SYN flooded, the source address reported by the kernel is
	  likely to have been forged by the attacker; it is only reported as
	  an aid in tracing the packets to their actual source and should not
	  be taken as absolute truth.

	  SYN cookies may prevent correct error reporting on clients when the
	  server is really overloaded. If this happens frequently better turn
	  them off.

293 294
	  If you say Y here, you can disable SYN cookies at run time by
	  saying Y to "/proc file system support" and
L
Linus Torvalds 已提交
295 296
	  "Sysctl support" below and executing the command

297
	  echo 0 > /proc/sys/net/ipv4/tcp_syncookies
L
Linus Torvalds 已提交
298

299
	  after the /proc file system has been mounted.
L
Linus Torvalds 已提交
300 301 302

	  If unsure, say N.

303 304 305
config NET_IPVTI
	tristate "Virtual (secure) IP: tunneling"
	select INET_TUNNEL
306
	select NET_IP_TUNNEL
307 308 309 310 311 312 313 314
	depends on INET_XFRM_MODE_TUNNEL
	---help---
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This can be used with xfrm mode tunnel to give
	  the notion of a secure tunnel for IPSEC and then use routing protocol
	  on top.

315 316
config NET_UDP_TUNNEL
	tristate
317
	select NET_IP_TUNNEL
318 319
	default n

320 321 322 323 324 325 326 327 328 329
config NET_FOU
	tristate "IP: Foo (IP protocols) over UDP"
	select XFRM
	select NET_UDP_TUNNEL
	---help---
	  Foo over UDP allows any IP protocol to be directly encapsulated
	  over UDP include tunnels (IPIP, GRE, SIT). By encapsulating in UDP
	  network mechanisms and optimizations for UDP (such as ECMP
	  and RSS) can be leveraged to provide better service.

330 331 332 333 334 335 336 337 338
config NET_FOU_IP_TUNNELS
	bool "IP: FOU encapsulation of IP tunnels"
	depends on NET_IPIP || NET_IPGRE || IPV6_SIT
	select NET_FOU
	---help---
	  Allow configuration of FOU or GUE encapsulation for IP tunnels.
	  When this option is enabled IP tunnels can be configured to use
	  FOU or GUE encapsulation.

L
Linus Torvalds 已提交
339 340
config INET_AH
	tristate "IP: AH transformation"
J
Jan Beulich 已提交
341
	select XFRM_ALGO
L
Linus Torvalds 已提交
342 343 344 345 346 347 348 349 350 351 352
	select CRYPTO
	select CRYPTO_HMAC
	select CRYPTO_MD5
	select CRYPTO_SHA1
	---help---
	  Support for IPsec AH.

	  If unsure, say Y.

config INET_ESP
	tristate "IP: ESP transformation"
J
Jan Beulich 已提交
353
	select XFRM_ALGO
L
Linus Torvalds 已提交
354
	select CRYPTO
H
Herbert Xu 已提交
355
	select CRYPTO_AUTHENC
L
Linus Torvalds 已提交
356 357
	select CRYPTO_HMAC
	select CRYPTO_MD5
358
	select CRYPTO_CBC
L
Linus Torvalds 已提交
359 360
	select CRYPTO_SHA1
	select CRYPTO_DES
361
	select CRYPTO_ECHAINIV
L
Linus Torvalds 已提交
362 363 364 365 366
	---help---
	  Support for IPsec ESP.

	  If unsure, say Y.

367 368 369 370 371 372 373 374 375 376 377 378 379
config INET_ESP_OFFLOAD
	tristate "IP: ESP transformation offload"
	depends on INET_ESP
	select XFRM_OFFLOAD
	default n
	---help---
	  Support for ESP transformation offload. This makes sense
	  only if this system really does IPsec and want to do it
	  with high throughput. A typical desktop system does not
	  need it, even if it does IPsec.

	  If unsure, say N.

L
Linus Torvalds 已提交
380 381
config INET_IPCOMP
	tristate "IP: IPComp transformation"
H
Herbert Xu 已提交
382
	select INET_XFRM_TUNNEL
383
	select XFRM_IPCOMP
L
Linus Torvalds 已提交
384 385 386
	---help---
	  Support for IP Payload Compression Protocol (IPComp) (RFC3173),
	  typically needed for IPsec.
387

L
Linus Torvalds 已提交
388 389
	  If unsure, say Y.

H
Herbert Xu 已提交
390 391 392 393 394
config INET_XFRM_TUNNEL
	tristate
	select INET_TUNNEL
	default n

L
Linus Torvalds 已提交
395
config INET_TUNNEL
H
Herbert Xu 已提交
396 397
	tristate
	default n
L
Linus Torvalds 已提交
398

399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416
config INET_XFRM_MODE_TRANSPORT
	tristate "IP: IPsec transport mode"
	default y
	select XFRM
	---help---
	  Support for IPsec transport mode.

	  If unsure, say Y.

config INET_XFRM_MODE_TUNNEL
	tristate "IP: IPsec tunnel mode"
	default y
	select XFRM
	---help---
	  Support for IPsec tunnel mode.

	  If unsure, say Y.

D
Diego Beltrami 已提交
417 418 419 420 421 422 423 424 425
config INET_XFRM_MODE_BEET
	tristate "IP: IPsec BEET mode"
	default y
	select XFRM
	---help---
	  Support for IPsec BEET mode.

	  If unsure, say Y.

426 427
config INET_DIAG
	tristate "INET: socket monitoring interface"
L
Linus Torvalds 已提交
428 429
	default y
	---help---
430 431
	  Support for INET (TCP, DCCP, etc) socket monitoring interface used by
	  native Linux tools such as ss. ss is included in iproute2, currently
432
	  downloadable at:
433

434
	    http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
435

L
Linus Torvalds 已提交
436 437
	  If unsure, say Y.

438 439 440 441
config INET_TCP_DIAG
	depends on INET_DIAG
	def_tristate INET_DIAG

442
config INET_UDP_DIAG
443
	tristate "UDP: socket monitoring interface"
444
	depends on INET_DIAG && (IPV6 || IPV6=n)
445 446 447 448
	default n
	---help---
	  Support for UDP socket monitoring interface used by the ss tool.
	  If unsure, say Y.
449

450 451 452 453 454 455 456 457
config INET_RAW_DIAG
	tristate "RAW: socket monitoring interface"
	depends on INET_DIAG && (IPV6 || IPV6=n)
	default n
	---help---
	  Support for RAW socket monitoring interface used by the ss tool.
	  If unsure, say Y.

458 459 460 461 462 463 464 465 466 467 468 469 470
config INET_DIAG_DESTROY
	bool "INET: allow privileged process to administratively close sockets"
	depends on INET_DIAG
	default n
	---help---
	  Provides a SOCK_DESTROY operation that allows privileged processes
	  (e.g., a connection manager or a network administration tool such as
	  ss) to close sockets opened by other processes. Closing a socket in
	  this way interrupts any blocking read/write/connect operations on
	  the socket and causes future socket calls to behave as if the socket
	  had been disconnected.
	  If unsure, say N.

471
menuconfig TCP_CONG_ADVANCED
472 473 474 475 476 477
	bool "TCP: advanced congestion control"
	---help---
	  Support for selection of various TCP congestion control
	  modules.

	  Nearly all users can safely say no here, and a safe default
478
	  selection will be made (CUBIC with new Reno as a fallback).
479 480 481

	  If unsure, say N.

482
if TCP_CONG_ADVANCED
483 484 485

config TCP_CONG_BIC
	tristate "Binary Increase Congestion (BIC) control"
486
	default m
487 488 489 490 491 492 493 494 495 496 497
	---help---
	BIC-TCP is a sender-side only change that ensures a linear RTT
	fairness under large windows while offering both scalability and
	bounded TCP-friendliness. The protocol combines two schemes
	called additive increase and binary search increase. When the
	congestion window is large, additive increase with a large
	increment ensures linear RTT fairness as well as good
	scalability. Under small congestion windows, binary search
	increase provides TCP friendliness.
	See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/

498 499
config TCP_CONG_CUBIC
	tristate "CUBIC TCP"
500
	default y
501 502 503 504 505
	---help---
	This is version 2.0 of BIC-TCP which uses a cubic growth function
	among other techniques.
	See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf

506 507 508 509 510 511 512 513 514 515 516 517 518 519
config TCP_CONG_WESTWOOD
	tristate "TCP Westwood+"
	default m
	---help---
	TCP Westwood+ is a sender-side only modification of the TCP Reno
	protocol stack that optimizes the performance of TCP congestion
	control. It is based on end-to-end bandwidth estimation to set
	congestion window and slow start threshold after a congestion
	episode. Using this estimation, TCP Westwood+ adaptively sets a
	slow start threshold and a congestion window which takes into
	account the bandwidth used  at the time congestion is experienced.
	TCP Westwood+ significantly increases fairness wrt TCP Reno in
	wired networks and throughput over wireless links.

520 521 522 523 524 525 526 527 528 529 530
config TCP_CONG_HTCP
        tristate "H-TCP"
        default m
	---help---
	H-TCP is a send-side only modifications of the TCP Reno
	protocol stack that optimizes the performance of TCP
	congestion control for high speed network links. It uses a
	modeswitch to change the alpha and beta parameters of TCP Reno
	based on network conditions and in a way so as to be fair with
	other Reno and H-TCP flows.

531 532 533 534 535 536 537 538 539 540
config TCP_CONG_HSTCP
	tristate "High Speed TCP"
	default n
	---help---
	Sally Floyd's High Speed TCP (RFC 3649) congestion control.
	A modification to TCP's congestion control mechanism for use
	with large congestion windows. A table indicates how much to
	increase the congestion window by when an ACK is received.
 	For more detail	see http://www.icir.org/floyd/hstcp.html

541 542 543 544 545 546
config TCP_CONG_HYBLA
	tristate "TCP-Hybla congestion control algorithm"
	default n
	---help---
	TCP-Hybla is a sender-side only change that eliminates penalization of
	long-RTT, large-bandwidth connections, like when satellite legs are
M
Matt LaPlante 已提交
547
	involved, especially when sharing a common bottleneck with normal
548 549
	terrestrial connections.

550 551 552 553 554 555 556 557 558 559
config TCP_CONG_VEGAS
	tristate "TCP Vegas"
	default n
	---help---
	TCP Vegas is a sender-side only change to TCP that anticipates
	the onset of congestion by estimating the bandwidth. TCP Vegas
	adjusts the sending rate by modifying the congestion
	window. TCP Vegas should provide less packet loss, but it is
	not as aggressive as TCP Reno.

L
Lawrence Brakmo 已提交
560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575
config TCP_CONG_NV
       tristate "TCP NV"
       default n
       ---help---
       TCP NV is a follow up to TCP Vegas. It has been modified to deal with
       10G networks, measurement noise introduced by LRO, GRO and interrupt
       coalescence. In addition, it will decrease its cwnd multiplicatively
       instead of linearly.

       Note that in general congestion avoidance (cwnd decreased when # packets
       queued grows) cannot coexist with congestion control (cwnd decreased only
       when there is packet loss) due to fairness issues. One scenario when they
       can coexist safely is when the CA flows have RTTs << CC flows RTTs.

       For further details see http://www.brakmo.org/networking/tcp-nv/

576 577 578 579 580 581 582
config TCP_CONG_SCALABLE
	tristate "Scalable TCP"
	default n
	---help---
	Scalable TCP is a sender-side only change to TCP which uses a
	MIMD congestion control algorithm which has some nice scaling
	properties, though is known to have fairness issues.
583
	See http://www.deneholme.net/tom/scalable/
584

585 586 587 588 589
config TCP_CONG_LP
	tristate "TCP Low Priority"
	default n
	---help---
	TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
M
Matt LaPlante 已提交
590
	to utilize only the excess network bandwidth as compared to the
591 592 593
	``fair share`` of bandwidth as targeted by TCP.
	See http://www-ece.rice.edu/networks/TCP-LP/

B
Bin Zhou 已提交
594 595 596 597 598 599 600 601 602
config TCP_CONG_VENO
	tristate "TCP Veno"
	default n
	---help---
	TCP Veno is a sender-side only enhancement of TCP to obtain better
	throughput over wireless networks. TCP Veno makes use of state
	distinguishing to circumvent the difficult judgment of the packet loss
	type. TCP Veno cuts down less congestion window in response to random
	loss packets.
603
	See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
B
Bin Zhou 已提交
604

605 606
config TCP_CONG_YEAH
	tristate "YeAH TCP"
607
	select TCP_CONG_VEGAS
608 609 610 611 612 613 614 615 616 617 618
	default n
	---help---
	YeAH-TCP is a sender-side high-speed enabled TCP congestion control
	algorithm, which uses a mixed loss/delay approach to compute the
	congestion window. It's design goals target high efficiency,
	internal, RTT and Reno fairness, resilience to link loss while
	keeping network elements load as low as possible.

	For further details look here:
	  http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf

619 620 621 622
config TCP_CONG_ILLINOIS
	tristate "TCP Illinois"
	default n
	---help---
M
Matt LaPlante 已提交
623
	TCP-Illinois is a sender-side modification of TCP Reno for
624 625 626 627 628 629 630
	high speed long delay links. It uses round-trip-time to
	adjust the alpha and beta parameters to achieve a higher average
	throughput and maintain fairness.

	For further details see:
	  http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html

631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651
config TCP_CONG_DCTCP
	tristate "DataCenter TCP (DCTCP)"
	default n
	---help---
	DCTCP leverages Explicit Congestion Notification (ECN) in the network to
	provide multi-bit feedback to the end hosts. It is designed to provide:

	- High burst tolerance (incast due to partition/aggregate),
	- Low latency (short flows, queries),
	- High throughput (continuous data updates, large file transfers) with
	  commodity, shallow-buffered switches.

	All switches in the data center network running DCTCP must support
	ECN marking and be configured for marking when reaching defined switch
	buffer thresholds. The default ECN marking threshold heuristic for
	DCTCP on switches is 20 packets (30KB) at 1Gbps, and 65 packets
	(~100KB) at 10Gbps, but might need further careful tweaking.

	For further details see:
	  http://simula.stanford.edu/~alizade/Site/DCTCP_files/dctcp-final.pdf

652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667
config TCP_CONG_CDG
	tristate "CAIA Delay-Gradient (CDG)"
	default n
	---help---
	CAIA Delay-Gradient (CDG) is a TCP congestion control that modifies
	the TCP sender in order to:

	  o Use the delay gradient as a congestion signal.
	  o Back off with an average probability that is independent of the RTT.
	  o Coexist with flows that use loss-based congestion control.
	  o Tolerate packet loss unrelated to congestion.

	For further details see:
	  D.A. Hayes and G. Armitage. "Revisiting TCP congestion control using
	  delay gradients." In Networking 2011. Preprint: http://goo.gl/No3vdg

668 669 670 671 672 673 674 675 676 677 678 679 680 681 682
config TCP_CONG_BBR
	tristate "BBR TCP"
	default n
	---help---

	BBR (Bottleneck Bandwidth and RTT) TCP congestion control aims to
	maximize network utilization and minimize queues. It builds an explicit
	model of the the bottleneck delivery rate and path round-trip
	propagation delay. It tolerates packet loss and delay unrelated to
	congestion. It can operate over LAN, WAN, cellular, wifi, or cable
	modem links. It can coexist with flows that use loss-based congestion
	control, and can operate with shallow buffers, deep buffers,
	bufferbloat, policers, or AQM schemes that do not provide a delay
	signal. It requires the fq ("Fair Queue") pacing packet scheduler.

683 684
choice
	prompt "Default TCP congestion control"
685
	default DEFAULT_CUBIC
686 687 688 689 690 691 692 693 694 695 696 697 698
	help
	  Select the TCP congestion control that will be used by default
	  for all connections.

	config DEFAULT_BIC
		bool "Bic" if TCP_CONG_BIC=y

	config DEFAULT_CUBIC
		bool "Cubic" if TCP_CONG_CUBIC=y

	config DEFAULT_HTCP
		bool "Htcp" if TCP_CONG_HTCP=y

699 700 701
	config DEFAULT_HYBLA
		bool "Hybla" if TCP_CONG_HYBLA=y

702 703 704
	config DEFAULT_VEGAS
		bool "Vegas" if TCP_CONG_VEGAS=y

705 706 707
	config DEFAULT_VENO
		bool "Veno" if TCP_CONG_VENO=y

708 709 710
	config DEFAULT_WESTWOOD
		bool "Westwood" if TCP_CONG_WESTWOOD=y

711 712 713
	config DEFAULT_DCTCP
		bool "DCTCP" if TCP_CONG_DCTCP=y

714 715 716
	config DEFAULT_CDG
		bool "CDG" if TCP_CONG_CDG=y

717 718 719
	config DEFAULT_BBR
		bool "BBR" if TCP_CONG_BBR=y

720 721 722 723 724
	config DEFAULT_RENO
		bool "Reno"
endchoice

endif
725

726
config TCP_CONG_CUBIC
727
	tristate
728 729 730
	depends on !TCP_CONG_ADVANCED
	default y

731 732 733 734 735
config DEFAULT_TCP_CONG
	string
	default "bic" if DEFAULT_BIC
	default "cubic" if DEFAULT_CUBIC
	default "htcp" if DEFAULT_HTCP
736
	default "hybla" if DEFAULT_HYBLA
737 738
	default "vegas" if DEFAULT_VEGAS
	default "westwood" if DEFAULT_WESTWOOD
739
	default "veno" if DEFAULT_VENO
740
	default "reno" if DEFAULT_RENO
741
	default "dctcp" if DEFAULT_DCTCP
742
	default "cdg" if DEFAULT_CDG
743
	default "bbr" if DEFAULT_BBR
744
	default "cubic"
745

746
config TCP_MD5SIG
747
	bool "TCP: MD5 Signature Option support (RFC2385)"
748 749 750
	select CRYPTO
	select CRYPTO_MD5
	---help---
751
	  RFC2385 specifies a method of giving MD5 protection to TCP sessions.
752 753 754 755
	  Its main (only?) use is to protect BGP sessions between core routers
	  on the Internet.

	  If unsure, say N.