net/Kconfig

   1 #
   2 # Network configuration
   3 #
   4
   5 menuconfig 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
  13           If you are upgrading from an older kernel, you
  14           should consider updating your networking tools too because changes
  15           in the kernel and the tools often go hand in hand. The tools are
  16           contained in the package net-tools, the location and version number
  17           of which are given in <file:Documentation/Changes>.
  18
  19           For a general introduction to Linux networking, it is highly
  20           recommended to read the NET-HOWTO, available from
  21           <http://www.tldp.org/docs.html#howto>.
  22
  23 if NET
  24
  25 menu "Networking options"
  26
  27 config NET_NS
  28         bool "Network namespace support"
  29         default n
  30         depends on EXPERIMENTAL && NAMESPACES
  31         help
  32           Allow user space to create what appear to be multiple instances
  33           of the network stack.
  34
  35 config COMPAT_NET_DEV_OPS
  36        def_bool y
  37
  38 source "net/packet/Kconfig"
  39 source "net/unix/Kconfig"
  40 source "net/xfrm/Kconfig"
  41 source "net/iucv/Kconfig"
  42
  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
  53           For an excellent introduction to Linux networking, please read the
  54           Linux Networking HOWTO, available from
  55           <http://www.tldp.org/docs.html#howto>.
  56
  57           If you say Y here and also to "/proc file system support" and
  58           "Sysctl support" below, you can change various aspects of the
  59           behavior of the TCP/IP code by writing to the (virtual) files in
  60           /proc/sys/net/ipv4/*; the options are explained in the file
  61           <file:Documentation/networking/ip-sysctl.txt>.
  62
  63           Short answer: say Y.
  64
  65 if INET
  66 source "net/ipv4/Kconfig"
  67 source "net/ipv6/Kconfig"
  68 source "net/netlabel/Kconfig"
  69
  70 endif # if INET
  71
  72 config NETWORK_SECMARK
  73         bool "Security Marking"
  74         help
  75           This enables security marking of network packets, similar
  76           to nfmark, but designated for security purposes.
  77           If you are unsure how to answer this question, answer N.
  78
  79 menuconfig NETFILTER
  80         bool "Network packet filtering framework (Netfilter)"
  81         ---help---
  82           Netfilter is a framework for filtering and mangling network packets
  83           that pass through your Linux box.
  84
  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
  99           You should also say Y here if you intend to use your Linux box as
 100           the gateway to the Internet for a local network of machines without
 101           globally valid IP addresses. This is called "masquerading": if one
 102           of the computers on your local network wants to send something to
 103           the outside, your box can "masquerade" as that computer, i.e. it
 104           forwards the traffic to the intended outside destination, but
 105           modifies the packets to make it look like they came from the
 106           firewall box itself. It works both ways: if the outside host
 107           replies, the Linux box will silently forward the traffic to the
 108           correct local computer. This way, the computers on your local net
 109           are completely invisible to the outside world, even though they can
 110           reach the outside and can receive replies. It is even possible to
 111           run globally visible servers from within a masqueraded local network
 112           using a mechanism called portforwarding. Masquerading is also often
 113           called NAT (Network Address Translation).
 114
 115           Another use of Netfilter is in transparent proxying: if a machine on
 116           the local network tries to connect to an outside host, your Linux
 117           box can transparently forward the traffic to a local server,
 118           typically a caching proxy server.
 119
 120           Yet another use of Netfilter is building a bridging firewall. Using
 121           a bridge with Network packet filtering enabled makes iptables "see"
 122           the bridged traffic. For filtering on the lower network and Ethernet
 123           protocols over the bridge, use ebtables (under bridge netfilter
 124           configuration).
 125
 126           Various modules exist for netfilter which replace the previous
 127           masquerading (ipmasqadm), packet filtering (ipchains), transparent
 128           proxying, and portforwarding mechanisms. Please see
 129           <file:Documentation/Changes> under "iptables" for the location of
 130           these packages.
 131
 132           Make sure to say N to "Fast switching" below if you intend to say Y
 133           here, as Fast switching currently bypasses netfilter.
 134
 135           Chances are that you should say Y here if you compile a kernel which
 136           will run as a router and N for regular hosts. If unsure, say N.
 137
 138 if NETFILTER
 139
 140 config NETFILTER_DEBUG
 141         bool "Network packet filtering debugging"
 142         depends on NETFILTER
 143         help
 144           You can say Y here if you want to get additional messages useful in
 145           debugging the netfilter code.
 146
 147 config NETFILTER_ADVANCED
 148         bool "Advanced netfilter configuration"
 149         depends on NETFILTER
 150         default y
 151         help
 152           If you say Y here you can select between all the netfilter modules.
 153           If you say N the more ununsual ones will not be shown and the
 154           basic ones needed by most people will default to 'M'.
 155
 156           If unsure, say Y.
 157
 158 config BRIDGE_NETFILTER
 159         bool "Bridged IP/ARP packets filtering"
 160         depends on BRIDGE && NETFILTER && INET
 161         depends on NETFILTER_ADVANCED
 162         default y
 163         ---help---
 164           Enabling this option will let arptables resp. iptables see bridged
 165           ARP resp. IP traffic. If you want a bridging firewall, you probably
 166           want this option enabled.
 167           Enabling or disabling this option doesn't enable or disable
 168           ebtables.
 169
 170           If unsure, say N.
 171
 172 source "net/netfilter/Kconfig"
 173 source "net/ipv4/netfilter/Kconfig"
 174 source "net/ipv6/netfilter/Kconfig"
 175 source "net/decnet/netfilter/Kconfig"
 176 source "net/bridge/netfilter/Kconfig"
 177
 178 endif
 179
 180 source "net/dccp/Kconfig"
 181 source "net/sctp/Kconfig"
 182 source "net/tipc/Kconfig"
 183 source "net/atm/Kconfig"
 184 source "net/802/Kconfig"
 185 source "net/bridge/Kconfig"
 186 source "net/dsa/Kconfig"
 187 source "net/8021q/Kconfig"
 188 source "net/decnet/Kconfig"
 189 source "net/llc/Kconfig"
 190 source "net/ipx/Kconfig"
 191 source "drivers/net/appletalk/Kconfig"
 192 source "net/x25/Kconfig"
 193 source "net/lapb/Kconfig"
 194 source "net/econet/Kconfig"
 195 source "net/wanrouter/Kconfig"
 196 source "net/sched/Kconfig"
 197 source "net/dcb/Kconfig"
 198
 199 menu "Network testing"
 200
 201 config NET_PKTGEN
 202         tristate "Packet Generator (USE WITH CAUTION)"
 203         depends on PROC_FS
 204         ---help---
 205           This module will inject preconfigured packets, at a configurable
 206           rate, out of a given interface.  It is used for network interface
 207           stress testing and performance analysis.  If you don't understand
 208           what was just said, you don't need it: say N.
 209
 210           Documentation on how to use the packet generator can be found
 211           at <file:Documentation/networking/pktgen.txt>.
 212
 213           To compile this code as a module, choose M here: the
 214           module will be called pktgen.
 215
 216 config NET_TCPPROBE
 217         tristate "TCP connection probing"
 218         depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
 219         ---help---
 220         This module allows for capturing the changes to TCP connection
 221         state in response to incoming packets. It is used for debugging
 222         TCP congestion avoidance modules. If you don't understand
 223         what was just said, you don't need it: say N.
 224
 225         Documentation on how to use TCP connection probing can be found
 226         at http://linux-net.osdl.org/index.php/TcpProbe
 227
 228         To compile this code as a module, choose M here: the
 229         module will be called tcp_probe.
 230
 231 endmenu
 232
 233 endmenu
 234
 235 source "net/ax25/Kconfig"
 236 source "net/can/Kconfig"
 237 source "net/irda/Kconfig"
 238 source "net/bluetooth/Kconfig"
 239 source "net/rxrpc/Kconfig"
 240 source "net/phonet/Kconfig"
 241
 242 config FIB_RULES
 243         bool
 244
 245 menuconfig WIRELESS
 246         bool "Wireless"
 247         depends on !S390
 248         default y
 249
 250 if WIRELESS
 251
 252 source "net/wireless/Kconfig"
 253 source "net/mac80211/Kconfig"
 254
 255 endif # WIRELESS
 256
 257 source "net/wimax/Kconfig"
 258
 259 source "net/rfkill/Kconfig"
 260 source "net/9p/Kconfig"
 261
 262 endif   # if NET