1# 2# Network configuration 3# 4 5menuconfig NET 6 bool "Networking support" 7 ---help--- 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 11 other computer. 12 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>. 18 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>. 22 23if NET 24 25menu "Networking options" 26 27config COMPAT_NET_DEV_OPS 28 def_bool y 29 30source "net/packet/Kconfig" 31source "net/unix/Kconfig" 32source "net/xfrm/Kconfig" 33source "net/iucv/Kconfig" 34 35config INET 36 bool "TCP/IP networking" 37 ---help--- 38 These are the protocols used on the Internet and on most local 39 Ethernets. It is highly recommended to say Y here (this will enlarge 40 your kernel by about 400 KB), since some programs (e.g. the X window 41 system) use TCP/IP even if your machine is not connected to any 42 other computer. You will get the so-called loopback device which 43 allows you to ping yourself (great fun, that!). 44 45 For an excellent introduction to Linux networking, please read the 46 Linux Networking HOWTO, available from 47 <http://www.tldp.org/docs.html#howto>. 48 49 If you say Y here and also to "/proc file system support" and 50 "Sysctl support" below, you can change various aspects of the 51 behavior of the TCP/IP code by writing to the (virtual) files in 52 /proc/sys/net/ipv4/*; the options are explained in the file 53 <file:Documentation/networking/ip-sysctl.txt>. 54 55 Short answer: say Y. 56 57if INET 58source "net/ipv4/Kconfig" 59source "net/ipv6/Kconfig" 60source "net/netlabel/Kconfig" 61 62endif # if INET 63 64config ANDROID_PARANOID_NETWORK 65 bool "Only allow certain groups to create sockets" 66 default y 67 help 68 none 69 70config NETWORK_SECMARK 71 bool "Security Marking" 72 help 73 This enables security marking of network packets, similar 74 to nfmark, but designated for security purposes. 75 If you are unsure how to answer this question, answer N. 76 77menuconfig NETFILTER 78 bool "Network packet filtering framework (Netfilter)" 79 ---help--- 80 Netfilter is a framework for filtering and mangling network packets 81 that pass through your Linux box. 82 83 The most common use of packet filtering is to run your Linux box as 84 a firewall protecting a local network from the Internet. The type of 85 firewall provided by this kernel support is called a "packet 86 filter", which means that it can reject individual network packets 87 based on type, source, destination etc. The other kind of firewall, 88 a "proxy-based" one, is more secure but more intrusive and more 89 bothersome to set up; it inspects the network traffic much more 90 closely, modifies it and has knowledge about the higher level 91 protocols, which a packet filter lacks. Moreover, proxy-based 92 firewalls often require changes to the programs running on the local 93 clients. Proxy-based firewalls don't need support by the kernel, but 94 they are often combined with a packet filter, which only works if 95 you say Y here. 96 97 You should also say Y here if you intend to use your Linux box as 98 the gateway to the Internet for a local network of machines without 99 globally valid IP addresses. This is called "masquerading": if one 100 of the computers on your local network wants to send something to 101 the outside, your box can "masquerade" as that computer, i.e. it 102 forwards the traffic to the intended outside destination, but 103 modifies the packets to make it look like they came from the 104 firewall box itself. It works both ways: if the outside host 105 replies, the Linux box will silently forward the traffic to the 106 correct local computer. This way, the computers on your local net 107 are completely invisible to the outside world, even though they can 108 reach the outside and can receive replies. It is even possible to 109 run globally visible servers from within a masqueraded local network 110 using a mechanism called portforwarding. Masquerading is also often 111 called NAT (Network Address Translation). 112 113 Another use of Netfilter is in transparent proxying: if a machine on 114 the local network tries to connect to an outside host, your Linux 115 box can transparently forward the traffic to a local server, 116 typically a caching proxy server. 117 118 Yet another use of Netfilter is building a bridging firewall. Using 119 a bridge with Network packet filtering enabled makes iptables "see" 120 the bridged traffic. For filtering on the lower network and Ethernet 121 protocols over the bridge, use ebtables (under bridge netfilter 122 configuration). 123 124 Various modules exist for netfilter which replace the previous 125 masquerading (ipmasqadm), packet filtering (ipchains), transparent 126 proxying, and portforwarding mechanisms. Please see 127 <file:Documentation/Changes> under "iptables" for the location of 128 these packages. 129 130 Make sure to say N to "Fast switching" below if you intend to say Y 131 here, as Fast switching currently bypasses netfilter. 132 133 Chances are that you should say Y here if you compile a kernel which 134 will run as a router and N for regular hosts. If unsure, say N. 135 136if NETFILTER 137 138config NETFILTER_DEBUG 139 bool "Network packet filtering debugging" 140 depends on NETFILTER 141 help 142 You can say Y here if you want to get additional messages useful in 143 debugging the netfilter code. 144 145config NETFILTER_ADVANCED 146 bool "Advanced netfilter configuration" 147 depends on NETFILTER 148 default y 149 help 150 If you say Y here you can select between all the netfilter modules. 151 If you say N the more ununsual ones will not be shown and the 152 basic ones needed by most people will default to 'M'. 153 154 If unsure, say Y. 155 156config BRIDGE_NETFILTER 157 bool "Bridged IP/ARP packets filtering" 158 depends on BRIDGE && NETFILTER && INET 159 depends on NETFILTER_ADVANCED 160 default y 161 ---help--- 162 Enabling this option will let arptables resp. iptables see bridged 163 ARP resp. IP traffic. If you want a bridging firewall, you probably 164 want this option enabled. 165 Enabling or disabling this option doesn't enable or disable 166 ebtables. 167 168 If unsure, say N. 169 170source "net/netfilter/Kconfig" 171source "net/ipv4/netfilter/Kconfig" 172source "net/ipv6/netfilter/Kconfig" 173source "net/decnet/netfilter/Kconfig" 174source "net/bridge/netfilter/Kconfig" 175 176endif 177 178source "net/dccp/Kconfig" 179source "net/sctp/Kconfig" 180source "net/tipc/Kconfig" 181source "net/atm/Kconfig" 182source "net/802/Kconfig" 183source "net/bridge/Kconfig" 184source "net/dsa/Kconfig" 185source "net/8021q/Kconfig" 186source "net/decnet/Kconfig" 187source "net/llc/Kconfig" 188source "net/ipx/Kconfig" 189source "drivers/net/appletalk/Kconfig" 190source "net/x25/Kconfig" 191source "net/lapb/Kconfig" 192source "net/econet/Kconfig" 193source "net/wanrouter/Kconfig" 194source "net/sched/Kconfig" 195source "net/dcb/Kconfig" 196 197menu "Network testing" 198 199config NET_PKTGEN 200 tristate "Packet Generator (USE WITH CAUTION)" 201 depends on PROC_FS 202 ---help--- 203 This module will inject preconfigured packets, at a configurable 204 rate, out of a given interface. It is used for network interface 205 stress testing and performance analysis. If you don't understand 206 what was just said, you don't need it: say N. 207 208 Documentation on how to use the packet generator can be found 209 at <file:Documentation/networking/pktgen.txt>. 210 211 To compile this code as a module, choose M here: the 212 module will be called pktgen. 213 214config NET_TCPPROBE 215 tristate "TCP connection probing" 216 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES 217 ---help--- 218 This module allows for capturing the changes to TCP connection 219 state in response to incoming packets. It is used for debugging 220 TCP congestion avoidance modules. If you don't understand 221 what was just said, you don't need it: say N. 222 223 Documentation on how to use TCP connection probing can be found 224 at http://linux-net.osdl.org/index.php/TcpProbe 225 226 To compile this code as a module, choose M here: the 227 module will be called tcp_probe. 228 229endmenu 230 231endmenu 232 233source "net/ax25/Kconfig" 234source "net/can/Kconfig" 235source "net/irda/Kconfig" 236source "net/bluetooth/Kconfig" 237source "net/rxrpc/Kconfig" 238source "net/phonet/Kconfig" 239 240config FIB_RULES 241 bool 242 243menuconfig WIRELESS 244 bool "Wireless" 245 depends on !S390 246 default y 247 248if WIRELESS 249 250source "net/wireless/Kconfig" 251source "net/mac80211/Kconfig" 252 253endif # WIRELESS 254 255source "net/wimax/Kconfig" 256 257source "net/rfkill/Kconfig" 258source "net/9p/Kconfig" 259 260endif # if NET 261