net.txt 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305
  1. Documentation for /proc/sys/net/*
  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. For general info and legal blurb, please look in README.
  7. ==============================================================
  8. This file contains the documentation for the sysctl files in
  9. /proc/sys/net
  10. The interface to the networking parts of the kernel is located in
  11. /proc/sys/net. The following table shows all possible subdirectories. You may
  12. see only some of them, depending on your kernel's configuration.
  13. Table : Subdirectories in /proc/sys/net
  14. ..............................................................................
  15. Directory Content Directory Content
  16. core General parameter appletalk Appletalk protocol
  17. unix Unix domain sockets netrom NET/ROM
  18. 802 E802 protocol ax25 AX25
  19. ethernet Ethernet protocol rose X.25 PLP layer
  20. ipv4 IP version 4 x25 X.25 protocol
  21. ipx IPX token-ring IBM token ring
  22. bridge Bridging decnet DEC net
  23. ipv6 IP version 6 tipc TIPC
  24. ..............................................................................
  25. 1. /proc/sys/net/core - Network core options
  26. -------------------------------------------------------
  27. bpf_jit_enable
  28. --------------
  29. This enables Berkeley Packet Filter Just in Time compiler.
  30. Currently supported on x86_64 architecture, bpf_jit provides a framework
  31. to speed packet filtering, the one used by tcpdump/libpcap for example.
  32. Values :
  33. 0 - disable the JIT (default value)
  34. 1 - enable the JIT
  35. 2 - enable the JIT and ask the compiler to emit traces on kernel log.
  36. dev_weight
  37. --------------
  38. The maximum number of packets that kernel can handle on a NAPI interrupt,
  39. it's a Per-CPU variable.
  40. Default: 64
  41. default_qdisc
  42. --------------
  43. The default queuing discipline to use for network devices. This allows
  44. overriding the default queue discipline of pfifo_fast with an
  45. alternative. Since the default queuing discipline is created with the
  46. no additional parameters so is best suited to queuing disciplines that
  47. work well without configuration like stochastic fair queue (sfq),
  48. CoDel (codel) or fair queue CoDel (fq_codel). Don't use queuing disciplines
  49. like Hierarchical Token Bucket or Deficit Round Robin which require setting
  50. up classes and bandwidths.
  51. Default: pfifo_fast
  52. busy_read
  53. ----------------
  54. Low latency busy poll timeout for socket reads. (needs CONFIG_NET_RX_BUSY_POLL)
  55. Approximate time in us to busy loop waiting for packets on the device queue.
  56. This sets the default value of the SO_BUSY_POLL socket option.
  57. Can be set or overridden per socket by setting socket option SO_BUSY_POLL,
  58. which is the preferred method of enabling. If you need to enable the feature
  59. globally via sysctl, a value of 50 is recommended.
  60. Will increase power usage.
  61. Default: 0 (off)
  62. busy_poll
  63. ----------------
  64. Low latency busy poll timeout for poll and select. (needs CONFIG_NET_RX_BUSY_POLL)
  65. Approximate time in us to busy loop waiting for events.
  66. Recommended value depends on the number of sockets you poll on.
  67. For several sockets 50, for several hundreds 100.
  68. For more than that you probably want to use epoll.
  69. Note that only sockets with SO_BUSY_POLL set will be busy polled,
  70. so you want to either selectively set SO_BUSY_POLL on those sockets or set
  71. sysctl.net.busy_read globally.
  72. Will increase power usage.
  73. Default: 0 (off)
  74. rmem_default
  75. ------------
  76. The default setting of the socket receive buffer in bytes.
  77. rmem_max
  78. --------
  79. The maximum receive socket buffer size in bytes.
  80. tstamp_allow_data
  81. -----------------
  82. Allow processes to receive tx timestamps looped together with the original
  83. packet contents. If disabled, transmit timestamp requests from unprivileged
  84. processes are dropped unless socket option SOF_TIMESTAMPING_OPT_TSONLY is set.
  85. Default: 1 (on)
  86. wmem_default
  87. ------------
  88. The default setting (in bytes) of the socket send buffer.
  89. wmem_max
  90. --------
  91. The maximum send socket buffer size in bytes.
  92. message_burst and message_cost
  93. ------------------------------
  94. These parameters are used to limit the warning messages written to the kernel
  95. log from the networking code. They enforce a rate limit to make a
  96. denial-of-service attack impossible. A higher message_cost factor, results in
  97. fewer messages that will be written. Message_burst controls when messages will
  98. be dropped. The default settings limit warning messages to one every five
  99. seconds.
  100. warnings
  101. --------
  102. This sysctl is now unused.
  103. This was used to control console messages from the networking stack that
  104. occur because of problems on the network like duplicate address or bad
  105. checksums.
  106. These messages are now emitted at KERN_DEBUG and can generally be enabled
  107. and controlled by the dynamic_debug facility.
  108. netdev_budget
  109. -------------
  110. Maximum number of packets taken from all interfaces in one polling cycle (NAPI
  111. poll). In one polling cycle interfaces which are registered to polling are
  112. probed in a round-robin manner.
  113. netdev_max_backlog
  114. ------------------
  115. Maximum number of packets, queued on the INPUT side, when the interface
  116. receives packets faster than kernel can process them.
  117. netdev_rss_key
  118. --------------
  119. RSS (Receive Side Scaling) enabled drivers use a 40 bytes host key that is
  120. randomly generated.
  121. Some user space might need to gather its content even if drivers do not
  122. provide ethtool -x support yet.
  123. myhost:~# cat /proc/sys/net/core/netdev_rss_key
  124. 84: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)
  125. File contains nul bytes if no driver ever called netdev_rss_key_fill() function.
  126. Note:
  127. /proc/sys/net/core/netdev_rss_key contains 52 bytes of key,
  128. but most drivers only use 40 bytes of it.
  129. myhost:~# ethtool -x eth0
  130. RX flow hash indirection table for eth0 with 8 RX ring(s):
  131. 0: 0 1 2 3 4 5 6 7
  132. RSS hash key:
  133. 84: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
  134. netdev_tstamp_prequeue
  135. ----------------------
  136. If set to 0, RX packet timestamps can be sampled after RPS processing, when
  137. the target CPU processes packets. It might give some delay on timestamps, but
  138. permit to distribute the load on several cpus.
  139. If set to 1 (default), timestamps are sampled as soon as possible, before
  140. queueing.
  141. optmem_max
  142. ----------
  143. Maximum ancillary buffer size allowed per socket. Ancillary data is a sequence
  144. of struct cmsghdr structures with appended data.
  145. 2. /proc/sys/net/unix - Parameters for Unix domain sockets
  146. -------------------------------------------------------
  147. There is only one file in this directory.
  148. unix_dgram_qlen limits the max number of datagrams queued in Unix domain
  149. socket's buffer. It will not take effect unless PF_UNIX flag is specified.
  150. 3. /proc/sys/net/ipv4 - IPV4 settings
  151. -------------------------------------------------------
  152. Please see: Documentation/networking/ip-sysctl.txt and ipvs-sysctl.txt for
  153. descriptions of these entries.
  154. 4. Appletalk
  155. -------------------------------------------------------
  156. The /proc/sys/net/appletalk directory holds the Appletalk configuration data
  157. when Appletalk is loaded. The configurable parameters are:
  158. aarp-expiry-time
  159. ----------------
  160. The amount of time we keep an ARP entry before expiring it. Used to age out
  161. old hosts.
  162. aarp-resolve-time
  163. -----------------
  164. The amount of time we will spend trying to resolve an Appletalk address.
  165. aarp-retransmit-limit
  166. ---------------------
  167. The number of times we will retransmit a query before giving up.
  168. aarp-tick-time
  169. --------------
  170. Controls the rate at which expires are checked.
  171. The directory /proc/net/appletalk holds the list of active Appletalk sockets
  172. on a machine.
  173. The fields indicate the DDP type, the local address (in network:node format)
  174. the remote address, the size of the transmit pending queue, the size of the
  175. received queue (bytes waiting for applications to read) the state and the uid
  176. owning the socket.
  177. /proc/net/atalk_iface lists all the interfaces configured for appletalk.It
  178. shows the name of the interface, its Appletalk address, the network range on
  179. that address (or network number for phase 1 networks), and the status of the
  180. interface.
  181. /proc/net/atalk_route lists each known network route. It lists the target
  182. (network) that the route leads to, the router (may be directly connected), the
  183. route flags, and the device the route is using.
  184. 5. IPX
  185. -------------------------------------------------------
  186. The IPX protocol has no tunable values in proc/sys/net.
  187. The IPX protocol does, however, provide proc/net/ipx. This lists each IPX
  188. socket giving the local and remote addresses in Novell format (that is
  189. network:node:port). In accordance with the strange Novell tradition,
  190. everything but the port is in hex. Not_Connected is displayed for sockets that
  191. are not tied to a specific remote address. The Tx and Rx queue sizes indicate
  192. the number of bytes pending for transmission and reception. The state
  193. indicates the state the socket is in and the uid is the owning uid of the
  194. socket.
  195. The /proc/net/ipx_interface file lists all IPX interfaces. For each interface
  196. it gives the network number, the node number, and indicates if the network is
  197. the primary network. It also indicates which device it is bound to (or
  198. Internal for internal networks) and the Frame Type if appropriate. Linux
  199. supports 802.3, 802.2, 802.2 SNAP and DIX (Blue Book) ethernet framing for
  200. IPX.
  201. The /proc/net/ipx_route table holds a list of IPX routes. For each route it
  202. gives the destination network, the router node (or Directly) and the network
  203. address of the router (or Connected) for internal networks.
  204. 6. TIPC
  205. -------------------------------------------------------
  206. tipc_rmem
  207. ----------
  208. The TIPC protocol now has a tunable for the receive memory, similar to the
  209. tcp_rmem - i.e. a vector of 3 INTEGERs: (min, default, max)
  210. # cat /proc/sys/net/tipc/tipc_rmem
  211. 4252725 34021800 68043600
  212. #
  213. The max value is set to CONN_OVERLOAD_LIMIT, and the default and min values
  214. are scaled (shifted) versions of that same value. Note that the min value
  215. is not at this point in time used in any meaningful way, but the triplet is
  216. preserved in order to be consistent with things like tcp_rmem.
  217. named_timeout
  218. --------------
  219. TIPC name table updates are distributed asynchronously in a cluster, without
  220. any form of transaction handling. This means that different race scenarios are
  221. possible. One such is that a name withdrawal sent out by one node and received
  222. by another node may arrive after a second, overlapping name publication already
  223. has been accepted from a third node, although the conflicting updates
  224. originally may have been issued in the correct sequential order.
  225. If named_timeout is nonzero, failed topology updates will be placed on a defer
  226. queue until another event arrives that clears the error, or until the timeout
  227. expires. Value is in milliseconds.