5 bool "IP: multicasting"
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
12 <http://www.savetz.com/mbone/>. For most people, it's safe to say N.
14 config IP_ADVANCED_ROUTER
15 bool "IP: advanced router"
17 If you intend to run your Linux box mostly as a router, i.e. as a
18 computer that forwards and redistributes network packets, say Y; you
19 will then be presented with several options that allow more precise
20 control about the routing process.
22 The answer to this question won't directly affect the kernel:
23 answering N will just cause the configurator to skip all the
24 questions about advanced routing.
26 Note that your box can only act as a router if you enable IP
27 forwarding in your kernel; you can do that by saying Y to "/proc
28 file system support" and "Sysctl support" below and executing the
31 echo "1" > /proc/sys/net/ipv4/ip_forward
33 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
36 automatically rejects incoming packets if the routing table entry
37 for their source address doesn't match the network interface they're
38 arriving on. This has security advantages because it prevents the
39 so-called IP spoofing, however it can pose problems if you use
40 asymmetric routing (packets from you to a host take a different path
41 than packets from that host to you) or if you operate a non-routing
42 host which has several IP addresses on different interfaces. To turn
45 echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
47 echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
49 Note that some distributions enable it in startup scripts.
50 For details about rp_filter strict and loose mode read
51 <file:Documentation/networking/ip-sysctl.txt>.
53 If unsure, say N here.
55 config IP_FIB_TRIE_STATS
56 bool "FIB TRIE statistics"
57 depends on IP_ADVANCED_ROUTER
59 Keep track of statistics on structure of FIB TRIE table.
60 Useful for testing and measuring TRIE performance.
62 config IP_MULTIPLE_TABLES
63 bool "IP: policy routing"
64 depends on IP_ADVANCED_ROUTER
67 Normally, a router decides what to do with a received packet based
68 solely on the packet's final destination address. If you say Y here,
69 the Linux router will also be able to take the packet's source
70 address into account. Furthermore, the TOS (Type-Of-Service) field
71 of the packet can be used for routing decisions as well.
73 If you need more information, see the Linux Advanced
74 Routing and Traffic Control documentation at
75 <http://lartc.org/howto/lartc.rpdb.html>
79 config IP_ROUTE_MULTIPATH
80 bool "IP: equal cost multipath"
81 depends on IP_ADVANCED_ROUTER
83 Normally, the routing tables specify a single action to be taken in
84 a deterministic manner for a given packet. If you say Y here
85 however, it becomes possible to attach several actions to a packet
86 pattern, in effect specifying several alternative paths to travel
87 for those packets. The router considers all these paths to be of
88 equal "cost" and chooses one of them in a non-deterministic fashion
89 if a matching packet arrives.
91 config IP_ROUTE_VERBOSE
92 bool "IP: verbose route monitoring"
93 depends on IP_ADVANCED_ROUTER
95 If you say Y here, which is recommended, then the kernel will print
96 verbose messages regarding the routing, for example warnings about
97 received packets which look strange and could be evidence of an
98 attack or a misconfigured system somewhere. The information is
99 handled by the klogd daemon which is responsible for kernel messages
102 config IP_ROUTE_CLASSID
106 bool "IP: kernel level autoconfiguration"
108 This enables automatic configuration of IP addresses of devices and
109 of the routing table during kernel boot, based on either information
110 supplied on the kernel command line or by BOOTP or RARP protocols.
111 You need to say Y only for diskless machines requiring network
112 access to boot (in which case you want to say Y to "Root file system
113 on NFS" as well), because all other machines configure the network
114 in their startup scripts.
117 bool "IP: DHCP support"
120 If you want your Linux box to mount its whole root file system (the
121 one containing the directory /) from some other computer over the
122 net via NFS and you want the IP address of your computer to be
123 discovered automatically at boot time using the DHCP protocol (a
124 special protocol designed for doing this job), say Y here. In case
125 the boot ROM of your network card was designed for booting Linux and
126 does DHCP itself, providing all necessary information on the kernel
127 command line, you can say N here.
129 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
130 must be operating on your network. Read
131 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
134 bool "IP: BOOTP support"
137 If you want your Linux box to mount its whole root file system (the
138 one containing the directory /) from some other computer over the
139 net via NFS and you want the IP address of your computer to be
140 discovered automatically at boot time using the BOOTP protocol (a
141 special protocol designed for doing this job), say Y here. In case
142 the boot ROM of your network card was designed for booting Linux and
143 does BOOTP itself, providing all necessary information on the kernel
144 command line, you can say N here. If unsure, say Y. Note that if you
145 want to use BOOTP, a BOOTP server must be operating on your network.
146 Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
149 bool "IP: RARP support"
152 If you want your Linux box to mount its whole root file system (the
153 one containing the directory /) from some other computer over the
154 net via NFS and you want the IP address of your computer to be
155 discovered automatically at boot time using the RARP protocol (an
156 older protocol which is being obsoleted by BOOTP and DHCP), say Y
157 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.
162 tristate "IP: tunneling"
166 Tunneling means encapsulating data of one protocol type within
167 another protocol and sending it over a channel that understands the
168 encapsulating protocol. This particular tunneling driver implements
169 encapsulation of IP within IP, which sounds kind of pointless, but
170 can be useful if you want to make your (or some other) machine
171 appear on a different network than it physically is, or to use
172 mobile-IP facilities (allowing laptops to seamlessly move between
173 networks without changing their IP addresses).
175 Saying Y to this option will produce two modules ( = code which can
176 be inserted in and removed from the running kernel whenever you
177 want). Most people won't need this and can say N.
179 config NET_IPGRE_DEMUX
180 tristate "IP: GRE demultiplexer"
182 This is helper module to demultiplex GRE packets on GRE version field criteria.
183 Required by ip_gre and pptp modules.
192 tristate "IP: GRE tunnels over IP"
193 depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
196 Tunneling means encapsulating data of one protocol type within
197 another protocol and sending it over a channel that understands the
198 encapsulating protocol. This particular tunneling driver implements
199 GRE (Generic Routing Encapsulation) and at this time allows
200 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
201 This driver is useful if the other endpoint is a Cisco router: Cisco
202 likes GRE much better than the other Linux tunneling driver ("IP
203 tunneling" above). In addition, GRE allows multicast redistribution
206 config NET_IPGRE_BROADCAST
207 bool "IP: broadcast GRE over IP"
208 depends on IP_MULTICAST && NET_IPGRE
210 One application of GRE/IP is to construct a broadcast WAN (Wide Area
211 Network), which looks like a normal Ethernet LAN (Local Area
212 Network), but can be distributed all over the Internet. If you want
213 to do that, say Y here and to "IP multicast routing" below.
216 bool "IP: multicast routing"
217 depends on IP_MULTICAST
219 This is used if you want your machine to act as a router for IP
220 packets that have several destination addresses. It is needed on the
221 MBONE, a high bandwidth network on top of the Internet which carries
222 audio and video broadcasts. In order to do that, you would most
223 likely run the program mrouted. If you haven't heard about it, you
226 config IP_MROUTE_MULTIPLE_TABLES
227 bool "IP: multicast policy routing"
228 depends on IP_MROUTE && IP_ADVANCED_ROUTER
231 Normally, a multicast router runs a userspace daemon and decides
232 what to do with a multicast packet based on the source and
233 destination addresses. If you say Y here, the multicast router
234 will also be able to take interfaces and packet marks into
235 account and run multiple instances of userspace daemons
236 simultaneously, each one handling a single table.
241 bool "IP: PIM-SM version 1 support"
244 Kernel side support for Sparse Mode PIM (Protocol Independent
245 Multicast) version 1. This multicast routing protocol is used widely
246 because Cisco supports it. You need special software to use it
247 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
248 information about PIM.
250 Say Y if you want to use PIM-SM v1. Note that you can say N here if
251 you just want to use Dense Mode PIM.
254 bool "IP: PIM-SM version 2 support"
257 Kernel side support for Sparse Mode PIM version 2. In order to use
258 this, you need an experimental routing daemon supporting it (pimd or
259 gated-5). This routing protocol is not used widely, so say N unless
260 you want to play with it.
263 bool "IP: TCP syncookie support"
265 Normal TCP/IP networking is open to an attack known as "SYN
266 flooding". This denial-of-service attack prevents legitimate remote
267 users from being able to connect to your computer during an ongoing
268 attack and requires very little work from the attacker, who can
269 operate from anywhere on the Internet.
271 SYN cookies provide protection against this type of attack. If you
272 say Y here, the TCP/IP stack will use a cryptographic challenge
273 protocol known as "SYN cookies" to enable legitimate users to
274 continue to connect, even when your machine is under attack. There
275 is no need for the legitimate users to change their TCP/IP software;
276 SYN cookies work transparently to them. For technical information
277 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
279 If you are SYN flooded, the source address reported by the kernel is
280 likely to have been forged by the attacker; it is only reported as
281 an aid in tracing the packets to their actual source and should not
282 be taken as absolute truth.
284 SYN cookies may prevent correct error reporting on clients when the
285 server is really overloaded. If this happens frequently better turn
288 If you say Y here, you can disable SYN cookies at run time by
289 saying Y to "/proc file system support" and
290 "Sysctl support" below and executing the command
292 echo 0 > /proc/sys/net/ipv4/tcp_syncookies
294 after the /proc file system has been mounted.
299 tristate "Virtual (secure) IP: tunneling"
300 depends on IPV6 || IPV6=n
303 depends on INET_XFRM_MODE_TUNNEL
305 Tunneling means encapsulating data of one protocol type within
306 another protocol and sending it over a channel that understands the
307 encapsulating protocol. This can be used with xfrm mode tunnel to give
308 the notion of a secure tunnel for IPSEC and then use routing protocol
311 config NET_UDP_TUNNEL
317 tristate "IP: Foo (IP protocols) over UDP"
319 select NET_UDP_TUNNEL
321 Foo over UDP allows any IP protocol to be directly encapsulated
322 over UDP include tunnels (IPIP, GRE, SIT). By encapsulating in UDP
323 network mechanisms and optimizations for UDP (such as ECMP
324 and RSS) can be leveraged to provide better service.
326 config NET_FOU_IP_TUNNELS
327 bool "IP: FOU encapsulation of IP tunnels"
328 depends on NET_IPIP || NET_IPGRE || IPV6_SIT
331 Allow configuration of FOU or GUE encapsulation for IP tunnels.
332 When this option is enabled IP tunnels can be configured to use
333 FOU or GUE encapsulation.
336 tristate "IP: AH transformation"
343 Support for IPsec AH.
348 tristate "IP: ESP transformation"
351 select CRYPTO_AUTHENC
357 select CRYPTO_ECHAINIV
359 Support for IPsec ESP.
363 config INET_ESP_OFFLOAD
364 tristate "IP: ESP transformation offload"
369 Support for ESP transformation offload. This makes sense
370 only if this system really does IPsec and want to do it
371 with high throughput. A typical desktop system does not
372 need it, even if it does IPsec.
377 tristate "IP: IPComp transformation"
378 select INET_XFRM_TUNNEL
381 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
382 typically needed for IPsec.
386 config INET_XFRM_TUNNEL
395 config INET_XFRM_MODE_TRANSPORT
396 tristate "IP: IPsec transport mode"
400 Support for IPsec transport mode.
404 config INET_XFRM_MODE_TUNNEL
405 tristate "IP: IPsec tunnel mode"
409 Support for IPsec tunnel mode.
413 config INET_XFRM_MODE_BEET
414 tristate "IP: IPsec BEET mode"
418 Support for IPsec BEET mode.
423 tristate "INET: socket monitoring interface"
426 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
427 native Linux tools such as ss. ss is included in iproute2, currently
430 http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
436 def_tristate INET_DIAG
439 tristate "UDP: socket monitoring interface"
440 depends on INET_DIAG && (IPV6 || IPV6=n)
443 Support for UDP socket monitoring interface used by the ss tool.
447 tristate "RAW: socket monitoring interface"
448 depends on INET_DIAG && (IPV6 || IPV6=n)
451 Support for RAW socket monitoring interface used by the ss tool.
454 config INET_DIAG_DESTROY
455 bool "INET: allow privileged process to administratively close sockets"
459 Provides a SOCK_DESTROY operation that allows privileged processes
460 (e.g., a connection manager or a network administration tool such as
461 ss) to close sockets opened by other processes. Closing a socket in
462 this way interrupts any blocking read/write/connect operations on
463 the socket and causes future socket calls to behave as if the socket
464 had been disconnected.
467 menuconfig TCP_CONG_ADVANCED
468 bool "TCP: advanced congestion control"
470 Support for selection of various TCP congestion control
473 Nearly all users can safely say no here, and a safe default
474 selection will be made (CUBIC with new Reno as a fallback).
481 tristate "Binary Increase Congestion (BIC) control"
484 BIC-TCP is a sender-side only change that ensures a linear RTT
485 fairness under large windows while offering both scalability and
486 bounded TCP-friendliness. The protocol combines two schemes
487 called additive increase and binary search increase. When the
488 congestion window is large, additive increase with a large
489 increment ensures linear RTT fairness as well as good
490 scalability. Under small congestion windows, binary search
491 increase provides TCP friendliness.
492 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
494 config TCP_CONG_CUBIC
498 This is version 2.0 of BIC-TCP which uses a cubic growth function
499 among other techniques.
500 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
502 config TCP_CONG_WESTWOOD
503 tristate "TCP Westwood+"
506 TCP Westwood+ is a sender-side only modification of the TCP Reno
507 protocol stack that optimizes the performance of TCP congestion
508 control. It is based on end-to-end bandwidth estimation to set
509 congestion window and slow start threshold after a congestion
510 episode. Using this estimation, TCP Westwood+ adaptively sets a
511 slow start threshold and a congestion window which takes into
512 account the bandwidth used at the time congestion is experienced.
513 TCP Westwood+ significantly increases fairness wrt TCP Reno in
514 wired networks and throughput over wireless links.
520 H-TCP is a send-side only modifications of the TCP Reno
521 protocol stack that optimizes the performance of TCP
522 congestion control for high speed network links. It uses a
523 modeswitch to change the alpha and beta parameters of TCP Reno
524 based on network conditions and in a way so as to be fair with
525 other Reno and H-TCP flows.
527 config TCP_CONG_HSTCP
528 tristate "High Speed TCP"
531 Sally Floyd's High Speed TCP (RFC 3649) congestion control.
532 A modification to TCP's congestion control mechanism for use
533 with large congestion windows. A table indicates how much to
534 increase the congestion window by when an ACK is received.
535 For more detail see http://www.icir.org/floyd/hstcp.html
537 config TCP_CONG_HYBLA
538 tristate "TCP-Hybla congestion control algorithm"
541 TCP-Hybla is a sender-side only change that eliminates penalization of
542 long-RTT, large-bandwidth connections, like when satellite legs are
543 involved, especially when sharing a common bottleneck with normal
544 terrestrial connections.
546 config TCP_CONG_VEGAS
550 TCP Vegas is a sender-side only change to TCP that anticipates
551 the onset of congestion by estimating the bandwidth. TCP Vegas
552 adjusts the sending rate by modifying the congestion
553 window. TCP Vegas should provide less packet loss, but it is
554 not as aggressive as TCP Reno.
560 TCP NV is a follow up to TCP Vegas. It has been modified to deal with
561 10G networks, measurement noise introduced by LRO, GRO and interrupt
562 coalescence. In addition, it will decrease its cwnd multiplicatively
565 Note that in general congestion avoidance (cwnd decreased when # packets
566 queued grows) cannot coexist with congestion control (cwnd decreased only
567 when there is packet loss) due to fairness issues. One scenario when they
568 can coexist safely is when the CA flows have RTTs << CC flows RTTs.
570 For further details see http://www.brakmo.org/networking/tcp-nv/
572 config TCP_CONG_SCALABLE
573 tristate "Scalable TCP"
576 Scalable TCP is a sender-side only change to TCP which uses a
577 MIMD congestion control algorithm which has some nice scaling
578 properties, though is known to have fairness issues.
579 See http://www.deneholme.net/tom/scalable/
582 tristate "TCP Low Priority"
585 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
586 to utilize only the excess network bandwidth as compared to the
587 ``fair share`` of bandwidth as targeted by TCP.
588 See http://www-ece.rice.edu/networks/TCP-LP/
594 TCP Veno is a sender-side only enhancement of TCP to obtain better
595 throughput over wireless networks. TCP Veno makes use of state
596 distinguishing to circumvent the difficult judgment of the packet loss
597 type. TCP Veno cuts down less congestion window in response to random
599 See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
603 select TCP_CONG_VEGAS
606 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
607 algorithm, which uses a mixed loss/delay approach to compute the
608 congestion window. It's design goals target high efficiency,
609 internal, RTT and Reno fairness, resilience to link loss while
610 keeping network elements load as low as possible.
612 For further details look here:
613 http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
615 config TCP_CONG_ILLINOIS
616 tristate "TCP Illinois"
619 TCP-Illinois is a sender-side modification of TCP Reno for
620 high speed long delay links. It uses round-trip-time to
621 adjust the alpha and beta parameters to achieve a higher average
622 throughput and maintain fairness.
624 For further details see:
625 http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
627 config TCP_CONG_DCTCP
628 tristate "DataCenter TCP (DCTCP)"
631 DCTCP leverages Explicit Congestion Notification (ECN) in the network to
632 provide multi-bit feedback to the end hosts. It is designed to provide:
634 - High burst tolerance (incast due to partition/aggregate),
635 - Low latency (short flows, queries),
636 - High throughput (continuous data updates, large file transfers) with
637 commodity, shallow-buffered switches.
639 All switches in the data center network running DCTCP must support
640 ECN marking and be configured for marking when reaching defined switch
641 buffer thresholds. The default ECN marking threshold heuristic for
642 DCTCP on switches is 20 packets (30KB) at 1Gbps, and 65 packets
643 (~100KB) at 10Gbps, but might need further careful tweaking.
645 For further details see:
646 http://simula.stanford.edu/~alizade/Site/DCTCP_files/dctcp-final.pdf
649 tristate "CAIA Delay-Gradient (CDG)"
652 CAIA Delay-Gradient (CDG) is a TCP congestion control that modifies
653 the TCP sender in order to:
655 o Use the delay gradient as a congestion signal.
656 o Back off with an average probability that is independent of the RTT.
657 o Coexist with flows that use loss-based congestion control.
658 o Tolerate packet loss unrelated to congestion.
660 For further details see:
661 D.A. Hayes and G. Armitage. "Revisiting TCP congestion control using
662 delay gradients." In Networking 2011. Preprint: http://goo.gl/No3vdg
669 BBR (Bottleneck Bandwidth and RTT) TCP congestion control aims to
670 maximize network utilization and minimize queues. It builds an explicit
671 model of the the bottleneck delivery rate and path round-trip
672 propagation delay. It tolerates packet loss and delay unrelated to
673 congestion. It can operate over LAN, WAN, cellular, wifi, or cable
674 modem links. It can coexist with flows that use loss-based congestion
675 control, and can operate with shallow buffers, deep buffers,
676 bufferbloat, policers, or AQM schemes that do not provide a delay
677 signal. It requires the fq ("Fair Queue") pacing packet scheduler.
680 prompt "Default TCP congestion control"
681 default DEFAULT_CUBIC
683 Select the TCP congestion control that will be used by default
687 bool "Bic" if TCP_CONG_BIC=y
690 bool "Cubic" if TCP_CONG_CUBIC=y
693 bool "Htcp" if TCP_CONG_HTCP=y
696 bool "Hybla" if TCP_CONG_HYBLA=y
699 bool "Vegas" if TCP_CONG_VEGAS=y
702 bool "Veno" if TCP_CONG_VENO=y
704 config DEFAULT_WESTWOOD
705 bool "Westwood" if TCP_CONG_WESTWOOD=y
708 bool "DCTCP" if TCP_CONG_DCTCP=y
711 bool "CDG" if TCP_CONG_CDG=y
714 bool "BBR" if TCP_CONG_BBR=y
722 config TCP_CONG_CUBIC
724 depends on !TCP_CONG_ADVANCED
727 config DEFAULT_TCP_CONG
729 default "bic" if DEFAULT_BIC
730 default "cubic" if DEFAULT_CUBIC
731 default "htcp" if DEFAULT_HTCP
732 default "hybla" if DEFAULT_HYBLA
733 default "vegas" if DEFAULT_VEGAS
734 default "westwood" if DEFAULT_WESTWOOD
735 default "veno" if DEFAULT_VENO
736 default "reno" if DEFAULT_RENO
737 default "dctcp" if DEFAULT_DCTCP
738 default "cdg" if DEFAULT_CDG
739 default "bbr" if DEFAULT_BBR
743 bool "TCP: MD5 Signature Option support (RFC2385)"
747 RFC2385 specifies a method of giving MD5 protection to TCP sessions.
748 Its main (only?) use is to protect BGP sessions between core routers