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