1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # IP configuration 2 # IP configuration
4 # 3 #
5 config IP_MULTICAST 4 config IP_MULTICAST
6 bool "IP: multicasting" 5 bool "IP: multicasting"
7 help 6 help
8 This is code for addressing several 7 This is code for addressing several networked computers at once,
9 enlarging your kernel by about 2 KB. 8 enlarging your kernel by about 2 KB. You need multicasting if you
10 intend to participate in the MBONE, 9 intend to participate in the MBONE, a high bandwidth network on top
11 of the Internet which carries audio 10 of the Internet which carries audio and video broadcasts. More
12 information about the MBONE is on th 11 information about the MBONE is on the WWW at
13 <https://www.savetz.com/mbone/>. For !! 12 <http://www.savetz.com/mbone/>. For most people, it's safe to say N.
14 13
15 config IP_ADVANCED_ROUTER 14 config IP_ADVANCED_ROUTER
16 bool "IP: advanced router" 15 bool "IP: advanced router"
17 help !! 16 ---help---
18 If you intend to run your Linux box 17 If you intend to run your Linux box mostly as a router, i.e. as a
19 computer that forwards and redistrib 18 computer that forwards and redistributes network packets, say Y; you
20 will then be presented with several 19 will then be presented with several options that allow more precise
21 control about the routing process. 20 control about the routing process.
22 21
23 The answer to this question won't di 22 The answer to this question won't directly affect the kernel:
24 answering N will just cause the conf 23 answering N will just cause the configurator to skip all the
25 questions about advanced routing. 24 questions about advanced routing.
26 25
27 Note that your box can only act as a 26 Note that your box can only act as a router if you enable IP
28 forwarding in your kernel; you can d 27 forwarding in your kernel; you can do that by saying Y to "/proc
29 file system support" and "Sysctl sup 28 file system support" and "Sysctl support" below and executing the
30 line 29 line
31 30
32 echo "1" > /proc/sys/net/ipv4/ip_for 31 echo "1" > /proc/sys/net/ipv4/ip_forward
33 32
34 at boot time after the /proc file sy 33 at boot time after the /proc file system has been mounted.
35 34
36 If you turn on IP forwarding, you sh 35 If you turn on IP forwarding, you should consider the rp_filter, which
37 automatically rejects incoming packe 36 automatically rejects incoming packets if the routing table entry
38 for their source address doesn't mat 37 for their source address doesn't match the network interface they're
39 arriving on. This has security advan 38 arriving on. This has security advantages because it prevents the
40 so-called IP spoofing, however it ca 39 so-called IP spoofing, however it can pose problems if you use
41 asymmetric routing (packets from you 40 asymmetric routing (packets from you to a host take a different path
42 than packets from that host to you) 41 than packets from that host to you) or if you operate a non-routing
43 host which has several IP addresses 42 host which has several IP addresses on different interfaces. To turn
44 rp_filter on use: 43 rp_filter on use:
45 44
46 echo 1 > /proc/sys/net/ipv4/conf/<de 45 echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
47 or 46 or
48 echo 1 > /proc/sys/net/ipv4/conf/all 47 echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
49 48
50 Note that some distributions enable 49 Note that some distributions enable it in startup scripts.
51 For details about rp_filter strict a 50 For details about rp_filter strict and loose mode read
52 <file:Documentation/networking/ip-sy !! 51 <file:Documentation/networking/ip-sysctl.txt>.
53 52
54 If unsure, say N here. 53 If unsure, say N here.
55 54
56 config IP_FIB_TRIE_STATS 55 config IP_FIB_TRIE_STATS
57 bool "FIB TRIE statistics" 56 bool "FIB TRIE statistics"
58 depends on IP_ADVANCED_ROUTER 57 depends on IP_ADVANCED_ROUTER
59 help !! 58 ---help---
60 Keep track of statistics on structur 59 Keep track of statistics on structure of FIB TRIE table.
61 Useful for testing and measuring TRI 60 Useful for testing and measuring TRIE performance.
62 61
63 config IP_MULTIPLE_TABLES 62 config IP_MULTIPLE_TABLES
64 bool "IP: policy routing" 63 bool "IP: policy routing"
65 depends on IP_ADVANCED_ROUTER 64 depends on IP_ADVANCED_ROUTER
66 select FIB_RULES 65 select FIB_RULES
67 help !! 66 ---help---
68 Normally, a router decides what to d 67 Normally, a router decides what to do with a received packet based
69 solely on the packet's final destina 68 solely on the packet's final destination address. If you say Y here,
70 the Linux router will also be able t 69 the Linux router will also be able to take the packet's source
71 address into account. Furthermore, t 70 address into account. Furthermore, the TOS (Type-Of-Service) field
72 of the packet can be used for routin 71 of the packet can be used for routing decisions as well.
73 72
74 If you need more information, see th 73 If you need more information, see the Linux Advanced
75 Routing and Traffic Control document 74 Routing and Traffic Control documentation at
76 <https://lartc.org/howto/lartc.rpdb. !! 75 <http://lartc.org/howto/lartc.rpdb.html>
77 76
78 If unsure, say N. 77 If unsure, say N.
79 78
80 config IP_ROUTE_MULTIPATH 79 config IP_ROUTE_MULTIPATH
81 bool "IP: equal cost multipath" 80 bool "IP: equal cost multipath"
82 depends on IP_ADVANCED_ROUTER 81 depends on IP_ADVANCED_ROUTER
83 help 82 help
84 Normally, the routing tables specify 83 Normally, the routing tables specify a single action to be taken in
85 a deterministic manner for a given p 84 a deterministic manner for a given packet. If you say Y here
86 however, it becomes possible to atta 85 however, it becomes possible to attach several actions to a packet
87 pattern, in effect specifying severa 86 pattern, in effect specifying several alternative paths to travel
88 for those packets. The router consid 87 for those packets. The router considers all these paths to be of
89 equal "cost" and chooses one of them 88 equal "cost" and chooses one of them in a non-deterministic fashion
90 if a matching packet arrives. 89 if a matching packet arrives.
91 90
92 config IP_ROUTE_VERBOSE 91 config IP_ROUTE_VERBOSE
93 bool "IP: verbose route monitoring" 92 bool "IP: verbose route monitoring"
94 depends on IP_ADVANCED_ROUTER 93 depends on IP_ADVANCED_ROUTER
95 help 94 help
96 If you say Y here, which is recommen 95 If you say Y here, which is recommended, then the kernel will print
97 verbose messages regarding the routi 96 verbose messages regarding the routing, for example warnings about
98 received packets which look strange 97 received packets which look strange and could be evidence of an
99 attack or a misconfigured system som 98 attack or a misconfigured system somewhere. The information is
100 handled by the klogd daemon which is 99 handled by the klogd daemon which is responsible for kernel messages
101 ("man klogd"). 100 ("man klogd").
102 101
103 config IP_ROUTE_CLASSID 102 config IP_ROUTE_CLASSID
104 bool 103 bool
105 104
106 config IP_PNP 105 config IP_PNP
107 bool "IP: kernel level autoconfigurati 106 bool "IP: kernel level autoconfiguration"
108 help 107 help
109 This enables automatic configuration 108 This enables automatic configuration of IP addresses of devices and
110 of the routing table during kernel b 109 of the routing table during kernel boot, based on either information
111 supplied on the kernel command line 110 supplied on the kernel command line or by BOOTP or RARP protocols.
112 You need to say Y only for diskless 111 You need to say Y only for diskless machines requiring network
113 access to boot (in which case you wa 112 access to boot (in which case you want to say Y to "Root file system
114 on NFS" as well), because all other 113 on NFS" as well), because all other machines configure the network
115 in their startup scripts. 114 in their startup scripts.
116 115
117 config IP_PNP_DHCP 116 config IP_PNP_DHCP
118 bool "IP: DHCP support" 117 bool "IP: DHCP support"
119 depends on IP_PNP 118 depends on IP_PNP
120 help !! 119 ---help---
121 If you want your Linux box to mount 120 If you want your Linux box to mount its whole root file system (the
122 one containing the directory /) from 121 one containing the directory /) from some other computer over the
123 net via NFS and you want the IP addr 122 net via NFS and you want the IP address of your computer to be
124 discovered automatically at boot tim 123 discovered automatically at boot time using the DHCP protocol (a
125 special protocol designed for doing 124 special protocol designed for doing this job), say Y here. In case
126 the boot ROM of your network card wa 125 the boot ROM of your network card was designed for booting Linux and
127 does DHCP itself, providing all nece 126 does DHCP itself, providing all necessary information on the kernel
128 command line, you can say N here. 127 command line, you can say N here.
129 128
130 If unsure, say Y. Note that if you w 129 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
131 must be operating on your network. 130 must be operating on your network. Read
132 <file:Documentation/admin-guide/nfs/ !! 131 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
133 132
134 config IP_PNP_BOOTP 133 config IP_PNP_BOOTP
135 bool "IP: BOOTP support" 134 bool "IP: BOOTP support"
136 depends on IP_PNP 135 depends on IP_PNP
137 help !! 136 ---help---
138 If you want your Linux box to mount 137 If you want your Linux box to mount its whole root file system (the
139 one containing the directory /) from 138 one containing the directory /) from some other computer over the
140 net via NFS and you want the IP addr 139 net via NFS and you want the IP address of your computer to be
141 discovered automatically at boot tim 140 discovered automatically at boot time using the BOOTP protocol (a
142 special protocol designed for doing 141 special protocol designed for doing this job), say Y here. In case
143 the boot ROM of your network card wa 142 the boot ROM of your network card was designed for booting Linux and
144 does BOOTP itself, providing all nec 143 does BOOTP itself, providing all necessary information on the kernel
145 command line, you can say N here. If 144 command line, you can say N here. If unsure, say Y. Note that if you
146 want to use BOOTP, a BOOTP server mu 145 want to use BOOTP, a BOOTP server must be operating on your network.
147 Read <file:Documentation/admin-guide !! 146 Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
148 147
149 config IP_PNP_RARP 148 config IP_PNP_RARP
150 bool "IP: RARP support" 149 bool "IP: RARP support"
151 depends on IP_PNP 150 depends on IP_PNP
152 help 151 help
153 If you want your Linux box to mount 152 If you want your Linux box to mount its whole root file system (the
154 one containing the directory /) from 153 one containing the directory /) from some other computer over the
155 net via NFS and you want the IP addr 154 net via NFS and you want the IP address of your computer to be
156 discovered automatically at boot tim 155 discovered automatically at boot time using the RARP protocol (an
157 older protocol which is being obsole 156 older protocol which is being obsoleted by BOOTP and DHCP), say Y
158 here. Note that if you want to use R 157 here. Note that if you want to use RARP, a RARP server must be
159 operating on your network. Read 158 operating on your network. Read
160 <file:Documentation/admin-guide/nfs/ !! 159 <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
161 160
162 config NET_IPIP 161 config NET_IPIP
163 tristate "IP: tunneling" 162 tristate "IP: tunneling"
164 select INET_TUNNEL 163 select INET_TUNNEL
165 select NET_IP_TUNNEL 164 select NET_IP_TUNNEL
166 help !! 165 ---help---
167 Tunneling means encapsulating data o 166 Tunneling means encapsulating data of one protocol type within
168 another protocol and sending it over 167 another protocol and sending it over a channel that understands the
169 encapsulating protocol. This particu 168 encapsulating protocol. This particular tunneling driver implements
170 encapsulation of IP within IP, which 169 encapsulation of IP within IP, which sounds kind of pointless, but
171 can be useful if you want to make yo 170 can be useful if you want to make your (or some other) machine
172 appear on a different network than i 171 appear on a different network than it physically is, or to use
173 mobile-IP facilities (allowing lapto 172 mobile-IP facilities (allowing laptops to seamlessly move between
174 networks without changing their IP a 173 networks without changing their IP addresses).
175 174
176 Saying Y to this option will produce 175 Saying Y to this option will produce two modules ( = code which can
177 be inserted in and removed from the 176 be inserted in and removed from the running kernel whenever you
178 want). Most people won't need this a 177 want). Most people won't need this and can say N.
179 178
180 config NET_IPGRE_DEMUX 179 config NET_IPGRE_DEMUX
181 tristate "IP: GRE demultiplexer" 180 tristate "IP: GRE demultiplexer"
182 help 181 help
183 This is helper module to demultiplex !! 182 This is helper module to demultiplex GRE packets on GRE version field criteria.
184 Required by ip_gre and pptp modules. !! 183 Required by ip_gre and pptp modules.
185 184
186 config NET_IP_TUNNEL 185 config NET_IP_TUNNEL
187 tristate 186 tristate
188 select DST_CACHE 187 select DST_CACHE
189 select GRO_CELLS 188 select GRO_CELLS
190 default n 189 default n
191 190
192 config NET_IPGRE 191 config NET_IPGRE
193 tristate "IP: GRE tunnels over IP" 192 tristate "IP: GRE tunnels over IP"
194 depends on (IPV6 || IPV6=n) && NET_IPG 193 depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
195 select NET_IP_TUNNEL 194 select NET_IP_TUNNEL
196 help 195 help
197 Tunneling means encapsulating data o 196 Tunneling means encapsulating data of one protocol type within
198 another protocol and sending it over 197 another protocol and sending it over a channel that understands the
199 encapsulating protocol. This particu 198 encapsulating protocol. This particular tunneling driver implements
200 GRE (Generic Routing Encapsulation) 199 GRE (Generic Routing Encapsulation) and at this time allows
201 encapsulating of IPv4 or IPv6 over e 200 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
202 This driver is useful if the other e 201 This driver is useful if the other endpoint is a Cisco router: Cisco
203 likes GRE much better than the other 202 likes GRE much better than the other Linux tunneling driver ("IP
204 tunneling" above). In addition, GRE 203 tunneling" above). In addition, GRE allows multicast redistribution
205 through the tunnel. 204 through the tunnel.
206 205
207 config NET_IPGRE_BROADCAST 206 config NET_IPGRE_BROADCAST
208 bool "IP: broadcast GRE over IP" 207 bool "IP: broadcast GRE over IP"
209 depends on IP_MULTICAST && NET_IPGRE 208 depends on IP_MULTICAST && NET_IPGRE
210 help 209 help
211 One application of GRE/IP is to cons 210 One application of GRE/IP is to construct a broadcast WAN (Wide Area
212 Network), which looks like a normal 211 Network), which looks like a normal Ethernet LAN (Local Area
213 Network), but can be distributed all 212 Network), but can be distributed all over the Internet. If you want
214 to do that, say Y here and to "IP mu 213 to do that, say Y here and to "IP multicast routing" below.
215 214
216 config IP_MROUTE_COMMON 215 config IP_MROUTE_COMMON
217 bool 216 bool
218 depends on IP_MROUTE || IPV6_MROUTE 217 depends on IP_MROUTE || IPV6_MROUTE
219 218
220 config IP_MROUTE 219 config IP_MROUTE
221 bool "IP: multicast routing" 220 bool "IP: multicast routing"
222 depends on IP_MULTICAST 221 depends on IP_MULTICAST
223 select IP_MROUTE_COMMON 222 select IP_MROUTE_COMMON
224 help 223 help
225 This is used if you want your machin 224 This is used if you want your machine to act as a router for IP
226 packets that have several destinatio 225 packets that have several destination addresses. It is needed on the
227 MBONE, a high bandwidth network on t 226 MBONE, a high bandwidth network on top of the Internet which carries
228 audio and video broadcasts. In order 227 audio and video broadcasts. In order to do that, you would most
229 likely run the program mrouted. If y 228 likely run the program mrouted. If you haven't heard about it, you
230 don't need it. 229 don't need it.
231 230
232 config IP_MROUTE_MULTIPLE_TABLES 231 config IP_MROUTE_MULTIPLE_TABLES
233 bool "IP: multicast policy routing" 232 bool "IP: multicast policy routing"
234 depends on IP_MROUTE && IP_ADVANCED_RO 233 depends on IP_MROUTE && IP_ADVANCED_ROUTER
235 select FIB_RULES 234 select FIB_RULES
236 help 235 help
237 Normally, a multicast router runs a 236 Normally, a multicast router runs a userspace daemon and decides
238 what to do with a multicast packet b 237 what to do with a multicast packet based on the source and
239 destination addresses. If you say Y 238 destination addresses. If you say Y here, the multicast router
240 will also be able to take interfaces 239 will also be able to take interfaces and packet marks into
241 account and run multiple instances o 240 account and run multiple instances of userspace daemons
242 simultaneously, each one handling a 241 simultaneously, each one handling a single table.
243 242
244 If unsure, say N. 243 If unsure, say N.
245 244
246 config IP_PIMSM_V1 245 config IP_PIMSM_V1
247 bool "IP: PIM-SM version 1 support" 246 bool "IP: PIM-SM version 1 support"
248 depends on IP_MROUTE 247 depends on IP_MROUTE
249 help 248 help
250 Kernel side support for Sparse Mode 249 Kernel side support for Sparse Mode PIM (Protocol Independent
251 Multicast) version 1. This multicast 250 Multicast) version 1. This multicast routing protocol is used widely
252 because Cisco supports it. You need 251 because Cisco supports it. You need special software to use it
253 (pimd-v1). Please see <http://netweb 252 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
254 information about PIM. 253 information about PIM.
255 254
256 Say Y if you want to use PIM-SM v1. 255 Say Y if you want to use PIM-SM v1. Note that you can say N here if
257 you just want to use Dense Mode PIM. 256 you just want to use Dense Mode PIM.
258 257
259 config IP_PIMSM_V2 258 config IP_PIMSM_V2
260 bool "IP: PIM-SM version 2 support" 259 bool "IP: PIM-SM version 2 support"
261 depends on IP_MROUTE 260 depends on IP_MROUTE
262 help 261 help
263 Kernel side support for Sparse Mode 262 Kernel side support for Sparse Mode PIM version 2. In order to use
264 this, you need an experimental routi 263 this, you need an experimental routing daemon supporting it (pimd or
265 gated-5). This routing protocol is n 264 gated-5). This routing protocol is not used widely, so say N unless
266 you want to play with it. 265 you want to play with it.
267 266
268 config SYN_COOKIES 267 config SYN_COOKIES
269 bool "IP: TCP syncookie support" 268 bool "IP: TCP syncookie support"
270 help !! 269 ---help---
271 Normal TCP/IP networking is open to 270 Normal TCP/IP networking is open to an attack known as "SYN
272 flooding". This denial-of-service at 271 flooding". This denial-of-service attack prevents legitimate remote
273 users from being able to connect to 272 users from being able to connect to your computer during an ongoing
274 attack and requires very little work 273 attack and requires very little work from the attacker, who can
275 operate from anywhere on the Interne 274 operate from anywhere on the Internet.
276 275
277 SYN cookies provide protection again 276 SYN cookies provide protection against this type of attack. If you
278 say Y here, the TCP/IP stack will us 277 say Y here, the TCP/IP stack will use a cryptographic challenge
279 protocol known as "SYN cookies" to e 278 protocol known as "SYN cookies" to enable legitimate users to
280 continue to connect, even when your 279 continue to connect, even when your machine is under attack. There
281 is no need for the legitimate users 280 is no need for the legitimate users to change their TCP/IP software;
282 SYN cookies work transparently to th 281 SYN cookies work transparently to them. For technical information
283 about SYN cookies, check out <https: !! 282 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
284 283
285 If you are SYN flooded, the source a 284 If you are SYN flooded, the source address reported by the kernel is
286 likely to have been forged by the at 285 likely to have been forged by the attacker; it is only reported as
287 an aid in tracing the packets to the 286 an aid in tracing the packets to their actual source and should not
288 be taken as absolute truth. 287 be taken as absolute truth.
289 288
290 SYN cookies may prevent correct erro 289 SYN cookies may prevent correct error reporting on clients when the
291 server is really overloaded. If this 290 server is really overloaded. If this happens frequently better turn
292 them off. 291 them off.
293 292
294 If you say Y here, you can disable S 293 If you say Y here, you can disable SYN cookies at run time by
295 saying Y to "/proc file system suppo 294 saying Y to "/proc file system support" and
296 "Sysctl support" below and executing 295 "Sysctl support" below and executing the command
297 296
298 echo 0 > /proc/sys/net/ipv4/tcp_sync 297 echo 0 > /proc/sys/net/ipv4/tcp_syncookies
299 298
300 after the /proc file system has been 299 after the /proc file system has been mounted.
301 300
302 If unsure, say N. 301 If unsure, say N.
303 302
304 config NET_IPVTI 303 config NET_IPVTI
305 tristate "Virtual (secure) IP: tunneli 304 tristate "Virtual (secure) IP: tunneling"
306 depends on IPV6 || IPV6=n <<
307 select INET_TUNNEL 305 select INET_TUNNEL
308 select NET_IP_TUNNEL 306 select NET_IP_TUNNEL
309 select XFRM !! 307 depends on INET_XFRM_MODE_TUNNEL
310 help !! 308 ---help---
311 Tunneling means encapsulating data o 309 Tunneling means encapsulating data of one protocol type within
312 another protocol and sending it over 310 another protocol and sending it over a channel that understands the
313 encapsulating protocol. This can be 311 encapsulating protocol. This can be used with xfrm mode tunnel to give
314 the notion of a secure tunnel for IP 312 the notion of a secure tunnel for IPSEC and then use routing protocol
315 on top. 313 on top.
316 314
317 config NET_UDP_TUNNEL 315 config NET_UDP_TUNNEL
318 tristate 316 tristate
319 select NET_IP_TUNNEL 317 select NET_IP_TUNNEL
320 default n 318 default n
321 319
322 config NET_FOU 320 config NET_FOU
323 tristate "IP: Foo (IP protocols) over 321 tristate "IP: Foo (IP protocols) over UDP"
>> 322 select XFRM
324 select NET_UDP_TUNNEL 323 select NET_UDP_TUNNEL
325 help !! 324 ---help---
326 Foo over UDP allows any IP protocol 325 Foo over UDP allows any IP protocol to be directly encapsulated
327 over UDP include tunnels (IPIP, GRE, 326 over UDP include tunnels (IPIP, GRE, SIT). By encapsulating in UDP
328 network mechanisms and optimizations 327 network mechanisms and optimizations for UDP (such as ECMP
329 and RSS) can be leveraged to provide 328 and RSS) can be leveraged to provide better service.
330 329
331 config NET_FOU_IP_TUNNELS 330 config NET_FOU_IP_TUNNELS
332 bool "IP: FOU encapsulation of IP tunn 331 bool "IP: FOU encapsulation of IP tunnels"
333 depends on NET_IPIP || NET_IPGRE || IP 332 depends on NET_IPIP || NET_IPGRE || IPV6_SIT
334 select NET_FOU 333 select NET_FOU
335 help !! 334 ---help---
336 Allow configuration of FOU or GUE en 335 Allow configuration of FOU or GUE encapsulation for IP tunnels.
337 When this option is enabled IP tunne 336 When this option is enabled IP tunnels can be configured to use
338 FOU or GUE encapsulation. 337 FOU or GUE encapsulation.
339 338
340 config INET_AH 339 config INET_AH
341 tristate "IP: AH transformation" 340 tristate "IP: AH transformation"
342 select XFRM_AH !! 341 select XFRM_ALGO
343 help !! 342 select CRYPTO
344 Support for IPsec AH (Authentication !! 343 select CRYPTO_HMAC
345 !! 344 select CRYPTO_MD5
346 AH can be used with various authenti !! 345 select CRYPTO_SHA1
347 enabling AH support itself, this opt !! 346 ---help---
348 implementations of the algorithms th !! 347 Support for IPsec AH.
349 implemented. If you need any other <<
350 them in the crypto API. You should <<
351 implementations of any needed algori <<
352 348
353 If unsure, say Y. 349 If unsure, say Y.
354 350
355 config INET_ESP 351 config INET_ESP
356 tristate "IP: ESP transformation" 352 tristate "IP: ESP transformation"
357 select XFRM_ESP !! 353 select XFRM_ALGO
358 help !! 354 select CRYPTO
359 Support for IPsec ESP (Encapsulating !! 355 select CRYPTO_AUTHENC
360 !! 356 select CRYPTO_HMAC
361 ESP can be used with various encrypt !! 357 select CRYPTO_MD5
362 Besides enabling ESP support itself, !! 358 select CRYPTO_CBC
363 implementations of the algorithms th !! 359 select CRYPTO_SHA1
364 implemented. If you need any other !! 360 select CRYPTO_DES
365 them in the crypto API. You should !! 361 select CRYPTO_ECHAINIV
366 implementations of any needed algori !! 362 ---help---
>> 363 Support for IPsec ESP.
367 364
368 If unsure, say Y. 365 If unsure, say Y.
369 366
370 config INET_ESP_OFFLOAD 367 config INET_ESP_OFFLOAD
371 tristate "IP: ESP transformation offlo 368 tristate "IP: ESP transformation offload"
372 depends on INET_ESP 369 depends on INET_ESP
373 select XFRM_OFFLOAD 370 select XFRM_OFFLOAD
374 default n 371 default n
375 help !! 372 ---help---
376 Support for ESP transformation offlo 373 Support for ESP transformation offload. This makes sense
377 only if this system really does IPse 374 only if this system really does IPsec and want to do it
378 with high throughput. A typical desk 375 with high throughput. A typical desktop system does not
379 need it, even if it does IPsec. 376 need it, even if it does IPsec.
380 377
381 If unsure, say N. 378 If unsure, say N.
382 379
383 config INET_ESPINTCP <<
384 bool "IP: ESP in TCP encapsulation (RF <<
385 depends on XFRM && INET_ESP <<
386 select STREAM_PARSER <<
387 select NET_SOCK_MSG <<
388 select XFRM_ESPINTCP <<
389 help <<
390 Support for RFC 8229 encapsulation o <<
391 TCP/IPv4 sockets. <<
392 <<
393 If unsure, say N. <<
394 <<
395 config INET_IPCOMP 380 config INET_IPCOMP
396 tristate "IP: IPComp transformation" 381 tristate "IP: IPComp transformation"
397 select INET_XFRM_TUNNEL 382 select INET_XFRM_TUNNEL
398 select XFRM_IPCOMP 383 select XFRM_IPCOMP
399 help !! 384 ---help---
400 Support for IP Payload Compression P 385 Support for IP Payload Compression Protocol (IPComp) (RFC3173),
401 typically needed for IPsec. 386 typically needed for IPsec.
402 387
403 If unsure, say Y. 388 If unsure, say Y.
404 389
405 config INET_TABLE_PERTURB_ORDER <<
406 int "INET: Source port perturbation ta <<
407 default 16 <<
408 help <<
409 Source port perturbation table size <<
410 RFC 6056 3.3.4. Algorithm 4: Double <<
411 <<
412 The default is almost always what yo <<
413 Only change this if you know what yo <<
414 <<
415 config INET_XFRM_TUNNEL 390 config INET_XFRM_TUNNEL
416 tristate 391 tristate
417 select INET_TUNNEL 392 select INET_TUNNEL
418 default n 393 default n
419 394
420 config INET_TUNNEL 395 config INET_TUNNEL
421 tristate 396 tristate
422 default n 397 default n
423 398
>> 399 config INET_XFRM_MODE_TRANSPORT
>> 400 tristate "IP: IPsec transport mode"
>> 401 default y
>> 402 select XFRM
>> 403 ---help---
>> 404 Support for IPsec transport mode.
>> 405
>> 406 If unsure, say Y.
>> 407
>> 408 config INET_XFRM_MODE_TUNNEL
>> 409 tristate "IP: IPsec tunnel mode"
>> 410 default y
>> 411 select XFRM
>> 412 ---help---
>> 413 Support for IPsec tunnel mode.
>> 414
>> 415 If unsure, say Y.
>> 416
>> 417 config INET_XFRM_MODE_BEET
>> 418 tristate "IP: IPsec BEET mode"
>> 419 default y
>> 420 select XFRM
>> 421 ---help---
>> 422 Support for IPsec BEET mode.
>> 423
>> 424 If unsure, say Y.
>> 425
424 config INET_DIAG 426 config INET_DIAG
425 tristate "INET: socket monitoring inte 427 tristate "INET: socket monitoring interface"
426 default y 428 default y
427 help !! 429 ---help---
428 Support for INET (TCP, DCCP, etc) so 430 Support for INET (TCP, DCCP, etc) socket monitoring interface used by
429 native Linux tools such as ss. ss is 431 native Linux tools such as ss. ss is included in iproute2, currently
430 downloadable at: 432 downloadable at:
431 433
432 http://www.linuxfoundation.org/col 434 http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
433 435
434 If unsure, say Y. 436 If unsure, say Y.
435 437
436 config INET_TCP_DIAG 438 config INET_TCP_DIAG
437 depends on INET_DIAG 439 depends on INET_DIAG
438 def_tristate INET_DIAG 440 def_tristate INET_DIAG
439 441
440 config INET_UDP_DIAG 442 config INET_UDP_DIAG
441 tristate "UDP: socket monitoring inter 443 tristate "UDP: socket monitoring interface"
442 depends on INET_DIAG && (IPV6 || IPV6= 444 depends on INET_DIAG && (IPV6 || IPV6=n)
443 default n 445 default n
444 help !! 446 ---help---
445 Support for UDP socket monitoring in 447 Support for UDP socket monitoring interface used by the ss tool.
446 If unsure, say Y. 448 If unsure, say Y.
447 449
448 config INET_RAW_DIAG 450 config INET_RAW_DIAG
449 tristate "RAW: socket monitoring inter 451 tristate "RAW: socket monitoring interface"
450 depends on INET_DIAG && (IPV6 || IPV6= 452 depends on INET_DIAG && (IPV6 || IPV6=n)
451 default n 453 default n
452 help !! 454 ---help---
453 Support for RAW socket monitoring in 455 Support for RAW socket monitoring interface used by the ss tool.
454 If unsure, say Y. 456 If unsure, say Y.
455 457
456 config INET_DIAG_DESTROY 458 config INET_DIAG_DESTROY
457 bool "INET: allow privileged process t 459 bool "INET: allow privileged process to administratively close sockets"
458 depends on INET_DIAG 460 depends on INET_DIAG
459 default n 461 default n
460 help !! 462 ---help---
461 Provides a SOCK_DESTROY operation th 463 Provides a SOCK_DESTROY operation that allows privileged processes
462 (e.g., a connection manager or a net 464 (e.g., a connection manager or a network administration tool such as
463 ss) to close sockets opened by other 465 ss) to close sockets opened by other processes. Closing a socket in
464 this way interrupts any blocking rea 466 this way interrupts any blocking read/write/connect operations on
465 the socket and causes future socket 467 the socket and causes future socket calls to behave as if the socket
466 had been disconnected. 468 had been disconnected.
467 If unsure, say N. 469 If unsure, say N.
468 470
469 menuconfig TCP_CONG_ADVANCED 471 menuconfig TCP_CONG_ADVANCED
470 bool "TCP: advanced congestion control 472 bool "TCP: advanced congestion control"
471 help !! 473 ---help---
472 Support for selection of various TCP 474 Support for selection of various TCP congestion control
473 modules. 475 modules.
474 476
475 Nearly all users can safely say no h 477 Nearly all users can safely say no here, and a safe default
476 selection will be made (CUBIC with n 478 selection will be made (CUBIC with new Reno as a fallback).
477 479
478 If unsure, say N. 480 If unsure, say N.
479 481
480 if TCP_CONG_ADVANCED 482 if TCP_CONG_ADVANCED
481 483
482 config TCP_CONG_BIC 484 config TCP_CONG_BIC
483 tristate "Binary Increase Congestion ( 485 tristate "Binary Increase Congestion (BIC) control"
484 default m 486 default m
485 help !! 487 ---help---
486 BIC-TCP is a sender-side only change !! 488 BIC-TCP is a sender-side only change that ensures a linear RTT
487 fairness under large windows while o !! 489 fairness under large windows while offering both scalability and
488 bounded TCP-friendliness. The protoc !! 490 bounded TCP-friendliness. The protocol combines two schemes
489 called additive increase and binary !! 491 called additive increase and binary search increase. When the
490 congestion window is large, additive !! 492 congestion window is large, additive increase with a large
491 increment ensures linear RTT fairnes !! 493 increment ensures linear RTT fairness as well as good
492 scalability. Under small congestion !! 494 scalability. Under small congestion windows, binary search
493 increase provides TCP friendliness. !! 495 increase provides TCP friendliness.
494 See http://www.csc.ncsu.edu/faculty/ !! 496 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
495 497
496 config TCP_CONG_CUBIC 498 config TCP_CONG_CUBIC
497 tristate "CUBIC TCP" 499 tristate "CUBIC TCP"
498 default y 500 default y
499 help !! 501 ---help---
500 This is version 2.0 of BIC-TCP which !! 502 This is version 2.0 of BIC-TCP which uses a cubic growth function
501 among other techniques. !! 503 among other techniques.
502 See http://www.csc.ncsu.edu/faculty/ !! 504 See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
503 505
504 config TCP_CONG_WESTWOOD 506 config TCP_CONG_WESTWOOD
505 tristate "TCP Westwood+" 507 tristate "TCP Westwood+"
506 default m 508 default m
507 help !! 509 ---help---
508 TCP Westwood+ is a sender-side only !! 510 TCP Westwood+ is a sender-side only modification of the TCP Reno
509 protocol stack that optimizes the pe !! 511 protocol stack that optimizes the performance of TCP congestion
510 control. It is based on end-to-end b !! 512 control. It is based on end-to-end bandwidth estimation to set
511 congestion window and slow start thr !! 513 congestion window and slow start threshold after a congestion
512 episode. Using this estimation, TCP !! 514 episode. Using this estimation, TCP Westwood+ adaptively sets a
513 slow start threshold and a congestio !! 515 slow start threshold and a congestion window which takes into
514 account the bandwidth used at the t !! 516 account the bandwidth used at the time congestion is experienced.
515 TCP Westwood+ significantly increase !! 517 TCP Westwood+ significantly increases fairness wrt TCP Reno in
516 wired networks and throughput over w !! 518 wired networks and throughput over wireless links.
517 519
518 config TCP_CONG_HTCP 520 config TCP_CONG_HTCP
519 tristate "H-TCP" !! 521 tristate "H-TCP"
520 default m !! 522 default m
521 help !! 523 ---help---
522 H-TCP is a send-side only modificati !! 524 H-TCP is a send-side only modifications of the TCP Reno
523 protocol stack that optimizes the pe !! 525 protocol stack that optimizes the performance of TCP
524 congestion control for high speed ne !! 526 congestion control for high speed network links. It uses a
525 modeswitch to change the alpha and b !! 527 modeswitch to change the alpha and beta parameters of TCP Reno
526 based on network conditions and in a !! 528 based on network conditions and in a way so as to be fair with
527 other Reno and H-TCP flows. !! 529 other Reno and H-TCP flows.
528 530
529 config TCP_CONG_HSTCP 531 config TCP_CONG_HSTCP
530 tristate "High Speed TCP" 532 tristate "High Speed TCP"
531 default n 533 default n
532 help !! 534 ---help---
533 Sally Floyd's High Speed TCP (RFC 36 !! 535 Sally Floyd's High Speed TCP (RFC 3649) congestion control.
534 A modification to TCP's congestion c !! 536 A modification to TCP's congestion control mechanism for use
535 with large congestion windows. A tab !! 537 with large congestion windows. A table indicates how much to
536 increase the congestion window by wh !! 538 increase the congestion window by when an ACK is received.
537 For more detail see https://www.icir !! 539 For more detail see http://www.icir.org/floyd/hstcp.html
538 540
539 config TCP_CONG_HYBLA 541 config TCP_CONG_HYBLA
540 tristate "TCP-Hybla congestion control 542 tristate "TCP-Hybla congestion control algorithm"
541 default n 543 default n
542 help !! 544 ---help---
543 TCP-Hybla is a sender-side only chan !! 545 TCP-Hybla is a sender-side only change that eliminates penalization of
544 long-RTT, large-bandwidth connection !! 546 long-RTT, large-bandwidth connections, like when satellite legs are
545 involved, especially when sharing a !! 547 involved, especially when sharing a common bottleneck with normal
546 terrestrial connections. !! 548 terrestrial connections.
547 549
548 config TCP_CONG_VEGAS 550 config TCP_CONG_VEGAS
549 tristate "TCP Vegas" 551 tristate "TCP Vegas"
550 default n 552 default n
551 help !! 553 ---help---
552 TCP Vegas is a sender-side only chan !! 554 TCP Vegas is a sender-side only change to TCP that anticipates
553 the onset of congestion by estimatin !! 555 the onset of congestion by estimating the bandwidth. TCP Vegas
554 adjusts the sending rate by modifyin !! 556 adjusts the sending rate by modifying the congestion
555 window. TCP Vegas should provide les !! 557 window. TCP Vegas should provide less packet loss, but it is
556 not as aggressive as TCP Reno. !! 558 not as aggressive as TCP Reno.
557 559
558 config TCP_CONG_NV 560 config TCP_CONG_NV
559 tristate "TCP NV" !! 561 tristate "TCP NV"
560 default n !! 562 default n
561 help !! 563 ---help---
562 TCP NV is a follow up to TCP Vegas. !! 564 TCP NV is a follow up to TCP Vegas. It has been modified to deal with
563 10G networks, measurement noise intr !! 565 10G networks, measurement noise introduced by LRO, GRO and interrupt
564 coalescence. In addition, it will de !! 566 coalescence. In addition, it will decrease its cwnd multiplicatively
565 instead of linearly. !! 567 instead of linearly.
566 !! 568
567 Note that in general congestion avoi !! 569 Note that in general congestion avoidance (cwnd decreased when # packets
568 queued grows) cannot coexist with co !! 570 queued grows) cannot coexist with congestion control (cwnd decreased only
569 when there is packet loss) due to fa !! 571 when there is packet loss) due to fairness issues. One scenario when they
570 can coexist safely is when the CA fl !! 572 can coexist safely is when the CA flows have RTTs << CC flows RTTs.
571 573
572 For further details see http://www.b !! 574 For further details see http://www.brakmo.org/networking/tcp-nv/
573 575
574 config TCP_CONG_SCALABLE 576 config TCP_CONG_SCALABLE
575 tristate "Scalable TCP" 577 tristate "Scalable TCP"
576 default n 578 default n
577 help !! 579 ---help---
578 Scalable TCP is a sender-side only c !! 580 Scalable TCP is a sender-side only change to TCP which uses a
579 MIMD congestion control algorithm wh !! 581 MIMD congestion control algorithm which has some nice scaling
580 properties, though is known to have !! 582 properties, though is known to have fairness issues.
581 See http://www.deneholme.net/tom/sca !! 583 See http://www.deneholme.net/tom/scalable/
582 584
583 config TCP_CONG_LP 585 config TCP_CONG_LP
584 tristate "TCP Low Priority" 586 tristate "TCP Low Priority"
585 default n 587 default n
586 help !! 588 ---help---
587 TCP Low Priority (TCP-LP), a distrib !! 589 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
588 to utilize only the excess network b !! 590 to utilize only the excess network bandwidth as compared to the
589 ``fair share`` of bandwidth as targe !! 591 ``fair share`` of bandwidth as targeted by TCP.
590 See http://www-ece.rice.edu/networks !! 592 See http://www-ece.rice.edu/networks/TCP-LP/
591 593
592 config TCP_CONG_VENO 594 config TCP_CONG_VENO
593 tristate "TCP Veno" 595 tristate "TCP Veno"
594 default n 596 default n
595 help !! 597 ---help---
596 TCP Veno is a sender-side only enhan !! 598 TCP Veno is a sender-side only enhancement of TCP to obtain better
597 throughput over wireless networks. T !! 599 throughput over wireless networks. TCP Veno makes use of state
598 distinguishing to circumvent the dif !! 600 distinguishing to circumvent the difficult judgment of the packet loss
599 type. TCP Veno cuts down less conges !! 601 type. TCP Veno cuts down less congestion window in response to random
600 loss packets. !! 602 loss packets.
601 See <http://ieeexplore.ieee.org/xpl/ !! 603 See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
602 604
603 config TCP_CONG_YEAH 605 config TCP_CONG_YEAH
604 tristate "YeAH TCP" 606 tristate "YeAH TCP"
605 select TCP_CONG_VEGAS 607 select TCP_CONG_VEGAS
606 default n 608 default n
607 help !! 609 ---help---
608 YeAH-TCP is a sender-side high-speed !! 610 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
609 algorithm, which uses a mixed loss/d !! 611 algorithm, which uses a mixed loss/delay approach to compute the
610 congestion window. It's design goals !! 612 congestion window. It's design goals target high efficiency,
611 internal, RTT and Reno fairness, res !! 613 internal, RTT and Reno fairness, resilience to link loss while
612 keeping network elements load as low !! 614 keeping network elements load as low as possible.
613 615
614 For further details look here: !! 616 For further details look here:
615 http://wil.cs.caltech.edu/pfldnet2 !! 617 http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
616 618
617 config TCP_CONG_ILLINOIS 619 config TCP_CONG_ILLINOIS
618 tristate "TCP Illinois" 620 tristate "TCP Illinois"
619 default n 621 default n
620 help !! 622 ---help---
621 TCP-Illinois is a sender-side modifi !! 623 TCP-Illinois is a sender-side modification of TCP Reno for
622 high speed long delay links. It uses !! 624 high speed long delay links. It uses round-trip-time to
623 adjust the alpha and beta parameters !! 625 adjust the alpha and beta parameters to achieve a higher average
624 throughput and maintain fairness. !! 626 throughput and maintain fairness.
625 627
626 For further details see: !! 628 For further details see:
627 http://www.ews.uiuc.edu/~shaoliu/t !! 629 http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
628 630
629 config TCP_CONG_DCTCP 631 config TCP_CONG_DCTCP
630 tristate "DataCenter TCP (DCTCP)" 632 tristate "DataCenter TCP (DCTCP)"
631 default n 633 default n
632 help !! 634 ---help---
633 DCTCP leverages Explicit Congestion !! 635 DCTCP leverages Explicit Congestion Notification (ECN) in the network to
634 provide multi-bit feedback to the en !! 636 provide multi-bit feedback to the end hosts. It is designed to provide:
>> 637
>> 638 - High burst tolerance (incast due to partition/aggregate),
>> 639 - Low latency (short flows, queries),
>> 640 - High throughput (continuous data updates, large file transfers) with
>> 641 commodity, shallow-buffered switches.
>> 642
>> 643 All switches in the data center network running DCTCP must support
>> 644 ECN marking and be configured for marking when reaching defined switch
>> 645 buffer thresholds. The default ECN marking threshold heuristic for
>> 646 DCTCP on switches is 20 packets (30KB) at 1Gbps, and 65 packets
>> 647 (~100KB) at 10Gbps, but might need further careful tweaking.
635 648
636 - High burst tolerance (incast due t !! 649 For further details see:
637 - Low latency (short flows, queries) !! 650 http://simula.stanford.edu/~alizade/Site/DCTCP_files/dctcp-final.pdf
638 - High throughput (continuous data u <<
639 commodity, shallow-buffered switch <<
640 <<
641 All switches in the data center netw <<
642 ECN marking and be configured for ma <<
643 buffer thresholds. The default ECN m <<
644 DCTCP on switches is 20 packets (30K <<
645 (~100KB) at 10Gbps, but might need f <<
646 <<
647 For further details see: <<
648 http://simula.stanford.edu/~alizad <<
649 651
650 config TCP_CONG_CDG 652 config TCP_CONG_CDG
651 tristate "CAIA Delay-Gradient (CDG)" 653 tristate "CAIA Delay-Gradient (CDG)"
652 default n 654 default n
653 help !! 655 ---help---
654 CAIA Delay-Gradient (CDG) is a TCP c !! 656 CAIA Delay-Gradient (CDG) is a TCP congestion control that modifies
655 the TCP sender in order to: !! 657 the TCP sender in order to:
656 658
657 o Use the delay gradient as a conges 659 o Use the delay gradient as a congestion signal.
658 o Back off with an average probabili 660 o Back off with an average probability that is independent of the RTT.
659 o Coexist with flows that use loss-b 661 o Coexist with flows that use loss-based congestion control.
660 o Tolerate packet loss unrelated to 662 o Tolerate packet loss unrelated to congestion.
661 663
662 For further details see: !! 664 For further details see:
663 D.A. Hayes and G. Armitage. "Revis !! 665 D.A. Hayes and G. Armitage. "Revisiting TCP congestion control using
664 delay gradients." In Networking 20 !! 666 delay gradients." In Networking 2011. Preprint: http://goo.gl/No3vdg
665 http://caia.swin.edu.au/cv/dahayes <<
666 667
667 config TCP_CONG_BBR 668 config TCP_CONG_BBR
668 tristate "BBR TCP" 669 tristate "BBR TCP"
669 default n 670 default n
670 help !! 671 ---help---
671 672
672 BBR (Bottleneck Bandwidth and RTT) T !! 673 BBR (Bottleneck Bandwidth and RTT) TCP congestion control aims to
673 maximize network utilization and min !! 674 maximize network utilization and minimize queues. It builds an explicit
674 model of the bottleneck delivery rat !! 675 model of the the bottleneck delivery rate and path round-trip
675 delay. It tolerates packet loss and !! 676 propagation delay. It tolerates packet loss and delay unrelated to
676 can operate over LAN, WAN, cellular, !! 677 congestion. It can operate over LAN, WAN, cellular, wifi, or cable
677 coexist with flows that use loss-bas !! 678 modem links. It can coexist with flows that use loss-based congestion
678 operate with shallow buffers, deep b !! 679 control, and can operate with shallow buffers, deep buffers,
679 AQM schemes that do not provide a de !! 680 bufferbloat, policers, or AQM schemes that do not provide a delay
680 ("Fair Queue") pacing packet schedul !! 681 signal. It requires the fq ("Fair Queue") pacing packet scheduler.
681 682
682 choice 683 choice
683 prompt "Default TCP congestion control 684 prompt "Default TCP congestion control"
684 default DEFAULT_CUBIC 685 default DEFAULT_CUBIC
685 help 686 help
686 Select the TCP congestion control th 687 Select the TCP congestion control that will be used by default
687 for all connections. 688 for all connections.
688 689
689 config DEFAULT_BIC 690 config DEFAULT_BIC
690 bool "Bic" if TCP_CONG_BIC=y 691 bool "Bic" if TCP_CONG_BIC=y
691 692
692 config DEFAULT_CUBIC 693 config DEFAULT_CUBIC
693 bool "Cubic" if TCP_CONG_CUBIC 694 bool "Cubic" if TCP_CONG_CUBIC=y
694 695
695 config DEFAULT_HTCP 696 config DEFAULT_HTCP
696 bool "Htcp" if TCP_CONG_HTCP=y 697 bool "Htcp" if TCP_CONG_HTCP=y
697 698
698 config DEFAULT_HYBLA 699 config DEFAULT_HYBLA
699 bool "Hybla" if TCP_CONG_HYBLA 700 bool "Hybla" if TCP_CONG_HYBLA=y
700 701
701 config DEFAULT_VEGAS 702 config DEFAULT_VEGAS
702 bool "Vegas" if TCP_CONG_VEGAS 703 bool "Vegas" if TCP_CONG_VEGAS=y
703 704
704 config DEFAULT_VENO 705 config DEFAULT_VENO
705 bool "Veno" if TCP_CONG_VENO=y 706 bool "Veno" if TCP_CONG_VENO=y
706 707
707 config DEFAULT_WESTWOOD 708 config DEFAULT_WESTWOOD
708 bool "Westwood" if TCP_CONG_WE 709 bool "Westwood" if TCP_CONG_WESTWOOD=y
709 710
710 config DEFAULT_DCTCP 711 config DEFAULT_DCTCP
711 bool "DCTCP" if TCP_CONG_DCTCP 712 bool "DCTCP" if TCP_CONG_DCTCP=y
712 713
713 config DEFAULT_CDG 714 config DEFAULT_CDG
714 bool "CDG" if TCP_CONG_CDG=y 715 bool "CDG" if TCP_CONG_CDG=y
715 716
716 config DEFAULT_BBR 717 config DEFAULT_BBR
717 bool "BBR" if TCP_CONG_BBR=y 718 bool "BBR" if TCP_CONG_BBR=y
718 719
719 config DEFAULT_RENO 720 config DEFAULT_RENO
720 bool "Reno" 721 bool "Reno"
721 endchoice 722 endchoice
722 723
723 endif 724 endif
724 725
725 config TCP_CONG_CUBIC 726 config TCP_CONG_CUBIC
726 tristate 727 tristate
727 depends on !TCP_CONG_ADVANCED 728 depends on !TCP_CONG_ADVANCED
728 default y 729 default y
729 730
730 config DEFAULT_TCP_CONG 731 config DEFAULT_TCP_CONG
731 string 732 string
732 default "bic" if DEFAULT_BIC 733 default "bic" if DEFAULT_BIC
733 default "cubic" if DEFAULT_CUBIC 734 default "cubic" if DEFAULT_CUBIC
734 default "htcp" if DEFAULT_HTCP 735 default "htcp" if DEFAULT_HTCP
735 default "hybla" if DEFAULT_HYBLA 736 default "hybla" if DEFAULT_HYBLA
736 default "vegas" if DEFAULT_VEGAS 737 default "vegas" if DEFAULT_VEGAS
737 default "westwood" if DEFAULT_WESTWOOD 738 default "westwood" if DEFAULT_WESTWOOD
738 default "veno" if DEFAULT_VENO 739 default "veno" if DEFAULT_VENO
739 default "reno" if DEFAULT_RENO 740 default "reno" if DEFAULT_RENO
740 default "dctcp" if DEFAULT_DCTCP 741 default "dctcp" if DEFAULT_DCTCP
741 default "cdg" if DEFAULT_CDG 742 default "cdg" if DEFAULT_CDG
742 default "bbr" if DEFAULT_BBR 743 default "bbr" if DEFAULT_BBR
743 default "cubic" 744 default "cubic"
744 745
745 config TCP_SIGPOOL <<
746 tristate <<
747 <<
748 config TCP_AO <<
749 bool "TCP: Authentication Option (RFC5 <<
750 select CRYPTO <<
751 select TCP_SIGPOOL <<
752 depends on 64BIT && IPV6 != m # seq-nu <<
753 help <<
754 TCP-AO specifies the use of stronger <<
755 protects against replays for long-li <<
756 provides more details on the associa <<
757 connections than TCP MD5 (See RFC592 <<
758 <<
759 If unsure, say N. <<
760 <<
761 config TCP_MD5SIG 746 config TCP_MD5SIG
762 bool "TCP: MD5 Signature Option suppor 747 bool "TCP: MD5 Signature Option support (RFC2385)"
763 select CRYPTO 748 select CRYPTO
764 select CRYPTO_MD5 749 select CRYPTO_MD5
765 select TCP_SIGPOOL !! 750 ---help---
766 help <<
767 RFC2385 specifies a method of giving 751 RFC2385 specifies a method of giving MD5 protection to TCP sessions.
768 Its main (only?) use is to protect B 752 Its main (only?) use is to protect BGP sessions between core routers
769 on the Internet. 753 on the Internet.
770 754
771 If unsure, say N. 755 If unsure, say N.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.