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