Blame view
net/ipv4/Kconfig
25.1 KB
ec8f24b7f
|
1 |
# SPDX-License-Identifier: GPL-2.0-only |
1da177e4c
|
2 3 4 5 6 |
# # IP configuration # config IP_MULTICAST bool "IP: multicasting" |
1da177e4c
|
7 8 9 10 11 12 |
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 |
4960c2c6f
|
13 |
<http://www.savetz.com/mbone/>. For most people, it's safe to say N. |
1da177e4c
|
14 15 16 |
config IP_ADVANCED_ROUTER bool "IP: advanced router" |
1da177e4c
|
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
---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. |
b2cc46a8e
|
35 |
If you turn on IP forwarding, you should consider the rp_filter, which |
1da177e4c
|
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 |
d73943720
|
43 |
rp_filter on use: |
1da177e4c
|
44 |
|
d73943720
|
45 |
echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter |
750e9fad8
|
46 |
or |
d73943720
|
47 |
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter |
1da177e4c
|
48 |
|
b2cc46a8e
|
49 |
Note that some distributions enable it in startup scripts. |
d18921a0e
|
50 51 |
For details about rp_filter strict and loose mode read <file:Documentation/networking/ip-sysctl.txt>. |
b2cc46a8e
|
52 |
|
1da177e4c
|
53 |
If unsure, say N here. |
66a2f7fd2
|
54 55 |
config IP_FIB_TRIE_STATS bool "FIB TRIE statistics" |
3630b7c05
|
56 |
depends on IP_ADVANCED_ROUTER |
66a2f7fd2
|
57 58 59 |
---help--- Keep track of statistics on structure of FIB TRIE table. Useful for testing and measuring TRIE performance. |
1da177e4c
|
60 61 62 |
config IP_MULTIPLE_TABLES bool "IP: policy routing" depends on IP_ADVANCED_ROUTER |
e1ef4bf23
|
63 |
select FIB_RULES |
1da177e4c
|
64 65 66 67 68 69 |
---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. |
12ed3772b
|
70 71 72 |
If you need more information, see the Linux Advanced Routing and Traffic Control documentation at <http://lartc.org/howto/lartc.rpdb.html> |
1da177e4c
|
73 74 |
If unsure, say N. |
1da177e4c
|
75 76 77 78 79 80 81 82 83 84 85 |
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. |
1da177e4c
|
86 87 88 89 90 91 92 93 94 95 |
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"). |
c7066f70d
|
96 97 |
config IP_ROUTE_CLASSID bool |
1da177e4c
|
98 99 |
config IP_PNP bool "IP: kernel level autoconfiguration" |
1da177e4c
|
100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 |
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 |
dc7a08166
|
124 |
<file:Documentation/filesystems/nfs/nfsroot.txt> for details. |
1da177e4c
|
125 126 127 128 129 130 131 132 133 134 135 136 137 138 |
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. |
dc7a08166
|
139 |
Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details. |
1da177e4c
|
140 141 142 143 144 145 146 147 148 149 150 |
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 |
6ded55da6
|
151 |
operating on your network. Read |
dc7a08166
|
152 |
<file:Documentation/filesystems/nfs/nfsroot.txt> for details. |
1da177e4c
|
153 |
|
1da177e4c
|
154 155 |
config NET_IPIP tristate "IP: tunneling" |
d2acc3479
|
156 |
select INET_TUNNEL |
fd58156e4
|
157 |
select NET_IP_TUNNEL |
1da177e4c
|
158 159 160 161 162 163 164 165 166 167 168 169 170 |
---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. |
00959ade3
|
171 172 173 174 175 |
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. |
c54419321
|
176 177 |
config NET_IP_TUNNEL tristate |
e09acddf8
|
178 |
select DST_CACHE |
97e219b7c
|
179 |
select GRO_CELLS |
c54419321
|
180 |
default n |
1da177e4c
|
181 182 |
config NET_IPGRE tristate "IP: GRE tunnels over IP" |
21a180cda
|
183 |
depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX |
c54419321
|
184 |
select NET_IP_TUNNEL |
1da177e4c
|
185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 |
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. |
6853f21f7
|
204 205 206 |
config IP_MROUTE_COMMON bool depends on IP_MROUTE || IPV6_MROUTE |
1da177e4c
|
207 208 209 |
config IP_MROUTE bool "IP: multicast routing" depends on IP_MULTICAST |
6853f21f7
|
210 |
select IP_MROUTE_COMMON |
1da177e4c
|
211 212 213 214 215 |
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 |
4960c2c6f
|
216 217 |
likely run the program mrouted. If you haven't heard about it, you don't need it. |
1da177e4c
|
218 |
|
f0ad0860d
|
219 220 |
config IP_MROUTE_MULTIPLE_TABLES bool "IP: multicast policy routing" |
66496d497
|
221 |
depends on IP_MROUTE && IP_ADVANCED_ROUTER |
f0ad0860d
|
222 223 224 225 226 227 228 229 230 231 |
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. |
1da177e4c
|
232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 |
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. |
1da177e4c
|
253 |
config SYN_COOKIES |
57f1553ee
|
254 |
bool "IP: TCP syncookie support" |
1da177e4c
|
255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 |
---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. |
57f1553ee
|
278 279 |
If you say Y here, you can disable SYN cookies at run time by saying Y to "/proc file system support" and |
1da177e4c
|
280 |
"Sysctl support" below and executing the command |
57f1553ee
|
281 |
echo 0 > /proc/sys/net/ipv4/tcp_syncookies |
1da177e4c
|
282 |
|
57f1553ee
|
283 |
after the /proc file system has been mounted. |
1da177e4c
|
284 285 |
If unsure, say N. |
1181412c1
|
286 287 288 |
config NET_IPVTI tristate "Virtual (secure) IP: tunneling" select INET_TUNNEL |
f61dd388a
|
289 |
select NET_IP_TUNNEL |
4c145dce2
|
290 |
select XFRM |
1181412c1
|
291 292 293 294 295 296 |
---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. |
8024e0287
|
297 298 |
config NET_UDP_TUNNEL tristate |
7c5df8fa1
|
299 |
select NET_IP_TUNNEL |
8024e0287
|
300 |
default n |
23461551c
|
301 302 303 304 305 306 307 308 309 |
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. |
63487babf
|
310 311 312 313 314 315 316 317 |
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. |
1da177e4c
|
318 319 |
config INET_AH tristate "IP: AH transformation" |
7e1525249
|
320 |
select XFRM_ALGO |
1da177e4c
|
321 322 323 324 325 326 327 328 329 330 331 |
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" |
7e1525249
|
332 |
select XFRM_ALGO |
1da177e4c
|
333 |
select CRYPTO |
ed58dd41f
|
334 |
select CRYPTO_AUTHENC |
1da177e4c
|
335 336 |
select CRYPTO_HMAC select CRYPTO_MD5 |
6b7326c84
|
337 |
select CRYPTO_CBC |
1da177e4c
|
338 339 |
select CRYPTO_SHA1 select CRYPTO_DES |
32b6170ca
|
340 |
select CRYPTO_ECHAINIV |
1da177e4c
|
341 342 343 344 |
---help--- Support for IPsec ESP. If unsure, say Y. |
7785bba29
|
345 346 347 348 349 350 351 352 353 354 355 356 |
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. |
1da177e4c
|
357 358 |
config INET_IPCOMP tristate "IP: IPComp transformation" |
d2acc3479
|
359 |
select INET_XFRM_TUNNEL |
6fccab671
|
360 |
select XFRM_IPCOMP |
1da177e4c
|
361 362 363 |
---help--- Support for IP Payload Compression Protocol (IPComp) (RFC3173), typically needed for IPsec. |
a6e8f27f3
|
364 |
|
1da177e4c
|
365 |
If unsure, say Y. |
d2acc3479
|
366 367 368 369 |
config INET_XFRM_TUNNEL tristate select INET_TUNNEL default n |
1da177e4c
|
370 |
config INET_TUNNEL |
d2acc3479
|
371 372 |
tristate default n |
1da177e4c
|
373 |
|
17b085eac
|
374 375 |
config INET_DIAG tristate "INET: socket monitoring interface" |
1da177e4c
|
376 377 |
default y ---help--- |
73c1f4a03
|
378 379 |
Support for INET (TCP, DCCP, etc) socket monitoring interface used by native Linux tools such as ss. ss is included in iproute2, currently |
c996d8b9a
|
380 |
downloadable at: |
e446a2760
|
381 |
|
c996d8b9a
|
382 |
http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 |
a6e8f27f3
|
383 |
|
1da177e4c
|
384 |
If unsure, say Y. |
17b085eac
|
385 386 387 |
config INET_TCP_DIAG depends on INET_DIAG def_tristate INET_DIAG |
507dd7961
|
388 |
config INET_UDP_DIAG |
6d62a66e4
|
389 |
tristate "UDP: socket monitoring interface" |
6d25886ee
|
390 |
depends on INET_DIAG && (IPV6 || IPV6=n) |
6d62a66e4
|
391 392 393 394 |
default n ---help--- Support for UDP socket monitoring interface used by the ss tool. If unsure, say Y. |
507dd7961
|
395 |
|
432490f9d
|
396 397 398 399 400 401 402 |
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. |
c1e64e298
|
403 404 405 406 407 408 409 410 411 412 413 414 |
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. |
3d2573f7e
|
415 |
menuconfig TCP_CONG_ADVANCED |
a6484045f
|
416 |
bool "TCP: advanced congestion control" |
a6484045f
|
417 418 419 420 421 |
---help--- Support for selection of various TCP congestion control modules. Nearly all users can safely say no here, and a safe default |
597811ec1
|
422 |
selection will be made (CUBIC with new Reno as a fallback). |
a6484045f
|
423 424 |
If unsure, say N. |
3d2573f7e
|
425 |
if TCP_CONG_ADVANCED |
83803034f
|
426 427 428 |
config TCP_CONG_BIC tristate "Binary Increase Congestion (BIC) control" |
597811ec1
|
429 |
default m |
83803034f
|
430 431 432 433 434 435 436 437 438 439 |
---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/ |
df3271f33
|
440 441 |
config TCP_CONG_CUBIC tristate "CUBIC TCP" |
597811ec1
|
442 |
default y |
df3271f33
|
443 444 445 446 |
---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 |
872707628
|
447 448 |
config TCP_CONG_WESTWOOD tristate "TCP Westwood+" |
872707628
|
449 450 451 452 453 454 455 456 457 458 459 |
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. |
a7868ea68
|
460 |
config TCP_CONG_HTCP |
bf69abad2
|
461 462 |
tristate "H-TCP" default m |
a7868ea68
|
463 464 465 466 467 468 469 |
---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. |
a628d29b5
|
470 471 |
config TCP_CONG_HSTCP tristate "High Speed TCP" |
a628d29b5
|
472 473 474 475 476 477 478 |
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 |
835b3f0c0
|
479 480 |
config TCP_CONG_HYBLA tristate "TCP-Hybla congestion control algorithm" |
835b3f0c0
|
481 482 483 484 |
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 |
44c09201a
|
485 |
involved, especially when sharing a common bottleneck with normal |
835b3f0c0
|
486 |
terrestrial connections. |
b87d8561d
|
487 488 |
config TCP_CONG_VEGAS tristate "TCP Vegas" |
b87d8561d
|
489 490 491 492 493 494 495 |
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. |
699fafafa
|
496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 |
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/ |
0e57976b6
|
511 512 |
config TCP_CONG_SCALABLE tristate "Scalable TCP" |
0e57976b6
|
513 514 515 516 517 |
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. |
f4b9479dc
|
518 |
See http://www.deneholme.net/tom/scalable/ |
a7868ea68
|
519 |
|
7c106d7e7
|
520 521 |
config TCP_CONG_LP tristate "TCP Low Priority" |
7c106d7e7
|
522 523 524 |
default n ---help--- TCP Low Priority (TCP-LP), a distributed algorithm whose goal is |
cab00891c
|
525 |
to utilize only the excess network bandwidth as compared to the |
7c106d7e7
|
526 527 |
``fair share`` of bandwidth as targeted by TCP. See http://www-ece.rice.edu/networks/TCP-LP/ |
76f101775
|
528 529 |
config TCP_CONG_VENO tristate "TCP Veno" |
76f101775
|
530 531 532 533 534 535 536 |
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. |
e446a2760
|
537 |
See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186> |
76f101775
|
538 |
|
5ef814753
|
539 540 |
config TCP_CONG_YEAH tristate "YeAH TCP" |
2ff011efa
|
541 |
select TCP_CONG_VEGAS |
5ef814753
|
542 543 544 545 546 547 548 549 550 551 |
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 |
c462238d6
|
552 553 |
config TCP_CONG_ILLINOIS tristate "TCP Illinois" |
c462238d6
|
554 555 |
default n ---help--- |
01dd2fbf0
|
556 |
TCP-Illinois is a sender-side modification of TCP Reno for |
c462238d6
|
557 558 559 560 561 562 |
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 |
e3118e835
|
563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 |
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 |
2b0a8c9ee
|
583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 |
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 |
0f8782ea1
|
598 599 600 601 602 603 604 605 606 607 608 609 610 611 |
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. |
3d2573f7e
|
612 613 |
choice prompt "Default TCP congestion control" |
597811ec1
|
614 |
default DEFAULT_CUBIC |
3d2573f7e
|
615 616 617 618 619 620 621 622 623 624 625 626 |
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 |
dd2acaa7b
|
627 628 |
config DEFAULT_HYBLA bool "Hybla" if TCP_CONG_HYBLA=y |
3d2573f7e
|
629 630 |
config DEFAULT_VEGAS bool "Vegas" if TCP_CONG_VEGAS=y |
6ce1a6df6
|
631 632 |
config DEFAULT_VENO bool "Veno" if TCP_CONG_VENO=y |
3d2573f7e
|
633 634 |
config DEFAULT_WESTWOOD bool "Westwood" if TCP_CONG_WESTWOOD=y |
e3118e835
|
635 636 |
config DEFAULT_DCTCP bool "DCTCP" if TCP_CONG_DCTCP=y |
2b0a8c9ee
|
637 638 |
config DEFAULT_CDG bool "CDG" if TCP_CONG_CDG=y |
0f8782ea1
|
639 640 |
config DEFAULT_BBR bool "BBR" if TCP_CONG_BBR=y |
3d2573f7e
|
641 642 |
config DEFAULT_RENO bool "Reno" |
3d2573f7e
|
643 644 645 |
endchoice endif |
83803034f
|
646 |
|
597811ec1
|
647 |
config TCP_CONG_CUBIC |
6c3607676
|
648 |
tristate |
a6484045f
|
649 650 |
depends on !TCP_CONG_ADVANCED default y |
3d2573f7e
|
651 652 653 654 655 |
config DEFAULT_TCP_CONG string default "bic" if DEFAULT_BIC default "cubic" if DEFAULT_CUBIC default "htcp" if DEFAULT_HTCP |
dd2acaa7b
|
656 |
default "hybla" if DEFAULT_HYBLA |
3d2573f7e
|
657 658 |
default "vegas" if DEFAULT_VEGAS default "westwood" if DEFAULT_WESTWOOD |
6ce1a6df6
|
659 |
default "veno" if DEFAULT_VENO |
3d2573f7e
|
660 |
default "reno" if DEFAULT_RENO |
e3118e835
|
661 |
default "dctcp" if DEFAULT_DCTCP |
2b0a8c9ee
|
662 |
default "cdg" if DEFAULT_CDG |
4df21dfcf
|
663 |
default "bbr" if DEFAULT_BBR |
597811ec1
|
664 |
default "cubic" |
3d2573f7e
|
665 |
|
cfb6eeb4c
|
666 |
config TCP_MD5SIG |
44fbe9200
|
667 |
bool "TCP: MD5 Signature Option support (RFC2385)" |
cfb6eeb4c
|
668 669 670 |
select CRYPTO select CRYPTO_MD5 ---help--- |
3dde6ad8f
|
671 |
RFC2385 specifies a method of giving MD5 protection to TCP sessions. |
cfb6eeb4c
|
672 673 674 675 |
Its main (only?) use is to protect BGP sessions between core routers on the Internet. If unsure, say N. |