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/dccp/Kconfig" 206source "net/sctp/Kconfig" 207source "net/rds/Kconfig" 208source "net/tipc/Kconfig" 209source "net/atm/Kconfig" 210source "net/l2tp/Kconfig" 211source "net/802/Kconfig" 212source "net/bridge/Kconfig" 213source "net/dsa/Kconfig" 214source "net/8021q/Kconfig" 215source "net/decnet/Kconfig" 216source "net/llc/Kconfig" 217source "drivers/net/appletalk/Kconfig" 218source "net/x25/Kconfig" 219source "net/lapb/Kconfig" 220source "net/phonet/Kconfig" 221source "net/6lowpan/Kconfig" 222source "net/ieee802154/Kconfig" 223source "net/mac802154/Kconfig" 224source "net/sched/Kconfig" 225source "net/dcb/Kconfig" 226source "net/dns_resolver/Kconfig" 227source "net/batman-adv/Kconfig" 228source "net/openvswitch/Kconfig" 229source "net/vmw_vsock/Kconfig" 230source "net/netlink/Kconfig" 231source "net/mpls/Kconfig" 232source "net/nsh/Kconfig" 233source "net/hsr/Kconfig" 234source "net/switchdev/Kconfig" 235source "net/l3mdev/Kconfig" 236source "net/qrtr/Kconfig" 237source "net/ncsi/Kconfig" 238 239config RPS 240 bool 241 depends on SMP && SYSFS 242 default y 243 244config RFS_ACCEL 245 bool 246 depends on RPS 247 select CPU_RMAP 248 default y 249 250config XPS 251 bool 252 depends on SMP 253 default y 254 255config HWBM 256 bool 257 258config CGROUP_NET_PRIO 259 bool "Network priority cgroup" 260 depends on CGROUPS 261 select SOCK_CGROUP_DATA 262 ---help--- 263 Cgroup subsystem for use in assigning processes to network priorities on 264 a per-interface basis. 265 266config CGROUP_NET_CLASSID 267 bool "Network classid cgroup" 268 depends on CGROUPS 269 select SOCK_CGROUP_DATA 270 ---help--- 271 Cgroup subsystem for use as general purpose socket classid marker that is 272 being used in cls_cgroup and for netfilter matching. 273 274config NET_RX_BUSY_POLL 275 bool 276 default y 277 278config BQL 279 bool 280 depends on SYSFS 281 select DQL 282 default y 283 284config BPF_JIT 285 bool "enable BPF Just In Time compiler" 286 depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT 287 depends on MODULES 288 ---help--- 289 Berkeley Packet Filter filtering capabilities are normally handled 290 by an interpreter. This option allows kernel to generate a native 291 code when filter is loaded in memory. This should speedup 292 packet sniffing (libpcap/tcpdump). 293 294 Note, admin should enable this feature changing: 295 /proc/sys/net/core/bpf_jit_enable 296 /proc/sys/net/core/bpf_jit_harden (optional) 297 /proc/sys/net/core/bpf_jit_kallsyms (optional) 298 299config BPF_STREAM_PARSER 300 bool "enable BPF STREAM_PARSER" 301 depends on BPF_SYSCALL 302 select STREAM_PARSER 303 ---help--- 304 Enabling this allows a stream parser to be used with 305 BPF_MAP_TYPE_SOCKMAP. 306 307 BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets. 308 It can be used to enforce socket policy, implement socket redirects, 309 etc. 310 311config NET_FLOW_LIMIT 312 bool 313 depends on RPS 314 default y 315 ---help--- 316 The network stack has to drop packets when a receive processing CPU's 317 backlog reaches netdev_max_backlog. If a few out of many active flows 318 generate the vast majority of load, drop their traffic earlier to 319 maintain capacity for the other flows. This feature provides servers 320 with many clients some protection against DoS by a single (spoofed) 321 flow that greatly exceeds average workload. 322 323menu "Network testing" 324 325config NET_PKTGEN 326 tristate "Packet Generator (USE WITH CAUTION)" 327 depends on INET && PROC_FS 328 ---help--- 329 This module will inject preconfigured packets, at a configurable 330 rate, out of a given interface. It is used for network interface 331 stress testing and performance analysis. If you don't understand 332 what was just said, you don't need it: say N. 333 334 Documentation on how to use the packet generator can be found 335 at <file:Documentation/networking/pktgen.txt>. 336 337 To compile this code as a module, choose M here: the 338 module will be called pktgen. 339 340config NET_DROP_MONITOR 341 tristate "Network packet drop alerting service" 342 depends on INET && TRACEPOINTS 343 ---help--- 344 This feature provides an alerting service to userspace in the 345 event that packets are discarded in the network stack. Alerts 346 are broadcast via netlink socket to any listening user space 347 process. If you don't need network drop alerts, or if you are ok 348 just checking the various proc files and other utilities for 349 drop statistics, say N here. 350 351endmenu 352 353endmenu 354 355source "net/ax25/Kconfig" 356source "net/can/Kconfig" 357source "net/bluetooth/Kconfig" 358source "net/rxrpc/Kconfig" 359source "net/kcm/Kconfig" 360source "net/strparser/Kconfig" 361 362config FIB_RULES 363 bool 364 365menuconfig WIRELESS 366 bool "Wireless" 367 depends on !S390 368 default y 369 370if WIRELESS 371 372source "net/wireless/Kconfig" 373source "net/mac80211/Kconfig" 374 375endif # WIRELESS 376 377source "net/wimax/Kconfig" 378 379source "net/rfkill/Kconfig" 380source "net/9p/Kconfig" 381source "net/caif/Kconfig" 382source "net/ceph/Kconfig" 383source "net/nfc/Kconfig" 384source "net/psample/Kconfig" 385source "net/ife/Kconfig" 386 387config LWTUNNEL 388 bool "Network light weight tunnels" 389 ---help--- 390 This feature provides an infrastructure to support light weight 391 tunnels like mpls. There is no netdevice associated with a light 392 weight tunnel endpoint. Tunnel encapsulation parameters are stored 393 with light weight tunnel state associated with fib routes. 394 395config LWTUNNEL_BPF 396 bool "Execute BPF program as route nexthop action" 397 depends on LWTUNNEL 398 default y if LWTUNNEL=y 399 ---help--- 400 Allows to run BPF programs as a nexthop action following a route 401 lookup for incoming and outgoing packets. 402 403config DST_CACHE 404 bool 405 default n 406 407config GRO_CELLS 408 bool 409 default n 410 411config NET_DEVLINK 412 tristate "Network physical/parent device Netlink interface" 413 help 414 Network physical/parent device Netlink interface provides 415 infrastructure to support access to physical chip-wide config and 416 monitoring. 417 418config MAY_USE_DEVLINK 419 tristate 420 default m if NET_DEVLINK=m 421 default y if NET_DEVLINK=y || NET_DEVLINK=n 422 help 423 Drivers using the devlink infrastructure should have a dependency 424 on MAY_USE_DEVLINK to ensure they do not cause link errors when 425 devlink is a loadable module and the driver using it is built-in. 426 427config PAGE_POOL 428 bool 429 430endif # if NET 431 432# Used by archs to tell that they support BPF JIT compiler plus which flavour. 433# Only one of the two can be selected for a specific arch since eBPF JIT supersedes 434# the cBPF JIT. 435 436# Classic BPF JIT (cBPF) 437config HAVE_CBPF_JIT 438 bool 439 440# Extended BPF JIT (eBPF) 441config HAVE_EBPF_JIT 442 bool 443