net/Kconfig

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