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"
56 These are the protocols used on the Internet and on most local
57 Ethernets. It is highly recommended to say Y here (this will enlarge
58 your kernel by about 400 KB), since some programs (e.g. the X window
59 system) use TCP/IP even if your machine is not connected to any
60 other computer. You will get the so-called loopback device which
61 allows you to ping yourself (great fun, that!).
63 For an excellent introduction to Linux networking, please read the
64 Linux Networking HOWTO, available from
65 <http://www.tldp.org/docs.html#howto>.
67 If you say Y here and also to "/proc file system support" and
68 "Sysctl support" below, you can change various aspects of the
69 behavior of the TCP/IP code by writing to the (virtual) files in
70 /proc/sys/net/ipv4/*; the options are explained in the file
71 <file:Documentation/networking/ip-sysctl.txt>.
76 source "net/ipv4/Kconfig"
77 source "net/ipv6/Kconfig"
78 source "net/netlabel/Kconfig"
81 bool "TCP/IP Generic Receive Offload"
86 config NETWORK_SECMARK
87 bool "Security Marking"
89 This enables security marking of network packets, similar
90 to nfmark, but designated for security purposes.
91 If you are unsure how to answer this question, answer N.
93 config NETWORK_PHY_TIMESTAMPING
94 bool "Timestamping in PHY devices"
95 depends on EXPERIMENTAL
97 This allows timestamping of network packets by PHYs with
98 hardware timestamping capabilities. This option adds some
99 overhead in the transmit and receive paths.
101 If you are unsure how to answer this question, answer N.
104 bool "Network packet filtering framework (Netfilter)"
106 Netfilter is a framework for filtering and mangling network packets
107 that pass through your Linux box.
109 The most common use of packet filtering is to run your Linux box as
110 a firewall protecting a local network from the Internet. The type of
111 firewall provided by this kernel support is called a "packet
112 filter", which means that it can reject individual network packets
113 based on type, source, destination etc. The other kind of firewall,
114 a "proxy-based" one, is more secure but more intrusive and more
115 bothersome to set up; it inspects the network traffic much more
116 closely, modifies it and has knowledge about the higher level
117 protocols, which a packet filter lacks. Moreover, proxy-based
118 firewalls often require changes to the programs running on the local
119 clients. Proxy-based firewalls don't need support by the kernel, but
120 they are often combined with a packet filter, which only works if
123 You should also say Y here if you intend to use your Linux box as
124 the gateway to the Internet for a local network of machines without
125 globally valid IP addresses. This is called "masquerading": if one
126 of the computers on your local network wants to send something to
127 the outside, your box can "masquerade" as that computer, i.e. it
128 forwards the traffic to the intended outside destination, but
129 modifies the packets to make it look like they came from the
130 firewall box itself. It works both ways: if the outside host
131 replies, the Linux box will silently forward the traffic to the
132 correct local computer. This way, the computers on your local net
133 are completely invisible to the outside world, even though they can
134 reach the outside and can receive replies. It is even possible to
135 run globally visible servers from within a masqueraded local network
136 using a mechanism called portforwarding. Masquerading is also often
137 called NAT (Network Address Translation).
139 Another use of Netfilter is in transparent proxying: if a machine on
140 the local network tries to connect to an outside host, your Linux
141 box can transparently forward the traffic to a local server,
142 typically a caching proxy server.
144 Yet another use of Netfilter is building a bridging firewall. Using
145 a bridge with Network packet filtering enabled makes iptables "see"
146 the bridged traffic. For filtering on the lower network and Ethernet
147 protocols over the bridge, use ebtables (under bridge netfilter
150 Various modules exist for netfilter which replace the previous
151 masquerading (ipmasqadm), packet filtering (ipchains), transparent
152 proxying, and portforwarding mechanisms. Please see
153 <file:Documentation/Changes> under "iptables" for the location of
158 config NETFILTER_DEBUG
159 bool "Network packet filtering debugging"
162 You can say Y here if you want to get additional messages useful in
163 debugging the netfilter code.
165 config NETFILTER_ADVANCED
166 bool "Advanced netfilter configuration"
170 If you say Y here you can select between all the netfilter modules.
171 If you say N the more unusual ones will not be shown and the
172 basic ones needed by most people will default to 'M'.
176 config BRIDGE_NETFILTER
177 bool "Bridged IP/ARP packets filtering"
178 depends on BRIDGE && NETFILTER && INET
179 depends on NETFILTER_ADVANCED
182 Enabling this option will let arptables resp. iptables see bridged
183 ARP resp. IP traffic. If you want a bridging firewall, you probably
184 want this option enabled.
185 Enabling or disabling this option doesn't enable or disable
190 source "net/netfilter/Kconfig"
191 source "net/ipv4/netfilter/Kconfig"
192 source "net/ipv6/netfilter/Kconfig"
193 source "net/decnet/netfilter/Kconfig"
194 source "net/bridge/netfilter/Kconfig"
198 source "net/dccp/Kconfig"
199 source "net/sctp/Kconfig"
200 source "net/rds/Kconfig"
201 source "net/tipc/Kconfig"
202 source "net/atm/Kconfig"
203 source "net/l2tp/Kconfig"
204 source "net/802/Kconfig"
205 source "net/bridge/Kconfig"
206 source "net/dsa/Kconfig"
207 source "net/8021q/Kconfig"
208 source "net/decnet/Kconfig"
209 source "net/llc/Kconfig"
210 source "net/ipx/Kconfig"
211 source "drivers/net/appletalk/Kconfig"
212 source "net/x25/Kconfig"
213 source "net/lapb/Kconfig"
214 source "net/econet/Kconfig"
215 source "net/wanrouter/Kconfig"
216 source "net/phonet/Kconfig"
217 source "net/ieee802154/Kconfig"
218 source "net/sched/Kconfig"
219 source "net/dcb/Kconfig"
220 source "net/dns_resolver/Kconfig"
224 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
227 menu "Network testing"
230 tristate "Packet Generator (USE WITH CAUTION)"
233 This module will inject preconfigured packets, at a configurable
234 rate, out of a given interface. It is used for network interface
235 stress testing and performance analysis. If you don't understand
236 what was just said, you don't need it: say N.
238 Documentation on how to use the packet generator can be found
239 at <file:Documentation/networking/pktgen.txt>.
241 To compile this code as a module, choose M here: the
242 module will be called pktgen.
245 tristate "TCP connection probing"
246 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
248 This module allows for capturing the changes to TCP connection
249 state in response to incoming packets. It is used for debugging
250 TCP congestion avoidance modules. If you don't understand
251 what was just said, you don't need it: say N.
253 Documentation on how to use TCP connection probing can be found
254 at http://linux-net.osdl.org/index.php/TcpProbe
256 To compile this code as a module, choose M here: the
257 module will be called tcp_probe.
259 config NET_DROP_MONITOR
260 boolean "Network packet drop alerting service"
261 depends on INET && EXPERIMENTAL && TRACEPOINTS
263 This feature provides an alerting service to userspace in the
264 event that packets are discarded in the network stack. Alerts
265 are broadcast via netlink socket to any listening user space
266 process. If you don't need network drop alerts, or if you are ok
267 just checking the various proc files and other utilities for
268 drop statistics, say N here.
274 source "net/ax25/Kconfig"
275 source "net/can/Kconfig"
276 source "net/irda/Kconfig"
277 source "net/bluetooth/Kconfig"
278 source "net/rxrpc/Kconfig"
290 source "net/wireless/Kconfig"
291 source "net/mac80211/Kconfig"
295 source "net/wimax/Kconfig"
297 source "net/rfkill/Kconfig"
298 source "net/9p/Kconfig"
299 source "net/caif/Kconfig"