net/Kconfig

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