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