~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/net/Kconfig

Version: ~ [ linux-6.1-rc7 ] ~ [ linux-6.0.10 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.80 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.156 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.225 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.267 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.300 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.334 ] ~ [ linux-4.8.17 ] ~ [ linux-4.7.10 ] ~ [ linux-4.6.7 ] ~ [ linux-4.5.7 ] ~ [ linux-4.4.302 ] ~ [ linux-4.3.6 ] ~ [ linux-4.2.8 ] ~ [ linux-4.1.52 ] ~ [ linux-4.0.9 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

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

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | Wiki (Japanese) | Wiki (English) | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

osdn.jp