2 # Network configuration
6 bool "Networking support"
9 Unless you really know what you are doing, you should say Y here.
10 The reason is that some programs need kernel networking support even
11 when running on a stand-alone machine that isn't connected to any
14 If you are upgrading from an older kernel, you
15 should consider updating your networking tools too because changes
16 in the kernel and the tools often go hand in hand. The tools are
17 contained in the package net-tools, the location and version number
18 of which are given in <file:Documentation/Changes>.
20 For a general introduction to Linux networking, it is highly
21 recommended to read the NET-HOWTO, available from
22 <http://www.tldp.org/docs.html#howto>.
27 bool "Netlink: mmaped IO"
29 This option enables support for memory mapped netlink IO. This
30 reduces overhead by avoiding copying data between kernel- and
35 config WANT_COMPAT_NETLINK_MESSAGES
38 This option can be selected by other options that need compat
41 config COMPAT_NETLINK_MESSAGES
44 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
46 This option makes it possible to send different netlink messages
47 to tasks depending on whether the task is a compat task or not. To
48 achieve this, you need to set skb_shinfo(skb)->frag_list to the
49 compat skb before sending the skb, the netlink code will sort out
50 which message to actually pass to the task.
52 Newly written code should NEVER need this option but do
53 compat-independent messages instead!
55 menu "Networking options"
57 source "net/packet/Kconfig"
58 source "net/unix/Kconfig"
59 source "net/xfrm/Kconfig"
60 source "net/iucv/Kconfig"
63 bool "TCP/IP networking"
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!).
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>.
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>.
87 source "net/ipv4/Kconfig"
88 source "net/ipv6/Kconfig"
89 source "net/netlabel/Kconfig"
93 config NETWORK_SECMARK
94 bool "Security Marking"
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.
100 config NETWORK_PHY_TIMESTAMPING
101 bool "Timestamping in PHY devices"
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.
107 If you are unsure how to answer this question, answer N.
110 bool "Network packet filtering framework (Netfilter)"
112 Netfilter is a framework for filtering and mangling network packets
113 that pass through your Linux box.
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
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).
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.
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
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
164 config NETFILTER_DEBUG
165 bool "Network packet filtering debugging"
168 You can say Y here if you want to get additional messages useful in
169 debugging the netfilter code.
171 config NETFILTER_ADVANCED
172 bool "Advanced netfilter configuration"
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'.
182 config BRIDGE_NETFILTER
183 bool "Bridged IP/ARP packets filtering"
184 depends on BRIDGE && NETFILTER && INET
185 depends on NETFILTER_ADVANCED
188 Enabling this option will let arptables resp. iptables see bridged
189 ARP resp. IP traffic. If you want a bridging firewall, you probably
190 want this option enabled.
191 Enabling or disabling this option doesn't enable or disable
196 source "net/netfilter/Kconfig"
197 source "net/ipv4/netfilter/Kconfig"
198 source "net/ipv6/netfilter/Kconfig"
199 source "net/decnet/netfilter/Kconfig"
200 source "net/bridge/netfilter/Kconfig"
204 source "net/dccp/Kconfig"
205 source "net/sctp/Kconfig"
206 source "net/rds/Kconfig"
207 source "net/tipc/Kconfig"
208 source "net/atm/Kconfig"
209 source "net/l2tp/Kconfig"
210 source "net/802/Kconfig"
211 source "net/bridge/Kconfig"
212 source "net/dsa/Kconfig"
213 source "net/8021q/Kconfig"
214 source "net/decnet/Kconfig"
215 source "net/llc/Kconfig"
216 source "net/ipx/Kconfig"
217 source "drivers/net/appletalk/Kconfig"
218 source "net/x25/Kconfig"
219 source "net/lapb/Kconfig"
220 source "net/phonet/Kconfig"
221 source "net/ieee802154/Kconfig"
222 source "net/mac802154/Kconfig"
223 source "net/sched/Kconfig"
224 source "net/dcb/Kconfig"
225 source "net/dns_resolver/Kconfig"
226 source "net/batman-adv/Kconfig"
227 source "net/openvswitch/Kconfig"
228 source "net/vmw_vsock/Kconfig"
229 source "net/netlink/Kconfig"
233 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
238 depends on RPS && GENERIC_HARDIRQS
244 depends on SMP && USE_GENERIC_SMP_HELPERS
247 config NETPRIO_CGROUP
248 tristate "Network priority cgroup"
251 Cgroup subsystem for use in assigning processes to network priorities on
252 a per-interface basis
261 bool "enable BPF Just In Time compiler"
262 depends on HAVE_BPF_JIT
265 Berkeley Packet Filter filtering capabilities are normally handled
266 by an interpreter. This option allows kernel to generate a native
267 code when filter is loaded in memory. This should speedup
268 packet sniffing (libpcap/tcpdump). Note : Admin should enable
269 this feature changing /proc/sys/net/core/bpf_jit_enable
271 menu "Network testing"
274 tristate "Packet Generator (USE WITH CAUTION)"
277 This module will inject preconfigured packets, at a configurable
278 rate, out of a given interface. It is used for network interface
279 stress testing and performance analysis. If you don't understand
280 what was just said, you don't need it: say N.
282 Documentation on how to use the packet generator can be found
283 at <file:Documentation/networking/pktgen.txt>.
285 To compile this code as a module, choose M here: the
286 module will be called pktgen.
289 tristate "TCP connection probing"
290 depends on INET && PROC_FS && KPROBES
292 This module allows for capturing the changes to TCP connection
293 state in response to incoming packets. It is used for debugging
294 TCP congestion avoidance modules. If you don't understand
295 what was just said, you don't need it: say N.
297 Documentation on how to use TCP connection probing can be found
300 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
302 To compile this code as a module, choose M here: the
303 module will be called tcp_probe.
305 config NET_DROP_MONITOR
306 tristate "Network packet drop alerting service"
307 depends on INET && TRACEPOINTS
309 This feature provides an alerting service to userspace in the
310 event that packets are discarded in the network stack. Alerts
311 are broadcast via netlink socket to any listening user space
312 process. If you don't need network drop alerts, or if you are ok
313 just checking the various proc files and other utilities for
314 drop statistics, say N here.
320 source "net/ax25/Kconfig"
321 source "net/can/Kconfig"
322 source "net/irda/Kconfig"
323 source "net/bluetooth/Kconfig"
324 source "net/rxrpc/Kconfig"
336 source "net/wireless/Kconfig"
337 source "net/mac80211/Kconfig"
341 source "net/wimax/Kconfig"
343 source "net/rfkill/Kconfig"
344 source "net/9p/Kconfig"
345 source "net/caif/Kconfig"
346 source "net/ceph/Kconfig"
347 source "net/nfc/Kconfig"
352 # Used by archs to tell that they support BPF_JIT