1 # Example hostapd build time configuration
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.
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.
12 # Driver interface for Host AP driver
13 CONFIG_DRIVER_HOSTAP=y
15 # Driver interface for wired authenticator
16 #CONFIG_DRIVER_WIRED=y
18 # Driver interface for madwifi driver
19 #CONFIG_DRIVER_MADWIFI=y
20 #CFLAGS += -I../../madwifi # change to the madwifi source directory
22 # Driver interface for drivers using the nl80211 kernel interface
23 #CONFIG_DRIVER_NL80211=y
24 # driver_nl80211.c requires a rather new libnl (version 1.1) which may not be
25 # shipped with your distribution yet. If that is the case, you need to build
26 # newer libnl version and point the hostapd build to use it.
28 #CFLAGS += -I$(LIBNL)/include
29 #LIBS += -L$(LIBNL)/lib
31 # Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
33 #CFLAGS += -I/usr/local/include
34 #LIBS += -L/usr/local/lib
35 #LIBS_p += -L/usr/local/lib
36 #LIBS_c += -L/usr/local/lib
38 # Driver interface for no driver (e.g., RADIUS server only)
44 # WPA2/IEEE 802.11i RSN pre-authentication
47 # PeerKey handshake for Station to Station Link (IEEE 802.11e DLS)
50 # IEEE 802.11w (management frame protection)
51 # This version is an experimental implementation based on IEEE 802.11w/D1.0
52 # draft and is subject to change since the standard has not yet been finalized.
53 # Driver support is also needed for IEEE 802.11w.
56 # Integrated EAP server
59 # EAP-MD5 for the integrated EAP server
62 # EAP-TLS for the integrated EAP server
65 # EAP-MSCHAPv2 for the integrated EAP server
68 # EAP-PEAP for the integrated EAP server
71 # EAP-GTC for the integrated EAP server
74 # EAP-TTLS for the integrated EAP server
77 # EAP-SIM for the integrated EAP server
80 # EAP-AKA for the integrated EAP server
83 # EAP-AKA' for the integrated EAP server
84 # This requires CONFIG_EAP_AKA to be enabled, too.
85 #CONFIG_EAP_AKA_PRIME=y
87 # EAP-PAX for the integrated EAP server
90 # EAP-PSK for the integrated EAP server (this is _not_ needed for WPA-PSK)
93 # EAP-SAKE for the integrated EAP server
96 # EAP-GPSK for the integrated EAP server
98 # Include support for optional SHA256 cipher suite in EAP-GPSK
99 #CONFIG_EAP_GPSK_SHA256=y
101 # EAP-FAST for the integrated EAP server
102 # Note: Default OpenSSL package does not include support for all the
103 # functionality needed for EAP-FAST. If EAP-FAST is enabled with OpenSSL,
104 # the OpenSSL library must be patched (openssl-0.9.9-session-ticket.patch)
105 # to add the needed functions.
108 # Wi-Fi Protected Setup (WPS)
110 # Enable WSC 2.0 support
112 # Enable UPnP support for external WPS Registrars
118 # Trusted Network Connect (EAP-TNC)
121 # PKCS#12 (PFX) support (used to read private key and certificate file from
122 # a file that usually has extension .p12 or .pfx)
125 # RADIUS authentication server. This provides access to the integrated EAP
126 # server from external hosts using RADIUS.
127 #CONFIG_RADIUS_SERVER=y
129 # Build IPv6 support for RADIUS operations
132 # IEEE Std 802.11r-2008 (Fast BSS Transition)
135 # Use the hostapd's IEEE 802.11 authentication (ACL), but without
136 # the IEEE 802.11 Management capability (e.g., madwifi or FreeBSD/net80211)
137 #CONFIG_DRIVER_RADIUS_ACL=y
139 # IEEE 802.11n (High Throughput) support
142 # Remove debugging code that is printing out debug messages to stdout.
143 # This can be used to reduce the size of the hostapd considerably if debugging
144 # code is not needed.
145 #CONFIG_NO_STDOUT_DEBUG=y
147 # Add support for writing debug log to a file: -f /tmp/hostapd.log
148 # Disabled by default.
151 # Remove support for RADIUS accounting
152 #CONFIG_NO_ACCOUNTING=y
154 # Remove support for RADIUS
157 # Remove support for VLANs
160 # Enable support for fully dynamic VLANs. This enables hostapd to
161 # automatically create bridge and VLAN interfaces if necessary.
162 #CONFIG_FULL_DYNAMIC_VLAN=y
164 # Remove support for dumping state into a file on SIGUSR1 signal
165 # This can be used to reduce binary size at the cost of disabling a debugging
167 #CONFIG_NO_DUMP_STATE=y
169 # Enable tracing code for developer debugging
170 # This tracks use of memory allocations and other registrations and reports
171 # incorrect use with a backtrace of call (or allocation) location.
173 # For BSD, comment out these.
175 #LIBS_p += -lexecinfo
176 #LIBS_c += -lexecinfo
178 # Use libbfd to get more details for developer debugging
179 # This enables use of libbfd to get more detailed symbols for the backtraces
180 # generated by CONFIG_WPA_TRACE=y.
181 #CONFIG_WPA_TRACE_BFD=y
182 # For BSD, comment out these.
183 #LIBS += -lbfd -liberty -lz
184 #LIBS_p += -lbfd -liberty -lz
185 #LIBS_c += -lbfd -liberty -lz
187 # hostapd depends on strong random number generation being available from the
188 # operating system. os_get_random() function is used to fetch random data when
189 # needed, e.g., for key generation. On Linux and BSD systems, this works by
190 # reading /dev/urandom. It should be noted that the OS entropy pool needs to be
191 # properly initialized before hostapd is started. This is important especially
192 # on embedded devices that do not have a hardware random number generator and
193 # may by default start up with minimal entropy available for random number
196 # As a safety net, hostapd is by default trying to internally collect
197 # additional entropy for generating random data to mix in with the data
198 # fetched from the OS. This by itself is not considered to be very strong, but
199 # it may help in cases where the system pool is not initialized properly.
200 # However, it is very strongly recommended that the system pool is initialized
201 # with enough entropy either by using hardware assisted random number
202 # generatior or by storing state over device reboots.
204 # If the os_get_random() is known to provide strong ramdom data (e.g., on
205 # Linux/BSD, the board in question is known to have reliable source of random
206 # data from /dev/urandom), the internal hostapd random pool can be disabled.
207 # This will save some in binary size and CPU use. However, this should only be
208 # considered for builds that are known to be used on devices that meet the
209 # requirements described above.
210 #CONFIG_NO_RANDOM_POOL=y