Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343
  1. #
  2. # Network configuration
  3. #
  4. menuconfig NET
  5. bool "Networking support"
  6. select NLATTR
  7. ---help---
  8. Unless you really know what you are doing, you should say Y here.
  9. The reason is that some programs need kernel networking support even
  10. when running on a stand-alone machine that isn't connected to any
  11. other computer.
  12. If you are upgrading from an older kernel, you
  13. should consider updating your networking tools too because changes
  14. in the kernel and the tools often go hand in hand. The tools are
  15. contained in the package net-tools, the location and version number
  16. of which are given in <file:Documentation/Changes>.
  17. For a general introduction to Linux networking, it is highly
  18. recommended to read the NET-HOWTO, available from
  19. <http://www.tldp.org/docs.html#howto>.
  20. if NET
  21. config WANT_COMPAT_NETLINK_MESSAGES
  22. bool
  23. help
  24. This option can be selected by other options that need compat
  25. netlink messages.
  26. config COMPAT_NETLINK_MESSAGES
  27. def_bool y
  28. depends on COMPAT
  29. depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
  30. help
  31. This option makes it possible to send different netlink messages
  32. to tasks depending on whether the task is a compat task or not. To
  33. achieve this, you need to set skb_shinfo(skb)->frag_list to the
  34. compat skb before sending the skb, the netlink code will sort out
  35. which message to actually pass to the task.
  36. Newly written code should NEVER need this option but do
  37. compat-independent messages instead!
  38. menu "Networking options"
  39. source "net/packet/Kconfig"
  40. source "net/unix/Kconfig"
  41. source "net/xfrm/Kconfig"
  42. source "net/iucv/Kconfig"
  43. config INET
  44. bool "TCP/IP networking"
  45. ---help---
  46. These are the protocols used on the Internet and on most local
  47. Ethernets. It is highly recommended to say Y here (this will enlarge
  48. your kernel by about 400 KB), since some programs (e.g. the X window
  49. system) use TCP/IP even if your machine is not connected to any
  50. other computer. You will get the so-called loopback device which
  51. allows you to ping yourself (great fun, that!).
  52. For an excellent introduction to Linux networking, please read the
  53. Linux Networking HOWTO, available from
  54. <http://www.tldp.org/docs.html#howto>.
  55. If you say Y here and also to "/proc file system support" and
  56. "Sysctl support" below, you can change various aspects of the
  57. behavior of the TCP/IP code by writing to the (virtual) files in
  58. /proc/sys/net/ipv4/*; the options are explained in the file
  59. <file:Documentation/networking/ip-sysctl.txt>.
  60. Short answer: say Y.
  61. if INET
  62. source "net/ipv4/Kconfig"
  63. source "net/ipv6/Kconfig"
  64. source "net/netlabel/Kconfig"
  65. endif # if INET
  66. config NETWORK_SECMARK
  67. bool "Security Marking"
  68. help
  69. This enables security marking of network packets, similar
  70. to nfmark, but designated for security purposes.
  71. If you are unsure how to answer this question, answer N.
  72. config NETWORK_PHY_TIMESTAMPING
  73. bool "Timestamping in PHY devices"
  74. depends on EXPERIMENTAL
  75. help
  76. This allows timestamping of network packets by PHYs with
  77. hardware timestamping capabilities. This option adds some
  78. overhead in the transmit and receive paths.
  79. If you are unsure how to answer this question, answer N.
  80. menuconfig NETFILTER
  81. bool "Network packet filtering framework (Netfilter)"
  82. ---help---
  83. Netfilter is a framework for filtering and mangling network packets
  84. that pass through your Linux box.
  85. The most common use of packet filtering is to run your Linux box as
  86. a firewall protecting a local network from the Internet. The type of
  87. firewall provided by this kernel support is called a "packet
  88. filter", which means that it can reject individual network packets
  89. based on type, source, destination etc. The other kind of firewall,
  90. a "proxy-based" one, is more secure but more intrusive and more
  91. bothersome to set up; it inspects the network traffic much more
  92. closely, modifies it and has knowledge about the higher level
  93. protocols, which a packet filter lacks. Moreover, proxy-based
  94. firewalls often require changes to the programs running on the local
  95. clients. Proxy-based firewalls don't need support by the kernel, but
  96. they are often combined with a packet filter, which only works if
  97. you say Y here.
  98. You should also say Y here if you intend to use your Linux box as
  99. the gateway to the Internet for a local network of machines without
  100. globally valid IP addresses. This is called "masquerading": if one
  101. of the computers on your local network wants to send something to
  102. the outside, your box can "masquerade" as that computer, i.e. it
  103. forwards the traffic to the intended outside destination, but
  104. modifies the packets to make it look like they came from the
  105. firewall box itself. It works both ways: if the outside host
  106. replies, the Linux box will silently forward the traffic to the
  107. correct local computer. This way, the computers on your local net
  108. are completely invisible to the outside world, even though they can
  109. reach the outside and can receive replies. It is even possible to
  110. run globally visible servers from within a masqueraded local network
  111. using a mechanism called portforwarding. Masquerading is also often
  112. called NAT (Network Address Translation).
  113. Another use of Netfilter is in transparent proxying: if a machine on
  114. the local network tries to connect to an outside host, your Linux
  115. box can transparently forward the traffic to a local server,
  116. typically a caching proxy server.
  117. Yet another use of Netfilter is building a bridging firewall. Using
  118. a bridge with Network packet filtering enabled makes iptables "see"
  119. the bridged traffic. For filtering on the lower network and Ethernet
  120. protocols over the bridge, use ebtables (under bridge netfilter
  121. configuration).
  122. Various modules exist for netfilter which replace the previous
  123. masquerading (ipmasqadm), packet filtering (ipchains), transparent
  124. proxying, and portforwarding mechanisms. Please see
  125. <file:Documentation/Changes> under "iptables" for the location of
  126. these packages.
  127. if NETFILTER
  128. config NETFILTER_DEBUG
  129. bool "Network packet filtering debugging"
  130. depends on NETFILTER
  131. help
  132. You can say Y here if you want to get additional messages useful in
  133. debugging the netfilter code.
  134. config NETFILTER_ADVANCED
  135. bool "Advanced netfilter configuration"
  136. depends on NETFILTER
  137. default y
  138. help
  139. If you say Y here you can select between all the netfilter modules.
  140. If you say N the more unusual ones will not be shown and the
  141. basic ones needed by most people will default to 'M'.
  142. If unsure, say Y.
  143. config BRIDGE_NETFILTER
  144. bool "Bridged IP/ARP packets filtering"
  145. depends on BRIDGE && NETFILTER && INET
  146. depends on NETFILTER_ADVANCED
  147. default y
  148. ---help---
  149. Enabling this option will let arptables resp. iptables see bridged
  150. ARP resp. IP traffic. If you want a bridging firewall, you probably
  151. want this option enabled.
  152. Enabling or disabling this option doesn't enable or disable
  153. ebtables.
  154. If unsure, say N.
  155. source "net/netfilter/Kconfig"
  156. source "net/ipv4/netfilter/Kconfig"
  157. source "net/ipv6/netfilter/Kconfig"
  158. source "net/decnet/netfilter/Kconfig"
  159. source "net/bridge/netfilter/Kconfig"
  160. endif
  161. source "net/dccp/Kconfig"
  162. source "net/sctp/Kconfig"
  163. source "net/rds/Kconfig"
  164. source "net/tipc/Kconfig"
  165. source "net/atm/Kconfig"
  166. source "net/l2tp/Kconfig"
  167. source "net/802/Kconfig"
  168. source "net/bridge/Kconfig"
  169. source "net/dsa/Kconfig"
  170. source "net/8021q/Kconfig"
  171. source "net/decnet/Kconfig"
  172. source "net/llc/Kconfig"
  173. source "net/ipx/Kconfig"
  174. source "drivers/net/appletalk/Kconfig"
  175. source "net/x25/Kconfig"
  176. source "net/lapb/Kconfig"
  177. source "net/econet/Kconfig"
  178. source "net/wanrouter/Kconfig"
  179. source "net/phonet/Kconfig"
  180. source "net/ieee802154/Kconfig"
  181. source "net/mac802154/Kconfig"
  182. source "net/sched/Kconfig"
  183. source "net/dcb/Kconfig"
  184. source "net/dns_resolver/Kconfig"
  185. source "net/batman-adv/Kconfig"
  186. source "net/openvswitch/Kconfig"
  187. config RPS
  188. boolean
  189. depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
  190. default y
  191. config RFS_ACCEL
  192. boolean
  193. depends on RPS && GENERIC_HARDIRQS
  194. select CPU_RMAP
  195. default y
  196. config XPS
  197. boolean
  198. depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
  199. default y
  200. config NETPRIO_CGROUP
  201. tristate "Network priority cgroup"
  202. depends on CGROUPS
  203. ---help---
  204. Cgroup subsystem for use in assigning processes to network priorities on
  205. a per-interface basis
  206. config BQL
  207. boolean
  208. depends on SYSFS
  209. select DQL
  210. default y
  211. config HAVE_BPF_JIT
  212. bool
  213. config BPF_JIT
  214. bool "enable BPF Just In Time compiler"
  215. depends on HAVE_BPF_JIT
  216. depends on MODULES
  217. ---help---
  218. Berkeley Packet Filter filtering capabilities are normally handled
  219. by an interpreter. This option allows kernel to generate a native
  220. code when filter is loaded in memory. This should speedup
  221. packet sniffing (libpcap/tcpdump). Note : Admin should enable
  222. this feature changing /proc/sys/net/core/bpf_jit_enable
  223. menu "Network testing"
  224. config NET_PKTGEN
  225. tristate "Packet Generator (USE WITH CAUTION)"
  226. depends on PROC_FS
  227. ---help---
  228. This module will inject preconfigured packets, at a configurable
  229. rate, out of a given interface. It is used for network interface
  230. stress testing and performance analysis. If you don't understand
  231. what was just said, you don't need it: say N.
  232. Documentation on how to use the packet generator can be found
  233. at <file:Documentation/networking/pktgen.txt>.
  234. To compile this code as a module, choose M here: the
  235. module will be called pktgen.
  236. config NET_TCPPROBE
  237. tristate "TCP connection probing"
  238. depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
  239. ---help---
  240. This module allows for capturing the changes to TCP connection
  241. state in response to incoming packets. It is used for debugging
  242. TCP congestion avoidance modules. If you don't understand
  243. what was just said, you don't need it: say N.
  244. Documentation on how to use TCP connection probing can be found
  245. at:
  246. http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
  247. To compile this code as a module, choose M here: the
  248. module will be called tcp_probe.
  249. config NET_DROP_MONITOR
  250. tristate "Network packet drop alerting service"
  251. depends on INET && EXPERIMENTAL && TRACEPOINTS
  252. ---help---
  253. This feature provides an alerting service to userspace in the
  254. event that packets are discarded in the network stack. Alerts
  255. are broadcast via netlink socket to any listening user space
  256. process. If you don't need network drop alerts, or if you are ok
  257. just checking the various proc files and other utilities for
  258. drop statistics, say N here.
  259. endmenu
  260. endmenu
  261. source "net/ax25/Kconfig"
  262. source "net/can/Kconfig"
  263. source "net/irda/Kconfig"
  264. source "net/bluetooth/Kconfig"
  265. source "net/rxrpc/Kconfig"
  266. config FIB_RULES
  267. bool
  268. menuconfig WIRELESS
  269. bool "Wireless"
  270. depends on !S390
  271. default y
  272. if WIRELESS
  273. source "net/wireless/Kconfig"
  274. source "net/mac80211/Kconfig"
  275. endif # WIRELESS
  276. source "net/wimax/Kconfig"
  277. source "net/rfkill/Kconfig"
  278. source "net/9p/Kconfig"
  279. source "net/caif/Kconfig"
  280. source "net/ceph/Kconfig"
  281. source "net/nfc/Kconfig"
  282. endif # if NET