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