]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Network configuration | |
3 | # | |
4 | ||
031cf19e | 5 | menuconfig NET |
1da177e4 | 6 | bool "Networking support" |
e9cc8bdd | 7 | select NLATTR |
4cd5773a | 8 | select GENERIC_NET_UTILS |
f89b7755 | 9 | select BPF |
1da177e4 LT |
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 | |
d5950b43 SR |
14 | other computer. |
15 | ||
16 | If you are upgrading from an older kernel, you | |
1da177e4 LT |
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 | ||
6a2e9b73 | 26 | if NET |
1da177e4 | 27 | |
1dacc76d JB |
28 | config WANT_COMPAT_NETLINK_MESSAGES |
29 | bool | |
30 | help | |
31 | This option can be selected by other options that need compat | |
32 | netlink messages. | |
33 | ||
34 | config COMPAT_NETLINK_MESSAGES | |
35 | def_bool y | |
36 | depends on COMPAT | |
40b53d8a | 37 | depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES |
1dacc76d JB |
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 | ||
1cf51900 PN |
48 | config NET_INGRESS |
49 | bool | |
50 | ||
1f211a1b DB |
51 | config NET_EGRESS |
52 | bool | |
53 | ||
6a2e9b73 | 54 | menu "Networking options" |
1da177e4 | 55 | |
6a2e9b73 SR |
56 | source "net/packet/Kconfig" |
57 | source "net/unix/Kconfig" | |
58 | source "net/xfrm/Kconfig" | |
2356f4cb | 59 | source "net/iucv/Kconfig" |
1da177e4 LT |
60 | |
61 | config INET | |
62 | bool "TCP/IP networking" | |
798b2cbf DM |
63 | select CRYPTO |
64 | select CRYPTO_AES | |
1da177e4 LT |
65 | ---help--- |
66 | These are the protocols used on the Internet and on most local | |
67 | Ethernets. It is highly recommended to say Y here (this will enlarge | |
cf80efc2 | 68 | your kernel by about 400 KB), since some programs (e.g. the X window |
1da177e4 LT |
69 | system) use TCP/IP even if your machine is not connected to any |
70 | other computer. You will get the so-called loopback device which | |
71 | allows you to ping yourself (great fun, that!). | |
72 | ||
73 | For an excellent introduction to Linux networking, please read the | |
74 | Linux Networking HOWTO, available from | |
75 | <http://www.tldp.org/docs.html#howto>. | |
76 | ||
77 | If you say Y here and also to "/proc file system support" and | |
78 | "Sysctl support" below, you can change various aspects of the | |
79 | behavior of the TCP/IP code by writing to the (virtual) files in | |
80 | /proc/sys/net/ipv4/*; the options are explained in the file | |
81 | <file:Documentation/networking/ip-sysctl.txt>. | |
82 | ||
83 | Short answer: say Y. | |
84 | ||
6a2e9b73 | 85 | if INET |
1da177e4 | 86 | source "net/ipv4/Kconfig" |
1da177e4 | 87 | source "net/ipv6/Kconfig" |
38c94377 | 88 | source "net/netlabel/Kconfig" |
1da177e4 | 89 | |
6a2e9b73 SR |
90 | endif # if INET |
91 | ||
984bc16c JM |
92 | config NETWORK_SECMARK |
93 | bool "Security Marking" | |
94 | help | |
95 | This enables security marking of network packets, similar | |
96 | to nfmark, but designated for security purposes. | |
97 | If you are unsure how to answer this question, answer N. | |
98 | ||
408eccce DB |
99 | config NET_PTP_CLASSIFY |
100 | def_bool n | |
101 | ||
c1f19b51 RC |
102 | config NETWORK_PHY_TIMESTAMPING |
103 | bool "Timestamping in PHY devices" | |
408eccce | 104 | select NET_PTP_CLASSIFY |
c1f19b51 RC |
105 | help |
106 | This allows timestamping of network packets by PHYs with | |
107 | hardware timestamping capabilities. This option adds some | |
108 | overhead in the transmit and receive paths. | |
109 | ||
110 | If you are unsure how to answer this question, answer N. | |
111 | ||
1da177e4 | 112 | menuconfig NETFILTER |
ef91fd52 | 113 | bool "Network packet filtering framework (Netfilter)" |
1da177e4 LT |
114 | ---help--- |
115 | Netfilter is a framework for filtering and mangling network packets | |
116 | that pass through your Linux box. | |
117 | ||
118 | The most common use of packet filtering is to run your Linux box as | |
119 | a firewall protecting a local network from the Internet. The type of | |
120 | firewall provided by this kernel support is called a "packet | |
121 | filter", which means that it can reject individual network packets | |
122 | based on type, source, destination etc. The other kind of firewall, | |
123 | a "proxy-based" one, is more secure but more intrusive and more | |
124 | bothersome to set up; it inspects the network traffic much more | |
125 | closely, modifies it and has knowledge about the higher level | |
126 | protocols, which a packet filter lacks. Moreover, proxy-based | |
127 | firewalls often require changes to the programs running on the local | |
128 | clients. Proxy-based firewalls don't need support by the kernel, but | |
129 | they are often combined with a packet filter, which only works if | |
130 | you say Y here. | |
131 | ||
132 | You should also say Y here if you intend to use your Linux box as | |
133 | the gateway to the Internet for a local network of machines without | |
134 | globally valid IP addresses. This is called "masquerading": if one | |
135 | of the computers on your local network wants to send something to | |
136 | the outside, your box can "masquerade" as that computer, i.e. it | |
137 | forwards the traffic to the intended outside destination, but | |
138 | modifies the packets to make it look like they came from the | |
139 | firewall box itself. It works both ways: if the outside host | |
140 | replies, the Linux box will silently forward the traffic to the | |
141 | correct local computer. This way, the computers on your local net | |
142 | are completely invisible to the outside world, even though they can | |
143 | reach the outside and can receive replies. It is even possible to | |
144 | run globally visible servers from within a masqueraded local network | |
145 | using a mechanism called portforwarding. Masquerading is also often | |
146 | called NAT (Network Address Translation). | |
147 | ||
148 | Another use of Netfilter is in transparent proxying: if a machine on | |
149 | the local network tries to connect to an outside host, your Linux | |
150 | box can transparently forward the traffic to a local server, | |
151 | typically a caching proxy server. | |
152 | ||
153 | Yet another use of Netfilter is building a bridging firewall. Using | |
154 | a bridge with Network packet filtering enabled makes iptables "see" | |
155 | the bridged traffic. For filtering on the lower network and Ethernet | |
156 | protocols over the bridge, use ebtables (under bridge netfilter | |
157 | configuration). | |
158 | ||
159 | Various modules exist for netfilter which replace the previous | |
160 | masquerading (ipmasqadm), packet filtering (ipchains), transparent | |
161 | proxying, and portforwarding mechanisms. Please see | |
162 | <file:Documentation/Changes> under "iptables" for the location of | |
163 | these packages. | |
164 | ||
1da177e4 LT |
165 | if NETFILTER |
166 | ||
167 | config NETFILTER_DEBUG | |
168 | bool "Network packet filtering debugging" | |
169 | depends on NETFILTER | |
170 | help | |
171 | You can say Y here if you want to get additional messages useful in | |
172 | debugging the netfilter code. | |
173 | ||
33b8e776 PM |
174 | config NETFILTER_ADVANCED |
175 | bool "Advanced netfilter configuration" | |
176 | depends on NETFILTER | |
177 | default y | |
178 | help | |
179 | If you say Y here you can select between all the netfilter modules. | |
692105b8 | 180 | If you say N the more unusual ones will not be shown and the |
33b8e776 PM |
181 | basic ones needed by most people will default to 'M'. |
182 | ||
183 | If unsure, say Y. | |
184 | ||
1da177e4 | 185 | config BRIDGE_NETFILTER |
34666d46 | 186 | tristate "Bridged IP/ARP packets filtering" |
57f5877c | 187 | depends on BRIDGE |
34666d46 | 188 | depends on NETFILTER && INET |
33b8e776 | 189 | depends on NETFILTER_ADVANCED |
34666d46 | 190 | default m |
1da177e4 LT |
191 | ---help--- |
192 | Enabling this option will let arptables resp. iptables see bridged | |
193 | ARP resp. IP traffic. If you want a bridging firewall, you probably | |
194 | want this option enabled. | |
195 | Enabling or disabling this option doesn't enable or disable | |
196 | ebtables. | |
197 | ||
198 | If unsure, say N. | |
199 | ||
9eb0eec7 | 200 | source "net/netfilter/Kconfig" |
1da177e4 LT |
201 | source "net/ipv4/netfilter/Kconfig" |
202 | source "net/ipv6/netfilter/Kconfig" | |
203 | source "net/decnet/netfilter/Kconfig" | |
204 | source "net/bridge/netfilter/Kconfig" | |
205 | ||
206 | endif | |
207 | ||
7c657876 | 208 | source "net/dccp/Kconfig" |
1da177e4 | 209 | source "net/sctp/Kconfig" |
fe17f84f | 210 | source "net/rds/Kconfig" |
1e63e681 | 211 | source "net/tipc/Kconfig" |
6a2e9b73 | 212 | source "net/atm/Kconfig" |
fd558d18 | 213 | source "net/l2tp/Kconfig" |
a19800d7 | 214 | source "net/802/Kconfig" |
6a2e9b73 | 215 | source "net/bridge/Kconfig" |
91da11f8 | 216 | source "net/dsa/Kconfig" |
6a2e9b73 | 217 | source "net/8021q/Kconfig" |
1da177e4 | 218 | source "net/decnet/Kconfig" |
1da177e4 | 219 | source "net/llc/Kconfig" |
1da177e4 | 220 | source "net/ipx/Kconfig" |
1da177e4 | 221 | source "drivers/net/appletalk/Kconfig" |
6a2e9b73 SR |
222 | source "net/x25/Kconfig" |
223 | source "net/lapb/Kconfig" | |
5075138d | 224 | source "net/phonet/Kconfig" |
2c6bed7c | 225 | source "net/6lowpan/Kconfig" |
9ec76716 | 226 | source "net/ieee802154/Kconfig" |
1010f540 | 227 | source "net/mac802154/Kconfig" |
1da177e4 | 228 | source "net/sched/Kconfig" |
2f90b865 | 229 | source "net/dcb/Kconfig" |
1a4240f4 | 230 | source "net/dns_resolver/Kconfig" |
c6c8fea2 | 231 | source "net/batman-adv/Kconfig" |
ccb1352e | 232 | source "net/openvswitch/Kconfig" |
d021c344 | 233 | source "net/vmw_vsock/Kconfig" |
eaaa3139 | 234 | source "net/netlink/Kconfig" |
0d89d203 | 235 | source "net/mpls/Kconfig" |
f421436a | 236 | source "net/hsr/Kconfig" |
007f790c | 237 | source "net/switchdev/Kconfig" |
1b69c6d0 | 238 | source "net/l3mdev/Kconfig" |
bdabad3e | 239 | source "net/qrtr/Kconfig" |
1da177e4 | 240 | |
df334545 | 241 | config RPS |
6341e62b | 242 | bool |
044c8d4b | 243 | depends on SMP && SYSFS |
df334545 ED |
244 | default y |
245 | ||
c445477d | 246 | config RFS_ACCEL |
6341e62b | 247 | bool |
0244ad00 | 248 | depends on RPS |
c445477d BH |
249 | select CPU_RMAP |
250 | default y | |
251 | ||
bf264145 | 252 | config XPS |
6341e62b | 253 | bool |
044c8d4b | 254 | depends on SMP |
bf264145 TH |
255 | default y |
256 | ||
8cb2d8bf GC |
257 | config HWBM |
258 | bool | |
259 | ||
2a56a1fe TH |
260 | config SOCK_CGROUP_DATA |
261 | bool | |
262 | default n | |
263 | ||
86f8515f | 264 | config CGROUP_NET_PRIO |
af636337 | 265 | bool "Network priority cgroup" |
5bc1421e | 266 | depends on CGROUPS |
2a56a1fe | 267 | select SOCK_CGROUP_DATA |
5bc1421e NH |
268 | ---help--- |
269 | Cgroup subsystem for use in assigning processes to network priorities on | |
86f8515f | 270 | a per-interface basis. |
5bc1421e | 271 | |
fe1217c4 | 272 | config CGROUP_NET_CLASSID |
6341e62b | 273 | bool "Network classid cgroup" |
fe1217c4 | 274 | depends on CGROUPS |
2a56a1fe | 275 | select SOCK_CGROUP_DATA |
fe1217c4 DB |
276 | ---help--- |
277 | Cgroup subsystem for use as general purpose socket classid marker that is | |
278 | being used in cls_cgroup and for netfilter matching. | |
279 | ||
e0d1095a | 280 | config NET_RX_BUSY_POLL |
6341e62b | 281 | bool |
89bf1b5a | 282 | default y |
06021292 | 283 | |
114cf580 | 284 | config BQL |
6341e62b | 285 | bool |
114cf580 TH |
286 | depends on SYSFS |
287 | select DQL | |
288 | default y | |
289 | ||
0a14842f ED |
290 | config BPF_JIT |
291 | bool "enable BPF Just In Time compiler" | |
6077776b | 292 | depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT |
b6202f97 | 293 | depends on MODULES |
0a14842f ED |
294 | ---help--- |
295 | Berkeley Packet Filter filtering capabilities are normally handled | |
296 | by an interpreter. This option allows kernel to generate a native | |
297 | code when filter is loaded in memory. This should speedup | |
298 | packet sniffing (libpcap/tcpdump). Note : Admin should enable | |
299 | this feature changing /proc/sys/net/core/bpf_jit_enable | |
300 | ||
99bbc707 | 301 | config NET_FLOW_LIMIT |
6341e62b | 302 | bool |
99bbc707 WB |
303 | depends on RPS |
304 | default y | |
305 | ---help--- | |
306 | The network stack has to drop packets when a receive processing CPU's | |
307 | backlog reaches netdev_max_backlog. If a few out of many active flows | |
308 | generate the vast majority of load, drop their traffic earlier to | |
309 | maintain capacity for the other flows. This feature provides servers | |
310 | with many clients some protection against DoS by a single (spoofed) | |
311 | flow that greatly exceeds average workload. | |
312 | ||
1da177e4 LT |
313 | menu "Network testing" |
314 | ||
315 | config NET_PKTGEN | |
316 | tristate "Packet Generator (USE WITH CAUTION)" | |
ffd756b3 | 317 | depends on INET && PROC_FS |
1da177e4 LT |
318 | ---help--- |
319 | This module will inject preconfigured packets, at a configurable | |
320 | rate, out of a given interface. It is used for network interface | |
321 | stress testing and performance analysis. If you don't understand | |
322 | what was just said, you don't need it: say N. | |
323 | ||
324 | Documentation on how to use the packet generator can be found | |
325 | at <file:Documentation/networking/pktgen.txt>. | |
326 | ||
327 | To compile this code as a module, choose M here: the | |
328 | module will be called pktgen. | |
329 | ||
a42e9d6c SH |
330 | config NET_TCPPROBE |
331 | tristate "TCP connection probing" | |
911f8635 | 332 | depends on INET && PROC_FS && KPROBES |
a42e9d6c SH |
333 | ---help--- |
334 | This module allows for capturing the changes to TCP connection | |
9dadaa19 | 335 | state in response to incoming packets. It is used for debugging |
a42e9d6c SH |
336 | TCP congestion avoidance modules. If you don't understand |
337 | what was just said, you don't need it: say N. | |
338 | ||
82fe7c92 | 339 | Documentation on how to use TCP connection probing can be found |
c996d8b9 MW |
340 | at: |
341 | ||
342 | http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe | |
a42e9d6c SH |
343 | |
344 | To compile this code as a module, choose M here: the | |
345 | module will be called tcp_probe. | |
346 | ||
273ae44b | 347 | config NET_DROP_MONITOR |
cad456d5 | 348 | tristate "Network packet drop alerting service" |
911f8635 | 349 | depends on INET && TRACEPOINTS |
273ae44b NH |
350 | ---help--- |
351 | This feature provides an alerting service to userspace in the | |
352 | event that packets are discarded in the network stack. Alerts | |
353 | are broadcast via netlink socket to any listening user space | |
354 | process. If you don't need network drop alerts, or if you are ok | |
355 | just checking the various proc files and other utilities for | |
356 | drop statistics, say N here. | |
357 | ||
1da177e4 LT |
358 | endmenu |
359 | ||
360 | endmenu | |
361 | ||
1da177e4 | 362 | source "net/ax25/Kconfig" |
0d66548a | 363 | source "net/can/Kconfig" |
1da177e4 | 364 | source "net/irda/Kconfig" |
1da177e4 | 365 | source "net/bluetooth/Kconfig" |
17926a79 | 366 | source "net/rxrpc/Kconfig" |
ab7ac4eb | 367 | source "net/kcm/Kconfig" |
d86b5e0e | 368 | |
14c0b97d TG |
369 | config FIB_RULES |
370 | bool | |
371 | ||
5442060c RD |
372 | menuconfig WIRELESS |
373 | bool "Wireless" | |
f54bfc0e | 374 | depends on !S390 |
5442060c RD |
375 | default y |
376 | ||
377 | if WIRELESS | |
2a5e1c0e JB |
378 | |
379 | source "net/wireless/Kconfig" | |
f0706e82 | 380 | source "net/mac80211/Kconfig" |
2a5e1c0e | 381 | |
5442060c | 382 | endif # WIRELESS |
2a5e1c0e | 383 | |
b0c83ae1 IPG |
384 | source "net/wimax/Kconfig" |
385 | ||
cf4328cd | 386 | source "net/rfkill/Kconfig" |
bd238fb4 | 387 | source "net/9p/Kconfig" |
3908c690 | 388 | source "net/caif/Kconfig" |
3d14c5d2 | 389 | source "net/ceph/Kconfig" |
3e256b8f | 390 | source "net/nfc/Kconfig" |
3908c690 | 391 | |
499a2425 RP |
392 | config LWTUNNEL |
393 | bool "Network light weight tunnels" | |
394 | ---help--- | |
395 | This feature provides an infrastructure to support light weight | |
396 | tunnels like mpls. There is no netdevice associated with a light | |
397 | weight tunnel endpoint. Tunnel encapsulation parameters are stored | |
398 | with light weight tunnel state associated with fib routes. | |
cf4328cd | 399 | |
911362c7 | 400 | config DST_CACHE |
9b246841 | 401 | bool |
911362c7 PA |
402 | default n |
403 | ||
bfcd3a46 JP |
404 | config NET_DEVLINK |
405 | tristate "Network physical/parent device Netlink interface" | |
406 | help | |
407 | Network physical/parent device Netlink interface provides | |
408 | infrastructure to support access to physical chip-wide config and | |
409 | monitoring. | |
410 | ||
3d1cbe83 AB |
411 | config MAY_USE_DEVLINK |
412 | tristate | |
413 | default m if NET_DEVLINK=m | |
414 | default y if NET_DEVLINK=y || NET_DEVLINK=n | |
415 | help | |
416 | Drivers using the devlink infrastructure should have a dependency | |
417 | on MAY_USE_DEVLINK to ensure they do not cause link errors when | |
418 | devlink is a loadable module and the driver using it is built-in. | |
419 | ||
6a2e9b73 | 420 | endif # if NET |
e47b65b0 | 421 | |
6077776b DB |
422 | # Used by archs to tell that they support BPF JIT compiler plus which flavour. |
423 | # Only one of the two can be selected for a specific arch since eBPF JIT supersedes | |
424 | # the cBPF JIT. | |
425 | ||
426 | # Classic BPF JIT (cBPF) | |
427 | config HAVE_CBPF_JIT | |
428 | bool | |
429 | ||
430 | # Extended BPF JIT (eBPF) | |
431 | config HAVE_EBPF_JIT | |
e47b65b0 | 432 | bool |