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 NETWORK_SECMARK
85 bool "Security Marking"
87 This enables security marking of network packets, similar
88 to nfmark, but designated for security purposes.
89 If you are unsure how to answer this question, answer N.
91 config NETWORK_PHY_TIMESTAMPING
92 bool "Timestamping in PHY devices"
93 depends on EXPERIMENTAL
95 This allows timestamping of network packets by PHYs with
96 hardware timestamping capabilities. This option adds some
97 overhead in the transmit and receive paths.
99 If you are unsure how to answer this question, answer N.
102 bool "Network packet filtering framework (Netfilter)"
104 Netfilter is a framework for filtering and mangling network packets
105 that pass through your Linux box.
107 The most common use of packet filtering is to run your Linux box as
108 a firewall protecting a local network from the Internet. The type of
109 firewall provided by this kernel support is called a "packet
110 filter", which means that it can reject individual network packets
111 based on type, source, destination etc. The other kind of firewall,
112 a "proxy-based" one, is more secure but more intrusive and more
113 bothersome to set up; it inspects the network traffic much more
114 closely, modifies it and has knowledge about the higher level
115 protocols, which a packet filter lacks. Moreover, proxy-based
116 firewalls often require changes to the programs running on the local
117 clients. Proxy-based firewalls don't need support by the kernel, but
118 they are often combined with a packet filter, which only works if
121 You should also say Y here if you intend to use your Linux box as
122 the gateway to the Internet for a local network of machines without
123 globally valid IP addresses. This is called "masquerading": if one
124 of the computers on your local network wants to send something to
125 the outside, your box can "masquerade" as that computer, i.e. it
126 forwards the traffic to the intended outside destination, but
127 modifies the packets to make it look like they came from the
128 firewall box itself. It works both ways: if the outside host
129 replies, the Linux box will silently forward the traffic to the
130 correct local computer. This way, the computers on your local net
131 are completely invisible to the outside world, even though they can
132 reach the outside and can receive replies. It is even possible to
133 run globally visible servers from within a masqueraded local network
134 using a mechanism called portforwarding. Masquerading is also often
135 called NAT (Network Address Translation).
137 Another use of Netfilter is in transparent proxying: if a machine on
138 the local network tries to connect to an outside host, your Linux
139 box can transparently forward the traffic to a local server,
140 typically a caching proxy server.
142 Yet another use of Netfilter is building a bridging firewall. Using
143 a bridge with Network packet filtering enabled makes iptables "see"
144 the bridged traffic. For filtering on the lower network and Ethernet
145 protocols over the bridge, use ebtables (under bridge netfilter
148 Various modules exist for netfilter which replace the previous
149 masquerading (ipmasqadm), packet filtering (ipchains), transparent
150 proxying, and portforwarding mechanisms. Please see
151 <file:Documentation/Changes> under "iptables" for the location of
156 config NETFILTER_DEBUG
157 bool "Network packet filtering debugging"
160 You can say Y here if you want to get additional messages useful in
161 debugging the netfilter code.
163 config NETFILTER_ADVANCED
164 bool "Advanced netfilter configuration"
168 If you say Y here you can select between all the netfilter modules.
169 If you say N the more unusual ones will not be shown and the
170 basic ones needed by most people will default to 'M'.
174 config BRIDGE_NETFILTER
175 bool "Bridged IP/ARP packets filtering"
176 depends on BRIDGE && NETFILTER && INET
177 depends on NETFILTER_ADVANCED
180 Enabling this option will let arptables resp. iptables see bridged
181 ARP resp. IP traffic. If you want a bridging firewall, you probably
182 want this option enabled.
183 Enabling or disabling this option doesn't enable or disable
188 source "net/netfilter/Kconfig"
189 source "net/ipv4/netfilter/Kconfig"
190 source "net/ipv6/netfilter/Kconfig"
191 source "net/decnet/netfilter/Kconfig"
192 source "net/bridge/netfilter/Kconfig"
196 source "net/dccp/Kconfig"
197 source "net/sctp/Kconfig"
198 source "net/rds/Kconfig"
199 source "net/tipc/Kconfig"
200 source "net/atm/Kconfig"
201 source "net/l2tp/Kconfig"
202 source "net/802/Kconfig"
203 source "net/bridge/Kconfig"
204 source "net/dsa/Kconfig"
205 source "net/8021q/Kconfig"
206 source "net/decnet/Kconfig"
207 source "net/llc/Kconfig"
208 source "net/ipx/Kconfig"
209 source "drivers/net/appletalk/Kconfig"
210 source "net/x25/Kconfig"
211 source "net/lapb/Kconfig"
212 source "net/wanrouter/Kconfig"
213 source "net/phonet/Kconfig"
214 source "net/ieee802154/Kconfig"
215 source "net/mac802154/Kconfig"
216 source "net/sched/Kconfig"
217 source "net/dcb/Kconfig"
218 source "net/dns_resolver/Kconfig"
219 source "net/batman-adv/Kconfig"
220 source "net/openvswitch/Kconfig"
224 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
229 depends on RPS && GENERIC_HARDIRQS
235 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
238 config NETPRIO_CGROUP
239 tristate "Network priority cgroup"
242 Cgroup subsystem for use in assigning processes to network priorities on
243 a per-interface basis
252 bool "enable BPF Just In Time compiler"
253 depends on HAVE_BPF_JIT
256 Berkeley Packet Filter filtering capabilities are normally handled
257 by an interpreter. This option allows kernel to generate a native
258 code when filter is loaded in memory. This should speedup
259 packet sniffing (libpcap/tcpdump). Note : Admin should enable
260 this feature changing /proc/sys/net/core/bpf_jit_enable
262 menu "Network testing"
265 tristate "Packet Generator (USE WITH CAUTION)"
268 This module will inject preconfigured packets, at a configurable
269 rate, out of a given interface. It is used for network interface
270 stress testing and performance analysis. If you don't understand
271 what was just said, you don't need it: say N.
273 Documentation on how to use the packet generator can be found
274 at <file:Documentation/networking/pktgen.txt>.
276 To compile this code as a module, choose M here: the
277 module will be called pktgen.
280 tristate "TCP connection probing"
281 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
283 This module allows for capturing the changes to TCP connection
284 state in response to incoming packets. It is used for debugging
285 TCP congestion avoidance modules. If you don't understand
286 what was just said, you don't need it: say N.
288 Documentation on how to use TCP connection probing can be found
291 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
293 To compile this code as a module, choose M here: the
294 module will be called tcp_probe.
296 config NET_DROP_MONITOR
297 tristate "Network packet drop alerting service"
298 depends on INET && EXPERIMENTAL && TRACEPOINTS
300 This feature provides an alerting service to userspace in the
301 event that packets are discarded in the network stack. Alerts
302 are broadcast via netlink socket to any listening user space
303 process. If you don't need network drop alerts, or if you are ok
304 just checking the various proc files and other utilities for
305 drop statistics, say N here.
311 source "net/ax25/Kconfig"
312 source "net/can/Kconfig"
313 source "net/irda/Kconfig"
314 source "net/bluetooth/Kconfig"
315 source "net/rxrpc/Kconfig"
327 source "net/wireless/Kconfig"
328 source "net/mac80211/Kconfig"
332 source "net/wimax/Kconfig"
334 source "net/rfkill/Kconfig"
335 source "net/9p/Kconfig"
336 source "net/caif/Kconfig"
337 source "net/ceph/Kconfig"
338 source "net/nfc/Kconfig"
343 # Used by archs to tell that they support BPF_JIT