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