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>.
75 config TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION
76 bool "TCP/IP zero-copy transfer completion notification"
80 Adds support for sending a notification upon completion of a
81 zero-copy TCP/IP transfer. This can speed up certain TCP/IP
82 software. Currently this is only used by the iSCSI target driver
88 source "net/ipv4/Kconfig"
89 source "net/ipv6/Kconfig"
90 source "net/netlabel/Kconfig"
94 config NETWORK_SECMARK
95 bool "Security Marking"
97 This enables security marking of network packets, similar
98 to nfmark, but designated for security purposes.
99 If you are unsure how to answer this question, answer N.
101 config NETWORK_PHY_TIMESTAMPING
102 bool "Timestamping in PHY devices"
103 depends on EXPERIMENTAL
105 This allows timestamping of network packets by PHYs with
106 hardware timestamping capabilities. This option adds some
107 overhead in the transmit and receive paths.
109 If you are unsure how to answer this question, answer N.
112 bool "Network packet filtering framework (Netfilter)"
114 Netfilter is a framework for filtering and mangling network packets
115 that pass through your Linux box.
117 The most common use of packet filtering is to run your Linux box as
118 a firewall protecting a local network from the Internet. The type of
119 firewall provided by this kernel support is called a "packet
120 filter", which means that it can reject individual network packets
121 based on type, source, destination etc. The other kind of firewall,
122 a "proxy-based" one, is more secure but more intrusive and more
123 bothersome to set up; it inspects the network traffic much more
124 closely, modifies it and has knowledge about the higher level
125 protocols, which a packet filter lacks. Moreover, proxy-based
126 firewalls often require changes to the programs running on the local
127 clients. Proxy-based firewalls don't need support by the kernel, but
128 they are often combined with a packet filter, which only works if
131 You should also say Y here if you intend to use your Linux box as
132 the gateway to the Internet for a local network of machines without
133 globally valid IP addresses. This is called "masquerading": if one
134 of the computers on your local network wants to send something to
135 the outside, your box can "masquerade" as that computer, i.e. it
136 forwards the traffic to the intended outside destination, but
137 modifies the packets to make it look like they came from the
138 firewall box itself. It works both ways: if the outside host
139 replies, the Linux box will silently forward the traffic to the
140 correct local computer. This way, the computers on your local net
141 are completely invisible to the outside world, even though they can
142 reach the outside and can receive replies. It is even possible to
143 run globally visible servers from within a masqueraded local network
144 using a mechanism called portforwarding. Masquerading is also often
145 called NAT (Network Address Translation).
147 Another use of Netfilter is in transparent proxying: if a machine on
148 the local network tries to connect to an outside host, your Linux
149 box can transparently forward the traffic to a local server,
150 typically a caching proxy server.
152 Yet another use of Netfilter is building a bridging firewall. Using
153 a bridge with Network packet filtering enabled makes iptables "see"
154 the bridged traffic. For filtering on the lower network and Ethernet
155 protocols over the bridge, use ebtables (under bridge netfilter
158 Various modules exist for netfilter which replace the previous
159 masquerading (ipmasqadm), packet filtering (ipchains), transparent
160 proxying, and portforwarding mechanisms. Please see
161 <file:Documentation/Changes> under "iptables" for the location of
166 config NETFILTER_DEBUG
167 bool "Network packet filtering debugging"
170 You can say Y here if you want to get additional messages useful in
171 debugging the netfilter code.
173 config NETFILTER_ADVANCED
174 bool "Advanced netfilter configuration"
178 If you say Y here you can select between all the netfilter modules.
179 If you say N the more unusual ones will not be shown and the
180 basic ones needed by most people will default to 'M'.
184 config BRIDGE_NETFILTER
185 bool "Bridged IP/ARP packets filtering"
186 depends on BRIDGE && NETFILTER && INET
187 depends on NETFILTER_ADVANCED
190 Enabling this option will let arptables resp. iptables see bridged
191 ARP resp. IP traffic. If you want a bridging firewall, you probably
192 want this option enabled.
193 Enabling or disabling this option doesn't enable or disable
198 source "net/netfilter/Kconfig"
199 source "net/ipv4/netfilter/Kconfig"
200 source "net/ipv6/netfilter/Kconfig"
201 source "net/decnet/netfilter/Kconfig"
202 source "net/bridge/netfilter/Kconfig"
206 source "net/dccp/Kconfig"
207 source "net/sctp/Kconfig"
208 source "net/rds/Kconfig"
209 source "net/tipc/Kconfig"
210 source "net/atm/Kconfig"
211 source "net/l2tp/Kconfig"
212 source "net/802/Kconfig"
213 source "net/bridge/Kconfig"
214 source "net/dsa/Kconfig"
215 source "net/8021q/Kconfig"
216 source "net/decnet/Kconfig"
217 source "net/llc/Kconfig"
218 source "net/ipx/Kconfig"
219 source "drivers/net/appletalk/Kconfig"
220 source "net/x25/Kconfig"
221 source "net/lapb/Kconfig"
222 source "net/econet/Kconfig"
223 source "net/wanrouter/Kconfig"
224 source "net/phonet/Kconfig"
225 source "net/ieee802154/Kconfig"
226 source "net/sched/Kconfig"
227 source "net/dcb/Kconfig"
228 source "net/dns_resolver/Kconfig"
232 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS
235 menu "Network testing"
238 tristate "Packet Generator (USE WITH CAUTION)"
241 This module will inject preconfigured packets, at a configurable
242 rate, out of a given interface. It is used for network interface
243 stress testing and performance analysis. If you don't understand
244 what was just said, you don't need it: say N.
246 Documentation on how to use the packet generator can be found
247 at <file:Documentation/networking/pktgen.txt>.
249 To compile this code as a module, choose M here: the
250 module will be called pktgen.
253 tristate "TCP connection probing"
254 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
256 This module allows for capturing the changes to TCP connection
257 state in response to incoming packets. It is used for debugging
258 TCP congestion avoidance modules. If you don't understand
259 what was just said, you don't need it: say N.
261 Documentation on how to use TCP connection probing can be found
262 at http://linux-net.osdl.org/index.php/TcpProbe
264 To compile this code as a module, choose M here: the
265 module will be called tcp_probe.
267 config NET_DROP_MONITOR
268 boolean "Network packet drop alerting service"
269 depends on INET && EXPERIMENTAL && TRACEPOINTS
271 This feature provides an alerting service to userspace in the
272 event that packets are discarded in the network stack. Alerts
273 are broadcast via netlink socket to any listening user space
274 process. If you don't need network drop alerts, or if you are ok
275 just checking the various proc files and other utilities for
276 drop statistics, say N here.
282 source "net/ax25/Kconfig"
283 source "net/can/Kconfig"
284 source "net/irda/Kconfig"
285 source "net/bluetooth/Kconfig"
286 source "net/rxrpc/Kconfig"
298 source "net/wireless/Kconfig"
299 source "net/mac80211/Kconfig"
303 source "net/wimax/Kconfig"
305 source "net/rfkill/Kconfig"
306 source "net/9p/Kconfig"
307 source "net/caif/Kconfig"
308 source "net/ceph/Kconfig"