1# Example hostapd build time configuration 2# 3# This file lists the configuration options that are used when building the 4# hostapd binary. All lines starting with # are ignored. Configuration option 5# lines must be commented out complete, if they are not to be included, i.e., 6# just setting VARIABLE=n is not disabling that variable. 7# 8# This file is included in Makefile, so variables like CFLAGS and LIBS can also 9# be modified from here. In most cass, these lines should use += in order not 10# to override previous values of the variables. 11 12# Driver interface for Host AP driver 13CONFIG_DRIVER_HOSTAP=y 14 15# Driver interface for wired authenticator 16#CONFIG_DRIVER_WIRED=y 17 18# Driver interface for drivers using the nl80211 kernel interface 19CONFIG_DRIVER_NL80211=y 20 21# QCA vendor extensions to nl80211 22#CONFIG_DRIVER_NL80211_QCA=y 23 24# driver_nl80211.c requires libnl. If you are compiling it yourself 25# you may need to point hostapd to your version of libnl. 26# 27#CFLAGS += -I$<path to libnl include files> 28#LIBS += -L$<path to libnl library files> 29 30# Use libnl v2.0 (or 3.0) libraries. 31#CONFIG_LIBNL20=y 32 33# Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is ignored) 34#CONFIG_LIBNL32=y 35 36 37# Driver interface for FreeBSD net80211 layer (e.g., Atheros driver) 38#CONFIG_DRIVER_BSD=y 39#CFLAGS += -I/usr/local/include 40#LIBS += -L/usr/local/lib 41#LIBS_p += -L/usr/local/lib 42#LIBS_c += -L/usr/local/lib 43 44# Driver interface for no driver (e.g., RADIUS server only) 45#CONFIG_DRIVER_NONE=y 46 47# IEEE 802.11F/IAPP 48CONFIG_IAPP=y 49 50# WPA2/IEEE 802.11i RSN pre-authentication 51CONFIG_RSN_PREAUTH=y 52 53# PeerKey handshake for Station to Station Link (IEEE 802.11e DLS) 54CONFIG_PEERKEY=y 55 56# IEEE 802.11w (management frame protection) 57CONFIG_IEEE80211W=y 58 59# Integrated EAP server 60CONFIG_EAP=y 61 62# EAP Re-authentication Protocol (ERP) in integrated EAP server 63CONFIG_ERP=y 64 65# EAP-MD5 for the integrated EAP server 66CONFIG_EAP_MD5=y 67 68# EAP-TLS for the integrated EAP server 69CONFIG_EAP_TLS=y 70 71# EAP-MSCHAPv2 for the integrated EAP server 72CONFIG_EAP_MSCHAPV2=y 73 74# EAP-PEAP for the integrated EAP server 75CONFIG_EAP_PEAP=y 76 77# EAP-GTC for the integrated EAP server 78CONFIG_EAP_GTC=y 79 80# EAP-TTLS for the integrated EAP server 81CONFIG_EAP_TTLS=y 82 83# EAP-SIM for the integrated EAP server 84#CONFIG_EAP_SIM=y 85 86# EAP-AKA for the integrated EAP server 87#CONFIG_EAP_AKA=y 88 89# EAP-AKA' for the integrated EAP server 90# This requires CONFIG_EAP_AKA to be enabled, too. 91#CONFIG_EAP_AKA_PRIME=y 92 93# EAP-PAX for the integrated EAP server 94#CONFIG_EAP_PAX=y 95 96# EAP-PSK for the integrated EAP server (this is _not_ needed for WPA-PSK) 97#CONFIG_EAP_PSK=y 98 99# EAP-pwd for the integrated EAP server (secure authentication with a password) 100#CONFIG_EAP_PWD=y 101 102# EAP-SAKE for the integrated EAP server 103#CONFIG_EAP_SAKE=y 104 105# EAP-GPSK for the integrated EAP server 106#CONFIG_EAP_GPSK=y 107# Include support for optional SHA256 cipher suite in EAP-GPSK 108#CONFIG_EAP_GPSK_SHA256=y 109 110# EAP-FAST for the integrated EAP server 111# Note: If OpenSSL is used as the TLS library, OpenSSL 1.0 or newer is needed 112# for EAP-FAST support. Older OpenSSL releases would need to be patched, e.g., 113# with openssl-0.9.8x-tls-extensions.patch, to add the needed functions. 114#CONFIG_EAP_FAST=y 115 116# Wi-Fi Protected Setup (WPS) 117#CONFIG_WPS=y 118# Enable UPnP support for external WPS Registrars 119#CONFIG_WPS_UPNP=y 120# Enable WPS support with NFC config method 121#CONFIG_WPS_NFC=y 122 123# EAP-IKEv2 124#CONFIG_EAP_IKEV2=y 125 126# Trusted Network Connect (EAP-TNC) 127#CONFIG_EAP_TNC=y 128 129# EAP-EKE for the integrated EAP server 130#CONFIG_EAP_EKE=y 131 132# PKCS#12 (PFX) support (used to read private key and certificate file from 133# a file that usually has extension .p12 or .pfx) 134CONFIG_PKCS12=y 135 136# RADIUS authentication server. This provides access to the integrated EAP 137# server from external hosts using RADIUS. 138#CONFIG_RADIUS_SERVER=y 139 140# Build IPv6 support for RADIUS operations 141CONFIG_IPV6=y 142 143# IEEE Std 802.11r-2008 (Fast BSS Transition) 144#CONFIG_IEEE80211R=y 145 146# Use the hostapd's IEEE 802.11 authentication (ACL), but without 147# the IEEE 802.11 Management capability (e.g., FreeBSD/net80211) 148#CONFIG_DRIVER_RADIUS_ACL=y 149 150# IEEE 802.11n (High Throughput) support 151#CONFIG_IEEE80211N=y 152 153# Wireless Network Management (IEEE Std 802.11v-2011) 154# Note: This is experimental and not complete implementation. 155#CONFIG_WNM=y 156 157# IEEE 802.11ac (Very High Throughput) support 158#CONFIG_IEEE80211AC=y 159 160# Remove debugging code that is printing out debug messages to stdout. 161# This can be used to reduce the size of the hostapd considerably if debugging 162# code is not needed. 163#CONFIG_NO_STDOUT_DEBUG=y 164 165# Add support for writing debug log to a file: -f /tmp/hostapd.log 166# Disabled by default. 167#CONFIG_DEBUG_FILE=y 168 169# Add support for sending all debug messages (regardless of debug verbosity) 170# to the Linux kernel tracing facility. This helps debug the entire stack by 171# making it easy to record everything happening from the driver up into the 172# same file, e.g., using trace-cmd. 173#CONFIG_DEBUG_LINUX_TRACING=y 174 175# Remove support for RADIUS accounting 176#CONFIG_NO_ACCOUNTING=y 177 178# Remove support for RADIUS 179#CONFIG_NO_RADIUS=y 180 181# Remove support for VLANs 182#CONFIG_NO_VLAN=y 183 184# Enable support for fully dynamic VLANs. This enables hostapd to 185# automatically create bridge and VLAN interfaces if necessary. 186#CONFIG_FULL_DYNAMIC_VLAN=y 187 188# Use netlink-based kernel API for VLAN operations instead of ioctl() 189# Note: This requires libnl 3.1 or newer. 190#CONFIG_VLAN_NETLINK=y 191 192# Remove support for dumping internal state through control interface commands 193# This can be used to reduce binary size at the cost of disabling a debugging 194# option. 195#CONFIG_NO_DUMP_STATE=y 196 197# Enable tracing code for developer debugging 198# This tracks use of memory allocations and other registrations and reports 199# incorrect use with a backtrace of call (or allocation) location. 200#CONFIG_WPA_TRACE=y 201# For BSD, comment out these. 202#LIBS += -lexecinfo 203#LIBS_p += -lexecinfo 204#LIBS_c += -lexecinfo 205 206# Use libbfd to get more details for developer debugging 207# This enables use of libbfd to get more detailed symbols for the backtraces 208# generated by CONFIG_WPA_TRACE=y. 209#CONFIG_WPA_TRACE_BFD=y 210# For BSD, comment out these. 211#LIBS += -lbfd -liberty -lz 212#LIBS_p += -lbfd -liberty -lz 213#LIBS_c += -lbfd -liberty -lz 214 215# hostapd depends on strong random number generation being available from the 216# operating system. os_get_random() function is used to fetch random data when 217# needed, e.g., for key generation. On Linux and BSD systems, this works by 218# reading /dev/urandom. It should be noted that the OS entropy pool needs to be 219# properly initialized before hostapd is started. This is important especially 220# on embedded devices that do not have a hardware random number generator and 221# may by default start up with minimal entropy available for random number 222# generation. 223# 224# As a safety net, hostapd is by default trying to internally collect 225# additional entropy for generating random data to mix in with the data 226# fetched from the OS. This by itself is not considered to be very strong, but 227# it may help in cases where the system pool is not initialized properly. 228# However, it is very strongly recommended that the system pool is initialized 229# with enough entropy either by using hardware assisted random number 230# generator or by storing state over device reboots. 231# 232# hostapd can be configured to maintain its own entropy store over restarts to 233# enhance random number generation. This is not perfect, but it is much more 234# secure than using the same sequence of random numbers after every reboot. 235# This can be enabled with -e<entropy file> command line option. The specified 236# file needs to be readable and writable by hostapd. 237# 238# If the os_get_random() is known to provide strong random data (e.g., on 239# Linux/BSD, the board in question is known to have reliable source of random 240# data from /dev/urandom), the internal hostapd random pool can be disabled. 241# This will save some in binary size and CPU use. However, this should only be 242# considered for builds that are known to be used on devices that meet the 243# requirements described above. 244#CONFIG_NO_RANDOM_POOL=y 245 246# Should we use poll instead of select? Select is used by default. 247#CONFIG_ELOOP_POLL=y 248 249# Should we use epoll instead of select? Select is used by default. 250#CONFIG_ELOOP_EPOLL=y 251 252# Should we use kqueue instead of select? Select is used by default. 253#CONFIG_ELOOP_KQUEUE=y 254 255# Select TLS implementation 256# openssl = OpenSSL (default) 257# gnutls = GnuTLS 258# internal = Internal TLSv1 implementation (experimental) 259# none = Empty template 260#CONFIG_TLS=openssl 261 262# TLS-based EAP methods require at least TLS v1.0. Newer version of TLS (v1.1) 263# can be enabled to get a stronger construction of messages when block ciphers 264# are used. 265#CONFIG_TLSV11=y 266 267# TLS-based EAP methods require at least TLS v1.0. Newer version of TLS (v1.2) 268# can be enabled to enable use of stronger crypto algorithms. 269#CONFIG_TLSV12=y 270 271# If CONFIG_TLS=internal is used, additional library and include paths are 272# needed for LibTomMath. Alternatively, an integrated, minimal version of 273# LibTomMath can be used. See beginning of libtommath.c for details on benefits 274# and drawbacks of this option. 275#CONFIG_INTERNAL_LIBTOMMATH=y 276#ifndef CONFIG_INTERNAL_LIBTOMMATH 277#LTM_PATH=/usr/src/libtommath-0.39 278#CFLAGS += -I$(LTM_PATH) 279#LIBS += -L$(LTM_PATH) 280#LIBS_p += -L$(LTM_PATH) 281#endif 282# At the cost of about 4 kB of additional binary size, the internal LibTomMath 283# can be configured to include faster routines for exptmod, sqr, and div to 284# speed up DH and RSA calculation considerably 285#CONFIG_INTERNAL_LIBTOMMATH_FAST=y 286 287# Interworking (IEEE 802.11u) 288# This can be used to enable functionality to improve interworking with 289# external networks. 290#CONFIG_INTERWORKING=y 291 292# Hotspot 2.0 293#CONFIG_HS20=y 294 295# Enable SQLite database support in hlr_auc_gw, EAP-SIM DB, and eap_user_file 296#CONFIG_SQLITE=y 297 298# Enable Fast Session Transfer (FST) 299#CONFIG_FST=y 300 301# Enable CLI commands for FST testing 302#CONFIG_FST_TEST=y 303 304# Testing options 305# This can be used to enable some testing options (see also the example 306# configuration file) that are really useful only for testing clients that 307# connect to this hostapd. These options allow, for example, to drop a 308# certain percentage of probe requests or auth/(re)assoc frames. 309# 310#CONFIG_TESTING_OPTIONS=y 311 312# Automatic Channel Selection 313# This will allow hostapd to pick the channel automatically when channel is set 314# to "acs_survey" or "0". Eventually, other ACS algorithms can be added in 315# similar way. 316# 317# Automatic selection is currently only done through initialization, later on 318# we hope to do background checks to keep us moving to more ideal channels as 319# time goes by. ACS is currently only supported through the nl80211 driver and 320# your driver must have survey dump capability that is filled by the driver 321# during scanning. 322# 323# You can customize the ACS survey algorithm with the hostapd.conf variable 324# acs_num_scans. 325# 326# Supported ACS drivers: 327# * ath9k 328# * ath5k 329# * ath10k 330# 331# For more details refer to: 332# http://wireless.kernel.org/en/users/Documentation/acs 333# 334#CONFIG_ACS=y 335 336# Multiband Operation support 337# These extentions facilitate efficient use of multiple frequency bands 338# available to the AP and the devices that may associate with it. 339#CONFIG_MBO=y 340 341# Client Taxonomy 342# Has the AP retain the Probe Request and (Re)Association Request frames from 343# a client, from which a signature can be produced which can identify the model 344# of client device like "Nexus 6P" or "iPhone 5s". 345#CONFIG_TAXONOMY=y 346