Kconfig 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232
  1. #
  2. # Network configuration
  3. #
  4. menu "Networking"
  5. config NET
  6. bool "Networking support"
  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. # Make sure that all config symbols are dependent on NET
  21. if NET
  22. menu "Networking options"
  23. config NETDEBUG
  24. bool "Network packet debugging"
  25. help
  26. You can say Y here if you want to get additional messages useful in
  27. debugging bad packets, but can overwhelm logs under denial of service
  28. attacks.
  29. source "net/packet/Kconfig"
  30. source "net/unix/Kconfig"
  31. source "net/xfrm/Kconfig"
  32. source "net/iucv/Kconfig"
  33. config INET
  34. bool "TCP/IP networking"
  35. ---help---
  36. These are the protocols used on the Internet and on most local
  37. Ethernets. It is highly recommended to say Y here (this will enlarge
  38. your kernel by about 144 KB), since some programs (e.g. the X window
  39. system) use TCP/IP even if your machine is not connected to any
  40. other computer. You will get the so-called loopback device which
  41. allows you to ping yourself (great fun, that!).
  42. For an excellent introduction to Linux networking, please read the
  43. Linux Networking HOWTO, available from
  44. <http://www.tldp.org/docs.html#howto>.
  45. If you say Y here and also to "/proc file system support" and
  46. "Sysctl support" below, you can change various aspects of the
  47. behavior of the TCP/IP code by writing to the (virtual) files in
  48. /proc/sys/net/ipv4/*; the options are explained in the file
  49. <file:Documentation/networking/ip-sysctl.txt>.
  50. Short answer: say Y.
  51. if INET
  52. source "net/ipv4/Kconfig"
  53. source "net/ipv6/Kconfig"
  54. source "net/netlabel/Kconfig"
  55. endif # if INET
  56. config NETWORK_SECMARK
  57. bool "Security Marking"
  58. help
  59. This enables security marking of network packets, similar
  60. to nfmark, but designated for security purposes.
  61. If you are unsure how to answer this question, answer N.
  62. menuconfig NETFILTER
  63. bool "Network packet filtering framework (Netfilter)"
  64. ---help---
  65. Netfilter is a framework for filtering and mangling network packets
  66. that pass through your Linux box.
  67. The most common use of packet filtering is to run your Linux box as
  68. a firewall protecting a local network from the Internet. The type of
  69. firewall provided by this kernel support is called a "packet
  70. filter", which means that it can reject individual network packets
  71. based on type, source, destination etc. The other kind of firewall,
  72. a "proxy-based" one, is more secure but more intrusive and more
  73. bothersome to set up; it inspects the network traffic much more
  74. closely, modifies it and has knowledge about the higher level
  75. protocols, which a packet filter lacks. Moreover, proxy-based
  76. firewalls often require changes to the programs running on the local
  77. clients. Proxy-based firewalls don't need support by the kernel, but
  78. they are often combined with a packet filter, which only works if
  79. you say Y here.
  80. You should also say Y here if you intend to use your Linux box as
  81. the gateway to the Internet for a local network of machines without
  82. globally valid IP addresses. This is called "masquerading": if one
  83. of the computers on your local network wants to send something to
  84. the outside, your box can "masquerade" as that computer, i.e. it
  85. forwards the traffic to the intended outside destination, but
  86. modifies the packets to make it look like they came from the
  87. firewall box itself. It works both ways: if the outside host
  88. replies, the Linux box will silently forward the traffic to the
  89. correct local computer. This way, the computers on your local net
  90. are completely invisible to the outside world, even though they can
  91. reach the outside and can receive replies. It is even possible to
  92. run globally visible servers from within a masqueraded local network
  93. using a mechanism called portforwarding. Masquerading is also often
  94. called NAT (Network Address Translation).
  95. Another use of Netfilter is in transparent proxying: if a machine on
  96. the local network tries to connect to an outside host, your Linux
  97. box can transparently forward the traffic to a local server,
  98. typically a caching proxy server.
  99. Yet another use of Netfilter is building a bridging firewall. Using
  100. a bridge with Network packet filtering enabled makes iptables "see"
  101. the bridged traffic. For filtering on the lower network and Ethernet
  102. protocols over the bridge, use ebtables (under bridge netfilter
  103. configuration).
  104. Various modules exist for netfilter which replace the previous
  105. masquerading (ipmasqadm), packet filtering (ipchains), transparent
  106. proxying, and portforwarding mechanisms. Please see
  107. <file:Documentation/Changes> under "iptables" for the location of
  108. these packages.
  109. Make sure to say N to "Fast switching" below if you intend to say Y
  110. here, as Fast switching currently bypasses netfilter.
  111. Chances are that you should say Y here if you compile a kernel which
  112. will run as a router and N for regular hosts. If unsure, say N.
  113. if NETFILTER
  114. config NETFILTER_DEBUG
  115. bool "Network packet filtering debugging"
  116. depends on NETFILTER
  117. help
  118. You can say Y here if you want to get additional messages useful in
  119. debugging the netfilter code.
  120. config BRIDGE_NETFILTER
  121. bool "Bridged IP/ARP packets filtering"
  122. depends on BRIDGE && NETFILTER && INET
  123. default y
  124. ---help---
  125. Enabling this option will let arptables resp. iptables see bridged
  126. ARP resp. IP traffic. If you want a bridging firewall, you probably
  127. want this option enabled.
  128. Enabling or disabling this option doesn't enable or disable
  129. ebtables.
  130. If unsure, say N.
  131. source "net/netfilter/Kconfig"
  132. source "net/ipv4/netfilter/Kconfig"
  133. source "net/ipv6/netfilter/Kconfig"
  134. source "net/decnet/netfilter/Kconfig"
  135. source "net/bridge/netfilter/Kconfig"
  136. endif
  137. source "net/dccp/Kconfig"
  138. source "net/sctp/Kconfig"
  139. source "net/tipc/Kconfig"
  140. source "net/atm/Kconfig"
  141. source "net/bridge/Kconfig"
  142. source "net/8021q/Kconfig"
  143. source "net/decnet/Kconfig"
  144. source "net/llc/Kconfig"
  145. source "net/ipx/Kconfig"
  146. source "drivers/net/appletalk/Kconfig"
  147. source "net/x25/Kconfig"
  148. source "net/lapb/Kconfig"
  149. source "net/econet/Kconfig"
  150. source "net/wanrouter/Kconfig"
  151. source "net/sched/Kconfig"
  152. menu "Network testing"
  153. config NET_PKTGEN
  154. tristate "Packet Generator (USE WITH CAUTION)"
  155. depends on PROC_FS
  156. ---help---
  157. This module will inject preconfigured packets, at a configurable
  158. rate, out of a given interface. It is used for network interface
  159. stress testing and performance analysis. If you don't understand
  160. what was just said, you don't need it: say N.
  161. Documentation on how to use the packet generator can be found
  162. at <file:Documentation/networking/pktgen.txt>.
  163. To compile this code as a module, choose M here: the
  164. module will be called pktgen.
  165. config NET_TCPPROBE
  166. tristate "TCP connection probing"
  167. depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
  168. ---help---
  169. This module allows for capturing the changes to TCP connection
  170. state in response to incoming packets. It is used for debugging
  171. TCP congestion avoidance modules. If you don't understand
  172. what was just said, you don't need it: say N.
  173. Documentation on how to use TCP connection probing can be found
  174. at http://linux-net.osdl.org/index.php/TcpProbe
  175. To compile this code as a module, choose M here: the
  176. module will be called tcp_probe.
  177. endmenu
  178. endmenu
  179. source "net/ax25/Kconfig"
  180. source "net/irda/Kconfig"
  181. source "net/bluetooth/Kconfig"
  182. source "net/ieee80211/Kconfig"
  183. config WIRELESS_EXT
  184. bool
  185. config FIB_RULES
  186. bool
  187. endif # if NET
  188. endmenu # Networking