2 # Network configuration
6 bool "Networking support"
8 select GENERIC_NET_UTILS
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
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>.
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>.
28 config WANT_COMPAT_NETLINK_MESSAGES
31 This option can be selected by other options that need compat
34 config COMPAT_NETLINK_MESSAGES
37 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
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.
45 Newly written code should NEVER need this option but do
46 compat-independent messages instead!
54 menu "Networking options"
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"
64 bool "TCP/IP networking"
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!).
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>.
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>.
88 source "net/ipv4/Kconfig"
89 source "net/ipv6/Kconfig"
90 source "net/netlabel/Kconfig"
94 config NETWORK_SECMARK
95 bool "Security Marking"
97 This enables security marking of network packets, similar
98 to nfmark, but designated for security purposes.
99 If you are unsure how to answer this question, answer N.
101 config NET_PTP_CLASSIFY
104 config NETWORK_PHY_TIMESTAMPING
105 bool "Timestamping in PHY devices"
106 select NET_PTP_CLASSIFY
108 This allows timestamping of network packets by PHYs with
109 hardware timestamping capabilities. This option adds some
110 overhead in the transmit and receive paths.
112 If you are unsure how to answer this question, answer N.
115 bool "Network packet filtering framework (Netfilter)"
117 Netfilter is a framework for filtering and mangling network packets
118 that pass through your Linux box.
120 The most common use of packet filtering is to run your Linux box as
121 a firewall protecting a local network from the Internet. The type of
122 firewall provided by this kernel support is called a "packet
123 filter", which means that it can reject individual network packets
124 based on type, source, destination etc. The other kind of firewall,
125 a "proxy-based" one, is more secure but more intrusive and more
126 bothersome to set up; it inspects the network traffic much more
127 closely, modifies it and has knowledge about the higher level
128 protocols, which a packet filter lacks. Moreover, proxy-based
129 firewalls often require changes to the programs running on the local
130 clients. Proxy-based firewalls don't need support by the kernel, but
131 they are often combined with a packet filter, which only works if
134 You should also say Y here if you intend to use your Linux box as
135 the gateway to the Internet for a local network of machines without
136 globally valid IP addresses. This is called "masquerading": if one
137 of the computers on your local network wants to send something to
138 the outside, your box can "masquerade" as that computer, i.e. it
139 forwards the traffic to the intended outside destination, but
140 modifies the packets to make it look like they came from the
141 firewall box itself. It works both ways: if the outside host
142 replies, the Linux box will silently forward the traffic to the
143 correct local computer. This way, the computers on your local net
144 are completely invisible to the outside world, even though they can
145 reach the outside and can receive replies. It is even possible to
146 run globally visible servers from within a masqueraded local network
147 using a mechanism called portforwarding. Masquerading is also often
148 called NAT (Network Address Translation).
150 Another use of Netfilter is in transparent proxying: if a machine on
151 the local network tries to connect to an outside host, your Linux
152 box can transparently forward the traffic to a local server,
153 typically a caching proxy server.
155 Yet another use of Netfilter is building a bridging firewall. Using
156 a bridge with Network packet filtering enabled makes iptables "see"
157 the bridged traffic. For filtering on the lower network and Ethernet
158 protocols over the bridge, use ebtables (under bridge netfilter
161 Various modules exist for netfilter which replace the previous
162 masquerading (ipmasqadm), packet filtering (ipchains), transparent
163 proxying, and portforwarding mechanisms. Please see
164 <file:Documentation/Changes> under "iptables" for the location of
169 config NETFILTER_ADVANCED
170 bool "Advanced netfilter configuration"
174 If you say Y here you can select between all the netfilter modules.
175 If you say N the more unusual ones will not be shown and the
176 basic ones needed by most people will default to 'M'.
180 config BRIDGE_NETFILTER
181 tristate "Bridged IP/ARP packets filtering"
183 depends on NETFILTER && INET
184 depends on NETFILTER_ADVANCED
187 Enabling this option will let arptables resp. iptables see bridged
188 ARP resp. IP traffic. If you want a bridging firewall, you probably
189 want this option enabled.
190 Enabling or disabling this option doesn't enable or disable
195 source "net/netfilter/Kconfig"
196 source "net/ipv4/netfilter/Kconfig"
197 source "net/ipv6/netfilter/Kconfig"
198 source "net/decnet/netfilter/Kconfig"
199 source "net/bridge/netfilter/Kconfig"
203 source "net/dccp/Kconfig"
204 source "net/sctp/Kconfig"
205 source "net/rds/Kconfig"
206 source "net/tipc/Kconfig"
207 source "net/atm/Kconfig"
208 source "net/l2tp/Kconfig"
209 source "net/802/Kconfig"
210 source "net/bridge/Kconfig"
211 source "net/dsa/Kconfig"
212 source "net/8021q/Kconfig"
213 source "net/decnet/Kconfig"
214 source "net/llc/Kconfig"
215 source "net/ipx/Kconfig"
216 source "drivers/net/appletalk/Kconfig"
217 source "net/x25/Kconfig"
218 source "net/lapb/Kconfig"
219 source "net/phonet/Kconfig"
220 source "net/6lowpan/Kconfig"
221 source "net/ieee802154/Kconfig"
222 source "net/mac802154/Kconfig"
223 source "net/sched/Kconfig"
224 source "net/dcb/Kconfig"
225 source "net/dns_resolver/Kconfig"
226 source "net/batman-adv/Kconfig"
227 source "net/openvswitch/Kconfig"
228 source "net/vmw_vsock/Kconfig"
229 source "net/netlink/Kconfig"
230 source "net/mpls/Kconfig"
231 source "net/nsh/Kconfig"
232 source "net/hsr/Kconfig"
233 source "net/switchdev/Kconfig"
234 source "net/l3mdev/Kconfig"
235 source "net/qrtr/Kconfig"
236 source "net/ncsi/Kconfig"
240 depends on SMP && SYSFS
257 config CGROUP_NET_PRIO
258 bool "Network priority cgroup"
260 select SOCK_CGROUP_DATA
262 Cgroup subsystem for use in assigning processes to network priorities on
263 a per-interface basis.
265 config CGROUP_NET_CLASSID
266 bool "Network classid cgroup"
268 select SOCK_CGROUP_DATA
270 Cgroup subsystem for use as general purpose socket classid marker that is
271 being used in cls_cgroup and for netfilter matching.
273 config NET_RX_BUSY_POLL
284 bool "enable BPF Just In Time compiler"
285 depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT
288 Berkeley Packet Filter filtering capabilities are normally handled
289 by an interpreter. This option allows kernel to generate a native
290 code when filter is loaded in memory. This should speedup
291 packet sniffing (libpcap/tcpdump).
293 Note, admin should enable this feature changing:
294 /proc/sys/net/core/bpf_jit_enable
295 /proc/sys/net/core/bpf_jit_harden (optional)
296 /proc/sys/net/core/bpf_jit_kallsyms (optional)
298 config BPF_STREAM_PARSER
299 bool "enable BPF STREAM_PARSER"
300 depends on BPF_SYSCALL
303 Enabling this allows a stream parser to be used with
304 BPF_MAP_TYPE_SOCKMAP.
306 BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets.
307 It can be used to enforce socket policy, implement socket redirects,
310 config NET_FLOW_LIMIT
315 The network stack has to drop packets when a receive processing CPU's
316 backlog reaches netdev_max_backlog. If a few out of many active flows
317 generate the vast majority of load, drop their traffic earlier to
318 maintain capacity for the other flows. This feature provides servers
319 with many clients some protection against DoS by a single (spoofed)
320 flow that greatly exceeds average workload.
322 menu "Network testing"
325 tristate "Packet Generator (USE WITH CAUTION)"
326 depends on INET && PROC_FS
328 This module will inject preconfigured packets, at a configurable
329 rate, out of a given interface. It is used for network interface
330 stress testing and performance analysis. If you don't understand
331 what was just said, you don't need it: say N.
333 Documentation on how to use the packet generator can be found
334 at <file:Documentation/networking/pktgen.txt>.
336 To compile this code as a module, choose M here: the
337 module will be called pktgen.
340 tristate "TCP connection probing"
341 depends on INET && PROC_FS && KPROBES
343 This module allows for capturing the changes to TCP connection
344 state in response to incoming packets. It is used for debugging
345 TCP congestion avoidance modules. If you don't understand
346 what was just said, you don't need it: say N.
348 Documentation on how to use TCP connection probing can be found
351 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
353 To compile this code as a module, choose M here: the
354 module will be called tcp_probe.
356 config NET_DROP_MONITOR
357 tristate "Network packet drop alerting service"
358 depends on INET && TRACEPOINTS
360 This feature provides an alerting service to userspace in the
361 event that packets are discarded in the network stack. Alerts
362 are broadcast via netlink socket to any listening user space
363 process. If you don't need network drop alerts, or if you are ok
364 just checking the various proc files and other utilities for
365 drop statistics, say N here.
371 source "net/ax25/Kconfig"
372 source "net/can/Kconfig"
373 source "net/bluetooth/Kconfig"
374 source "net/rxrpc/Kconfig"
375 source "net/kcm/Kconfig"
376 source "net/strparser/Kconfig"
388 source "net/wireless/Kconfig"
389 source "net/mac80211/Kconfig"
393 source "net/wimax/Kconfig"
395 source "net/rfkill/Kconfig"
396 source "net/9p/Kconfig"
397 source "net/caif/Kconfig"
398 source "net/ceph/Kconfig"
399 source "net/nfc/Kconfig"
400 source "net/psample/Kconfig"
401 source "net/ife/Kconfig"
404 bool "Network light weight tunnels"
406 This feature provides an infrastructure to support light weight
407 tunnels like mpls. There is no netdevice associated with a light
408 weight tunnel endpoint. Tunnel encapsulation parameters are stored
409 with light weight tunnel state associated with fib routes.
412 bool "Execute BPF program as route nexthop action"
414 default y if LWTUNNEL=y
416 Allows to run BPF programs as a nexthop action following a route
417 lookup for incoming and outgoing packets.
428 tristate "Network physical/parent device Netlink interface"
430 Network physical/parent device Netlink interface provides
431 infrastructure to support access to physical chip-wide config and
434 config MAY_USE_DEVLINK
436 default m if NET_DEVLINK=m
437 default y if NET_DEVLINK=y || NET_DEVLINK=n
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.
445 # Used by archs to tell that they support BPF JIT compiler plus which flavour.
446 # Only one of the two can be selected for a specific arch since eBPF JIT supersedes
449 # Classic BPF JIT (cBPF)
453 # Extended BPF JIT (eBPF)