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 NETWORK_SECMARK
91 bool "Security Marking"
93 This enables security marking of network packets, similar
94 to nfmark, but designated for security purposes.
95 If you are unsure how to answer this question, answer N.
97 config NETWORK_PHY_TIMESTAMPING
98 bool "Timestamping in PHY devices"
100 This allows timestamping of network packets by PHYs with
101 hardware timestamping capabilities. This option adds some
102 overhead in the transmit and receive paths.
104 If you are unsure how to answer this question, answer N.
107 bool "Network packet filtering framework (Netfilter)"
109 Netfilter is a framework for filtering and mangling network packets
110 that pass through your Linux box.
112 The most common use of packet filtering is to run your Linux box as
113 a firewall protecting a local network from the Internet. The type of
114 firewall provided by this kernel support is called a "packet
115 filter", which means that it can reject individual network packets
116 based on type, source, destination etc. The other kind of firewall,
117 a "proxy-based" one, is more secure but more intrusive and more
118 bothersome to set up; it inspects the network traffic much more
119 closely, modifies it and has knowledge about the higher level
120 protocols, which a packet filter lacks. Moreover, proxy-based
121 firewalls often require changes to the programs running on the local
122 clients. Proxy-based firewalls don't need support by the kernel, but
123 they are often combined with a packet filter, which only works if
126 You should also say Y here if you intend to use your Linux box as
127 the gateway to the Internet for a local network of machines without
128 globally valid IP addresses. This is called "masquerading": if one
129 of the computers on your local network wants to send something to
130 the outside, your box can "masquerade" as that computer, i.e. it
131 forwards the traffic to the intended outside destination, but
132 modifies the packets to make it look like they came from the
133 firewall box itself. It works both ways: if the outside host
134 replies, the Linux box will silently forward the traffic to the
135 correct local computer. This way, the computers on your local net
136 are completely invisible to the outside world, even though they can
137 reach the outside and can receive replies. It is even possible to
138 run globally visible servers from within a masqueraded local network
139 using a mechanism called portforwarding. Masquerading is also often
140 called NAT (Network Address Translation).
142 Another use of Netfilter is in transparent proxying: if a machine on
143 the local network tries to connect to an outside host, your Linux
144 box can transparently forward the traffic to a local server,
145 typically a caching proxy server.
147 Yet another use of Netfilter is building a bridging firewall. Using
148 a bridge with Network packet filtering enabled makes iptables "see"
149 the bridged traffic. For filtering on the lower network and Ethernet
150 protocols over the bridge, use ebtables (under bridge netfilter
153 Various modules exist for netfilter which replace the previous
154 masquerading (ipmasqadm), packet filtering (ipchains), transparent
155 proxying, and portforwarding mechanisms. Please see
156 <file:Documentation/Changes> under "iptables" for the location of
161 config NETFILTER_DEBUG
162 bool "Network packet filtering debugging"
165 You can say Y here if you want to get additional messages useful in
166 debugging the netfilter code.
168 config NETFILTER_ADVANCED
169 bool "Advanced netfilter configuration"
173 If you say Y here you can select between all the netfilter modules.
174 If you say N the more unusual ones will not be shown and the
175 basic ones needed by most people will default to 'M'.
179 config BRIDGE_NETFILTER
180 bool "Bridged IP/ARP packets filtering"
181 depends on BRIDGE && NETFILTER && INET
182 depends on NETFILTER_ADVANCED
185 Enabling this option will let arptables resp. iptables see bridged
186 ARP resp. IP traffic. If you want a bridging firewall, you probably
187 want this option enabled.
188 Enabling or disabling this option doesn't enable or disable
193 source "net/netfilter/Kconfig"
194 source "net/ipv4/netfilter/Kconfig"
195 source "net/ipv6/netfilter/Kconfig"
196 source "net/decnet/netfilter/Kconfig"
197 source "net/bridge/netfilter/Kconfig"
201 source "net/dccp/Kconfig"
202 source "net/sctp/Kconfig"
203 source "net/rds/Kconfig"
204 source "net/tipc/Kconfig"
205 source "net/atm/Kconfig"
206 source "net/l2tp/Kconfig"
207 source "net/802/Kconfig"
208 source "net/bridge/Kconfig"
209 source "net/dsa/Kconfig"
210 source "net/8021q/Kconfig"
211 source "net/decnet/Kconfig"
212 source "net/llc/Kconfig"
213 source "net/ipx/Kconfig"
214 source "drivers/net/appletalk/Kconfig"
215 source "net/x25/Kconfig"
216 source "net/lapb/Kconfig"
217 source "net/phonet/Kconfig"
218 source "net/ieee802154/Kconfig"
219 source "net/mac802154/Kconfig"
220 source "net/sched/Kconfig"
221 source "net/dcb/Kconfig"
222 source "net/dns_resolver/Kconfig"
223 source "net/batman-adv/Kconfig"
224 source "net/openvswitch/Kconfig"
225 source "net/vmw_vsock/Kconfig"
226 source "net/netlink/Kconfig"
230 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
235 depends on RPS && GENERIC_HARDIRQS
241 depends on SMP && USE_GENERIC_SMP_HELPERS
244 config NETPRIO_CGROUP
245 tristate "Network priority cgroup"
248 Cgroup subsystem for use in assigning processes to network priorities on
249 a per-interface basis
258 bool "enable BPF Just In Time compiler"
259 depends on HAVE_BPF_JIT
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
268 menu "Network testing"
271 tristate "Packet Generator (USE WITH CAUTION)"
274 This module will inject preconfigured packets, at a configurable
275 rate, out of a given interface. It is used for network interface
276 stress testing and performance analysis. If you don't understand
277 what was just said, you don't need it: say N.
279 Documentation on how to use the packet generator can be found
280 at <file:Documentation/networking/pktgen.txt>.
282 To compile this code as a module, choose M here: the
283 module will be called pktgen.
286 tristate "TCP connection probing"
287 depends on INET && PROC_FS && KPROBES
289 This module allows for capturing the changes to TCP connection
290 state in response to incoming packets. It is used for debugging
291 TCP congestion avoidance modules. If you don't understand
292 what was just said, you don't need it: say N.
294 Documentation on how to use TCP connection probing can be found
297 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
299 To compile this code as a module, choose M here: the
300 module will be called tcp_probe.
302 config NET_DROP_MONITOR
303 tristate "Network packet drop alerting service"
304 depends on INET && TRACEPOINTS
306 This feature provides an alerting service to userspace in the
307 event that packets are discarded in the network stack. Alerts
308 are broadcast via netlink socket to any listening user space
309 process. If you don't need network drop alerts, or if you are ok
310 just checking the various proc files and other utilities for
311 drop statistics, say N here.
317 source "net/ax25/Kconfig"
318 source "net/can/Kconfig"
319 source "net/irda/Kconfig"
320 source "net/bluetooth/Kconfig"
321 source "net/rxrpc/Kconfig"
333 source "net/wireless/Kconfig"
334 source "net/mac80211/Kconfig"
338 source "net/wimax/Kconfig"
340 source "net/rfkill/Kconfig"
341 source "net/9p/Kconfig"
342 source "net/caif/Kconfig"
343 source "net/ceph/Kconfig"
344 source "net/nfc/Kconfig"
349 # Used by archs to tell that they support BPF_JIT