blob: dd05c2ffde46da60fdfda0ab79a6056c639abe44 [file] [log] [blame]
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001##### hostapd configuration file ##############################################
2# Empty lines and lines starting with # are ignored
3
4# AP netdevice name (without 'ap' postfix, i.e., wlan0 uses wlan0ap for
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -08005# management frames with the Host AP driver); wlan0 with many nl80211 drivers
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07006interface=wlan0
7
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -08008# In case of atheros and nl80211 driver interfaces, an additional
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07009# configuration parameter, bridge, may be used to notify hostapd if the
10# interface is included in a bridge. This parameter is not used with Host AP
11# driver. If the bridge parameter is not set, the drivers will automatically
12# figure out the bridge interface (assuming sysfs is enabled and mounted to
13# /sys) and this parameter may not be needed.
14#
15# For nl80211, this parameter can be used to request the AP interface to be
16# added to the bridge automatically (brctl may refuse to do this before hostapd
17# has been started to change the interface mode). If needed, the bridge
18# interface is also created.
19#bridge=br0
20
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -080021# Driver interface type (hostap/wired/none/nl80211/bsd);
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070022# default: hostap). nl80211 is used with all Linux mac80211 drivers.
23# Use driver=none if building hostapd as a standalone RADIUS server that does
24# not control any wireless/wired driver.
25# driver=hostap
26
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -080027# Driver interface parameters (mainly for development testing use)
28# driver_params=<params>
29
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070030# hostapd event logger configuration
31#
32# Two output method: syslog and stdout (only usable if not forking to
33# background).
34#
35# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
36# modules):
37# bit 0 (1) = IEEE 802.11
38# bit 1 (2) = IEEE 802.1X
39# bit 2 (4) = RADIUS
40# bit 3 (8) = WPA
41# bit 4 (16) = driver interface
42# bit 5 (32) = IAPP
43# bit 6 (64) = MLME
44#
45# Levels (minimum value for logged events):
46# 0 = verbose debugging
47# 1 = debugging
48# 2 = informational messages
49# 3 = notification
50# 4 = warning
51#
52logger_syslog=-1
53logger_syslog_level=2
54logger_stdout=-1
55logger_stdout_level=2
56
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070057# Interface for separate control program. If this is specified, hostapd
58# will create this directory and a UNIX domain socket for listening to requests
59# from external programs (CLI/GUI, etc.) for status information and
60# configuration. The socket file will be named based on the interface name, so
61# multiple hostapd processes/interfaces can be run at the same time if more
62# than one interface is used.
63# /var/run/hostapd is the recommended directory for sockets and by default,
64# hostapd_cli will use it when trying to connect with hostapd.
65ctrl_interface=/var/run/hostapd
66
67# Access control for the control interface can be configured by setting the
68# directory to allow only members of a group to use sockets. This way, it is
69# possible to run hostapd as root (since it needs to change network
70# configuration and open raw sockets) and still allow GUI/CLI components to be
71# run as non-root users. However, since the control interface can be used to
72# change the network configuration, this access needs to be protected in many
73# cases. By default, hostapd is configured to use gid 0 (root). If you
74# want to allow non-root users to use the contron interface, add a new group
75# and change this value to match with that group. Add users that should have
76# control interface access to this group.
77#
78# This variable can be a group name or gid.
79#ctrl_interface_group=wheel
80ctrl_interface_group=0
81
82
83##### IEEE 802.11 related configuration #######################################
84
85# SSID to be used in IEEE 802.11 management frames
86ssid=test
Dmitry Shmidt61d9df32012-08-29 16:22:06 -070087# Alternative formats for configuring SSID
88# (double quoted string, hexdump, printf-escaped string)
89#ssid2="test"
90#ssid2=74657374
91#ssid2=P"hello\nthere"
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070092
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -080093# UTF-8 SSID: Whether the SSID is to be interpreted using UTF-8 encoding
94#utf8_ssid=1
95
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070096# Country code (ISO/IEC 3166-1). Used to set regulatory domain.
97# Set as needed to indicate country in which device is operating.
98# This can limit available channels and transmit power.
99#country_code=US
100
101# Enable IEEE 802.11d. This advertises the country_code and the set of allowed
102# channels and transmit power levels based on the regulatory limits. The
103# country_code setting must be configured with the correct country for
104# IEEE 802.11d functions.
105# (default: 0 = disabled)
106#ieee80211d=1
107
Dmitry Shmidtea69e842013-05-13 14:52:28 -0700108# Enable IEEE 802.11h. This enables radar detection and DFS support if
109# available. DFS support is required on outdoor 5 GHz channels in most countries
110# of the world. This can be used only with ieee80211d=1.
111# (default: 0 = disabled)
112#ieee80211h=1
113
Dmitry Shmidtf21452a2014-02-26 10:55:25 -0800114# Add Power Constraint element to Beacon and Probe Response frames
115# This config option adds Power Constraint element when applicable and Country
116# element is added. Power Constraint element is required by Transmit Power
117# Control. This can be used only with ieee80211d=1.
118# Valid values are 0..255.
119#local_pwr_constraint=3
120
121# Set Spectrum Management subfield in the Capability Information field.
122# This config option forces the Spectrum Management bit to be set. When this
123# option is not set, the value of the Spectrum Management bit depends on whether
124# DFS or TPC is required by regulatory authorities. This can be used only with
125# ieee80211d=1 and local_pwr_constraint configured.
126#spectrum_mgmt_required=1
127
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700128# Operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g,
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800129# ad = IEEE 802.11ad (60 GHz); a/g options are used with IEEE 802.11n, too, to
130# specify band)
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700131# Default: IEEE 802.11b
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800132hw_mode=g
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700133
134# Channel number (IEEE 802.11)
135# (default: 0, i.e., not set)
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800136# Please note that some drivers do not use this value from hostapd and the
137# channel will need to be configured separately with iwconfig.
Dmitry Shmidt391c59f2013-09-03 12:16:28 -0700138#
139# If CONFIG_ACS build option is enabled, the channel can be selected
140# automatically at run time by setting channel=acs_survey or channel=0, both of
141# which will enable the ACS survey based algorithm.
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800142channel=1
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700143
Dmitry Shmidt391c59f2013-09-03 12:16:28 -0700144# ACS tuning - Automatic Channel Selection
145# See: http://wireless.kernel.org/en/users/Documentation/acs
146#
147# You can customize the ACS survey algorithm with following variables:
148#
149# acs_num_scans requirement is 1..100 - number of scans to be performed that
150# are used to trigger survey data gathering of an underlying device driver.
151# Scans are passive and typically take a little over 100ms (depending on the
152# driver) on each available channel for given hw_mode. Increasing this value
153# means sacrificing startup time and gathering more data wrt channel
154# interference that may help choosing a better channel. This can also help fine
155# tune the ACS scan time in case a driver has different scan dwell times.
156#
Dmitry Shmidt7f656022015-02-25 14:36:37 -0800157# acs_chan_bias is a space-separated list of <channel>:<bias> pairs. It can be
158# used to increase (or decrease) the likelihood of a specific channel to be
159# selected by the ACS algorithm. The total interference factor for each channel
160# gets multiplied by the specified bias value before finding the channel with
161# the lowest value. In other words, values between 0.0 and 1.0 can be used to
162# make a channel more likely to be picked while values larger than 1.0 make the
163# specified channel less likely to be picked. This can be used, e.g., to prefer
164# the commonly used 2.4 GHz band channels 1, 6, and 11 (which is the default
165# behavior on 2.4 GHz band if no acs_chan_bias parameter is specified).
166#
Dmitry Shmidt391c59f2013-09-03 12:16:28 -0700167# Defaults:
168#acs_num_scans=5
Dmitry Shmidt7f656022015-02-25 14:36:37 -0800169#acs_chan_bias=1:0.8 6:0.8 11:0.8
Dmitry Shmidt391c59f2013-09-03 12:16:28 -0700170
Dmitry Shmidt98660862014-03-11 17:26:21 -0700171# Channel list restriction. This option allows hostapd to select one of the
Dmitry Shmidt2f74e362015-01-21 13:19:05 -0800172# provided channels when a channel should be automatically selected.
Dmitry Shmidt98660862014-03-11 17:26:21 -0700173# Default: not set (allow any enabled channel to be selected)
174#chanlist=100 104 108 112 116
175
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700176# Beacon interval in kus (1.024 ms) (default: 100; range 15..65535)
177beacon_int=100
178
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800179# DTIM (delivery traffic information message) period (range 1..255):
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700180# number of beacons between DTIMs (1 = every beacon includes DTIM element)
181# (default: 2)
182dtim_period=2
183
184# Maximum number of stations allowed in station table. New stations will be
185# rejected after the station table is full. IEEE 802.11 has a limit of 2007
186# different association IDs, so this number should not be larger than that.
187# (default: 2007)
188max_num_sta=255
189
190# RTS/CTS threshold; 2347 = disabled (default); range 0..2347
191# If this field is not included in hostapd.conf, hostapd will not control
192# RTS threshold and 'iwconfig wlan# rts <val>' can be used to set it.
193rts_threshold=2347
194
195# Fragmentation threshold; 2346 = disabled (default); range 256..2346
196# If this field is not included in hostapd.conf, hostapd will not control
197# fragmentation threshold and 'iwconfig wlan# frag <val>' can be used to set
198# it.
199fragm_threshold=2346
200
201# Rate configuration
202# Default is to enable all rates supported by the hardware. This configuration
203# item allows this list be filtered so that only the listed rates will be left
204# in the list. If the list is empty, all rates are used. This list can have
205# entries that are not in the list of rates the hardware supports (such entries
206# are ignored). The entries in this list are in 100 kbps, i.e., 11 Mbps = 110.
207# If this item is present, at least one rate have to be matching with the rates
208# hardware supports.
209# default: use the most common supported rate setting for the selected
210# hw_mode (i.e., this line can be removed from configuration file in most
211# cases)
212#supported_rates=10 20 55 110 60 90 120 180 240 360 480 540
213
214# Basic rate set configuration
215# List of rates (in 100 kbps) that are included in the basic rate set.
216# If this item is not included, usually reasonable default set is used.
217#basic_rates=10 20
218#basic_rates=10 20 55 110
219#basic_rates=60 120 240
220
221# Short Preamble
222# This parameter can be used to enable optional use of short preamble for
223# frames sent at 2 Mbps, 5.5 Mbps, and 11 Mbps to improve network performance.
224# This applies only to IEEE 802.11b-compatible networks and this should only be
225# enabled if the local hardware supports use of short preamble. If any of the
226# associated STAs do not support short preamble, use of short preamble will be
227# disabled (and enabled when such STAs disassociate) dynamically.
228# 0 = do not allow use of short preamble (default)
229# 1 = allow use of short preamble
230#preamble=1
231
232# Station MAC address -based authentication
233# Please note that this kind of access control requires a driver that uses
234# hostapd to take care of management frame processing and as such, this can be
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800235# used with driver=hostap or driver=nl80211, but not with driver=atheros.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700236# 0 = accept unless in deny list
237# 1 = deny unless in accept list
238# 2 = use external RADIUS server (accept/deny lists are searched first)
239macaddr_acl=0
240
241# Accept/deny lists are read from separate files (containing list of
242# MAC addresses, one per line). Use absolute path name to make sure that the
243# files can be read on SIGHUP configuration reloads.
244#accept_mac_file=/etc/hostapd.accept
245#deny_mac_file=/etc/hostapd.deny
246
247# IEEE 802.11 specifies two authentication algorithms. hostapd can be
248# configured to allow both of these or only one. Open system authentication
249# should be used with IEEE 802.1X.
250# Bit fields of allowed authentication algorithms:
251# bit 0 = Open System Authentication
252# bit 1 = Shared Key Authentication (requires WEP)
253auth_algs=3
254
255# Send empty SSID in beacons and ignore probe request frames that do not
256# specify full SSID, i.e., require stations to know SSID.
257# default: disabled (0)
258# 1 = send empty (length=0) SSID in beacon and ignore probe request for
259# broadcast SSID
260# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
261# with some clients that do not support empty SSID) and ignore probe
262# requests for broadcast SSID
263ignore_broadcast_ssid=0
264
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700265# Additional vendor specfic elements for Beacon and Probe Response frames
266# This parameter can be used to add additional vendor specific element(s) into
267# the end of the Beacon and Probe Response frames. The format for these
268# element(s) is a hexdump of the raw information elements (id+len+payload for
269# one or more elements)
270#vendor_elements=dd0411223301
271
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700272# TX queue parameters (EDCF / bursting)
273# tx_queue_<queue name>_<param>
274# queues: data0, data1, data2, data3, after_beacon, beacon
275# (data0 is the highest priority queue)
276# parameters:
277# aifs: AIFS (default 2)
278# cwmin: cwMin (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023)
279# cwmax: cwMax (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023); cwMax >= cwMin
280# burst: maximum length (in milliseconds with precision of up to 0.1 ms) for
281# bursting
282#
283# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
284# These parameters are used by the access point when transmitting frames
285# to the clients.
286#
287# Low priority / AC_BK = background
288#tx_queue_data3_aifs=7
289#tx_queue_data3_cwmin=15
290#tx_queue_data3_cwmax=1023
291#tx_queue_data3_burst=0
292# Note: for IEEE 802.11b mode: cWmin=31 cWmax=1023 burst=0
293#
294# Normal priority / AC_BE = best effort
295#tx_queue_data2_aifs=3
296#tx_queue_data2_cwmin=15
297#tx_queue_data2_cwmax=63
298#tx_queue_data2_burst=0
299# Note: for IEEE 802.11b mode: cWmin=31 cWmax=127 burst=0
300#
301# High priority / AC_VI = video
302#tx_queue_data1_aifs=1
303#tx_queue_data1_cwmin=7
304#tx_queue_data1_cwmax=15
305#tx_queue_data1_burst=3.0
306# Note: for IEEE 802.11b mode: cWmin=15 cWmax=31 burst=6.0
307#
308# Highest priority / AC_VO = voice
309#tx_queue_data0_aifs=1
310#tx_queue_data0_cwmin=3
311#tx_queue_data0_cwmax=7
312#tx_queue_data0_burst=1.5
313# Note: for IEEE 802.11b mode: cWmin=7 cWmax=15 burst=3.3
314
315# 802.1D Tag (= UP) to AC mappings
316# WMM specifies following mapping of data frames to different ACs. This mapping
317# can be configured using Linux QoS/tc and sch_pktpri.o module.
318# 802.1D Tag 802.1D Designation Access Category WMM Designation
319# 1 BK AC_BK Background
320# 2 - AC_BK Background
321# 0 BE AC_BE Best Effort
322# 3 EE AC_BE Best Effort
323# 4 CL AC_VI Video
324# 5 VI AC_VI Video
325# 6 VO AC_VO Voice
326# 7 NC AC_VO Voice
327# Data frames with no priority information: AC_BE
328# Management frames: AC_VO
329# PS-Poll frames: AC_BE
330
331# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
332# for 802.11a or 802.11g networks
333# These parameters are sent to WMM clients when they associate.
334# The parameters will be used by WMM clients for frames transmitted to the
335# access point.
336#
337# note - txop_limit is in units of 32microseconds
338# note - acm is admission control mandatory flag. 0 = admission control not
339# required, 1 = mandatory
340# note - here cwMin and cmMax are in exponent form. the actual cw value used
341# will be (2^n)-1 where n is the value given here
342#
343wmm_enabled=1
344#
345# WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]
346# Enable this flag if U-APSD supported outside hostapd (eg., Firmware/driver)
347#uapsd_advertisement_enabled=1
348#
349# Low priority / AC_BK = background
350wmm_ac_bk_cwmin=4
351wmm_ac_bk_cwmax=10
352wmm_ac_bk_aifs=7
353wmm_ac_bk_txop_limit=0
354wmm_ac_bk_acm=0
355# Note: for IEEE 802.11b mode: cWmin=5 cWmax=10
356#
357# Normal priority / AC_BE = best effort
358wmm_ac_be_aifs=3
359wmm_ac_be_cwmin=4
360wmm_ac_be_cwmax=10
361wmm_ac_be_txop_limit=0
362wmm_ac_be_acm=0
363# Note: for IEEE 802.11b mode: cWmin=5 cWmax=7
364#
365# High priority / AC_VI = video
366wmm_ac_vi_aifs=2
367wmm_ac_vi_cwmin=3
368wmm_ac_vi_cwmax=4
369wmm_ac_vi_txop_limit=94
370wmm_ac_vi_acm=0
371# Note: for IEEE 802.11b mode: cWmin=4 cWmax=5 txop_limit=188
372#
373# Highest priority / AC_VO = voice
374wmm_ac_vo_aifs=2
375wmm_ac_vo_cwmin=2
376wmm_ac_vo_cwmax=3
377wmm_ac_vo_txop_limit=47
378wmm_ac_vo_acm=0
379# Note: for IEEE 802.11b mode: cWmin=3 cWmax=4 burst=102
380
381# Static WEP key configuration
382#
383# The key number to use when transmitting.
384# It must be between 0 and 3, and the corresponding key must be set.
385# default: not set
386#wep_default_key=0
387# The WEP keys to use.
388# A key may be a quoted string or unquoted hexadecimal digits.
389# The key length should be 5, 13, or 16 characters, or 10, 26, or 32
390# digits, depending on whether 40-bit (64-bit), 104-bit (128-bit), or
391# 128-bit (152-bit) WEP is used.
392# Only the default key must be supplied; the others are optional.
393# default: not set
394#wep_key0=123456789a
395#wep_key1="vwxyz"
396#wep_key2=0102030405060708090a0b0c0d
397#wep_key3=".2.4.6.8.0.23"
398
399# Station inactivity limit
400#
401# If a station does not send anything in ap_max_inactivity seconds, an
402# empty data frame is sent to it in order to verify whether it is
403# still in range. If this frame is not ACKed, the station will be
404# disassociated and then deauthenticated. This feature is used to
405# clear station table of old entries when the STAs move out of the
406# range.
407#
408# The station can associate again with the AP if it is still in range;
409# this inactivity poll is just used as a nicer way of verifying
410# inactivity; i.e., client will not report broken connection because
411# disassociation frame is not sent immediately without first polling
412# the STA with a data frame.
413# default: 300 (i.e., 5 minutes)
414#ap_max_inactivity=300
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800415#
416# The inactivity polling can be disabled to disconnect stations based on
417# inactivity timeout so that idle stations are more likely to be disconnected
418# even if they are still in range of the AP. This can be done by setting
419# skip_inactivity_poll to 1 (default 0).
420#skip_inactivity_poll=0
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700421
422# Disassociate stations based on excessive transmission failures or other
423# indications of connection loss. This depends on the driver capabilities and
424# may not be available with all drivers.
425#disassoc_low_ack=1
426
427# Maximum allowed Listen Interval (how many Beacon periods STAs are allowed to
428# remain asleep). Default: 65535 (no limit apart from field size)
429#max_listen_interval=100
430
431# WDS (4-address frame) mode with per-station virtual interfaces
432# (only supported with driver=nl80211)
433# This mode allows associated stations to use 4-address frames to allow layer 2
434# bridging to be used.
435#wds_sta=1
436
437# If bridge parameter is set, the WDS STA interface will be added to the same
438# bridge by default. This can be overridden with the wds_bridge parameter to
439# use a separate bridge.
440#wds_bridge=wds-br0
441
Dmitry Shmidtc2ebb4b2013-07-24 12:57:51 -0700442# Start the AP with beaconing disabled by default.
443#start_disabled=0
444
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700445# Client isolation can be used to prevent low-level bridging of frames between
446# associated stations in the BSS. By default, this bridging is allowed.
447#ap_isolate=1
448
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800449# BSS Load update period (in BUs)
450# This field is used to enable and configure adding a BSS Load element into
451# Beacon and Probe Response frames.
452#bss_load_update_period=50
453
Dmitry Shmidt051af732013-10-22 13:52:46 -0700454# Fixed BSS Load value for testing purposes
455# This field can be used to configure hostapd to add a fixed BSS Load element
456# into Beacon and Probe Response frames for testing purposes. The format is
457# <station count>:<channel utilization>:<available admission capacity>
458#bss_load_test=12:80:20000
459
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700460##### IEEE 802.11n related configuration ######################################
461
462# ieee80211n: Whether IEEE 802.11n (HT) is enabled
463# 0 = disabled (default)
464# 1 = enabled
465# Note: You will also need to enable WMM for full HT functionality.
466#ieee80211n=1
467
468# ht_capab: HT capabilities (list of flags)
469# LDPC coding capability: [LDPC] = supported
470# Supported channel width set: [HT40-] = both 20 MHz and 40 MHz with secondary
471# channel below the primary channel; [HT40+] = both 20 MHz and 40 MHz
Dmitry Shmidtd11f0192014-03-24 12:09:47 -0700472# with secondary channel above the primary channel
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700473# (20 MHz only if neither is set)
474# Note: There are limits on which channels can be used with HT40- and
475# HT40+. Following table shows the channels that may be available for
476# HT40- and HT40+ use per IEEE 802.11n Annex J:
477# freq HT40- HT40+
478# 2.4 GHz 5-13 1-7 (1-9 in Europe/Japan)
479# 5 GHz 40,48,56,64 36,44,52,60
480# (depending on the location, not all of these channels may be available
481# for use)
482# Please note that 40 MHz channels may switch their primary and secondary
483# channels if needed or creation of 40 MHz channel maybe rejected based
484# on overlapping BSSes. These changes are done automatically when hostapd
485# is setting up the 40 MHz channel.
486# Spatial Multiplexing (SM) Power Save: [SMPS-STATIC] or [SMPS-DYNAMIC]
487# (SMPS disabled if neither is set)
488# HT-greenfield: [GF] (disabled if not set)
489# Short GI for 20 MHz: [SHORT-GI-20] (disabled if not set)
490# Short GI for 40 MHz: [SHORT-GI-40] (disabled if not set)
491# Tx STBC: [TX-STBC] (disabled if not set)
492# Rx STBC: [RX-STBC1] (one spatial stream), [RX-STBC12] (one or two spatial
493# streams), or [RX-STBC123] (one, two, or three spatial streams); Rx STBC
494# disabled if none of these set
495# HT-delayed Block Ack: [DELAYED-BA] (disabled if not set)
496# Maximum A-MSDU length: [MAX-AMSDU-7935] for 7935 octets (3839 octets if not
497# set)
498# DSSS/CCK Mode in 40 MHz: [DSSS_CCK-40] = allowed (not allowed if not set)
Dmitry Shmidtd11f0192014-03-24 12:09:47 -0700499# 40 MHz intolerant [40-INTOLERANT] (not advertised if not set)
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700500# L-SIG TXOP protection support: [LSIG-TXOP-PROT] (disabled if not set)
501#ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40]
502
503# Require stations to support HT PHY (reject association if they do not)
504#require_ht=1
505
Dmitry Shmidt54605472013-11-08 11:10:19 -0800506# If set non-zero, require stations to perform scans of overlapping
507# channels to test for stations which would be affected by 40 MHz traffic.
Dmitry Shmidt216983b2015-02-06 10:50:36 -0800508# This parameter sets the interval in seconds between these scans. Setting this
509# to non-zero allows 2.4 GHz band AP to move dynamically to a 40 MHz channel if
510# no co-existence issues with neighboring devices are found.
Dmitry Shmidt54605472013-11-08 11:10:19 -0800511#obss_interval=0
512
Dmitry Shmidt04949592012-07-19 12:16:46 -0700513##### IEEE 802.11ac related configuration #####################################
514
515# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled
516# 0 = disabled (default)
517# 1 = enabled
518# Note: You will also need to enable WMM for full VHT functionality.
519#ieee80211ac=1
520
521# vht_capab: VHT capabilities (list of flags)
522#
523# vht_max_mpdu_len: [MAX-MPDU-7991] [MAX-MPDU-11454]
524# Indicates maximum MPDU length
525# 0 = 3895 octets (default)
526# 1 = 7991 octets
527# 2 = 11454 octets
528# 3 = reserved
529#
530# supported_chan_width: [VHT160] [VHT160-80PLUS80]
531# Indicates supported Channel widths
532# 0 = 160 MHz & 80+80 channel widths are not supported (default)
533# 1 = 160 MHz channel width is supported
534# 2 = 160 MHz & 80+80 channel widths are supported
535# 3 = reserved
536#
537# Rx LDPC coding capability: [RXLDPC]
538# Indicates support for receiving LDPC coded pkts
539# 0 = Not supported (default)
540# 1 = Supported
541#
542# Short GI for 80 MHz: [SHORT-GI-80]
543# Indicates short GI support for reception of packets transmitted with TXVECTOR
544# params format equal to VHT and CBW = 80Mhz
545# 0 = Not supported (default)
546# 1 = Supported
547#
548# Short GI for 160 MHz: [SHORT-GI-160]
549# Indicates short GI support for reception of packets transmitted with TXVECTOR
550# params format equal to VHT and CBW = 160Mhz
551# 0 = Not supported (default)
552# 1 = Supported
553#
554# Tx STBC: [TX-STBC-2BY1]
555# Indicates support for the transmission of at least 2x1 STBC
556# 0 = Not supported (default)
557# 1 = Supported
558#
559# Rx STBC: [RX-STBC-1] [RX-STBC-12] [RX-STBC-123] [RX-STBC-1234]
560# Indicates support for the reception of PPDUs using STBC
561# 0 = Not supported (default)
562# 1 = support of one spatial stream
563# 2 = support of one and two spatial streams
564# 3 = support of one, two and three spatial streams
565# 4 = support of one, two, three and four spatial streams
566# 5,6,7 = reserved
567#
568# SU Beamformer Capable: [SU-BEAMFORMER]
569# Indicates support for operation as a single user beamformer
570# 0 = Not supported (default)
571# 1 = Supported
572#
573# SU Beamformee Capable: [SU-BEAMFORMEE]
574# Indicates support for operation as a single user beamformee
575# 0 = Not supported (default)
576# 1 = Supported
577#
578# Compressed Steering Number of Beamformer Antennas Supported: [BF-ANTENNA-2]
579# Beamformee's capability indicating the maximum number of beamformer
580# antennas the beamformee can support when sending compressed beamforming
581# feedback
582# If SU beamformer capable, set to maximum value minus 1
583# else reserved (default)
584#
585# Number of Sounding Dimensions: [SOUNDING-DIMENSION-2]
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700586# Beamformer's capability indicating the maximum value of the NUM_STS parameter
Dmitry Shmidt04949592012-07-19 12:16:46 -0700587# in the TXVECTOR of a VHT NDP
588# If SU beamformer capable, set to maximum value minus 1
589# else reserved (default)
590#
591# MU Beamformer Capable: [MU-BEAMFORMER]
592# Indicates support for operation as an MU beamformer
593# 0 = Not supported or sent by Non-AP STA (default)
594# 1 = Supported
595#
596# MU Beamformee Capable: [MU-BEAMFORMEE]
597# Indicates support for operation as an MU beamformee
598# 0 = Not supported or sent by AP (default)
599# 1 = Supported
600#
601# VHT TXOP PS: [VHT-TXOP-PS]
602# Indicates whether or not the AP supports VHT TXOP Power Save Mode
603# or whether or not the STA is in VHT TXOP Power Save mode
604# 0 = VHT AP doesnt support VHT TXOP PS mode (OR) VHT Sta not in VHT TXOP PS
605# mode
606# 1 = VHT AP supports VHT TXOP PS mode (OR) VHT Sta is in VHT TXOP power save
607# mode
608#
609# +HTC-VHT Capable: [HTC-VHT]
610# Indicates whether or not the STA supports receiving a VHT variant HT Control
611# field.
612# 0 = Not supported (default)
613# 1 = supported
614#
615# Maximum A-MPDU Length Exponent: [MAX-A-MPDU-LEN-EXP0]..[MAX-A-MPDU-LEN-EXP7]
616# Indicates the maximum length of A-MPDU pre-EOF padding that the STA can recv
617# This field is an integer in the range of 0 to 7.
618# The length defined by this field is equal to
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700619# 2 pow(13 + Maximum A-MPDU Length Exponent) -1 octets
Dmitry Shmidt04949592012-07-19 12:16:46 -0700620#
621# VHT Link Adaptation Capable: [VHT-LINK-ADAPT2] [VHT-LINK-ADAPT3]
622# Indicates whether or not the STA supports link adaptation using VHT variant
623# HT Control field
624# If +HTC-VHTcapable is 1
625# 0 = (no feedback) if the STA does not provide VHT MFB (default)
626# 1 = reserved
627# 2 = (Unsolicited) if the STA provides only unsolicited VHT MFB
628# 3 = (Both) if the STA can provide VHT MFB in response to VHT MRQ and if the
629# STA provides unsolicited VHT MFB
630# Reserved if +HTC-VHTcapable is 0
631#
632# Rx Antenna Pattern Consistency: [RX-ANTENNA-PATTERN]
633# Indicates the possibility of Rx antenna pattern change
634# 0 = Rx antenna pattern might change during the lifetime of an association
635# 1 = Rx antenna pattern does not change during the lifetime of an association
636#
637# Tx Antenna Pattern Consistency: [TX-ANTENNA-PATTERN]
638# Indicates the possibility of Tx antenna pattern change
639# 0 = Tx antenna pattern might change during the lifetime of an association
640# 1 = Tx antenna pattern does not change during the lifetime of an association
641#vht_capab=[SHORT-GI-80][HTC-VHT]
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700642#
643# Require stations to support VHT PHY (reject association if they do not)
644#require_vht=1
645
646# 0 = 20 or 40 MHz operating Channel width
647# 1 = 80 MHz channel width
648# 2 = 160 MHz channel width
649# 3 = 80+80 MHz channel width
Dmitry Shmidt04949592012-07-19 12:16:46 -0700650#vht_oper_chwidth=1
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700651#
652# center freq = 5 GHz + (5 * index)
653# So index 42 gives center freq 5.210 GHz
654# which is channel 42 in 5G band
655#
656#vht_oper_centr_freq_seg0_idx=42
Dmitry Shmidtd5e49232012-12-03 15:08:10 -0800657#
658# center freq = 5 GHz + (5 * index)
659# So index 159 gives center freq 5.795 GHz
660# which is channel 159 in 5G band
661#
662#vht_oper_centr_freq_seg1_idx=159
Dmitry Shmidt04949592012-07-19 12:16:46 -0700663
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700664##### IEEE 802.1X-2004 related configuration ##################################
665
666# Require IEEE 802.1X authorization
667#ieee8021x=1
668
669# IEEE 802.1X/EAPOL version
670# hostapd is implemented based on IEEE Std 802.1X-2004 which defines EAPOL
671# version 2. However, there are many client implementations that do not handle
672# the new version number correctly (they seem to drop the frames completely).
673# In order to make hostapd interoperate with these clients, the version number
674# can be set to the older version (1) with this configuration value.
675#eapol_version=2
676
677# Optional displayable message sent with EAP Request-Identity. The first \0
678# in this string will be converted to ASCII-0 (nul). This can be used to
679# separate network info (comma separated list of attribute=value pairs); see,
680# e.g., RFC 4284.
681#eap_message=hello
682#eap_message=hello\0networkid=netw,nasid=foo,portid=0,NAIRealms=example.com
683
684# WEP rekeying (disabled if key lengths are not set or are set to 0)
685# Key lengths for default/broadcast and individual/unicast keys:
686# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
687# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
688#wep_key_len_broadcast=5
689#wep_key_len_unicast=5
690# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
691#wep_rekey_period=300
692
693# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
694# only broadcast keys are used)
695eapol_key_index_workaround=0
696
697# EAP reauthentication period in seconds (default: 3600 seconds; 0 = disable
698# reauthentication).
699#eap_reauth_period=3600
700
701# Use PAE group address (01:80:c2:00:00:03) instead of individual target
702# address when sending EAPOL frames with driver=wired. This is the most common
703# mechanism used in wired authentication, but it also requires that the port
704# is only used by one station.
705#use_pae_group_addr=1
706
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800707# EAP Re-authentication Protocol (ERP) authenticator (RFC 6696)
708#
709# Whether to initiate EAP authentication with EAP-Initiate/Re-auth-Start before
710# EAP-Identity/Request
711#erp_send_reauth_start=1
712#
713# Domain name for EAP-Initiate/Re-auth-Start. Omitted from the message if not
714# set (no local ER server). This is also used by the integrated EAP server if
715# ERP is enabled (eap_server_erp=1).
716#erp_domain=example.com
717
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700718##### Integrated EAP server ###################################################
719
720# Optionally, hostapd can be configured to use an integrated EAP server
721# to process EAP authentication locally without need for an external RADIUS
722# server. This functionality can be used both as a local authentication server
723# for IEEE 802.1X/EAPOL and as a RADIUS server for other devices.
724
725# Use integrated EAP server instead of external RADIUS authentication
726# server. This is also needed if hostapd is configured to act as a RADIUS
727# authentication server.
728eap_server=0
729
730# Path for EAP server user database
Dmitry Shmidtd5e49232012-12-03 15:08:10 -0800731# If SQLite support is included, this can be set to "sqlite:/path/to/sqlite.db"
732# to use SQLite database instead of a text file.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700733#eap_user_file=/etc/hostapd.eap_user
734
735# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
736#ca_cert=/etc/hostapd.ca.pem
737
738# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
739#server_cert=/etc/hostapd.server.pem
740
741# Private key matching with the server certificate for EAP-TLS/PEAP/TTLS
742# This may point to the same file as server_cert if both certificate and key
743# are included in a single file. PKCS#12 (PFX) file (.p12/.pfx) can also be
744# used by commenting out server_cert and specifying the PFX file as the
745# private_key.
746#private_key=/etc/hostapd.server.prv
747
748# Passphrase for private key
749#private_key_passwd=secret passphrase
750
Dmitry Shmidt34af3062013-07-11 10:46:32 -0700751# Server identity
752# EAP methods that provide mechanism for authenticated server identity delivery
753# use this value. If not set, "hostapd" is used as a default.
754#server_id=server.example.com
755
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700756# Enable CRL verification.
757# Note: hostapd does not yet support CRL downloading based on CDP. Thus, a
758# valid CRL signed by the CA is required to be included in the ca_cert file.
759# This can be done by using PEM format for CA certificate and CRL and
760# concatenating these into one file. Whenever CRL changes, hostapd needs to be
761# restarted to take the new CRL into use.
762# 0 = do not verify CRLs (default)
763# 1 = check the CRL of the user certificate
764# 2 = check all CRLs in the certificate path
765#check_crl=1
766
Dmitry Shmidt34af3062013-07-11 10:46:32 -0700767# Cached OCSP stapling response (DER encoded)
768# If set, this file is sent as a certificate status response by the EAP server
769# if the EAP peer requests certificate status in the ClientHello message.
770# This cache file can be updated, e.g., by running following command
771# periodically to get an update from the OCSP responder:
772# openssl ocsp \
773# -no_nonce \
774# -CAfile /etc/hostapd.ca.pem \
775# -issuer /etc/hostapd.ca.pem \
776# -cert /etc/hostapd.server.pem \
777# -url http://ocsp.example.com:8888/ \
778# -respout /tmp/ocsp-cache.der
779#ocsp_stapling_response=/tmp/ocsp-cache.der
780
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700781# dh_file: File path to DH/DSA parameters file (in PEM format)
782# This is an optional configuration file for setting parameters for an
783# ephemeral DH key exchange. In most cases, the default RSA authentication does
784# not use this configuration. However, it is possible setup RSA to use
785# ephemeral DH key exchange. In addition, ciphers with DSA keys always use
786# ephemeral DH keys. This can be used to achieve forward secrecy. If the file
787# is in DSA parameters format, it will be automatically converted into DH
788# params. This parameter is required if anonymous EAP-FAST is used.
789# You can generate DH parameters file with OpenSSL, e.g.,
790# "openssl dhparam -out /etc/hostapd.dh.pem 1024"
791#dh_file=/etc/hostapd.dh.pem
792
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800793# OpenSSL cipher string
794#
795# This is an OpenSSL specific configuration option for configuring the default
796# ciphers. If not set, "DEFAULT:!EXP:!LOW" is used as the default.
797# See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation
798# on cipher suite configuration. This is applicable only if hostapd is built to
799# use OpenSSL.
800#openssl_ciphers=DEFAULT:!EXP:!LOW
801
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700802# Fragment size for EAP methods
803#fragment_size=1400
804
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -0800805# Finite cyclic group for EAP-pwd. Number maps to group of domain parameters
806# using the IANA repository for IKE (RFC 2409).
807#pwd_group=19
808
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700809# Configuration data for EAP-SIM database/authentication gateway interface.
810# This is a text string in implementation specific format. The example
811# implementation in eap_sim_db.c uses this as the UNIX domain socket name for
812# the HLR/AuC gateway (e.g., hlr_auc_gw). In this case, the path uses "unix:"
Dmitry Shmidt4530cfd2012-09-09 15:20:40 -0700813# prefix. If hostapd is built with SQLite support (CONFIG_SQLITE=y in .config),
814# database file can be described with an optional db=<path> parameter.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700815#eap_sim_db=unix:/tmp/hlr_auc_gw.sock
Dmitry Shmidt4530cfd2012-09-09 15:20:40 -0700816#eap_sim_db=unix:/tmp/hlr_auc_gw.sock db=/tmp/hostapd.db
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700817
818# Encryption key for EAP-FAST PAC-Opaque values. This key must be a secret,
819# random value. It is configured as a 16-octet value in hex format. It can be
820# generated, e.g., with the following command:
821# od -tx1 -v -N16 /dev/random | colrm 1 8 | tr -d ' '
822#pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f
823
824# EAP-FAST authority identity (A-ID)
825# A-ID indicates the identity of the authority that issues PACs. The A-ID
826# should be unique across all issuing servers. In theory, this is a variable
827# length field, but due to some existing implementations requiring A-ID to be
828# 16 octets in length, it is strongly recommended to use that length for the
829# field to provid interoperability with deployed peer implementations. This
830# field is configured in hex format.
831#eap_fast_a_id=101112131415161718191a1b1c1d1e1f
832
833# EAP-FAST authority identifier information (A-ID-Info)
834# This is a user-friendly name for the A-ID. For example, the enterprise name
835# and server name in a human-readable format. This field is encoded as UTF-8.
836#eap_fast_a_id_info=test server
837
838# Enable/disable different EAP-FAST provisioning modes:
839#0 = provisioning disabled
840#1 = only anonymous provisioning allowed
841#2 = only authenticated provisioning allowed
842#3 = both provisioning modes allowed (default)
843#eap_fast_prov=3
844
845# EAP-FAST PAC-Key lifetime in seconds (hard limit)
846#pac_key_lifetime=604800
847
848# EAP-FAST PAC-Key refresh time in seconds (soft limit on remaining hard
849# limit). The server will generate a new PAC-Key when this number of seconds
850# (or fewer) of the lifetime remains.
851#pac_key_refresh_time=86400
852
853# EAP-SIM and EAP-AKA protected success/failure indication using AT_RESULT_IND
854# (default: 0 = disabled).
855#eap_sim_aka_result_ind=1
856
857# Trusted Network Connect (TNC)
858# If enabled, TNC validation will be required before the peer is allowed to
859# connect. Note: This is only used with EAP-TTLS and EAP-FAST. If any other
860# EAP method is enabled, the peer will be allowed to connect without TNC.
861#tnc=1
862
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800863# EAP Re-authentication Protocol (ERP) - RFC 6696
864#
865# Whether to enable ERP on the EAP server.
866#eap_server_erp=1
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700867
868##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################
869
870# Interface to be used for IAPP broadcast packets
871#iapp_interface=eth0
872
873
874##### RADIUS client configuration #############################################
875# for IEEE 802.1X with external Authentication Server, IEEE 802.11
876# authentication with external ACL for MAC addresses, and accounting
877
878# The own IP address of the access point (used as NAS-IP-Address)
879own_ip_addr=127.0.0.1
880
881# Optional NAS-Identifier string for RADIUS messages. When used, this should be
882# a unique to the NAS within the scope of the RADIUS server. For example, a
883# fully qualified domain name can be used here.
884# When using IEEE 802.11r, nas_identifier must be set and must be between 1 and
885# 48 octets long.
886#nas_identifier=ap.example.com
887
888# RADIUS authentication server
889#auth_server_addr=127.0.0.1
890#auth_server_port=1812
891#auth_server_shared_secret=secret
892
893# RADIUS accounting server
894#acct_server_addr=127.0.0.1
895#acct_server_port=1813
896#acct_server_shared_secret=secret
897
898# Secondary RADIUS servers; to be used if primary one does not reply to
899# RADIUS packets. These are optional and there can be more than one secondary
900# server listed.
901#auth_server_addr=127.0.0.2
902#auth_server_port=1812
903#auth_server_shared_secret=secret2
904#
905#acct_server_addr=127.0.0.2
906#acct_server_port=1813
907#acct_server_shared_secret=secret2
908
909# Retry interval for trying to return to the primary RADIUS server (in
910# seconds). RADIUS client code will automatically try to use the next server
911# when the current server is not replying to requests. If this interval is set,
912# primary server will be retried after configured amount of time even if the
913# currently used secondary server is still working.
914#radius_retry_primary_interval=600
915
916
917# Interim accounting update interval
918# If this is set (larger than 0) and acct_server is configured, hostapd will
919# send interim accounting updates every N seconds. Note: if set, this overrides
920# possible Acct-Interim-Interval attribute in Access-Accept message. Thus, this
921# value should not be configured in hostapd.conf, if RADIUS server is used to
922# control the interim interval.
923# This value should not be less 600 (10 minutes) and must not be less than
924# 60 (1 minute).
925#radius_acct_interim_interval=600
926
Dmitry Shmidt04949592012-07-19 12:16:46 -0700927# Request Chargeable-User-Identity (RFC 4372)
928# This parameter can be used to configure hostapd to request CUI from the
929# RADIUS server by including Chargeable-User-Identity attribute into
930# Access-Request packets.
931#radius_request_cui=1
932
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700933# Dynamic VLAN mode; allow RADIUS authentication server to decide which VLAN
934# is used for the stations. This information is parsed from following RADIUS
935# attributes based on RFC 3580 and RFC 2868: Tunnel-Type (value 13 = VLAN),
936# Tunnel-Medium-Type (value 6 = IEEE 802), Tunnel-Private-Group-ID (value
Dmitry Shmidt4b060592013-04-29 16:42:49 -0700937# VLANID as a string). Optionally, the local MAC ACL list (accept_mac_file) can
938# be used to set static client MAC address to VLAN ID mapping.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700939# 0 = disabled (default)
940# 1 = option; use default interface if RADIUS server does not include VLAN ID
941# 2 = required; reject authentication if RADIUS server does not include VLAN ID
942#dynamic_vlan=0
943
944# VLAN interface list for dynamic VLAN mode is read from a separate text file.
945# This list is used to map VLAN ID from the RADIUS server to a network
946# interface. Each station is bound to one interface in the same way as with
947# multiple BSSIDs or SSIDs. Each line in this text file is defining a new
948# interface and the line must include VLAN ID and interface name separated by
949# white space (space or tab).
Dmitry Shmidt4b060592013-04-29 16:42:49 -0700950# If no entries are provided by this file, the station is statically mapped
951# to <bss-iface>.<vlan-id> interfaces.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700952#vlan_file=/etc/hostapd.vlan
953
954# Interface where 802.1q tagged packets should appear when a RADIUS server is
955# used to determine which VLAN a station is on. hostapd creates a bridge for
956# each VLAN. Then hostapd adds a VLAN interface (associated with the interface
957# indicated by 'vlan_tagged_interface') and the appropriate wireless interface
958# to the bridge.
959#vlan_tagged_interface=eth0
960
Dmitry Shmidt34af3062013-07-11 10:46:32 -0700961# Bridge (prefix) to add the wifi and the tagged interface to. This gets the
962# VLAN ID appended. It defaults to brvlan%d if no tagged interface is given
963# and br%s.%d if a tagged interface is given, provided %s = tagged interface
964# and %d = VLAN ID.
965#vlan_bridge=brvlan
966
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700967# When hostapd creates a VLAN interface on vlan_tagged_interfaces, it needs
968# to know how to name it.
969# 0 = vlan<XXX>, e.g., vlan1
970# 1 = <vlan_tagged_interface>.<XXX>, e.g. eth0.1
971#vlan_naming=0
972
Dmitry Shmidt04949592012-07-19 12:16:46 -0700973# Arbitrary RADIUS attributes can be added into Access-Request and
974# Accounting-Request packets by specifying the contents of the attributes with
975# the following configuration parameters. There can be multiple of these to
976# add multiple attributes. These parameters can also be used to override some
977# of the attributes added automatically by hostapd.
978# Format: <attr_id>[:<syntax:value>]
979# attr_id: RADIUS attribute type (e.g., 26 = Vendor-Specific)
980# syntax: s = string (UTF-8), d = integer, x = octet string
981# value: attribute value in format indicated by the syntax
982# If syntax and value parts are omitted, a null value (single 0x00 octet) is
983# used.
984#
985# Additional Access-Request attributes
986# radius_auth_req_attr=<attr_id>[:<syntax:value>]
987# Examples:
988# Operator-Name = "Operator"
989#radius_auth_req_attr=126:s:Operator
990# Service-Type = Framed (2)
991#radius_auth_req_attr=6:d:2
992# Connect-Info = "testing" (this overrides the automatically generated value)
993#radius_auth_req_attr=77:s:testing
994# Same Connect-Info value set as a hexdump
995#radius_auth_req_attr=77:x:74657374696e67
996
997#
998# Additional Accounting-Request attributes
999# radius_acct_req_attr=<attr_id>[:<syntax:value>]
1000# Examples:
1001# Operator-Name = "Operator"
1002#radius_acct_req_attr=126:s:Operator
1003
1004# Dynamic Authorization Extensions (RFC 5176)
1005# This mechanism can be used to allow dynamic changes to user session based on
1006# commands from a RADIUS server (or some other disconnect client that has the
1007# needed session information). For example, Disconnect message can be used to
1008# request an associated station to be disconnected.
1009#
1010# This is disabled by default. Set radius_das_port to non-zero UDP port
1011# number to enable.
1012#radius_das_port=3799
1013#
1014# DAS client (the host that can send Disconnect/CoA requests) and shared secret
1015#radius_das_client=192.168.1.123 shared secret here
1016#
1017# DAS Event-Timestamp time window in seconds
1018#radius_das_time_window=300
1019#
1020# DAS require Event-Timestamp
1021#radius_das_require_event_timestamp=1
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001022
1023##### RADIUS authentication server configuration ##############################
1024
1025# hostapd can be used as a RADIUS authentication server for other hosts. This
1026# requires that the integrated EAP server is also enabled and both
1027# authentication services are sharing the same configuration.
1028
1029# File name of the RADIUS clients configuration for the RADIUS server. If this
1030# commented out, RADIUS server is disabled.
1031#radius_server_clients=/etc/hostapd.radius_clients
1032
1033# The UDP port number for the RADIUS authentication server
1034#radius_server_auth_port=1812
1035
Dmitry Shmidtbd14a572014-02-18 10:33:49 -08001036# The UDP port number for the RADIUS accounting server
1037# Commenting this out or setting this to 0 can be used to disable RADIUS
1038# accounting while still enabling RADIUS authentication.
1039#radius_server_acct_port=1813
1040
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001041# Use IPv6 with RADIUS server (IPv4 will also be supported using IPv6 API)
1042#radius_server_ipv6=1
1043
1044
1045##### WPA/IEEE 802.11i configuration ##########################################
1046
1047# Enable WPA. Setting this variable configures the AP to require WPA (either
1048# WPA-PSK or WPA-RADIUS/EAP based on other configuration). For WPA-PSK, either
1049# wpa_psk or wpa_passphrase must be set and wpa_key_mgmt must include WPA-PSK.
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001050# Instead of wpa_psk / wpa_passphrase, wpa_psk_radius might suffice.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001051# For WPA-RADIUS/EAP, ieee8021x must be set (but without dynamic WEP keys),
1052# RADIUS authentication server must be configured, and WPA-EAP must be included
1053# in wpa_key_mgmt.
1054# This field is a bit field that can be used to enable WPA (IEEE 802.11i/D3.0)
1055# and/or WPA2 (full IEEE 802.11i/RSN):
1056# bit0 = WPA
1057# bit1 = IEEE 802.11i/RSN (WPA2) (dot11RSNAEnabled)
1058#wpa=1
1059
1060# WPA pre-shared keys for WPA-PSK. This can be either entered as a 256-bit
1061# secret in hex format (64 hex digits), wpa_psk, or as an ASCII passphrase
1062# (8..63 characters) that will be converted to PSK. This conversion uses SSID
1063# so the PSK changes when ASCII passphrase is used and the SSID is changed.
1064# wpa_psk (dot11RSNAConfigPSKValue)
1065# wpa_passphrase (dot11RSNAConfigPSKPassPhrase)
1066#wpa_psk=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
1067#wpa_passphrase=secret passphrase
1068
1069# Optionally, WPA PSKs can be read from a separate text file (containing list
1070# of (PSK,MAC address) pairs. This allows more than one PSK to be configured.
1071# Use absolute path name to make sure that the files can be read on SIGHUP
1072# configuration reloads.
1073#wpa_psk_file=/etc/hostapd.wpa_psk
1074
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001075# Optionally, WPA passphrase can be received from RADIUS authentication server
1076# This requires macaddr_acl to be set to 2 (RADIUS)
1077# 0 = disabled (default)
1078# 1 = optional; use default passphrase/psk if RADIUS server does not include
1079# Tunnel-Password
1080# 2 = required; reject authentication if RADIUS server does not include
1081# Tunnel-Password
1082#wpa_psk_radius=0
1083
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001084# Set of accepted key management algorithms (WPA-PSK, WPA-EAP, or both). The
1085# entries are separated with a space. WPA-PSK-SHA256 and WPA-EAP-SHA256 can be
1086# added to enable SHA256-based stronger algorithms.
1087# (dot11RSNAConfigAuthenticationSuitesTable)
1088#wpa_key_mgmt=WPA-PSK WPA-EAP
1089
1090# Set of accepted cipher suites (encryption algorithms) for pairwise keys
1091# (unicast packets). This is a space separated list of algorithms:
1092# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
1093# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
1094# Group cipher suite (encryption algorithm for broadcast and multicast frames)
1095# is automatically selected based on this configuration. If only CCMP is
1096# allowed as the pairwise cipher, group cipher will also be CCMP. Otherwise,
1097# TKIP will be used as the group cipher.
1098# (dot11RSNAConfigPairwiseCiphersTable)
1099# Pairwise cipher for WPA (v1) (default: TKIP)
1100#wpa_pairwise=TKIP CCMP
1101# Pairwise cipher for RSN/WPA2 (default: use wpa_pairwise value)
1102#rsn_pairwise=CCMP
1103
1104# Time interval for rekeying GTK (broadcast/multicast encryption keys) in
1105# seconds. (dot11RSNAConfigGroupRekeyTime)
1106#wpa_group_rekey=600
1107
1108# Rekey GTK when any STA that possesses the current GTK is leaving the BSS.
1109# (dot11RSNAConfigGroupRekeyStrict)
1110#wpa_strict_rekey=1
1111
1112# Time interval for rekeying GMK (master key used internally to generate GTKs
1113# (in seconds).
1114#wpa_gmk_rekey=86400
1115
1116# Maximum lifetime for PTK in seconds. This can be used to enforce rekeying of
1117# PTK to mitigate some attacks against TKIP deficiencies.
1118#wpa_ptk_rekey=600
1119
1120# Enable IEEE 802.11i/RSN/WPA2 pre-authentication. This is used to speed up
1121# roaming be pre-authenticating IEEE 802.1X/EAP part of the full RSN
1122# authentication and key handshake before actually associating with a new AP.
1123# (dot11RSNAPreauthenticationEnabled)
1124#rsn_preauth=1
1125#
1126# Space separated list of interfaces from which pre-authentication frames are
1127# accepted (e.g., 'eth0' or 'eth0 wlan0wds0'. This list should include all
1128# interface that are used for connections to other APs. This could include
1129# wired interfaces and WDS links. The normal wireless data interface towards
1130# associated stations (e.g., wlan0) should not be added, since
1131# pre-authentication is only used with APs other than the currently associated
1132# one.
1133#rsn_preauth_interfaces=eth0
1134
1135# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e) is
1136# allowed. This is only used with RSN/WPA2.
1137# 0 = disabled (default)
1138# 1 = enabled
1139#peerkey=1
1140
1141# ieee80211w: Whether management frame protection (MFP) is enabled
1142# 0 = disabled (default)
1143# 1 = optional
1144# 2 = required
1145#ieee80211w=0
1146
Dmitry Shmidtb36ed7c2014-03-17 10:57:26 -07001147# Group management cipher suite
1148# Default: AES-128-CMAC (BIP)
1149# Other options (depending on driver support):
1150# BIP-GMAC-128
1151# BIP-GMAC-256
1152# BIP-CMAC-256
1153# Note: All the stations connecting to the BSS will also need to support the
1154# selected cipher. The default AES-128-CMAC is the only option that is commonly
1155# available in deployed devices.
1156#group_mgmt_cipher=AES-128-CMAC
1157
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001158# Association SA Query maximum timeout (in TU = 1.024 ms; for MFP)
1159# (maximum time to wait for a SA Query response)
1160# dot11AssociationSAQueryMaximumTimeout, 1...4294967295
1161#assoc_sa_query_max_timeout=1000
1162
1163# Association SA Query retry timeout (in TU = 1.024 ms; for MFP)
1164# (time between two subsequent SA Query requests)
1165# dot11AssociationSAQueryRetryTimeout, 1...4294967295
1166#assoc_sa_query_retry_timeout=201
1167
Dmitry Shmidtc55524a2011-07-07 11:18:38 -07001168# disable_pmksa_caching: Disable PMKSA caching
1169# This parameter can be used to disable caching of PMKSA created through EAP
1170# authentication. RSN preauthentication may still end up using PMKSA caching if
1171# it is enabled (rsn_preauth=1).
1172# 0 = PMKSA caching enabled (default)
1173# 1 = PMKSA caching disabled
1174#disable_pmksa_caching=0
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001175
1176# okc: Opportunistic Key Caching (aka Proactive Key Caching)
1177# Allow PMK cache to be shared opportunistically among configured interfaces
1178# and BSSes (i.e., all configurations within a single hostapd process).
1179# 0 = disabled (default)
1180# 1 = enabled
1181#okc=1
1182
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001183# SAE threshold for anti-clogging mechanism (dot11RSNASAEAntiCloggingThreshold)
1184# This parameter defines how many open SAE instances can be in progress at the
1185# same time before the anti-clogging mechanism is taken into use.
1186#sae_anti_clogging_threshold=5
1187
1188# Enabled SAE finite cyclic groups
1189# SAE implementation are required to support group 19 (ECC group defined over a
1190# 256-bit prime order field). All groups that are supported by the
1191# implementation are enabled by default. This configuration parameter can be
1192# used to specify a limited set of allowed groups. The group values are listed
1193# in the IANA registry:
1194# http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
1195#sae_groups=19 20 21 25 26
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001196
1197##### IEEE 802.11r configuration ##############################################
1198
1199# Mobility Domain identifier (dot11FTMobilityDomainID, MDID)
1200# MDID is used to indicate a group of APs (within an ESS, i.e., sharing the
1201# same SSID) between which a STA can use Fast BSS Transition.
1202# 2-octet identifier as a hex string.
1203#mobility_domain=a1b2
1204
1205# PMK-R0 Key Holder identifier (dot11FTR0KeyHolderID)
1206# 1 to 48 octet identifier.
1207# This is configured with nas_identifier (see RADIUS client section above).
1208
1209# Default lifetime of the PMK-RO in minutes; range 1..65535
1210# (dot11FTR0KeyLifetime)
1211#r0_key_lifetime=10000
1212
1213# PMK-R1 Key Holder identifier (dot11FTR1KeyHolderID)
1214# 6-octet identifier as a hex string.
1215#r1_key_holder=000102030405
1216
1217# Reassociation deadline in time units (TUs / 1.024 ms; range 1000..65535)
1218# (dot11FTReassociationDeadline)
1219#reassociation_deadline=1000
1220
1221# List of R0KHs in the same Mobility Domain
1222# format: <MAC address> <NAS Identifier> <128-bit key as hex string>
1223# This list is used to map R0KH-ID (NAS Identifier) to a destination MAC
1224# address when requesting PMK-R1 key from the R0KH that the STA used during the
1225# Initial Mobility Domain Association.
1226#r0kh=02:01:02:03:04:05 r0kh-1.example.com 000102030405060708090a0b0c0d0e0f
1227#r0kh=02:01:02:03:04:06 r0kh-2.example.com 00112233445566778899aabbccddeeff
1228# And so on.. One line per R0KH.
1229
1230# List of R1KHs in the same Mobility Domain
1231# format: <MAC address> <R1KH-ID> <128-bit key as hex string>
1232# This list is used to map R1KH-ID to a destination MAC address when sending
1233# PMK-R1 key from the R0KH. This is also the list of authorized R1KHs in the MD
1234# that can request PMK-R1 keys.
1235#r1kh=02:01:02:03:04:05 02:11:22:33:44:55 000102030405060708090a0b0c0d0e0f
1236#r1kh=02:01:02:03:04:06 02:11:22:33:44:66 00112233445566778899aabbccddeeff
1237# And so on.. One line per R1KH.
1238
1239# Whether PMK-R1 push is enabled at R0KH
1240# 0 = do not push PMK-R1 to all configured R1KHs (default)
1241# 1 = push PMK-R1 to all configured R1KHs whenever a new PMK-R0 is derived
1242#pmk_r1_push=1
1243
1244##### Neighbor table ##########################################################
1245# Maximum number of entries kept in AP table (either for neigbor table or for
1246# detecting Overlapping Legacy BSS Condition). The oldest entry will be
1247# removed when adding a new entry that would make the list grow over this
1248# limit. Note! WFA certification for IEEE 802.11g requires that OLBC is
1249# enabled, so this field should not be set to 0 when using IEEE 802.11g.
1250# default: 255
1251#ap_table_max_size=255
1252
1253# Number of seconds of no frames received after which entries may be deleted
1254# from the AP table. Since passive scanning is not usually performed frequently
1255# this should not be set to very small value. In addition, there is no
1256# guarantee that every scan cycle will receive beacon frames from the
1257# neighboring APs.
1258# default: 60
1259#ap_table_expiration_time=3600
1260
1261
1262##### Wi-Fi Protected Setup (WPS) #############################################
1263
1264# WPS state
1265# 0 = WPS disabled (default)
1266# 1 = WPS enabled, not configured
1267# 2 = WPS enabled, configured
1268#wps_state=2
1269
Dmitry Shmidt444d5672013-04-01 13:08:44 -07001270# Whether to manage this interface independently from other WPS interfaces
1271# By default, a single hostapd process applies WPS operations to all configured
1272# interfaces. This parameter can be used to disable that behavior for a subset
1273# of interfaces. If this is set to non-zero for an interface, WPS commands
1274# issued on that interface do not apply to other interfaces and WPS operations
1275# performed on other interfaces do not affect this interface.
1276#wps_independent=0
1277
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001278# AP can be configured into a locked state where new WPS Registrar are not
1279# accepted, but previously authorized Registrars (including the internal one)
1280# can continue to add new Enrollees.
1281#ap_setup_locked=1
1282
1283# Universally Unique IDentifier (UUID; see RFC 4122) of the device
1284# This value is used as the UUID for the internal WPS Registrar. If the AP
1285# is also using UPnP, this value should be set to the device's UPnP UUID.
1286# If not configured, UUID will be generated based on the local MAC address.
1287#uuid=12345678-9abc-def0-1234-56789abcdef0
1288
1289# Note: If wpa_psk_file is set, WPS is used to generate random, per-device PSKs
1290# that will be appended to the wpa_psk_file. If wpa_psk_file is not set, the
1291# default PSK (wpa_psk/wpa_passphrase) will be delivered to Enrollees. Use of
1292# per-device PSKs is recommended as the more secure option (i.e., make sure to
1293# set wpa_psk_file when using WPS with WPA-PSK).
1294
1295# When an Enrollee requests access to the network with PIN method, the Enrollee
1296# PIN will need to be entered for the Registrar. PIN request notifications are
1297# sent to hostapd ctrl_iface monitor. In addition, they can be written to a
1298# text file that could be used, e.g., to populate the AP administration UI with
1299# pending PIN requests. If the following variable is set, the PIN requests will
1300# be written to the configured file.
1301#wps_pin_requests=/var/run/hostapd_wps_pin_requests
1302
1303# Device Name
1304# User-friendly description of device; up to 32 octets encoded in UTF-8
1305#device_name=Wireless AP
1306
1307# Manufacturer
1308# The manufacturer of the device (up to 64 ASCII characters)
1309#manufacturer=Company
1310
1311# Model Name
1312# Model of the device (up to 32 ASCII characters)
1313#model_name=WAP
1314
1315# Model Number
1316# Additional device description (up to 32 ASCII characters)
1317#model_number=123
1318
1319# Serial Number
1320# Serial number of the device (up to 32 characters)
1321#serial_number=12345
1322
1323# Primary Device Type
1324# Used format: <categ>-<OUI>-<subcateg>
1325# categ = Category as an integer value
1326# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
1327# default WPS OUI
1328# subcateg = OUI-specific Sub Category as an integer value
1329# Examples:
1330# 1-0050F204-1 (Computer / PC)
1331# 1-0050F204-2 (Computer / Server)
1332# 5-0050F204-1 (Storage / NAS)
1333# 6-0050F204-1 (Network Infrastructure / AP)
1334#device_type=6-0050F204-1
1335
1336# OS Version
1337# 4-octet operating system version number (hex string)
1338#os_version=01020300
1339
1340# Config Methods
1341# List of the supported configuration methods
1342# Available methods: usba ethernet label display ext_nfc_token int_nfc_token
1343# nfc_interface push_button keypad virtual_display physical_display
1344# virtual_push_button physical_push_button
1345#config_methods=label virtual_display virtual_push_button keypad
1346
Jouni Malinen87fd2792011-05-16 18:35:42 +03001347# WPS capability discovery workaround for PBC with Windows 7
1348# Windows 7 uses incorrect way of figuring out AP's WPS capabilities by acting
1349# as a Registrar and using M1 from the AP. The config methods attribute in that
1350# message is supposed to indicate only the configuration method supported by
1351# the AP in Enrollee role, i.e., to add an external Registrar. For that case,
1352# PBC shall not be used and as such, the PushButton config method is removed
1353# from M1 by default. If pbc_in_m1=1 is included in the configuration file,
1354# the PushButton config method is left in M1 (if included in config_methods
1355# parameter) to allow Windows 7 to use PBC instead of PIN (e.g., from a label
1356# in the AP).
1357#pbc_in_m1=1
1358
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001359# Static access point PIN for initial configuration and adding Registrars
1360# If not set, hostapd will not allow external WPS Registrars to control the
1361# access point. The AP PIN can also be set at runtime with hostapd_cli
1362# wps_ap_pin command. Use of temporary (enabled by user action) and random
1363# AP PIN is much more secure than configuring a static AP PIN here. As such,
1364# use of the ap_pin parameter is not recommended if the AP device has means for
1365# displaying a random PIN.
1366#ap_pin=12345670
1367
1368# Skip building of automatic WPS credential
1369# This can be used to allow the automatically generated Credential attribute to
1370# be replaced with pre-configured Credential(s).
1371#skip_cred_build=1
1372
1373# Additional Credential attribute(s)
1374# This option can be used to add pre-configured Credential attributes into M8
1375# message when acting as a Registrar. If skip_cred_build=1, this data will also
1376# be able to override the Credential attribute that would have otherwise been
1377# automatically generated based on network configuration. This configuration
1378# option points to an external file that much contain the WPS Credential
1379# attribute(s) as binary data.
1380#extra_cred=hostapd.cred
1381
1382# Credential processing
1383# 0 = process received credentials internally (default)
1384# 1 = do not process received credentials; just pass them over ctrl_iface to
1385# external program(s)
1386# 2 = process received credentials internally and pass them over ctrl_iface
1387# to external program(s)
1388# Note: With wps_cred_processing=1, skip_cred_build should be set to 1 and
1389# extra_cred be used to provide the Credential data for Enrollees.
1390#
1391# wps_cred_processing=1 will disabled automatic updates of hostapd.conf file
1392# both for Credential processing and for marking AP Setup Locked based on
1393# validation failures of AP PIN. An external program is responsible on updating
1394# the configuration appropriately in this case.
1395#wps_cred_processing=0
1396
1397# AP Settings Attributes for M7
1398# By default, hostapd generates the AP Settings Attributes for M7 based on the
1399# current configuration. It is possible to override this by providing a file
1400# with pre-configured attributes. This is similar to extra_cred file format,
1401# but the AP Settings attributes are not encapsulated in a Credential
1402# attribute.
1403#ap_settings=hostapd.ap_settings
1404
1405# WPS UPnP interface
1406# If set, support for external Registrars is enabled.
1407#upnp_iface=br0
1408
1409# Friendly Name (required for UPnP)
1410# Short description for end use. Should be less than 64 characters.
1411#friendly_name=WPS Access Point
1412
1413# Manufacturer URL (optional for UPnP)
1414#manufacturer_url=http://www.example.com/
1415
1416# Model Description (recommended for UPnP)
1417# Long description for end user. Should be less than 128 characters.
1418#model_description=Wireless Access Point
1419
1420# Model URL (optional for UPnP)
1421#model_url=http://www.example.com/model/
1422
1423# Universal Product Code (optional for UPnP)
1424# 12-digit, all-numeric code that identifies the consumer package.
1425#upc=123456789012
1426
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001427# WPS RF Bands (a = 5G, b = 2.4G, g = 2.4G, ag = dual band)
1428# This value should be set according to RF band(s) supported by the AP if
1429# hw_mode is not set. For dual band dual concurrent devices, this needs to be
1430# set to ag to allow both RF bands to be advertized.
1431#wps_rf_bands=ag
1432
Dmitry Shmidt04949592012-07-19 12:16:46 -07001433# NFC password token for WPS
1434# These parameters can be used to configure a fixed NFC password token for the
1435# AP. This can be generated, e.g., with nfc_pw_token from wpa_supplicant. When
1436# these parameters are used, the AP is assumed to be deployed with a NFC tag
1437# that includes the matching NFC password token (e.g., written based on the
1438# NDEF record from nfc_pw_token).
1439#
1440#wps_nfc_dev_pw_id: Device Password ID (16..65535)
1441#wps_nfc_dh_pubkey: Hexdump of DH Public Key
1442#wps_nfc_dh_privkey: Hexdump of DH Private Key
1443#wps_nfc_dev_pw: Hexdump of Device Password
1444
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001445##### Wi-Fi Direct (P2P) ######################################################
1446
1447# Enable P2P Device management
1448#manage_p2p=1
1449
1450# Allow cross connection
1451#allow_cross_connection=1
1452
1453#### TDLS (IEEE 802.11z-2010) #################################################
1454
1455# Prohibit use of TDLS in this BSS
1456#tdls_prohibit=1
1457
1458# Prohibit use of TDLS Channel Switching in this BSS
1459#tdls_prohibit_chan_switch=1
1460
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001461##### IEEE 802.11v-2011 #######################################################
1462
1463# Time advertisement
1464# 0 = disabled (default)
1465# 2 = UTC time at which the TSF timer is 0
1466#time_advertisement=2
1467
1468# Local time zone as specified in 8.3 of IEEE Std 1003.1-2004:
1469# stdoffset[dst[offset][,start[/time],end[/time]]]
1470#time_zone=EST5
1471
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001472# WNM-Sleep Mode (extended sleep mode for stations)
1473# 0 = disabled (default)
1474# 1 = enabled (allow stations to use WNM-Sleep Mode)
1475#wnm_sleep_mode=1
1476
1477# BSS Transition Management
1478# 0 = disabled (default)
1479# 1 = enabled
1480#bss_transition=1
1481
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -08001482# Proxy ARP
1483# 0 = disabled (default)
1484# 1 = enabled
1485#proxy_arp=1
1486
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001487##### IEEE 802.11u-2011 #######################################################
1488
1489# Enable Interworking service
1490#interworking=1
1491
1492# Access Network Type
1493# 0 = Private network
1494# 1 = Private network with guest access
1495# 2 = Chargeable public network
1496# 3 = Free public network
1497# 4 = Personal device network
1498# 5 = Emergency services only network
1499# 14 = Test or experimental
1500# 15 = Wildcard
1501#access_network_type=0
1502
1503# Whether the network provides connectivity to the Internet
1504# 0 = Unspecified
1505# 1 = Network provides connectivity to the Internet
1506#internet=1
1507
1508# Additional Step Required for Access
1509# Note: This is only used with open network, i.e., ASRA shall ne set to 0 if
1510# RSN is used.
1511#asra=0
1512
1513# Emergency services reachable
1514#esr=0
1515
1516# Unauthenticated emergency service accessible
1517#uesa=0
1518
1519# Venue Info (optional)
1520# The available values are defined in IEEE Std 802.11u-2011, 7.3.1.34.
1521# Example values (group,type):
1522# 0,0 = Unspecified
1523# 1,7 = Convention Center
1524# 1,13 = Coffee Shop
1525# 2,0 = Unspecified Business
1526# 7,1 Private Residence
1527#venue_group=7
1528#venue_type=1
1529
1530# Homogeneous ESS identifier (optional; dot11HESSID)
1531# If set, this shall be identifical to one of the BSSIDs in the homogeneous
1532# ESS and this shall be set to the same value across all BSSs in homogeneous
1533# ESS.
1534#hessid=02:03:04:05:06:07
1535
1536# Roaming Consortium List
1537# Arbitrary number of Roaming Consortium OIs can be configured with each line
1538# adding a new OI to the list. The first three entries are available through
1539# Beacon and Probe Response frames. Any additional entry will be available only
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001540# through ANQP queries. Each OI is between 3 and 15 octets and is configured as
Dmitry Shmidt1f69aa52012-01-24 16:10:04 -08001541# a hexstring.
1542#roaming_consortium=021122
1543#roaming_consortium=2233445566
1544
Dmitry Shmidt04949592012-07-19 12:16:46 -07001545# Venue Name information
1546# This parameter can be used to configure one or more Venue Name Duples for
1547# Venue Name ANQP information. Each entry has a two or three character language
1548# code (ISO-639) separated by colon from the venue name string.
1549# Note that venue_group and venue_type have to be set for Venue Name
1550# information to be complete.
1551#venue_name=eng:Example venue
1552#venue_name=fin:Esimerkkipaikka
Dmitry Shmidt56052862013-10-04 10:23:25 -07001553# Alternative format for language:value strings:
1554# (double quoted string, printf-escaped string)
1555#venue_name=P"eng:Example\nvenue"
Dmitry Shmidt04949592012-07-19 12:16:46 -07001556
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001557# Network Authentication Type
1558# This parameter indicates what type of network authentication is used in the
1559# network.
1560# format: <network auth type indicator (1-octet hex str)> [redirect URL]
1561# Network Authentication Type Indicator values:
1562# 00 = Acceptance of terms and conditions
1563# 01 = On-line enrollment supported
1564# 02 = http/https redirection
1565# 03 = DNS redirection
1566#network_auth_type=00
1567#network_auth_type=02http://www.example.com/redirect/me/here/
1568
1569# IP Address Type Availability
1570# format: <1-octet encoded value as hex str>
1571# (ipv4_type & 0x3f) << 2 | (ipv6_type & 0x3)
1572# ipv4_type:
1573# 0 = Address type not available
1574# 1 = Public IPv4 address available
1575# 2 = Port-restricted IPv4 address available
1576# 3 = Single NATed private IPv4 address available
1577# 4 = Double NATed private IPv4 address available
1578# 5 = Port-restricted IPv4 address and single NATed IPv4 address available
1579# 6 = Port-restricted IPv4 address and double NATed IPv4 address available
1580# 7 = Availability of the address type is not known
1581# ipv6_type:
1582# 0 = Address type not available
1583# 1 = Address type available
1584# 2 = Availability of the address type not known
1585#ipaddr_type_availability=14
1586
1587# Domain Name
1588# format: <variable-octet str>[,<variable-octet str>]
1589#domain_name=example.com,another.example.com,yet-another.example.com
1590
1591# 3GPP Cellular Network information
1592# format: <MCC1,MNC1>[;<MCC2,MNC2>][;...]
1593#anqp_3gpp_cell_net=244,91;310,026;234,56
1594
1595# NAI Realm information
1596# One or more realm can be advertised. Each nai_realm line adds a new realm to
1597# the set. These parameters provide information for stations using Interworking
1598# network selection to allow automatic connection to a network based on
1599# credentials.
1600# format: <encoding>,<NAI Realm(s)>[,<EAP Method 1>][,<EAP Method 2>][,...]
1601# encoding:
1602# 0 = Realm formatted in accordance with IETF RFC 4282
1603# 1 = UTF-8 formatted character string that is not formatted in
1604# accordance with IETF RFC 4282
1605# NAI Realm(s): Semi-colon delimited NAI Realm(s)
1606# EAP Method: <EAP Method>[:<[AuthParam1:Val1]>][<[AuthParam2:Val2]>][...]
Dmitry Shmidt98660862014-03-11 17:26:21 -07001607# EAP Method types, see:
1608# http://www.iana.org/assignments/eap-numbers/eap-numbers.xhtml#eap-numbers-4
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001609# AuthParam (Table 8-188 in IEEE Std 802.11-2012):
1610# ID 2 = Non-EAP Inner Authentication Type
1611# 1 = PAP, 2 = CHAP, 3 = MSCHAP, 4 = MSCHAPV2
1612# ID 3 = Inner authentication EAP Method Type
1613# ID 5 = Credential Type
1614# 1 = SIM, 2 = USIM, 3 = NFC Secure Element, 4 = Hardware Token,
1615# 5 = Softoken, 6 = Certificate, 7 = username/password, 9 = Anonymous,
1616# 10 = Vendor Specific
1617#nai_realm=0,example.com;example.net
1618# EAP methods EAP-TLS with certificate and EAP-TTLS/MSCHAPv2 with
1619# username/password
1620#nai_realm=0,example.org,13[5:6],21[2:4][5:7]
1621
Dmitry Shmidt051af732013-10-22 13:52:46 -07001622# QoS Map Set configuration
1623#
1624# Comma delimited QoS Map Set in decimal values
1625# (see IEEE Std 802.11-2012, 8.4.2.97)
1626#
1627# format:
1628# [<DSCP Exceptions[DSCP,UP]>,]<UP 0 range[low,high]>,...<UP 7 range[low,high]>
1629#
1630# There can be up to 21 optional DSCP Exceptions which are pairs of DSCP Value
1631# (0..63 or 255) and User Priority (0..7). This is followed by eight DSCP Range
1632# descriptions with DSCP Low Value and DSCP High Value pairs (0..63 or 255) for
1633# each UP starting from 0. If both low and high value are set to 255, the
1634# corresponding UP is not used.
1635#
1636# default: not set
1637#qos_map_set=53,2,22,6,8,15,0,7,255,255,16,31,32,39,255,255,40,47,255,255
1638
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001639##### Hotspot 2.0 #############################################################
1640
1641# Enable Hotspot 2.0 support
1642#hs20=1
1643
1644# Disable Downstream Group-Addressed Forwarding (DGAF)
1645# This can be used to configure a network where no group-addressed frames are
1646# allowed. The AP will not forward any group-address frames to the stations and
1647# random GTKs are issued for each station to prevent associated stations from
1648# forging such frames to other stations in the BSS.
1649#disable_dgaf=1
1650
Dmitry Shmidtf21452a2014-02-26 10:55:25 -08001651# OSU Server-Only Authenticated L2 Encryption Network
1652#osen=1
1653
1654# ANQP Domain ID (0..65535)
1655# An identifier for a set of APs in an ESS that share the same common ANQP
1656# information. 0 = Some of the ANQP information is unique to this AP (default).
1657#anqp_domain_id=1234
1658
1659# Deauthentication request timeout
1660# If the RADIUS server indicates that the station is not allowed to connect to
1661# the BSS/ESS, the AP can allow the station some time to download a
1662# notification page (URL included in the message). This parameter sets that
1663# timeout in seconds.
1664#hs20_deauth_req_timeout=60
1665
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001666# Operator Friendly Name
1667# This parameter can be used to configure one or more Operator Friendly Name
1668# Duples. Each entry has a two or three character language code (ISO-639)
1669# separated by colon from the operator friendly name string.
1670#hs20_oper_friendly_name=eng:Example operator
1671#hs20_oper_friendly_name=fin:Esimerkkioperaattori
1672
1673# Connection Capability
1674# This can be used to advertise what type of IP traffic can be sent through the
1675# hotspot (e.g., due to firewall allowing/blocking protocols/ports).
1676# format: <IP Protocol>:<Port Number>:<Status>
1677# IP Protocol: 1 = ICMP, 6 = TCP, 17 = UDP
1678# Port Number: 0..65535
1679# Status: 0 = Closed, 1 = Open, 2 = Unknown
1680# Each hs20_conn_capab line is added to the list of advertised tuples.
1681#hs20_conn_capab=1:0:2
1682#hs20_conn_capab=6:22:1
1683#hs20_conn_capab=17:5060:0
1684
1685# WAN Metrics
1686# format: <WAN Info>:<DL Speed>:<UL Speed>:<DL Load>:<UL Load>:<LMD>
1687# WAN Info: B0-B1: Link Status, B2: Symmetric Link, B3: At Capabity
1688# (encoded as two hex digits)
1689# Link Status: 1 = Link up, 2 = Link down, 3 = Link in test state
1690# Downlink Speed: Estimate of WAN backhaul link current downlink speed in kbps;
1691# 1..4294967295; 0 = unknown
1692# Uplink Speed: Estimate of WAN backhaul link current uplink speed in kbps
1693# 1..4294967295; 0 = unknown
1694# Downlink Load: Current load of downlink WAN connection (scaled to 255 = 100%)
1695# Uplink Load: Current load of uplink WAN connection (scaled to 255 = 100%)
1696# Load Measurement Duration: Duration for measuring downlink/uplink load in
1697# tenths of a second (1..65535); 0 if load cannot be determined
1698#hs20_wan_metrics=01:8000:1000:80:240:3000
1699
1700# Operating Class Indication
1701# List of operating classes the BSSes in this ESS use. The Global operating
1702# classes in Table E-4 of IEEE Std 802.11-2012 Annex E define the values that
1703# can be used in this.
1704# format: hexdump of operating class octets
1705# for example, operating classes 81 (2.4 GHz channels 1-13) and 115 (5 GHz
1706# channels 36-48):
1707#hs20_operating_class=5173
1708
Dmitry Shmidtf21452a2014-02-26 10:55:25 -08001709# OSU icons
1710# <Icon Width>:<Icon Height>:<Language code>:<Icon Type>:<Name>:<file path>
1711#hs20_icon=32:32:eng:image/png:icon32:/tmp/icon32.png
1712#hs20_icon=64:64:eng:image/png:icon64:/tmp/icon64.png
1713
1714# OSU SSID (see ssid2 for format description)
1715# This is the SSID used for all OSU connections to all the listed OSU Providers.
1716#osu_ssid="example"
1717
1718# OSU Providers
1719# One or more sets of following parameter. Each OSU provider is started by the
1720# mandatory osu_server_uri item. The other parameters add information for the
1721# last added OSU provider.
1722#
1723#osu_server_uri=https://example.com/osu/
1724#osu_friendly_name=eng:Example operator
1725#osu_friendly_name=fin:Esimerkkipalveluntarjoaja
1726#osu_nai=anonymous@example.com
1727#osu_method_list=1 0
1728#osu_icon=icon32
1729#osu_icon=icon64
1730#osu_service_desc=eng:Example services
1731#osu_service_desc=fin:Esimerkkipalveluja
1732#
1733#osu_server_uri=...
1734
Dmitry Shmidt8da800a2013-04-24 12:57:01 -07001735##### TESTING OPTIONS #########################################################
1736#
1737# The options in this section are only available when the build configuration
1738# option CONFIG_TESTING_OPTIONS is set while compiling hostapd. They allow
1739# testing some scenarios that are otherwise difficult to reproduce.
1740#
1741# Ignore probe requests sent to hostapd with the given probability, must be a
1742# floating point number in the range [0, 1).
1743#ignore_probe_probability=0.0
1744#
1745# Ignore authentication frames with the given probability
1746#ignore_auth_probability=0.0
1747#
1748# Ignore association requests with the given probability
1749#ignore_assoc_probability=0.0
1750#
1751# Ignore reassociation requests with the given probability
1752#ignore_reassoc_probability=0.0
Dmitry Shmidt51b6ea82013-05-08 10:42:09 -07001753#
1754# Corrupt Key MIC in GTK rekey EAPOL-Key frames with the given probability
1755#corrupt_gtk_rekey_mic_probability=0.0
Dmitry Shmidt8da800a2013-04-24 12:57:01 -07001756
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001757##### Multiple BSSID support ##################################################
1758#
1759# Above configuration is using the default interface (wlan#, or multi-SSID VLAN
1760# interfaces). Other BSSIDs can be added by using separator 'bss' with
1761# default interface name to be allocated for the data packets of the new BSS.
1762#
1763# hostapd will generate BSSID mask based on the BSSIDs that are
1764# configured. hostapd will verify that dev_addr & MASK == dev_addr. If this is
1765# not the case, the MAC address of the radio must be changed before starting
1766# hostapd (ifconfig wlan0 hw ether <MAC addr>). If a BSSID is configured for
1767# every secondary BSS, this limitation is not applied at hostapd and other
1768# masks may be used if the driver supports them (e.g., swap the locally
1769# administered bit)
1770#
1771# BSSIDs are assigned in order to each BSS, unless an explicit BSSID is
1772# specified using the 'bssid' parameter.
1773# If an explicit BSSID is specified, it must be chosen such that it:
1774# - results in a valid MASK that covers it and the dev_addr
1775# - is not the same as the MAC address of the radio
1776# - is not the same as any other explicitly specified BSSID
1777#
Dmitry Shmidtdf5a7e42014-04-02 12:59:59 -07001778# Not all drivers support multiple BSSes. The exact mechanism for determining
1779# the driver capabilities is driver specific. With the current (i.e., a recent
1780# kernel) drivers using nl80211, this information can be checked with "iw list"
1781# (search for "valid interface combinations").
1782#
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -07001783# Please note that hostapd uses some of the values configured for the first BSS
1784# as the defaults for the following BSSes. However, it is recommended that all
1785# BSSes include explicit configuration of all relevant configuration items.
1786#
1787#bss=wlan0_0
1788#ssid=test2
1789# most of the above items can be used here (apart from radio interface specific
1790# items, like channel)
1791
1792#bss=wlan0_1
1793#bssid=00:13:10:95:fe:0b
1794# ...