1# 2# Network configuration 3# 4 5menuconfig NET 6 bool "Networking support" 7 select NLATTR 8 ---help--- 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 12 other computer. 13 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>. 19 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>. 23 24if NET 25 26config WANT_COMPAT_NETLINK_MESSAGES 27 bool 28 help 29 This option can be selected by other options that need compat 30 netlink messages. 31 32config COMPAT_NETLINK_MESSAGES 33 def_bool y 34 depends on COMPAT 35 depends on WIRELESS_EXT || WANT_COMPAT_NETLINK_MESSAGES 36 help 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. 42 43 Newly written code should NEVER need this option but do 44 compat-independent messages instead! 45 46menu "Networking options" 47 48source "net/packet/Kconfig" 49source "net/unix/Kconfig" 50source "net/xfrm/Kconfig" 51source "net/iucv/Kconfig" 52 53config INET 54 bool "TCP/IP networking" 55 ---help--- 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!). 62 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>. 66 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>. 72 73 Short answer: say Y. 74 75if INET 76source "net/ipv4/Kconfig" 77source "net/ipv6/Kconfig" 78source "net/netlabel/Kconfig" 79 80endif # if INET 81 82config NETWORK_SECMARK 83 bool "Security Marking" 84 help 85 This enables security marking of network packets, similar 86 to nfmark, but designated for security purposes. 87 If you are unsure how to answer this question, answer N. 88 89menuconfig NETFILTER 90 bool "Network packet filtering framework (Netfilter)" 91 ---help--- 92 Netfilter is a framework for filtering and mangling network packets 93 that pass through your Linux box. 94 95 The most common use of packet filtering is to run your Linux box as 96 a firewall protecting a local network from the Internet. The type of 97 firewall provided by this kernel support is called a "packet 98 filter", which means that it can reject individual network packets 99 based on type, source, destination etc. The other kind of firewall, 100 a "proxy-based" one, is more secure but more intrusive and more 101 bothersome to set up; it inspects the network traffic much more 102 closely, modifies it and has knowledge about the higher level 103 protocols, which a packet filter lacks. Moreover, proxy-based 104 firewalls often require changes to the programs running on the local 105 clients. Proxy-based firewalls don't need support by the kernel, but 106 they are often combined with a packet filter, which only works if 107 you say Y here. 108 109 You should also say Y here if you intend to use your Linux box as 110 the gateway to the Internet for a local network of machines without 111 globally valid IP addresses. This is called "masquerading": if one 112 of the computers on your local network wants to send something to 113 the outside, your box can "masquerade" as that computer, i.e. it 114 forwards the traffic to the intended outside destination, but 115 modifies the packets to make it look like they came from the 116 firewall box itself. It works both ways: if the outside host 117 replies, the Linux box will silently forward the traffic to the 118 correct local computer. This way, the computers on your local net 119 are completely invisible to the outside world, even though they can 120 reach the outside and can receive replies. It is even possible to 121 run globally visible servers from within a masqueraded local network 122 using a mechanism called portforwarding. Masquerading is also often 123 called NAT (Network Address Translation). 124 125 Another use of Netfilter is in transparent proxying: if a machine on 126 the local network tries to connect to an outside host, your Linux 127 box can transparently forward the traffic to a local server, 128 typically a caching proxy server. 129 130 Yet another use of Netfilter is building a bridging firewall. Using 131 a bridge with Network packet filtering enabled makes iptables "see" 132 the bridged traffic. For filtering on the lower network and Ethernet 133 protocols over the bridge, use ebtables (under bridge netfilter 134 configuration). 135 136 Various modules exist for netfilter which replace the previous 137 masquerading (ipmasqadm), packet filtering (ipchains), transparent 138 proxying, and portforwarding mechanisms. Please see 139 <file:Documentation/Changes> under "iptables" for the location of 140 these packages. 141 142if NETFILTER 143 144config NETFILTER_DEBUG 145 bool "Network packet filtering debugging" 146 depends on NETFILTER 147 help 148 You can say Y here if you want to get additional messages useful in 149 debugging the netfilter code. 150 151config NETFILTER_ADVANCED 152 bool "Advanced netfilter configuration" 153 depends on NETFILTER 154 default y 155 help 156 If you say Y here you can select between all the netfilter modules. 157 If you say N the more unusual ones will not be shown and the 158 basic ones needed by most people will default to 'M'. 159 160 If unsure, say Y. 161 162config BRIDGE_NETFILTER 163 bool "Bridged IP/ARP packets filtering" 164 depends on BRIDGE && NETFILTER && INET 165 depends on NETFILTER_ADVANCED 166 default y 167 ---help--- 168 Enabling this option will let arptables resp. iptables see bridged 169 ARP resp. IP traffic. If you want a bridging firewall, you probably 170 want this option enabled. 171 Enabling or disabling this option doesn't enable or disable 172 ebtables. 173 174 If unsure, say N. 175 176source "net/netfilter/Kconfig" 177source "net/ipv4/netfilter/Kconfig" 178source "net/ipv6/netfilter/Kconfig" 179source "net/decnet/netfilter/Kconfig" 180source "net/bridge/netfilter/Kconfig" 181 182endif 183 184source "net/dccp/Kconfig" 185source "net/sctp/Kconfig" 186source "net/rds/Kconfig" 187source "net/tipc/Kconfig" 188source "net/atm/Kconfig" 189source "net/l2tp/Kconfig" 190source "net/802/Kconfig" 191source "net/bridge/Kconfig" 192source "net/dsa/Kconfig" 193source "net/8021q/Kconfig" 194source "net/decnet/Kconfig" 195source "net/llc/Kconfig" 196source "net/ipx/Kconfig" 197source "drivers/net/appletalk/Kconfig" 198source "net/x25/Kconfig" 199source "net/lapb/Kconfig" 200source "net/econet/Kconfig" 201source "net/wanrouter/Kconfig" 202source "net/phonet/Kconfig" 203source "net/ieee802154/Kconfig" 204source "net/sched/Kconfig" 205source "net/dcb/Kconfig" 206 207config RPS 208 boolean 209 depends on SMP && SYSFS 210 default y 211 212menu "Network testing" 213 214config NET_PKTGEN 215 tristate "Packet Generator (USE WITH CAUTION)" 216 depends on PROC_FS 217 ---help--- 218 This module will inject preconfigured packets, at a configurable 219 rate, out of a given interface. It is used for network interface 220 stress testing and performance analysis. If you don't understand 221 what was just said, you don't need it: say N. 222 223 Documentation on how to use the packet generator can be found 224 at <file:Documentation/networking/pktgen.txt>. 225 226 To compile this code as a module, choose M here: the 227 module will be called pktgen. 228 229config NET_TCPPROBE 230 tristate "TCP connection probing" 231 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES 232 ---help--- 233 This module allows for capturing the changes to TCP connection 234 state in response to incoming packets. It is used for debugging 235 TCP congestion avoidance modules. If you don't understand 236 what was just said, you don't need it: say N. 237 238 Documentation on how to use TCP connection probing can be found 239 at http://linux-net.osdl.org/index.php/TcpProbe 240 241 To compile this code as a module, choose M here: the 242 module will be called tcp_probe. 243 244config NET_DROP_MONITOR 245 boolean "Network packet drop alerting service" 246 depends on INET && EXPERIMENTAL && TRACEPOINTS 247 ---help--- 248 This feature provides an alerting service to userspace in the 249 event that packets are discarded in the network stack. Alerts 250 are broadcast via netlink socket to any listening user space 251 process. If you don't need network drop alerts, or if you are ok 252 just checking the various proc files and other utilities for 253 drop statistics, say N here. 254 255endmenu 256 257endmenu 258 259source "net/ax25/Kconfig" 260source "net/can/Kconfig" 261source "net/irda/Kconfig" 262source "net/bluetooth/Kconfig" 263source "net/rxrpc/Kconfig" 264 265config FIB_RULES 266 bool 267 268menuconfig WIRELESS 269 bool "Wireless" 270 depends on !S390 271 default y 272 273if WIRELESS 274 275source "net/wireless/Kconfig" 276source "net/mac80211/Kconfig" 277 278endif # WIRELESS 279 280source "net/wimax/Kconfig" 281 282source "net/rfkill/Kconfig" 283source "net/9p/Kconfig" 284source "net/caif/Kconfig" 285 286 287endif # if NET 288