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>.
26 config WANT_COMPAT_NETLINK_MESSAGES
29 This option can be selected by other options that need compat
32 config COMPAT_NETLINK_MESSAGES
35 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
37 This option makes it possible to send different netlink messages
38 to tasks depending on whether the task is a compat task or not. To
39 achieve this, you need to set skb_shinfo(skb)->frag_list to the
40 compat skb before sending the skb, the netlink code will sort out
41 which message to actually pass to the task.
43 Newly written code should NEVER need this option but do
44 compat-independent messages instead!
46 menu "Networking options"
48 source "net/packet/Kconfig"
49 source "net/unix/Kconfig"
50 source "net/xfrm/Kconfig"
51 source "net/iucv/Kconfig"
54 bool "TCP/IP networking"
58 These are the protocols used on the Internet and on most local
59 Ethernets. It is highly recommended to say Y here (this will enlarge
60 your kernel by about 400 KB), since some programs (e.g. the X window
61 system) use TCP/IP even if your machine is not connected to any
62 other computer. You will get the so-called loopback device which
63 allows you to ping yourself (great fun, that!).
65 For an excellent introduction to Linux networking, please read the
66 Linux Networking HOWTO, available from
67 <http://www.tldp.org/docs.html#howto>.
69 If you say Y here and also to "/proc file system support" and
70 "Sysctl support" below, you can change various aspects of the
71 behavior of the TCP/IP code by writing to the (virtual) files in
72 /proc/sys/net/ipv4/*; the options are explained in the file
73 <file:Documentation/networking/ip-sysctl.txt>.
78 source "net/ipv4/Kconfig"
79 source "net/ipv6/Kconfig"
80 source "net/netlabel/Kconfig"
84 config ANDROID_PARANOID_NETWORK
85 bool "Only allow certain groups to create sockets"
90 config NET_ACTIVITY_STATS
91 bool "Network activity statistics tracking"
94 Network activity statistics are useful for tracking wireless
95 modem activity on 2G, 3G, 4G wireless networks. Counts number of
96 transmissions and groups them in specified time buckets.
98 config NETWORK_SECMARK
99 bool "Security Marking"
101 This enables security marking of network packets, similar
102 to nfmark, but designated for security purposes.
103 If you are unsure how to answer this question, answer N.
105 config NETWORK_PHY_TIMESTAMPING
106 bool "Timestamping in PHY devices"
108 This allows timestamping of network packets by PHYs with
109 hardware timestamping capabilities. This option adds some
110 overhead in the transmit and receive paths.
112 If you are unsure how to answer this question, answer N.
115 bool "Network packet filtering framework (Netfilter)"
117 Netfilter is a framework for filtering and mangling network packets
118 that pass through your Linux box.
120 The most common use of packet filtering is to run your Linux box as
121 a firewall protecting a local network from the Internet. The type of
122 firewall provided by this kernel support is called a "packet
123 filter", which means that it can reject individual network packets
124 based on type, source, destination etc. The other kind of firewall,
125 a "proxy-based" one, is more secure but more intrusive and more
126 bothersome to set up; it inspects the network traffic much more
127 closely, modifies it and has knowledge about the higher level
128 protocols, which a packet filter lacks. Moreover, proxy-based
129 firewalls often require changes to the programs running on the local
130 clients. Proxy-based firewalls don't need support by the kernel, but
131 they are often combined with a packet filter, which only works if
134 You should also say Y here if you intend to use your Linux box as
135 the gateway to the Internet for a local network of machines without
136 globally valid IP addresses. This is called "masquerading": if one
137 of the computers on your local network wants to send something to
138 the outside, your box can "masquerade" as that computer, i.e. it
139 forwards the traffic to the intended outside destination, but
140 modifies the packets to make it look like they came from the
141 firewall box itself. It works both ways: if the outside host
142 replies, the Linux box will silently forward the traffic to the
143 correct local computer. This way, the computers on your local net
144 are completely invisible to the outside world, even though they can
145 reach the outside and can receive replies. It is even possible to
146 run globally visible servers from within a masqueraded local network
147 using a mechanism called portforwarding. Masquerading is also often
148 called NAT (Network Address Translation).
150 Another use of Netfilter is in transparent proxying: if a machine on
151 the local network tries to connect to an outside host, your Linux
152 box can transparently forward the traffic to a local server,
153 typically a caching proxy server.
155 Yet another use of Netfilter is building a bridging firewall. Using
156 a bridge with Network packet filtering enabled makes iptables "see"
157 the bridged traffic. For filtering on the lower network and Ethernet
158 protocols over the bridge, use ebtables (under bridge netfilter
161 Various modules exist for netfilter which replace the previous
162 masquerading (ipmasqadm), packet filtering (ipchains), transparent
163 proxying, and portforwarding mechanisms. Please see
164 <file:Documentation/Changes> under "iptables" for the location of
169 config NETFILTER_DEBUG
170 bool "Network packet filtering debugging"
173 You can say Y here if you want to get additional messages useful in
174 debugging the netfilter code.
176 config NETFILTER_ADVANCED
177 bool "Advanced netfilter configuration"
181 If you say Y here you can select between all the netfilter modules.
182 If you say N the more unusual ones will not be shown and the
183 basic ones needed by most people will default to 'M'.
187 config BRIDGE_NETFILTER
188 bool "Bridged IP/ARP packets filtering"
189 depends on BRIDGE && NETFILTER && INET
190 depends on NETFILTER_ADVANCED
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
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"
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/ieee802154/Kconfig"
227 source "net/mac802154/Kconfig"
228 source "net/sched/Kconfig"
229 source "net/dcb/Kconfig"
230 source "net/dns_resolver/Kconfig"
231 source "net/batman-adv/Kconfig"
232 source "net/openvswitch/Kconfig"
233 source "net/vmw_vsock/Kconfig"
234 source "net/netlink/Kconfig"
238 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
243 depends on RPS && GENERIC_HARDIRQS
249 depends on SMP && USE_GENERIC_SMP_HELPERS
252 config NETPRIO_CGROUP
253 tristate "Network priority cgroup"
256 Cgroup subsystem for use in assigning processes to network priorities on
257 a per-interface basis
266 bool "enable BPF Just In Time compiler"
267 depends on HAVE_BPF_JIT
270 Berkeley Packet Filter filtering capabilities are normally handled
271 by an interpreter. This option allows kernel to generate a native
272 code when filter is loaded in memory. This should speedup
273 packet sniffing (libpcap/tcpdump). Note : Admin should enable
274 this feature changing /proc/sys/net/core/bpf_jit_enable
276 menu "Network testing"
279 tristate "Packet Generator (USE WITH CAUTION)"
282 This module will inject preconfigured packets, at a configurable
283 rate, out of a given interface. It is used for network interface
284 stress testing and performance analysis. If you don't understand
285 what was just said, you don't need it: say N.
287 Documentation on how to use the packet generator can be found
288 at <file:Documentation/networking/pktgen.txt>.
290 To compile this code as a module, choose M here: the
291 module will be called pktgen.
294 tristate "TCP connection probing"
295 depends on INET && PROC_FS && KPROBES
297 This module allows for capturing the changes to TCP connection
298 state in response to incoming packets. It is used for debugging
299 TCP congestion avoidance modules. If you don't understand
300 what was just said, you don't need it: say N.
302 Documentation on how to use TCP connection probing can be found
305 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
307 To compile this code as a module, choose M here: the
308 module will be called tcp_probe.
310 config NET_DROP_MONITOR
311 tristate "Network packet drop alerting service"
312 depends on INET && TRACEPOINTS
314 This feature provides an alerting service to userspace in the
315 event that packets are discarded in the network stack. Alerts
316 are broadcast via netlink socket to any listening user space
317 process. If you don't need network drop alerts, or if you are ok
318 just checking the various proc files and other utilities for
319 drop statistics, say N here.
325 source "net/ax25/Kconfig"
326 source "net/can/Kconfig"
327 source "net/irda/Kconfig"
328 source "net/bluetooth/Kconfig"
329 source "net/rxrpc/Kconfig"
341 source "net/wireless/Kconfig"
342 source "net/mac80211/Kconfig"
346 source "net/wimax/Kconfig"
348 source "net/rfkill/Kconfig"
349 source "net/9p/Kconfig"
350 source "net/caif/Kconfig"
351 source "net/ceph/Kconfig"
352 source "net/nfc/Kconfig"
357 # Used by archs to tell that they support BPF_JIT