linux/net/Kconfig
<<
>>
Prefs
   1#
   2# Network configuration
   3#
   4
   5menuconfig 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
  24if NET
  25
  26config WANT_COMPAT_NETLINK_MESSAGES
  27        bool
  28        help
  29          This option can be selected by other options that need compat
  30          netlink messages.
  31
  32config 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
  46menu "Networking options"
  47
  48source "net/packet/Kconfig"
  49source "net/unix/Kconfig"
  50source "net/xfrm/Kconfig"
  51source "net/iucv/Kconfig"
  52
  53config 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
  77if INET
  78source "net/ipv4/Kconfig"
  79source "net/ipv6/Kconfig"
  80source "net/netlabel/Kconfig"
  81
  82endif # if INET
  83
  84config 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
  91config NETWORK_PHY_TIMESTAMPING
  92        bool "Timestamping in PHY devices"
  93        depends on EXPERIMENTAL
  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
 101menuconfig 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
 154if NETFILTER
 155
 156config 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
 163config 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
 174config 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
 188source "net/netfilter/Kconfig"
 189source "net/ipv4/netfilter/Kconfig"
 190source "net/ipv6/netfilter/Kconfig"
 191source "net/decnet/netfilter/Kconfig"
 192source "net/bridge/netfilter/Kconfig"
 193
 194endif
 195
 196source "net/dccp/Kconfig"
 197source "net/sctp/Kconfig"
 198source "net/rds/Kconfig"
 199source "net/tipc/Kconfig"
 200source "net/atm/Kconfig"
 201source "net/l2tp/Kconfig"
 202source "net/802/Kconfig"
 203source "net/bridge/Kconfig"
 204source "net/dsa/Kconfig"
 205source "net/8021q/Kconfig"
 206source "net/decnet/Kconfig"
 207source "net/llc/Kconfig"
 208source "net/ipx/Kconfig"
 209source "drivers/net/appletalk/Kconfig"
 210source "net/x25/Kconfig"
 211source "net/lapb/Kconfig"
 212source "net/wanrouter/Kconfig"
 213source "net/phonet/Kconfig"
 214source "net/ieee802154/Kconfig"
 215source "net/mac802154/Kconfig"
 216source "net/sched/Kconfig"
 217source "net/dcb/Kconfig"
 218source "net/dns_resolver/Kconfig"
 219source "net/batman-adv/Kconfig"
 220source "net/openvswitch/Kconfig"
 221
 222config RPS
 223        boolean
 224        depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
 225        default y
 226
 227config RFS_ACCEL
 228        boolean
 229        depends on RPS && GENERIC_HARDIRQS
 230        select CPU_RMAP
 231        default y
 232
 233config XPS
 234        boolean
 235        depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
 236        default y
 237
 238config 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
 245config BQL
 246        boolean
 247        depends on SYSFS
 248        select DQL
 249        default y
 250
 251config 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
 262menu "Network testing"
 263
 264config 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
 279config NET_TCPPROBE
 280        tristate "TCP connection probing"
 281        depends on INET && EXPERIMENTAL && 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
 296config NET_DROP_MONITOR
 297        tristate "Network packet drop alerting service"
 298        depends on INET && EXPERIMENTAL && 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
 307endmenu
 308
 309endmenu
 310
 311source "net/ax25/Kconfig"
 312source "net/can/Kconfig"
 313source "net/irda/Kconfig"
 314source "net/bluetooth/Kconfig"
 315source "net/rxrpc/Kconfig"
 316
 317config FIB_RULES
 318        bool
 319
 320menuconfig WIRELESS
 321        bool "Wireless"
 322        depends on !S390
 323        default y
 324
 325if WIRELESS
 326
 327source "net/wireless/Kconfig"
 328source "net/mac80211/Kconfig"
 329
 330endif # WIRELESS
 331
 332source "net/wimax/Kconfig"
 333
 334source "net/rfkill/Kconfig"
 335source "net/9p/Kconfig"
 336source "net/caif/Kconfig"
 337source "net/ceph/Kconfig"
 338source "net/nfc/Kconfig"
 339
 340
 341endif   # if NET
 342
 343# Used by archs to tell that they support BPF_JIT
 344config HAVE_BPF_JIT
 345        bool
 346
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.