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