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