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