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