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