linux/net/Kconfig
<<
>>
Prefs
   1#
   2# Network configuration
   3#
   4
   5menuconfig NET
   6        bool "Networking support"
   7        select NLATTR
   8        select GENERIC_NET_UTILS
   9        select BPF
  10        ---help---
  11          Unless you really know what you are doing, you should say Y here.
  12          The reason is that some programs need kernel networking support even
  13          when running on a stand-alone machine that isn't connected to any
  14          other computer.
  15
  16          If you are upgrading from an older kernel, you
  17          should consider updating your networking tools too because changes
  18          in the kernel and the tools often go hand in hand. The tools are
  19          contained in the package net-tools, the location and version number
  20          of which are given in <file:Documentation/Changes>.
  21
  22          For a general introduction to Linux networking, it is highly
  23          recommended to read the NET-HOWTO, available from
  24          <http://www.tldp.org/docs.html#howto>.
  25
  26if NET
  27
  28config WANT_COMPAT_NETLINK_MESSAGES
  29        bool
  30        help
  31          This option can be selected by other options that need compat
  32          netlink messages.
  33
  34config COMPAT_NETLINK_MESSAGES
  35        def_bool y
  36        depends on COMPAT
  37        depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
  38        help
  39          This option makes it possible to send different netlink messages
  40          to tasks depending on whether the task is a compat task or not. To
  41          achieve this, you need to set skb_shinfo(skb)->frag_list to the
  42          compat skb before sending the skb, the netlink code will sort out
  43          which message to actually pass to the task.
  44
  45          Newly written code should NEVER need this option but do
  46          compat-independent messages instead!
  47
  48config NET_INGRESS
  49        bool
  50
  51config NET_EGRESS
  52        bool
  53
  54menu "Networking options"
  55
  56source "net/packet/Kconfig"
  57source "net/unix/Kconfig"
  58source "net/tls/Kconfig"
  59source "net/xfrm/Kconfig"
  60source "net/iucv/Kconfig"
  61source "net/smc/Kconfig"
  62source "net/xdp/Kconfig"
  63
  64config INET
  65        bool "TCP/IP networking"
  66        select CRYPTO
  67        select CRYPTO_AES
  68        ---help---
  69          These are the protocols used on the Internet and on most local
  70          Ethernets. It is highly recommended to say Y here (this will enlarge
  71          your kernel by about 400 KB), since some programs (e.g. the X window
  72          system) use TCP/IP even if your machine is not connected to any
  73          other computer. You will get the so-called loopback device which
  74          allows you to ping yourself (great fun, that!).
  75
  76          For an excellent introduction to Linux networking, please read the
  77          Linux Networking HOWTO, available from
  78          <http://www.tldp.org/docs.html#howto>.
  79
  80          If you say Y here and also to "/proc file system support" and
  81          "Sysctl support" below, you can change various aspects of the
  82          behavior of the TCP/IP code by writing to the (virtual) files in
  83          /proc/sys/net/ipv4/*; the options are explained in the file
  84          <file:Documentation/networking/ip-sysctl.txt>.
  85
  86          Short answer: say Y.
  87
  88if INET
  89source "net/ipv4/Kconfig"
  90source "net/ipv6/Kconfig"
  91source "net/netlabel/Kconfig"
  92
  93endif # if INET
  94
  95config NETWORK_SECMARK
  96        bool "Security Marking"
  97        help
  98          This enables security marking of network packets, similar
  99          to nfmark, but designated for security purposes.
 100          If you are unsure how to answer this question, answer N.
 101
 102config NET_PTP_CLASSIFY
 103        def_bool n
 104
 105config NETWORK_PHY_TIMESTAMPING
 106        bool "Timestamping in PHY devices"
 107        select NET_PTP_CLASSIFY
 108        help
 109          This allows timestamping of network packets by PHYs with
 110          hardware timestamping capabilities. This option adds some
 111          overhead in the transmit and receive paths.
 112
 113          If you are unsure how to answer this question, answer N.
 114
 115menuconfig NETFILTER
 116        bool "Network packet filtering framework (Netfilter)"
 117        ---help---
 118          Netfilter is a framework for filtering and mangling network packets
 119          that pass through your Linux box.
 120
 121          The most common use of packet filtering is to run your Linux box as
 122          a firewall protecting a local network from the Internet. The type of
 123          firewall provided by this kernel support is called a "packet
 124          filter", which means that it can reject individual network packets
 125          based on type, source, destination etc. The other kind of firewall,
 126          a "proxy-based" one, is more secure but more intrusive and more
 127          bothersome to set up; it inspects the network traffic much more
 128          closely, modifies it and has knowledge about the higher level
 129          protocols, which a packet filter lacks. Moreover, proxy-based
 130          firewalls often require changes to the programs running on the local
 131          clients. Proxy-based firewalls don't need support by the kernel, but
 132          they are often combined with a packet filter, which only works if
 133          you say Y here.
 134
 135          You should also say Y here if you intend to use your Linux box as
 136          the gateway to the Internet for a local network of machines without
 137          globally valid IP addresses. This is called "masquerading": if one
 138          of the computers on your local network wants to send something to
 139          the outside, your box can "masquerade" as that computer, i.e. it
 140          forwards the traffic to the intended outside destination, but
 141          modifies the packets to make it look like they came from the
 142          firewall box itself. It works both ways: if the outside host
 143          replies, the Linux box will silently forward the traffic to the
 144          correct local computer. This way, the computers on your local net
 145          are completely invisible to the outside world, even though they can
 146          reach the outside and can receive replies. It is even possible to
 147          run globally visible servers from within a masqueraded local network
 148          using a mechanism called portforwarding. Masquerading is also often
 149          called NAT (Network Address Translation).
 150
 151          Another use of Netfilter is in transparent proxying: if a machine on
 152          the local network tries to connect to an outside host, your Linux
 153          box can transparently forward the traffic to a local server,
 154          typically a caching proxy server.
 155
 156          Yet another use of Netfilter is building a bridging firewall. Using
 157          a bridge with Network packet filtering enabled makes iptables "see"
 158          the bridged traffic. For filtering on the lower network and Ethernet
 159          protocols over the bridge, use ebtables (under bridge netfilter
 160          configuration).
 161
 162          Various modules exist for netfilter which replace the previous
 163          masquerading (ipmasqadm), packet filtering (ipchains), transparent
 164          proxying, and portforwarding mechanisms. Please see
 165          <file:Documentation/Changes> under "iptables" for the location of
 166          these packages.
 167
 168if NETFILTER
 169
 170config NETFILTER_ADVANCED
 171        bool "Advanced netfilter configuration"
 172        depends on NETFILTER
 173        default y
 174        help
 175          If you say Y here you can select between all the netfilter modules.
 176          If you say N the more unusual ones will not be shown and the
 177          basic ones needed by most people will default to 'M'.
 178
 179          If unsure, say Y.
 180
 181config BRIDGE_NETFILTER
 182        tristate "Bridged IP/ARP packets filtering"
 183        depends on BRIDGE
 184        depends on NETFILTER && INET
 185        depends on NETFILTER_ADVANCED
 186        select NETFILTER_FAMILY_BRIDGE
 187        default m
 188        ---help---
 189          Enabling this option will let arptables resp. iptables see bridged
 190          ARP resp. IP traffic. If you want a bridging firewall, you probably
 191          want this option enabled.
 192          Enabling or disabling this option doesn't enable or disable
 193          ebtables.
 194
 195          If unsure, say N.
 196
 197source "net/netfilter/Kconfig"
 198source "net/ipv4/netfilter/Kconfig"
 199source "net/ipv6/netfilter/Kconfig"
 200source "net/decnet/netfilter/Kconfig"
 201source "net/bridge/netfilter/Kconfig"
 202
 203endif
 204
 205source "net/bpfilter/Kconfig"
 206
 207source "net/dccp/Kconfig"
 208source "net/sctp/Kconfig"
 209source "net/rds/Kconfig"
 210source "net/tipc/Kconfig"
 211source "net/atm/Kconfig"
 212source "net/l2tp/Kconfig"
 213source "net/802/Kconfig"
 214source "net/bridge/Kconfig"
 215source "net/dsa/Kconfig"
 216source "net/8021q/Kconfig"
 217source "net/decnet/Kconfig"
 218source "net/llc/Kconfig"
 219source "drivers/net/appletalk/Kconfig"
 220source "net/x25/Kconfig"
 221source "net/lapb/Kconfig"
 222source "net/phonet/Kconfig"
 223source "net/6lowpan/Kconfig"
 224source "net/ieee802154/Kconfig"
 225source "net/mac802154/Kconfig"
 226source "net/sched/Kconfig"
 227source "net/dcb/Kconfig"
 228source "net/dns_resolver/Kconfig"
 229source "net/batman-adv/Kconfig"
 230source "net/openvswitch/Kconfig"
 231source "net/vmw_vsock/Kconfig"
 232source "net/netlink/Kconfig"
 233source "net/mpls/Kconfig"
 234source "net/nsh/Kconfig"
 235source "net/hsr/Kconfig"
 236source "net/switchdev/Kconfig"
 237source "net/l3mdev/Kconfig"
 238source "net/qrtr/Kconfig"
 239source "net/ncsi/Kconfig"
 240
 241config RPS
 242        bool
 243        depends on SMP && SYSFS
 244        default y
 245
 246config RFS_ACCEL
 247        bool
 248        depends on RPS
 249        select CPU_RMAP
 250        default y
 251
 252config XPS
 253        bool
 254        depends on SMP
 255        default y
 256
 257config HWBM
 258       bool
 259
 260config CGROUP_NET_PRIO
 261        bool "Network priority cgroup"
 262        depends on CGROUPS
 263        select SOCK_CGROUP_DATA
 264        ---help---
 265          Cgroup subsystem for use in assigning processes to network priorities on
 266          a per-interface basis.
 267
 268config CGROUP_NET_CLASSID
 269        bool "Network classid cgroup"
 270        depends on CGROUPS
 271        select SOCK_CGROUP_DATA
 272        ---help---
 273          Cgroup subsystem for use as general purpose socket classid marker that is
 274          being used in cls_cgroup and for netfilter matching.
 275
 276config NET_RX_BUSY_POLL
 277        bool
 278        default y
 279
 280config BQL
 281        bool
 282        depends on SYSFS
 283        select DQL
 284        default y
 285
 286config BPF_JIT
 287        bool "enable BPF Just In Time compiler"
 288        depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT
 289        depends on MODULES
 290        ---help---
 291          Berkeley Packet Filter filtering capabilities are normally handled
 292          by an interpreter. This option allows kernel to generate a native
 293          code when filter is loaded in memory. This should speedup
 294          packet sniffing (libpcap/tcpdump).
 295
 296          Note, admin should enable this feature changing:
 297          /proc/sys/net/core/bpf_jit_enable
 298          /proc/sys/net/core/bpf_jit_harden   (optional)
 299          /proc/sys/net/core/bpf_jit_kallsyms (optional)
 300
 301config BPF_STREAM_PARSER
 302        bool "enable BPF STREAM_PARSER"
 303        depends on INET
 304        depends on BPF_SYSCALL
 305        depends on CGROUP_BPF
 306        select STREAM_PARSER
 307        select NET_SOCK_MSG
 308        ---help---
 309         Enabling this allows a stream parser to be used with
 310         BPF_MAP_TYPE_SOCKMAP.
 311
 312         BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets.
 313         It can be used to enforce socket policy, implement socket redirects,
 314         etc.
 315
 316config NET_FLOW_LIMIT
 317        bool
 318        depends on RPS
 319        default y
 320        ---help---
 321          The network stack has to drop packets when a receive processing CPU's
 322          backlog reaches netdev_max_backlog. If a few out of many active flows
 323          generate the vast majority of load, drop their traffic earlier to
 324          maintain capacity for the other flows. This feature provides servers
 325          with many clients some protection against DoS by a single (spoofed)
 326          flow that greatly exceeds average workload.
 327
 328menu "Network testing"
 329
 330config NET_PKTGEN
 331        tristate "Packet Generator (USE WITH CAUTION)"
 332        depends on INET && PROC_FS
 333        ---help---
 334          This module will inject preconfigured packets, at a configurable
 335          rate, out of a given interface.  It is used for network interface
 336          stress testing and performance analysis.  If you don't understand
 337          what was just said, you don't need it: say N.
 338
 339          Documentation on how to use the packet generator can be found
 340          at <file:Documentation/networking/pktgen.txt>.
 341
 342          To compile this code as a module, choose M here: the
 343          module will be called pktgen.
 344
 345config NET_DROP_MONITOR
 346        tristate "Network packet drop alerting service"
 347        depends on INET && TRACEPOINTS
 348        ---help---
 349        This feature provides an alerting service to userspace in the
 350        event that packets are discarded in the network stack.  Alerts
 351        are broadcast via netlink socket to any listening user space
 352        process.  If you don't need network drop alerts, or if you are ok
 353        just checking the various proc files and other utilities for
 354        drop statistics, say N here.
 355
 356endmenu
 357
 358endmenu
 359
 360source "net/ax25/Kconfig"
 361source "net/can/Kconfig"
 362source "net/bluetooth/Kconfig"
 363source "net/rxrpc/Kconfig"
 364source "net/kcm/Kconfig"
 365source "net/strparser/Kconfig"
 366
 367config FIB_RULES
 368        bool
 369
 370menuconfig WIRELESS
 371        bool "Wireless"
 372        depends on !S390
 373        default y
 374
 375if WIRELESS
 376
 377source "net/wireless/Kconfig"
 378source "net/mac80211/Kconfig"
 379
 380endif # WIRELESS
 381
 382source "net/wimax/Kconfig"
 383
 384source "net/rfkill/Kconfig"
 385source "net/9p/Kconfig"
 386source "net/caif/Kconfig"
 387source "net/ceph/Kconfig"
 388source "net/nfc/Kconfig"
 389source "net/psample/Kconfig"
 390source "net/ife/Kconfig"
 391
 392config LWTUNNEL
 393        bool "Network light weight tunnels"
 394        ---help---
 395          This feature provides an infrastructure to support light weight
 396          tunnels like mpls. There is no netdevice associated with a light
 397          weight tunnel endpoint. Tunnel encapsulation parameters are stored
 398          with light weight tunnel state associated with fib routes.
 399
 400config LWTUNNEL_BPF
 401        bool "Execute BPF program as route nexthop action"
 402        depends on LWTUNNEL
 403        default y if LWTUNNEL=y
 404        ---help---
 405          Allows to run BPF programs as a nexthop action following a route
 406          lookup for incoming and outgoing packets.
 407
 408config DST_CACHE
 409        bool
 410        default n
 411
 412config GRO_CELLS
 413        bool
 414        default n
 415
 416config SOCK_VALIDATE_XMIT
 417        bool
 418
 419config NET_SOCK_MSG
 420        bool
 421        default n
 422        help
 423          The NET_SOCK_MSG provides a framework for plain sockets (e.g. TCP) or
 424          ULPs (upper layer modules, e.g. TLS) to process L7 application data
 425          with the help of BPF programs.
 426
 427config NET_DEVLINK
 428        tristate "Network physical/parent device Netlink interface"
 429        help
 430          Network physical/parent device Netlink interface provides
 431          infrastructure to support access to physical chip-wide config and
 432          monitoring.
 433
 434config MAY_USE_DEVLINK
 435        tristate
 436        default m if NET_DEVLINK=m
 437        default y if NET_DEVLINK=y || NET_DEVLINK=n
 438        help
 439          Drivers using the devlink infrastructure should have a dependency
 440          on MAY_USE_DEVLINK to ensure they do not cause link errors when
 441          devlink is a loadable module and the driver using it is built-in.
 442
 443config PAGE_POOL
 444       bool
 445
 446config FAILOVER
 447        tristate "Generic failover module"
 448        help
 449          The failover module provides a generic interface for paravirtual
 450          drivers to register a netdev and a set of ops with a failover
 451          instance. The ops are used as event handlers that get called to
 452          handle netdev register/unregister/link change/name change events
 453          on slave pci ethernet devices with the same mac address as the
 454          failover netdev. This enables paravirtual drivers to use a
 455          VF as an accelerated low latency datapath. It also allows live
 456          migration of VMs with direct attached VFs by failing over to the
 457          paravirtual datapath when the VF is unplugged.
 458
 459endif   # if NET
 460
 461# Used by archs to tell that they support BPF JIT compiler plus which flavour.
 462# Only one of the two can be selected for a specific arch since eBPF JIT supersedes
 463# the cBPF JIT.
 464
 465# Classic BPF JIT (cBPF)
 466config HAVE_CBPF_JIT
 467        bool
 468
 469# Extended BPF JIT (eBPF)
 470config HAVE_EBPF_JIT
 471        bool
 472