]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - Documentation/sysctl/net.txt
ipv4: better IP_MAX_MTU enforcement
[mirror_ubuntu-bionic-kernel.git] / Documentation / sysctl / net.txt
CommitLineData
faa5273c 1Documentation for /proc/sys/net/*
760df93e
SF
2 (c) 1999 Terrehon Bowden <terrehon@pacbell.net>
3 Bodo Bauer <bb@ricochet.net>
4 (c) 2000 Jorge Nerin <comandante@zaralinux.com>
5 (c) 2009 Shen Feng <shen@cn.fujitsu.com>
6
7For general info and legal blurb, please look in README.
8
9==============================================================
10
11This file contains the documentation for the sysctl files in
faa5273c 12/proc/sys/net
760df93e
SF
13
14The interface to the networking parts of the kernel is located in
faa5273c 15/proc/sys/net. The following table shows all possible subdirectories. You may
760df93e
SF
16see only some of them, depending on your kernel's configuration.
17
18
19Table : Subdirectories in /proc/sys/net
20..............................................................................
21 Directory Content Directory Content
22 core General parameter appletalk Appletalk protocol
23 unix Unix domain sockets netrom NET/ROM
24 802 E802 protocol ax25 AX25
25 ethernet Ethernet protocol rose X.25 PLP layer
26 ipv4 IP version 4 x25 X.25 protocol
27 ipx IPX token-ring IBM token ring
28 bridge Bridging decnet DEC net
cc79dd1b 29 ipv6 IP version 6 tipc TIPC
760df93e
SF
30..............................................................................
31
321. /proc/sys/net/core - Network core options
33-------------------------------------------------------
34
0a14842f
ED
35bpf_jit_enable
36--------------
37
38This enables Berkeley Packet Filter Just in Time compiler.
39Currently supported on x86_64 architecture, bpf_jit provides a framework
40to speed packet filtering, the one used by tcpdump/libpcap for example.
41Values :
42 0 - disable the JIT (default value)
43 1 - enable the JIT
44 2 - enable the JIT and ask the compiler to emit traces on kernel log.
45
4f3446bb
DB
46bpf_jit_harden
47--------------
48
49This enables hardening for the Berkeley Packet Filter Just in Time compiler.
50Supported are eBPF JIT backends. Enabling hardening trades off performance,
51but can mitigate JIT spraying.
52Values :
53 0 - disable JIT hardening (default value)
54 1 - enable JIT hardening for unprivileged users only
55 2 - enable JIT hardening for all users
56
74451e66
DB
57bpf_jit_kallsyms
58----------------
59
60When Berkeley Packet Filter Just in Time compiler is enabled, then compiled
61images are unknown addresses to the kernel, meaning they neither show up in
62traces nor in /proc/kallsyms. This enables export of these addresses, which
63can be used for debugging/tracing. If bpf_jit_harden is enabled, this feature
64is disabled.
65Values :
66 0 - disable JIT kallsyms export (default value)
67 1 - enable JIT kallsyms export for privileged users only
68
c60f6aa8
SW
69dev_weight
70--------------
71
72The maximum number of packets that kernel can handle on a NAPI interrupt,
73it's a Per-CPU variable.
74Default: 64
75
3d48b53f
MT
76dev_weight_rx_bias
77--------------
78
79RPS (e.g. RFS, aRFS) processing is competing with the registered NAPI poll function
80of the driver for the per softirq cycle netdev_budget. This parameter influences
81the proportion of the configured netdev_budget that is spent on RPS based packet
82processing during RX softirq cycles. It is further meant for making current
83dev_weight adaptable for asymmetric CPU needs on RX/TX side of the network stack.
84(see dev_weight_tx_bias) It is effective on a per CPU basis. Determination is based
85on dev_weight and is calculated multiplicative (dev_weight * dev_weight_rx_bias).
86Default: 1
87
88dev_weight_tx_bias
89--------------
90
91Scales the maximum number of packets that can be processed during a TX softirq cycle.
92Effective on a per CPU basis. Allows scaling of current dev_weight for asymmetric
93net stack processing needs. Be careful to avoid making TX softirq processing a CPU hog.
94Calculation is based on dev_weight (dev_weight * dev_weight_tx_bias).
95Default: 1
96
6da7c8fc 97default_qdisc
98--------------
99
100The default queuing discipline to use for network devices. This allows
2e64126b
PS
101overriding the default of pfifo_fast with an alternative. Since the default
102queuing discipline is created without additional parameters so is best suited
103to queuing disciplines that work well without configuration like stochastic
104fair queue (sfq), CoDel (codel) or fair queue CoDel (fq_codel). Don't use
105queuing disciplines like Hierarchical Token Bucket or Deficit Round Robin
106which require setting up classes and bandwidths. Note that physical multiqueue
107interfaces still use mq as root qdisc, which in turn uses this default for its
108leaves. Virtual devices (like e.g. lo or veth) ignore this setting and instead
109default to noqueue.
6da7c8fc 110Default: pfifo_fast
111
64b0dc51 112busy_read
06021292 113----------------
e0d1095a 114Low latency busy poll timeout for socket reads. (needs CONFIG_NET_RX_BUSY_POLL)
cbf55001 115Approximate time in us to busy loop waiting for packets on the device queue.
64b0dc51
ET
116This sets the default value of the SO_BUSY_POLL socket option.
117Can be set or overridden per socket by setting socket option SO_BUSY_POLL,
118which is the preferred method of enabling. If you need to enable the feature
119globally via sysctl, a value of 50 is recommended.
cbf55001 120Will increase power usage.
06021292
ET
121Default: 0 (off)
122
64b0dc51 123busy_poll
2d48d67f 124----------------
e0d1095a 125Low latency busy poll timeout for poll and select. (needs CONFIG_NET_RX_BUSY_POLL)
cbf55001 126Approximate time in us to busy loop waiting for events.
2d48d67f
ET
127Recommended value depends on the number of sockets you poll on.
128For several sockets 50, for several hundreds 100.
129For more than that you probably want to use epoll.
64b0dc51
ET
130Note that only sockets with SO_BUSY_POLL set will be busy polled,
131so you want to either selectively set SO_BUSY_POLL on those sockets or set
132sysctl.net.busy_read globally.
cbf55001 133Will increase power usage.
2d48d67f
ET
134Default: 0 (off)
135
760df93e
SF
136rmem_default
137------------
138
139The default setting of the socket receive buffer in bytes.
140
141rmem_max
142--------
143
144The maximum receive socket buffer size in bytes.
145
b245be1f
WB
146tstamp_allow_data
147-----------------
148Allow processes to receive tx timestamps looped together with the original
149packet contents. If disabled, transmit timestamp requests from unprivileged
150processes are dropped unless socket option SOF_TIMESTAMPING_OPT_TSONLY is set.
151Default: 1 (on)
152
153
760df93e
SF
154wmem_default
155------------
156
157The default setting (in bytes) of the socket send buffer.
158
159wmem_max
160--------
161
162The maximum send socket buffer size in bytes.
163
164message_burst and message_cost
165------------------------------
166
167These parameters are used to limit the warning messages written to the kernel
168log from the networking code. They enforce a rate limit to make a
169denial-of-service attack impossible. A higher message_cost factor, results in
170fewer messages that will be written. Message_burst controls when messages will
171be dropped. The default settings limit warning messages to one every five
172seconds.
173
174warnings
175--------
176
ba7a46f1
JP
177This sysctl is now unused.
178
179This was used to control console messages from the networking stack that
180occur because of problems on the network like duplicate address or bad
181checksums.
182
183These messages are now emitted at KERN_DEBUG and can generally be enabled
184and controlled by the dynamic_debug facility.
760df93e
SF
185
186netdev_budget
187-------------
188
189Maximum number of packets taken from all interfaces in one polling cycle (NAPI
190poll). In one polling cycle interfaces which are registered to polling are
7acf8a1e
MW
191probed in a round-robin manner. Also, a polling cycle may not exceed
192netdev_budget_usecs microseconds, even if netdev_budget has not been
193exhausted.
194
195netdev_budget_usecs
196---------------------
197
198Maximum number of microseconds in one NAPI polling cycle. Polling
199will exit when either netdev_budget_usecs have elapsed during the
200poll cycle or the number of packets processed reaches netdev_budget.
760df93e
SF
201
202netdev_max_backlog
203------------------
204
205Maximum number of packets, queued on the INPUT side, when the interface
206receives packets faster than kernel can process them.
207
960fb622
ED
208netdev_rss_key
209--------------
210
211RSS (Receive Side Scaling) enabled drivers use a 40 bytes host key that is
212randomly generated.
213Some user space might need to gather its content even if drivers do not
214provide ethtool -x support yet.
215
216myhost:~# cat /proc/sys/net/core/netdev_rss_key
21784:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8: ... (52 bytes total)
218
219File contains nul bytes if no driver ever called netdev_rss_key_fill() function.
220Note:
221/proc/sys/net/core/netdev_rss_key contains 52 bytes of key,
222but most drivers only use 40 bytes of it.
223
224myhost:~# ethtool -x eth0
225RX flow hash indirection table for eth0 with 8 RX ring(s):
226 0: 0 1 2 3 4 5 6 7
227RSS hash key:
22884:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8:43:e3:c9:0c:fd:17:55:c2:3a:4d:69:ed:f1:42:89
229
3b098e2d
ED
230netdev_tstamp_prequeue
231----------------------
232
233If set to 0, RX packet timestamps can be sampled after RPS processing, when
234the target CPU processes packets. It might give some delay on timestamps, but
235permit to distribute the load on several cpus.
236
237If set to 1 (default), timestamps are sampled as soon as possible, before
238queueing.
239
760df93e
SF
240optmem_max
241----------
242
243Maximum ancillary buffer size allowed per socket. Ancillary data is a sequence
244of struct cmsghdr structures with appended data.
245
2462. /proc/sys/net/unix - Parameters for Unix domain sockets
247-------------------------------------------------------
248
45dad7bd
LX
249There is only one file in this directory.
250unix_dgram_qlen limits the max number of datagrams queued in Unix domain
ca8b9950 251socket's buffer. It will not take effect unless PF_UNIX flag is specified.
760df93e
SF
252
253
2543. /proc/sys/net/ipv4 - IPV4 settings
255-------------------------------------------------------
256Please see: Documentation/networking/ip-sysctl.txt and ipvs-sysctl.txt for
257descriptions of these entries.
258
259
2604. Appletalk
261-------------------------------------------------------
262
263The /proc/sys/net/appletalk directory holds the Appletalk configuration data
264when Appletalk is loaded. The configurable parameters are:
265
266aarp-expiry-time
267----------------
268
269The amount of time we keep an ARP entry before expiring it. Used to age out
270old hosts.
271
272aarp-resolve-time
273-----------------
274
275The amount of time we will spend trying to resolve an Appletalk address.
276
277aarp-retransmit-limit
278---------------------
279
280The number of times we will retransmit a query before giving up.
281
282aarp-tick-time
283--------------
284
285Controls the rate at which expires are checked.
286
287The directory /proc/net/appletalk holds the list of active Appletalk sockets
288on a machine.
289
290The fields indicate the DDP type, the local address (in network:node format)
291the remote address, the size of the transmit pending queue, the size of the
292received queue (bytes waiting for applications to read) the state and the uid
293owning the socket.
294
295/proc/net/atalk_iface lists all the interfaces configured for appletalk.It
296shows the name of the interface, its Appletalk address, the network range on
297that address (or network number for phase 1 networks), and the status of the
298interface.
299
300/proc/net/atalk_route lists each known network route. It lists the target
301(network) that the route leads to, the router (may be directly connected), the
302route flags, and the device the route is using.
303
304
3055. IPX
306-------------------------------------------------------
307
308The IPX protocol has no tunable values in proc/sys/net.
309
310The IPX protocol does, however, provide proc/net/ipx. This lists each IPX
311socket giving the local and remote addresses in Novell format (that is
312network:node:port). In accordance with the strange Novell tradition,
313everything but the port is in hex. Not_Connected is displayed for sockets that
314are not tied to a specific remote address. The Tx and Rx queue sizes indicate
315the number of bytes pending for transmission and reception. The state
316indicates the state the socket is in and the uid is the owning uid of the
317socket.
318
319The /proc/net/ipx_interface file lists all IPX interfaces. For each interface
320it gives the network number, the node number, and indicates if the network is
321the primary network. It also indicates which device it is bound to (or
322Internal for internal networks) and the Frame Type if appropriate. Linux
323supports 802.3, 802.2, 802.2 SNAP and DIX (Blue Book) ethernet framing for
324IPX.
325
326The /proc/net/ipx_route table holds a list of IPX routes. For each route it
327gives the destination network, the router node (or Directly) and the network
328address of the router (or Connected) for internal networks.
cc79dd1b
YX
329
3306. TIPC
331-------------------------------------------------------
332
a5325ae5
EH
333tipc_rmem
334----------
335
cc79dd1b
YX
336The TIPC protocol now has a tunable for the receive memory, similar to the
337tcp_rmem - i.e. a vector of 3 INTEGERs: (min, default, max)
338
339 # cat /proc/sys/net/tipc/tipc_rmem
340 4252725 34021800 68043600
341 #
342
343The max value is set to CONN_OVERLOAD_LIMIT, and the default and min values
344are scaled (shifted) versions of that same value. Note that the min value
345is not at this point in time used in any meaningful way, but the triplet is
346preserved in order to be consistent with things like tcp_rmem.
a5325ae5
EH
347
348named_timeout
349--------------
350
351TIPC name table updates are distributed asynchronously in a cluster, without
352any form of transaction handling. This means that different race scenarios are
353possible. One such is that a name withdrawal sent out by one node and received
354by another node may arrive after a second, overlapping name publication already
355has been accepted from a third node, although the conflicting updates
356originally may have been issued in the correct sequential order.
357If named_timeout is nonzero, failed topology updates will be placed on a defer
358queue until another event arrives that clears the error, or until the timeout
359expires. Value is in milliseconds.