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