net/Kconfig

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