2 # Network configuration
6 bool "Networking support"
8 Unless you really know what you are doing, you should say Y here.
9 The reason is that some programs need kernel networking support even
10 when running on a stand-alone machine that isn't connected to any
13 If you are upgrading from an older kernel, you
14 should consider updating your networking tools too because changes
15 in the kernel and the tools often go hand in hand. The tools are
16 contained in the package net-tools, the location and version number
17 of which are given in <file:Documentation/Changes>.
19 For a general introduction to Linux networking, it is highly
20 recommended to read the NET-HOWTO, available from
21 <http://www.tldp.org/docs.html#howto>.
25 menu "Networking options"
27 source "net/packet/Kconfig"
28 source "net/unix/Kconfig"
29 source "net/xfrm/Kconfig"
30 source "net/iucv/Kconfig"
33 bool "TCP/IP networking"
35 These are the protocols used on the Internet and on most local
36 Ethernets. It is highly recommended to say Y here (this will enlarge
37 your kernel by about 400 KB), since some programs (e.g. the X window
38 system) use TCP/IP even if your machine is not connected to any
39 other computer. You will get the so-called loopback device which
40 allows you to ping yourself (great fun, that!).
42 For an excellent introduction to Linux networking, please read the
43 Linux Networking HOWTO, available from
44 <http://www.tldp.org/docs.html#howto>.
46 If you say Y here and also to "/proc file system support" and
47 "Sysctl support" below, you can change various aspects of the
48 behavior of the TCP/IP code by writing to the (virtual) files in
49 /proc/sys/net/ipv4/*; the options are explained in the file
50 <file:Documentation/networking/ip-sysctl.txt>.
55 source "net/ipv4/Kconfig"
56 source "net/ipv6/Kconfig"
57 source "net/netlabel/Kconfig"
61 config NETWORK_SECMARK
62 bool "Security Marking"
64 This enables security marking of network packets, similar
65 to nfmark, but designated for security purposes.
66 If you are unsure how to answer this question, answer N.
69 bool "Network packet filtering framework (Netfilter)"
71 Netfilter is a framework for filtering and mangling network packets
72 that pass through your Linux box.
74 The most common use of packet filtering is to run your Linux box as
75 a firewall protecting a local network from the Internet. The type of
76 firewall provided by this kernel support is called a "packet
77 filter", which means that it can reject individual network packets
78 based on type, source, destination etc. The other kind of firewall,
79 a "proxy-based" one, is more secure but more intrusive and more
80 bothersome to set up; it inspects the network traffic much more
81 closely, modifies it and has knowledge about the higher level
82 protocols, which a packet filter lacks. Moreover, proxy-based
83 firewalls often require changes to the programs running on the local
84 clients. Proxy-based firewalls don't need support by the kernel, but
85 they are often combined with a packet filter, which only works if
88 You should also say Y here if you intend to use your Linux box as
89 the gateway to the Internet for a local network of machines without
90 globally valid IP addresses. This is called "masquerading": if one
91 of the computers on your local network wants to send something to
92 the outside, your box can "masquerade" as that computer, i.e. it
93 forwards the traffic to the intended outside destination, but
94 modifies the packets to make it look like they came from the
95 firewall box itself. It works both ways: if the outside host
96 replies, the Linux box will silently forward the traffic to the
97 correct local computer. This way, the computers on your local net
98 are completely invisible to the outside world, even though they can
99 reach the outside and can receive replies. It is even possible to
100 run globally visible servers from within a masqueraded local network
101 using a mechanism called portforwarding. Masquerading is also often
102 called NAT (Network Address Translation).
104 Another use of Netfilter is in transparent proxying: if a machine on
105 the local network tries to connect to an outside host, your Linux
106 box can transparently forward the traffic to a local server,
107 typically a caching proxy server.
109 Yet another use of Netfilter is building a bridging firewall. Using
110 a bridge with Network packet filtering enabled makes iptables "see"
111 the bridged traffic. For filtering on the lower network and Ethernet
112 protocols over the bridge, use ebtables (under bridge netfilter
115 Various modules exist for netfilter which replace the previous
116 masquerading (ipmasqadm), packet filtering (ipchains), transparent
117 proxying, and portforwarding mechanisms. Please see
118 <file:Documentation/Changes> under "iptables" for the location of
121 Make sure to say N to "Fast switching" below if you intend to say Y
122 here, as Fast switching currently bypasses netfilter.
124 Chances are that you should say Y here if you compile a kernel which
125 will run as a router and N for regular hosts. If unsure, say N.
129 config NETFILTER_DEBUG
130 bool "Network packet filtering debugging"
133 You can say Y here if you want to get additional messages useful in
134 debugging the netfilter code.
136 config NETFILTER_ADVANCED
137 bool "Advanced netfilter configuration"
141 If you say Y here you can select between all the netfilter modules.
142 If you say N the more ununsual ones will not be shown and the
143 basic ones needed by most people will default to 'M'.
147 config BRIDGE_NETFILTER
148 bool "Bridged IP/ARP packets filtering"
149 depends on BRIDGE && NETFILTER && INET
150 depends on NETFILTER_ADVANCED
153 Enabling this option will let arptables resp. iptables see bridged
154 ARP resp. IP traffic. If you want a bridging firewall, you probably
155 want this option enabled.
156 Enabling or disabling this option doesn't enable or disable
161 source "net/netfilter/Kconfig"
162 source "net/ipv4/netfilter/Kconfig"
163 source "net/ipv6/netfilter/Kconfig"
164 source "net/decnet/netfilter/Kconfig"
165 source "net/bridge/netfilter/Kconfig"
169 source "net/dccp/Kconfig"
170 source "net/sctp/Kconfig"
171 source "net/rds/Kconfig"
172 source "net/tipc/Kconfig"
173 source "net/atm/Kconfig"
174 source "net/802/Kconfig"
175 source "net/bridge/Kconfig"
176 source "net/dsa/Kconfig"
177 source "net/8021q/Kconfig"
178 source "net/decnet/Kconfig"
179 source "net/llc/Kconfig"
180 source "net/ipx/Kconfig"
181 source "drivers/net/appletalk/Kconfig"
182 source "net/x25/Kconfig"
183 source "net/lapb/Kconfig"
184 source "net/econet/Kconfig"
185 source "net/wanrouter/Kconfig"
186 source "net/phonet/Kconfig"
187 source "net/sched/Kconfig"
188 source "net/dcb/Kconfig"
190 menu "Network testing"
193 tristate "Packet Generator (USE WITH CAUTION)"
196 This module will inject preconfigured packets, at a configurable
197 rate, out of a given interface. It is used for network interface
198 stress testing and performance analysis. If you don't understand
199 what was just said, you don't need it: say N.
201 Documentation on how to use the packet generator can be found
202 at <file:Documentation/networking/pktgen.txt>.
204 To compile this code as a module, choose M here: the
205 module will be called pktgen.
208 tristate "TCP connection probing"
209 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
211 This module allows for capturing the changes to TCP connection
212 state in response to incoming packets. It is used for debugging
213 TCP congestion avoidance modules. If you don't understand
214 what was just said, you don't need it: say N.
216 Documentation on how to use TCP connection probing can be found
217 at http://linux-net.osdl.org/index.php/TcpProbe
219 To compile this code as a module, choose M here: the
220 module will be called tcp_probe.
222 config NET_DROP_MONITOR
223 boolean "Network packet drop alerting service"
224 depends on INET && EXPERIMENTAL && TRACEPOINTS
226 This feature provides an alerting service to userspace in the
227 event that packets are discarded in the network stack. Alerts
228 are broadcast via netlink socket to any listening user space
229 process. If you don't need network drop alerts, or if you are ok
230 just checking the various proc files and other utilities for
231 drop statistics, say N here.
237 source "net/ax25/Kconfig"
238 source "net/can/Kconfig"
239 source "net/irda/Kconfig"
240 source "net/bluetooth/Kconfig"
241 source "net/rxrpc/Kconfig"
253 source "net/wireless/Kconfig"
254 source "net/mac80211/Kconfig"
258 source "net/wimax/Kconfig"
260 source "net/rfkill/Kconfig"
261 source "net/9p/Kconfig"