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 WEXT_CORE || 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 select CRYPTO 56 select CRYPTO_AES 57 ---help--- 58 These are the protocols used on the Internet and on most local 59 Ethernets. It is highly recommended to say Y here (this will enlarge 60 your kernel by about 400 KB), since some programs (e.g. the X window 61 system) use TCP/IP even if your machine is not connected to any 62 other computer. You will get the so-called loopback device which 63 allows you to ping yourself (great fun, that!). 64 65 For an excellent introduction to Linux networking, please read the 66 Linux Networking HOWTO, available from 67 <http://www.tldp.org/docs.html#howto>. 68 69 If you say Y here and also to "/proc file system support" and 70 "Sysctl support" below, you can change various aspects of the 71 behavior of the TCP/IP code by writing to the (virtual) files in 72 /proc/sys/net/ipv4/*; the options are explained in the file 73 <file:Documentation/networking/ip-sysctl.txt>. 74 75 Short answer: say Y. 76 77if INET 78source "net/ipv4/Kconfig" 79source "net/ipv6/Kconfig" 80source "net/netlabel/Kconfig" 81 82endif # if INET 83 84config ANDROID_PARANOID_NETWORK 85 bool "Only allow certain groups to create sockets" 86 default y 87 help 88 none 89 90config NET_ACTIVITY_STATS 91 bool "Network activity statistics tracking" 92 default y 93 help 94 Network activity statistics are useful for tracking wireless 95 modem activity on 2G, 3G, 4G wireless networks. Counts number of 96 transmissions and groups them in specified time buckets. 97 98config NETWORK_SECMARK 99 bool "Security Marking" 100 help 101 This enables security marking of network packets, similar 102 to nfmark, but designated for security purposes. 103 If you are unsure how to answer this question, answer N. 104 105config NETWORK_PHY_TIMESTAMPING 106 bool "Timestamping in PHY devices" 107 help 108 This allows timestamping of network packets by PHYs with 109 hardware timestamping capabilities. This option adds some 110 overhead in the transmit and receive paths. 111 112 If you are unsure how to answer this question, answer N. 113 114menuconfig NETFILTER 115 bool "Network packet filtering framework (Netfilter)" 116 ---help--- 117 Netfilter is a framework for filtering and mangling network packets 118 that pass through your Linux box. 119 120 The most common use of packet filtering is to run your Linux box as 121 a firewall protecting a local network from the Internet. The type of 122 firewall provided by this kernel support is called a "packet 123 filter", which means that it can reject individual network packets 124 based on type, source, destination etc. The other kind of firewall, 125 a "proxy-based" one, is more secure but more intrusive and more 126 bothersome to set up; it inspects the network traffic much more 127 closely, modifies it and has knowledge about the higher level 128 protocols, which a packet filter lacks. Moreover, proxy-based 129 firewalls often require changes to the programs running on the local 130 clients. Proxy-based firewalls don't need support by the kernel, but 131 they are often combined with a packet filter, which only works if 132 you say Y here. 133 134 You should also say Y here if you intend to use your Linux box as 135 the gateway to the Internet for a local network of machines without 136 globally valid IP addresses. This is called "masquerading": if one 137 of the computers on your local network wants to send something to 138 the outside, your box can "masquerade" as that computer, i.e. it 139 forwards the traffic to the intended outside destination, but 140 modifies the packets to make it look like they came from the 141 firewall box itself. It works both ways: if the outside host 142 replies, the Linux box will silently forward the traffic to the 143 correct local computer. This way, the computers on your local net 144 are completely invisible to the outside world, even though they can 145 reach the outside and can receive replies. It is even possible to 146 run globally visible servers from within a masqueraded local network 147 using a mechanism called portforwarding. Masquerading is also often 148 called NAT (Network Address Translation). 149 150 Another use of Netfilter is in transparent proxying: if a machine on 151 the local network tries to connect to an outside host, your Linux 152 box can transparently forward the traffic to a local server, 153 typically a caching proxy server. 154 155 Yet another use of Netfilter is building a bridging firewall. Using 156 a bridge with Network packet filtering enabled makes iptables "see" 157 the bridged traffic. For filtering on the lower network and Ethernet 158 protocols over the bridge, use ebtables (under bridge netfilter 159 configuration). 160 161 Various modules exist for netfilter which replace the previous 162 masquerading (ipmasqadm), packet filtering (ipchains), transparent 163 proxying, and portforwarding mechanisms. Please see 164 <file:Documentation/Changes> under "iptables" for the location of 165 these packages. 166 167if NETFILTER 168 169config NETFILTER_DEBUG 170 bool "Network packet filtering debugging" 171 depends on NETFILTER 172 help 173 You can say Y here if you want to get additional messages useful in 174 debugging the netfilter code. 175 176config NETFILTER_ADVANCED 177 bool "Advanced netfilter configuration" 178 depends on NETFILTER 179 default y 180 help 181 If you say Y here you can select between all the netfilter modules. 182 If you say N the more unusual ones will not be shown and the 183 basic ones needed by most people will default to 'M'. 184 185 If unsure, say Y. 186 187config BRIDGE_NETFILTER 188 bool "Bridged IP/ARP packets filtering" 189 depends on BRIDGE && NETFILTER && INET 190 depends on NETFILTER_ADVANCED 191 default y 192 ---help--- 193 Enabling this option will let arptables resp. iptables see bridged 194 ARP resp. IP traffic. If you want a bridging firewall, you probably 195 want this option enabled. 196 Enabling or disabling this option doesn't enable or disable 197 ebtables. 198 199 If unsure, say N. 200 201source "net/netfilter/Kconfig" 202source "net/ipv4/netfilter/Kconfig" 203source "net/ipv6/netfilter/Kconfig" 204source "net/decnet/netfilter/Kconfig" 205source "net/bridge/netfilter/Kconfig" 206 207endif 208 209source "net/dccp/Kconfig" 210source "net/sctp/Kconfig" 211source "net/rds/Kconfig" 212source "net/tipc/Kconfig" 213source "net/atm/Kconfig" 214source "net/l2tp/Kconfig" 215source "net/802/Kconfig" 216source "net/bridge/Kconfig" 217source "net/dsa/Kconfig" 218source "net/8021q/Kconfig" 219source "net/decnet/Kconfig" 220source "net/llc/Kconfig" 221source "net/ipx/Kconfig" 222source "drivers/net/appletalk/Kconfig" 223source "net/x25/Kconfig" 224source "net/lapb/Kconfig" 225source "net/phonet/Kconfig" 226source "net/ieee802154/Kconfig" 227source "net/mac802154/Kconfig" 228source "net/sched/Kconfig" 229source "net/dcb/Kconfig" 230source "net/dns_resolver/Kconfig" 231source "net/batman-adv/Kconfig" 232source "net/openvswitch/Kconfig" 233source "net/vmw_vsock/Kconfig" 234source "net/netlink/Kconfig" 235 236config RPS 237 boolean "RPS" 238 depends on SMP && SYSFS && USE_GENERIC_SMP_HELPERS 239 default y 240 241config RFS_ACCEL 242 boolean 243 depends on RPS && GENERIC_HARDIRQS 244 select CPU_RMAP 245 default y 246 247config XPS 248 boolean 249 depends on SMP && USE_GENERIC_SMP_HELPERS 250 default y 251 252config NETPRIO_CGROUP 253 tristate "Network priority cgroup" 254 depends on CGROUPS 255 ---help--- 256 Cgroup subsystem for use in assigning processes to network priorities on 257 a per-interface basis 258 259config BQL 260 boolean 261 depends on SYSFS 262 select DQL 263 default y 264 265config BPF_JIT 266 bool "enable BPF Just In Time compiler" 267 depends on HAVE_BPF_JIT 268 depends on MODULES 269 ---help--- 270 Berkeley Packet Filter filtering capabilities are normally handled 271 by an interpreter. This option allows kernel to generate a native 272 code when filter is loaded in memory. This should speedup 273 packet sniffing (libpcap/tcpdump). Note : Admin should enable 274 this feature changing /proc/sys/net/core/bpf_jit_enable 275 276menu "Network testing" 277 278config NET_PKTGEN 279 tristate "Packet Generator (USE WITH CAUTION)" 280 depends on PROC_FS 281 ---help--- 282 This module will inject preconfigured packets, at a configurable 283 rate, out of a given interface. It is used for network interface 284 stress testing and performance analysis. If you don't understand 285 what was just said, you don't need it: say N. 286 287 Documentation on how to use the packet generator can be found 288 at <file:Documentation/networking/pktgen.txt>. 289 290 To compile this code as a module, choose M here: the 291 module will be called pktgen. 292 293config NET_TCPPROBE 294 tristate "TCP connection probing" 295 depends on INET && PROC_FS && KPROBES 296 ---help--- 297 This module allows for capturing the changes to TCP connection 298 state in response to incoming packets. It is used for debugging 299 TCP congestion avoidance modules. If you don't understand 300 what was just said, you don't need it: say N. 301 302 Documentation on how to use TCP connection probing can be found 303 at: 304 305 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe 306 307 To compile this code as a module, choose M here: the 308 module will be called tcp_probe. 309 310config NET_DROP_MONITOR 311 tristate "Network packet drop alerting service" 312 depends on INET && TRACEPOINTS 313 ---help--- 314 This feature provides an alerting service to userspace in the 315 event that packets are discarded in the network stack. Alerts 316 are broadcast via netlink socket to any listening user space 317 process. If you don't need network drop alerts, or if you are ok 318 just checking the various proc files and other utilities for 319 drop statistics, say N here. 320 321endmenu 322 323endmenu 324 325source "net/ax25/Kconfig" 326source "net/can/Kconfig" 327source "net/irda/Kconfig" 328source "net/bluetooth/Kconfig" 329source "net/rxrpc/Kconfig" 330 331config FIB_RULES 332 bool 333 334menuconfig WIRELESS 335 bool "Wireless" 336 depends on !S390 337 default y 338 339if WIRELESS 340 341source "net/wireless/Kconfig" 342source "net/mac80211/Kconfig" 343 344endif # WIRELESS 345 346source "net/wimax/Kconfig" 347 348source "net/rfkill/Kconfig" 349source "net/9p/Kconfig" 350source "net/caif/Kconfig" 351source "net/ceph/Kconfig" 352source "net/nfc/Kconfig" 353 354 355endif # if NET 356 357# Used by archs to tell that they support BPF_JIT 358config HAVE_BPF_JIT 359 bool 360