blob: ba511b9cb60d3941c786de8c78e5f6870d6226f7 [file] [log] [blame]
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001##### Example wpa_supplicant configuration file ###############################
2#
3# This file describes configuration file format and lists all available option.
4# Please also take a look at simpler configuration examples in 'examples'
5# subdirectory.
6#
7# Empty lines and lines starting with # are ignored
8
9# NOTE! This file may contain password information and should probably be made
10# readable only by root user on multiuser systems.
11
12# Note: All file paths in this configuration file should use full (absolute,
13# not relative to working directory) path in order to allow working directory
14# to be changed. This can happen if wpa_supplicant is run in the background.
15
16# Whether to allow wpa_supplicant to update (overwrite) configuration
17#
18# This option can be used to allow wpa_supplicant to overwrite configuration
19# file whenever configuration is changed (e.g., new network block is added with
20# wpa_cli or wpa_gui, or a password is changed). This is required for
21# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
22# Please note that overwriting configuration file will remove the comments from
23# it.
24#update_config=1
25
26# global configuration (shared by all network blocks)
27#
28# Parameters for the control interface. If this is specified, wpa_supplicant
29# will open a control interface that is available for external programs to
30# manage wpa_supplicant. The meaning of this string depends on which control
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -080031# interface mechanism is used. For all cases, the existence of this parameter
Dmitry Shmidt30f94812012-02-21 17:02:48 -080032# in configuration is used to determine whether the control interface is
33# enabled.
34#
35# For UNIX domain sockets (default on Linux and BSD): This is a directory that
36# will be created for UNIX domain sockets for listening to requests from
37# external programs (CLI/GUI, etc.) for status information and configuration.
38# The socket file will be named based on the interface name, so multiple
39# wpa_supplicant processes can be run at the same time if more than one
40# interface is used.
41# /var/run/wpa_supplicant is the recommended directory for sockets and by
42# default, wpa_cli will use it when trying to connect with wpa_supplicant.
43#
44# Access control for the control interface can be configured by setting the
45# directory to allow only members of a group to use sockets. This way, it is
46# possible to run wpa_supplicant as root (since it needs to change network
47# configuration and open raw sockets) and still allow GUI/CLI components to be
48# run as non-root users. However, since the control interface can be used to
49# change the network configuration, this access needs to be protected in many
50# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
51# want to allow non-root users to use the control interface, add a new group
52# and change this value to match with that group. Add users that should have
53# control interface access to this group. If this variable is commented out or
54# not included in the configuration file, group will not be changed from the
55# value it got by default when the directory or socket was created.
56#
57# When configuring both the directory and group, use following format:
58# DIR=/var/run/wpa_supplicant GROUP=wheel
59# DIR=/var/run/wpa_supplicant GROUP=0
60# (group can be either group name or gid)
61#
62# For UDP connections (default on Windows): The value will be ignored. This
63# variable is just used to select that the control interface is to be created.
64# The value can be set to, e.g., udp (ctrl_interface=udp)
65#
66# For Windows Named Pipe: This value can be used to set the security descriptor
67# for controlling access to the control interface. Security descriptor can be
68# set using Security Descriptor String Format (see http://msdn.microsoft.com/
69# library/default.asp?url=/library/en-us/secauthz/security/
70# security_descriptor_string_format.asp). The descriptor string needs to be
71# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
72# DACL (which will reject all connections). See README-Windows.txt for more
73# information about SDDL string format.
74#
75ctrl_interface=/var/run/wpa_supplicant
76
77# IEEE 802.1X/EAPOL version
78# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
79# EAPOL version 2. However, there are many APs that do not handle the new
80# version number correctly (they seem to drop the frames completely). In order
81# to make wpa_supplicant interoperate with these APs, the version number is set
82# to 1 by default. This configuration value can be used to set it to the new
83# version (2).
Dmitry Shmidt5a1480c2014-05-12 09:46:02 -070084# Note: When using MACsec, eapol_version shall be set to 3, which is
85# defined in IEEE Std 802.1X-2010.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -070086eapol_version=1
Dmitry Shmidt30f94812012-02-21 17:02:48 -080087
88# AP scanning/selection
89# By default, wpa_supplicant requests driver to perform AP scanning and then
90# uses the scan results to select a suitable AP. Another alternative is to
91# allow the driver to take care of AP scanning and selection and use
92# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
93# information from the driver.
94# 1: wpa_supplicant initiates scanning and AP selection; if no APs matching to
95# the currently enabled networks are found, a new network (IBSS or AP mode
96# operation) may be initialized (if configured) (default)
97# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
98# parameters (e.g., WPA IE generation); this mode can also be used with
99# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
100# APs (i.e., external program needs to control association). This mode must
Dmitry Shmidtabb90a32016-12-05 15:34:39 -0800101# also be used when using wired Ethernet drivers (including MACsec).
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800102# 2: like 0, but associate with APs using security policy and SSID (but not
103# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
104# enable operation with hidden SSIDs and optimized roaming; in this mode,
105# the network blocks in the configuration file are tried one by one until
106# the driver reports successful association; each network block should have
107# explicit security policy (i.e., only one option in the lists) for
108# key_mgmt, pairwise, group, proto variables
Dmitry Shmidtd80a4012015-11-05 16:35:40 -0800109# Note: ap_scan=2 should not be used with the nl80211 driver interface (the
110# current Linux interface). ap_scan=1 is optimized work working with nl80211.
111# For finding networks using hidden SSID, scan_ssid=1 in the network block can
112# be used with nl80211.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800113# When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
114# created immediately regardless of scan results. ap_scan=1 mode will first try
115# to scan for existing networks and only if no matches with the enabled
116# networks are found, a new IBSS or AP mode network is created.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700117ap_scan=1
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800118
Dmitry Shmidtb70d0bb2015-11-16 10:43:06 -0800119# Whether to force passive scan for network connection
120#
121# By default, scans will send out Probe Request frames on channels that allow
122# active scanning. This advertise the local station to the world. Normally this
123# is fine, but users may wish to do passive scanning where the radio should only
124# listen quietly for Beacon frames and not send any Probe Request frames. Actual
125# functionality may be driver dependent.
126#
127# This parameter can be used to force only passive scanning to be used
128# for network connection cases. It should be noted that this will slow
129# down scan operations and reduce likelihood of finding the AP. In
130# addition, some use cases will override this due to functional
131# requirements, e.g., for finding an AP that uses hidden SSID
132# (scan_ssid=1) or P2P device discovery.
133#
134# 0: Do normal scans (allow active scans) (default)
135# 1: Do passive scans.
136#passive_scan=0
137
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800138# MPM residency
139# By default, wpa_supplicant implements the mesh peering manager (MPM) for an
140# open mesh. However, if the driver can implement the MPM, you may set this to
141# 0 to use the driver version. When AMPE is enabled, the wpa_supplicant MPM is
142# always used.
143# 0: MPM lives in the driver
144# 1: wpa_supplicant provides an MPM which handles peering (default)
145#user_mpm=1
146
147# Maximum number of peer links (0-255; default: 99)
148# Maximum number of mesh peering currently maintained by the STA.
149#max_peer_links=99
150
Dmitry Shmidt2f74e362015-01-21 13:19:05 -0800151# Timeout in seconds to detect STA inactivity (default: 300 seconds)
152#
153# This timeout value is used in mesh STA to clean up inactive stations.
154#mesh_max_inactivity=300
155
156# cert_in_cb - Whether to include a peer certificate dump in events
157# This controls whether peer certificates for authentication server and
158# its certificate chain are included in EAP peer certificate events. This is
159# enabled by default.
160#cert_in_cb=1
161
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800162# EAP fast re-authentication
163# By default, fast re-authentication is enabled for all EAP methods that
164# support it. This variable can be used to disable fast re-authentication.
165# Normally, there is no need to disable this.
Dmitry Shmidt8d520ff2011-05-09 14:06:53 -0700166fast_reauth=1
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800167
168# OpenSSL Engine support
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -0700169# These options can be used to load OpenSSL engines in special or legacy
170# modes.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800171# The two engines that are supported currently are shown below:
172# They are both from the opensc project (http://www.opensc.org/)
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -0700173# By default the PKCS#11 engine is loaded if the client_cert or
174# private_key option appear to be a PKCS#11 URI, and these options
175# should not need to be used explicitly.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800176# make the opensc engine available
177#opensc_engine_path=/usr/lib/opensc/engine_opensc.so
178# make the pkcs11 engine available
179#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
180# configure the path to the pkcs11 module required by the pkcs11 engine
181#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
182
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800183# OpenSSL cipher string
184#
185# This is an OpenSSL specific configuration option for configuring the default
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700186# ciphers. If not set, the value configured at build time ("DEFAULT:!EXP:!LOW"
187# by default) is used.
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -0800188# See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation
189# on cipher suite configuration. This is applicable only if wpa_supplicant is
190# built to use OpenSSL.
191#openssl_ciphers=DEFAULT:!EXP:!LOW
192
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800193# Dynamic EAP methods
194# If EAP methods were built dynamically as shared object files, they need to be
195# loaded here before being used in the network blocks. By default, EAP methods
196# are included statically in the build, so these lines are not needed
197#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
198#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
199
200# Driver interface parameters
Dmitry Shmidtaca489e2016-09-28 15:44:14 -0700201# This field can be used to configure arbitrary driver interface parameters. The
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800202# format is specific to the selected driver interface. This field is not used
203# in most cases.
204#driver_param="field=value"
205
206# Country code
207# The ISO/IEC alpha2 country code for the country in which this device is
208# currently operating.
209#country=US
210
211# Maximum lifetime for PMKSA in seconds; default 43200
212#dot11RSNAConfigPMKLifetime=43200
213# Threshold for reauthentication (percentage of PMK lifetime); default 70
214#dot11RSNAConfigPMKReauthThreshold=70
215# Timeout for security association negotiation in seconds; default 60
216#dot11RSNAConfigSATimeout=60
217
218# Wi-Fi Protected Setup (WPS) parameters
219
220# Universally Unique IDentifier (UUID; see RFC 4122) of the device
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700221# If not configured, UUID will be generated based on the mechanism selected with
222# the auto_uuid parameter.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800223#uuid=12345678-9abc-def0-1234-56789abcdef0
224
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700225# Automatic UUID behavior
226# 0 = generate static value based on the local MAC address (default)
227# 1 = generate a random UUID every time wpa_supplicant starts
228#auto_uuid=0
229
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800230# Device Name
231# User-friendly description of device; up to 32 octets encoded in UTF-8
232#device_name=Wireless Client
233
234# Manufacturer
235# The manufacturer of the device (up to 64 ASCII characters)
236#manufacturer=Company
237
238# Model Name
239# Model of the device (up to 32 ASCII characters)
240#model_name=cmodel
241
242# Model Number
243# Additional device description (up to 32 ASCII characters)
244#model_number=123
245
246# Serial Number
247# Serial number of the device (up to 32 characters)
248#serial_number=12345
249
250# Primary Device Type
251# Used format: <categ>-<OUI>-<subcateg>
252# categ = Category as an integer value
253# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
254# default WPS OUI
255# subcateg = OUI-specific Sub Category as an integer value
256# Examples:
257# 1-0050F204-1 (Computer / PC)
258# 1-0050F204-2 (Computer / Server)
259# 5-0050F204-1 (Storage / NAS)
260# 6-0050F204-1 (Network Infrastructure / AP)
261#device_type=1-0050F204-1
262
263# OS Version
264# 4-octet operating system version number (hex string)
265#os_version=01020300
266
267# Config Methods
268# List of the supported configuration methods
269# Available methods: usba ethernet label display ext_nfc_token int_nfc_token
270# nfc_interface push_button keypad virtual_display physical_display
271# virtual_push_button physical_push_button
272# For WSC 1.0:
273#config_methods=label display push_button keypad
274# For WSC 2.0:
275#config_methods=label virtual_display virtual_push_button keypad
276
277# Credential processing
278# 0 = process received credentials internally (default)
279# 1 = do not process received credentials; just pass them over ctrl_iface to
280# external program(s)
281# 2 = process received credentials internally and pass them over ctrl_iface
282# to external program(s)
283#wps_cred_processing=0
284
Hai Shalom021b0b52019-04-10 11:17:58 -0700285# Whether to enable SAE (WPA3-Personal transition mode) automatically for
286# WPA2-PSK credentials received using WPS.
287# 0 = only add the explicitly listed WPA2-PSK configuration (default)
288# 1 = add both the WPA2-PSK and SAE configuration and enable PMF so that the
289# station gets configured in WPA3-Personal transition mode (supports both
290# WPA2-Personal (PSK) and WPA3-Personal (SAE) APs).
291#wps_cred_add_sae=0
292
Dmitry Shmidt04949592012-07-19 12:16:46 -0700293# Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing
294# The vendor attribute contents to be added in M1 (hex string)
295#wps_vendor_ext_m1=000137100100020001
296
297# NFC password token for WPS
298# These parameters can be used to configure a fixed NFC password token for the
299# station. This can be generated, e.g., with nfc_pw_token. When these
300# parameters are used, the station is assumed to be deployed with a NFC tag
301# that includes the matching NFC password token (e.g., written based on the
302# NDEF record from nfc_pw_token).
303#
304#wps_nfc_dev_pw_id: Device Password ID (16..65535)
305#wps_nfc_dh_pubkey: Hexdump of DH Public Key
306#wps_nfc_dh_privkey: Hexdump of DH Private Key
307#wps_nfc_dev_pw: Hexdump of Device Password
308
Dmitry Shmidt7a53dbb2015-06-11 13:13:53 -0700309# Priority for the networks added through WPS
310# This priority value will be set to each network profile that is added
311# by executing the WPS protocol.
312#wps_priority=0
313
Hai Shalomc3565922019-10-28 11:58:20 -0700314# Device Provisioning Protocol (DPP) parameters
315#
316# How to process DPP configuration
317# 0 = report received configuration to an external program for
318# processing; do not generate any network profile internally (default)
319# 1 = report received configuration to an external program and generate
320# a network profile internally, but do not automatically connect
321# to the created (disabled) profile; the network profile id is
322# reported to external programs
323# 2 = report received configuration to an external program, generate
324# a network profile internally, try to connect to the created
325# profile automatically
326#dpp_config_processing=0
327#
328# Name for Enrollee's DPP Configuration Request
329#dpp_name=Test
330#
331# MUD URL for Enrollee's DPP Configuration Request (optional)
332#dpp_mud_url=https://example.com/mud
333
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800334# Maximum number of BSS entries to keep in memory
335# Default: 200
336# This can be used to limit memory use on the BSS entries (cached scan
337# results). A larger value may be needed in environments that have huge number
338# of APs when using ap_scan=1 mode.
339#bss_max_count=200
340
Hai Shalom5f92bc92019-04-18 11:54:11 -0700341# BSS expiration age in seconds. A BSS will be removed from the local cache
342# if it is not in use and has not been seen for this time. Default is 180.
343#bss_expiration_age=180
344
345# BSS expiration after number of scans. A BSS will be removed from the local
346# cache if it is not seen in this number of scans.
347# Default is 2.
348#bss_expiration_scan_count=2
349
Dmitry Shmidt04949592012-07-19 12:16:46 -0700350# Automatic scan
351# This is an optional set of parameters for automatic scanning
352# within an interface in following format:
353#autoscan=<autoscan module name>:<module parameters>
Dmitry Shmidtcce06662013-11-04 18:44:24 -0800354# autoscan is like bgscan but on disconnected or inactive state.
355# For instance, on exponential module parameters would be <base>:<limit>
Dmitry Shmidt04949592012-07-19 12:16:46 -0700356#autoscan=exponential:3:300
357# Which means a delay between scans on a base exponential of 3,
Dmitry Shmidtcce06662013-11-04 18:44:24 -0800358# up to the limit of 300 seconds (3, 9, 27 ... 300)
359# For periodic module, parameters would be <fixed interval>
Dmitry Shmidt04949592012-07-19 12:16:46 -0700360#autoscan=periodic:30
Dmitry Shmidtd7ff03d2015-12-04 14:49:35 -0800361# So a delay of 30 seconds will be applied between each scan.
362# Note: If sched_scan_plans are configured and supported by the driver,
363# autoscan is ignored.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800364
365# filter_ssids - SSID-based scan result filtering
366# 0 = do not filter scan results (default)
367# 1 = only include configured SSIDs in scan results/BSS table
368#filter_ssids=0
369
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700370# Password (and passphrase, etc.) backend for external storage
371# format: <backend name>[:<optional backend parameters>]
372#ext_password_backend=test:pw1=password|pw2=testing
373
Dmitry Shmidt1d755d02015-04-28 10:34:29 -0700374
375# Disable P2P functionality
376# p2p_disabled=1
377
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700378# Timeout in seconds to detect STA inactivity (default: 300 seconds)
379#
380# This timeout value is used in P2P GO mode to clean up
381# inactive stations.
382#p2p_go_max_inactivity=300
383
Dmitry Shmidt2271d3f2014-06-23 12:16:31 -0700384# Passphrase length (8..63) for P2P GO
385#
386# This parameter controls the length of the random passphrase that is
387# generated at the GO. Default: 8.
388#p2p_passphrase_len=8
389
Dmitry Shmidt09f57ba2014-06-10 16:07:13 -0700390# Extra delay between concurrent P2P search iterations
391#
392# This value adds extra delay in milliseconds between concurrent search
393# iterations to make p2p_find friendlier to concurrent operations by avoiding
394# it from taking 100% of radio resources. The default value is 500 ms.
395#p2p_search_delay=500
396
Dmitry Shmidtd5e49232012-12-03 15:08:10 -0800397# Opportunistic Key Caching (also known as Proactive Key Caching) default
398# This parameter can be used to set the default behavior for the
399# proactive_key_caching parameter. By default, OKC is disabled unless enabled
400# with the global okc=1 parameter or with the per-network
401# proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but
402# can be disabled with per-network proactive_key_caching=0 parameter.
403#okc=0
404
405# Protected Management Frames default
406# This parameter can be used to set the default behavior for the ieee80211w
Dmitry Shmidt849734c2016-05-27 09:59:01 -0700407# parameter for RSN networks. By default, PMF is disabled unless enabled with
408# the global pmf=1/2 parameter or with the per-network ieee80211w=1/2 parameter.
409# With pmf=1/2, PMF is enabled/required by default, but can be disabled with the
410# per-network ieee80211w parameter. This global default value does not apply
411# for non-RSN networks (key_mgmt=NONE) since PMF is available only when using
412# RSN.
Dmitry Shmidtd5e49232012-12-03 15:08:10 -0800413#pmf=0
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800414
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800415# Enabled SAE finite cyclic groups in preference order
416# By default (if this parameter is not set), the mandatory group 19 (ECC group
Hai Shalom021b0b52019-04-10 11:17:58 -0700417# defined over a 256-bit prime order field, NIST P-256) is preferred and groups
418# 20 (NIST P-384) and 21 (NIST P-521) are also enabled. If this parameter is
419# set, the groups will be tried in the indicated order.
420# The group values are listed in the IANA registry:
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800421# http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
Hai Shalom021b0b52019-04-10 11:17:58 -0700422# Note that groups 1, 2, 5, 22, 23, and 24 should not be used in production
423# purposes due limited security (see RFC 8247). Groups that are not as strong as
424# group 19 (ECC, NIST P-256) are unlikely to be useful for production use cases
425# since all implementations are required to support group 19.
426#sae_groups=19 20 21
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800427
Hai Shalomc3565922019-10-28 11:58:20 -0700428# SAE mechanism for PWE derivation
429# 0 = hunting-and-pecking loop only (default)
430# 1 = hash-to-element only
431# 2 = both hunting-and-pecking loop and hash-to-element enabled
432# Note: The default value is likely to change from 0 to 2 once the new
433# hash-to-element mechanism has received more interoperability testing.
434#sae_pwe=0
435
Dmitry Shmidt7a5e50a2013-03-05 12:37:16 -0800436# Default value for DTIM period (if not overridden in network block)
437#dtim_period=2
438
439# Default value for Beacon interval (if not overridden in network block)
440#beacon_int=100
441
Dmitry Shmidt0ccb66e2013-03-29 16:41:28 -0700442# Additional vendor specific elements for Beacon and Probe Response frames
443# This parameter can be used to add additional vendor specific element(s) into
444# the end of the Beacon and Probe Response frames. The format for these
445# element(s) is a hexdump of the raw information elements (id+len+payload for
446# one or more elements). This is used in AP and P2P GO modes.
447#ap_vendor_elements=dd0411223301
448
Dmitry Shmidt444d5672013-04-01 13:08:44 -0700449# Ignore scan results older than request
450#
451# The driver may have a cache of scan results that makes it return
452# information that is older than our scan trigger. This parameter can
453# be used to configure such old information to be ignored instead of
454# allowing it to update the internal BSS table.
455#ignore_old_scan_res=0
456
Dmitry Shmidtea69e842013-05-13 14:52:28 -0700457# scan_cur_freq: Whether to scan only the current frequency
458# 0: Scan all available frequencies. (Default)
459# 1: Scan current operating frequency if another VIF on the same radio
460# is already associated.
Dmitry Shmidt444d5672013-04-01 13:08:44 -0700461
Dmitry Shmidt661b4f72014-09-29 14:58:27 -0700462# MAC address policy default
463# 0 = use permanent MAC address
464# 1 = use random MAC address for each ESS connection
465# 2 = like 1, but maintain OUI (with local admin bit set)
466#
467# By default, permanent MAC address is used unless policy is changed by
468# the per-network mac_addr parameter. Global mac_addr=1 can be used to
469# change this default behavior.
470#mac_addr=0
471
472# Lifetime of random MAC address in seconds (default: 60)
473#rand_addr_lifetime=60
474
475# MAC address policy for pre-association operations (scanning, ANQP)
476# 0 = use permanent MAC address
477# 1 = use random MAC address
478# 2 = like 1, but maintain OUI (with local admin bit set)
479#preassoc_mac_addr=0
480
Dmitry Shmidtebd93af2017-02-21 13:40:44 -0800481# MAC address policy for GAS operations
482# 0 = use permanent MAC address
483# 1 = use random MAC address
484# 2 = like 1, but maintain OUI (with local admin bit set)
485#gas_rand_mac_addr=0
486
487# Lifetime of GAS random MAC address in seconds (default: 60)
488#gas_rand_addr_lifetime=60
489
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -0800490# Interworking (IEEE 802.11u)
491
492# Enable Interworking
493# interworking=1
494
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700495# Enable P2P GO advertisement of Interworking
496# go_interworking=1
497
498# P2P GO Interworking: Access Network Type
499# 0 = Private network
500# 1 = Private network with guest access
501# 2 = Chargeable public network
502# 3 = Free public network
503# 4 = Personal device network
504# 5 = Emergency services only network
505# 14 = Test or experimental
506# 15 = Wildcard
507#go_access_network_type=0
508
509# P2P GO Interworking: Whether the network provides connectivity to the Internet
510# 0 = Unspecified
511# 1 = Network provides connectivity to the Internet
512#go_internet=1
513
514# P2P GO Interworking: Group Venue Info (optional)
515# The available values are defined in IEEE Std 802.11-2016, 9.4.1.35.
516# Example values (group,type):
517# 0,0 = Unspecified
518# 1,7 = Convention Center
519# 1,13 = Coffee Shop
520# 2,0 = Unspecified Business
521# 7,1 Private Residence
522#go_venue_group=7
523#go_venue_type=1
524
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -0800525# Homogenous ESS identifier
526# If this is set, scans will be used to request response only from BSSes
527# belonging to the specified Homogeneous ESS. This is used only if interworking
528# is enabled.
529# hessid=00:11:22:33:44:55
530
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700531# Automatic network selection behavior
532# 0 = do not automatically go through Interworking network selection
533# (i.e., require explicit interworking_select command for this; default)
534# 1 = perform Interworking network selection if one or more
535# credentials have been configured and scan did not find a
536# matching network block
537#auto_interworking=0
538
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -0700539# GAS Address3 field behavior
540# 0 = P2P specification (Address3 = AP BSSID); default
541# 1 = IEEE 802.11 standard compliant (Address3 = Wildcard BSSID when
542# sent to not-associated AP; if associated, AP BSSID)
543#gas_address3=0
544
Dmitry Shmidt7d175302016-09-06 13:11:34 -0700545# Publish fine timing measurement (FTM) responder functionality in
546# the Extended Capabilities element bit 70.
547# Controls whether FTM responder functionality will be published by AP/STA.
548# Note that actual FTM responder operation is managed outside wpa_supplicant.
549# 0 = Do not publish; default
550# 1 = Publish
551#ftm_responder=0
552
553# Publish fine timing measurement (FTM) initiator functionality in
554# the Extended Capabilities element bit 71.
555# Controls whether FTM initiator functionality will be published by AP/STA.
556# Note that actual FTM initiator operation is managed outside wpa_supplicant.
557# 0 = Do not publish; default
558# 1 = Publish
559#ftm_initiator=0
560
Dmitry Shmidt04949592012-07-19 12:16:46 -0700561# credential block
562#
563# Each credential used for automatic network selection is configured as a set
564# of parameters that are compared to the information advertised by the APs when
565# interworking_select and interworking_connect commands are used.
566#
567# credential fields:
568#
Dmitry Shmidtfb79edc2014-01-10 10:45:54 -0800569# temporary: Whether this credential is temporary and not to be saved
570#
Dmitry Shmidt04949592012-07-19 12:16:46 -0700571# priority: Priority group
572# By default, all networks and credentials get the same priority group
573# (0). This field can be used to give higher priority for credentials
574# (and similarly in struct wpa_ssid for network blocks) to change the
575# Interworking automatic networking selection behavior. The matching
576# network (based on either an enabled network block or a credential)
577# with the highest priority value will be selected.
578#
579# pcsc: Use PC/SC and SIM/USIM card
580#
581# realm: Home Realm for Interworking
582#
583# username: Username for Interworking network selection
584#
585# password: Password for Interworking network selection
586#
587# ca_cert: CA certificate for Interworking network selection
588#
589# client_cert: File path to client certificate file (PEM/DER)
590# This field is used with Interworking networking selection for a case
591# where client certificate/private key is used for authentication
592# (EAP-TLS). Full path to the file should be used since working
593# directory may change when wpa_supplicant is run in the background.
594#
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -0700595# Certificates from PKCS#11 tokens can be referenced by a PKCS#11 URI.
596#
597# For example: private_key="pkcs11:manufacturer=piv_II;id=%01"
598#
Dmitry Shmidt04949592012-07-19 12:16:46 -0700599# Alternatively, a named configuration blob can be used by setting
600# this to blob://blob_name.
601#
602# private_key: File path to client private key file (PEM/DER/PFX)
603# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
604# commented out. Both the private key and certificate will be read
605# from the PKCS#12 file in this case. Full path to the file should be
606# used since working directory may change when wpa_supplicant is run
607# in the background.
608#
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -0700609# Keys in PKCS#11 tokens can be referenced by a PKCS#11 URI.
610# For example: private_key="pkcs11:manufacturer=piv_II;id=%01"
611#
Dmitry Shmidt04949592012-07-19 12:16:46 -0700612# Windows certificate store can be used by leaving client_cert out and
613# configuring private_key in one of the following formats:
614#
615# cert://substring_to_match
616#
617# hash://certificate_thumbprint_in_hex
618#
619# For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
620#
621# Note that when running wpa_supplicant as an application, the user
622# certificate store (My user account) is used, whereas computer store
623# (Computer account) is used when running wpasvc as a service.
624#
625# Alternatively, a named configuration blob can be used by setting
626# this to blob://blob_name.
627#
628# private_key_passwd: Password for private key file
629#
630# imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format
631#
632# milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN>
633# format
634#
Dmitry Shmidt051af732013-10-22 13:52:46 -0700635# domain: Home service provider FQDN(s)
Dmitry Shmidt04949592012-07-19 12:16:46 -0700636# This is used to compare against the Domain Name List to figure out
Dmitry Shmidt051af732013-10-22 13:52:46 -0700637# whether the AP is operated by the Home SP. Multiple domain entries can
638# be used to configure alternative FQDNs that will be considered home
639# networks.
Dmitry Shmidt04949592012-07-19 12:16:46 -0700640#
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700641# roaming_consortium: Roaming Consortium OI
642# If roaming_consortium_len is non-zero, this field contains the
643# Roaming Consortium OI that can be used to determine which access
644# points support authentication with this credential. This is an
645# alternative to the use of the realm parameter. When using Roaming
646# Consortium to match the network, the EAP parameters need to be
647# pre-configured with the credential since the NAI Realm information
648# may not be available or fetched.
649#
Roshan Pius3a1667e2018-07-03 15:17:14 -0700650# required_roaming_consortium: Required Roaming Consortium OI
651# If required_roaming_consortium_len is non-zero, this field contains the
652# Roaming Consortium OI that is required to be advertised by the AP for
653# the credential to be considered matching.
654#
655# roaming_consortiums: Roaming Consortium OI(s) memberships
656# This string field contains one or more comma delimited OIs (hexdump)
657# identifying the roaming consortiums of which the provider is a member.
658# The list is sorted from the most preferred one to the least preferred
659# one. A match between the Roaming Consortium OIs advertised by an AP and
660# the OIs in this list indicates that successful authentication is
661# possible.
662# (Hotspot 2.0 PerProviderSubscription/<X+>/HomeSP/RoamingConsortiumOI)
663#
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700664# eap: Pre-configured EAP method
665# This optional field can be used to specify which EAP method will be
666# used with this credential. If not set, the EAP method is selected
667# automatically based on ANQP information (e.g., NAI Realm).
668#
669# phase1: Pre-configure Phase 1 (outer authentication) parameters
670# This optional field is used with like the 'eap' parameter.
671#
672# phase2: Pre-configure Phase 2 (inner authentication) parameters
673# This optional field is used with like the 'eap' parameter.
674#
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800675# excluded_ssid: Excluded SSID
676# This optional field can be used to excluded specific SSID(s) from
677# matching with the network. Multiple entries can be used to specify more
678# than one SSID.
679#
Dmitry Shmidtf21452a2014-02-26 10:55:25 -0800680# roaming_partner: Roaming partner information
681# This optional field can be used to configure preferences between roaming
682# partners. The field is a string in following format:
683# <FQDN>,<0/1 exact match>,<priority>,<* or country code>
684# (non-exact match means any subdomain matches the entry; priority is in
685# 0..255 range with 0 being the highest priority)
686#
687# update_identifier: PPS MO ID
688# (Hotspot 2.0 PerProviderSubscription/UpdateIdentifier)
689#
690# provisioning_sp: FQDN of the SP that provisioned the credential
691# This optional field can be used to keep track of the SP that provisioned
692# the credential to find the PPS MO (./Wi-Fi/<provisioning_sp>).
693#
694# Minimum backhaul threshold (PPS/<X+>/Policy/MinBackhauldThreshold/*)
695# These fields can be used to specify minimum download/upload backhaul
696# bandwidth that is preferred for the credential. This constraint is
697# ignored if the AP does not advertise WAN Metrics information or if the
698# limit would prevent any connection. Values are in kilobits per second.
699# min_dl_bandwidth_home
700# min_ul_bandwidth_home
701# min_dl_bandwidth_roaming
702# min_ul_bandwidth_roaming
703#
704# max_bss_load: Maximum BSS Load Channel Utilization (1..255)
705# (PPS/<X+>/Policy/MaximumBSSLoadValue)
706# This value is used as the maximum channel utilization for network
707# selection purposes for home networks. If the AP does not advertise
708# BSS Load or if the limit would prevent any connection, this constraint
709# will be ignored.
710#
711# req_conn_capab: Required connection capability
712# (PPS/<X+>/Policy/RequiredProtoPortTuple)
713# This value is used to configure set of required protocol/port pairs that
714# a roaming network shall support (include explicitly in Connection
715# Capability ANQP element). This constraint is ignored if the AP does not
716# advertise Connection Capability or if this constraint would prevent any
717# network connection. This policy is not used in home networks.
718# Format: <protocol>[:<comma-separated list of ports]
719# Multiple entries can be used to list multiple requirements.
720# For example, number of common TCP protocols:
721# req_conn_capab=6,22,80,443
722# For example, IPSec/IKE:
723# req_conn_capab=17:500
724# req_conn_capab=50
725#
726# ocsp: Whether to use/require OCSP to check server certificate
727# 0 = do not use OCSP stapling (TLS certificate status extension)
728# 1 = try to use OCSP stapling, but not require response
729# 2 = require valid OCSP stapling response
Dmitry Shmidt014a3ff2015-12-28 13:27:49 -0800730# 3 = require valid OCSP stapling response for all not-trusted
731# certificates in the server certificate chain
Dmitry Shmidtf21452a2014-02-26 10:55:25 -0800732#
Dmitry Shmidtf9bdef92014-04-25 10:46:36 -0700733# sim_num: Identifier for which SIM to use in multi-SIM devices
734#
Dmitry Shmidt04949592012-07-19 12:16:46 -0700735# for example:
736#
737#cred={
738# realm="example.com"
739# username="user@example.com"
740# password="password"
741# ca_cert="/etc/wpa_supplicant/ca.pem"
742# domain="example.com"
743#}
744#
745#cred={
746# imsi="310026-000000000"
747# milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82"
748#}
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700749#
750#cred={
751# realm="example.com"
752# username="user"
753# password="password"
754# ca_cert="/etc/wpa_supplicant/ca.pem"
755# domain="example.com"
756# roaming_consortium=223344
757# eap=TTLS
758# phase2="auth=MSCHAPV2"
759#}
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -0800760
Dmitry Shmidt04949592012-07-19 12:16:46 -0700761# Hotspot 2.0
762# hs20=1
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -0800763
Dmitry Shmidtd7ff03d2015-12-04 14:49:35 -0800764# Scheduled scan plans
765#
766# A space delimited list of scan plans. Each scan plan specifies the scan
767# interval and number of iterations, delimited by a colon. The last scan plan
768# will run infinitely and thus must specify only the interval and not the number
769# of iterations.
770#
771# The driver advertises the maximum number of scan plans supported. If more scan
772# plans than supported are configured, only the first ones are set (up to the
773# maximum supported). The last scan plan that specifies only the interval is
774# always set as the last plan.
775#
776# If the scan interval or the number of iterations for a scan plan exceeds the
777# maximum supported, it will be set to the maximum supported value.
778#
779# Format:
780# sched_scan_plans=<interval:iterations> <interval:iterations> ... <interval>
781#
782# Example:
783# sched_scan_plans=10:100 20:200 30
784
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800785# Multi Band Operation (MBO) non-preferred channels
786# A space delimited list of non-preferred channels where each channel is a colon
Dmitry Shmidtaca489e2016-09-28 15:44:14 -0700787# delimited list of values.
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800788# Format:
Dmitry Shmidtaca489e2016-09-28 15:44:14 -0700789# non_pref_chan=<oper_class>:<chan>:<preference>:<reason>
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800790# Example:
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700791# non_pref_chan=81:5:10:2 81:1:0:2 81:9:0:2
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800792
793# MBO Cellular Data Capabilities
794# 1 = Cellular data connection available
795# 2 = Cellular data connection not available
796# 3 = Not cellular capable (default)
797#mbo_cell_capa=3
798
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700799# Optimized Connectivity Experience (OCE)
800# oce: Enable OCE features (bitmap)
801# Set BIT(0) to Enable OCE in non-AP STA mode (default; disabled if the driver
802# does not indicate support for OCE in STA mode)
803# Set BIT(1) to Enable OCE in STA-CFON mode
804#oce=1
805
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800806# network block
807#
808# Each network (usually AP's sharing the same SSID) is configured as a separate
809# block in this configuration file. The network blocks are in preference order
810# (the first match is used).
811#
812# network block fields:
813#
814# disabled:
815# 0 = this network can be used (default)
816# 1 = this network block is disabled (can be enabled through ctrl_iface,
817# e.g., with wpa_cli or wpa_gui)
818#
819# id_str: Network identifier string for external scripts. This value is passed
820# to external action script through wpa_cli as WPA_ID_STR environment
821# variable to make it easier to do network specific configuration.
822#
Dmitry Shmidt61d9df32012-08-29 16:22:06 -0700823# ssid: SSID (mandatory); network name in one of the optional formats:
824# - an ASCII string with double quotation
825# - a hex string (two characters per octet of SSID)
826# - a printf-escaped ASCII string P"<escaped string>"
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800827#
828# scan_ssid:
829# 0 = do not scan this SSID with specific Probe Request frames (default)
830# 1 = scan with SSID-specific Probe Request frames (this can be used to
831# find APs that do not accept broadcast SSID or use multiple SSIDs;
832# this will add latency to scanning, so enable this only when needed)
833#
834# bssid: BSSID (optional); if set, this network block is used only when
835# associating with the AP using the configured BSSID
836#
837# priority: priority group (integer)
838# By default, all networks will get same priority group (0). If some of the
839# networks are more desirable, this field can be used to change the order in
840# which wpa_supplicant goes through the networks when selecting a BSS. The
841# priority groups will be iterated in decreasing priority (i.e., the larger the
842# priority value, the sooner the network is matched against the scan results).
843# Within each priority group, networks will be selected based on security
844# policy, signal strength, etc.
845# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
846# using this priority to select the order for scanning. Instead, they try the
847# networks in the order that used in the configuration file.
848#
849# mode: IEEE 802.11 operation mode
850# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
851# 1 = IBSS (ad-hoc, peer-to-peer)
852# 2 = AP (access point)
Dmitry Shmidtfb79edc2014-01-10 10:45:54 -0800853# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) and
854# WPA-PSK (with proto=RSN). In addition, key_mgmt=WPA-NONE (fixed group key
855# TKIP/CCMP) is available for backwards compatibility, but its use is
856# deprecated. WPA-None requires following network block options:
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800857# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
858# both), and psk must also be set.
859#
860# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
861# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
862# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
863# In addition, this value is only used by the station that creates the IBSS. If
864# an IBSS network with the configured SSID is already present, the frequency of
865# the network will be used instead of this configured value.
866#
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800867# pbss: Whether to use PBSS. Relevant to IEEE 802.11ad networks only.
Dmitry Shmidt849734c2016-05-27 09:59:01 -0700868# 0 = do not use PBSS
869# 1 = use PBSS
870# 2 = don't care (not allowed in AP mode)
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800871# Used together with mode configuration. When mode is AP, it means to start a
872# PCP instead of a regular AP. When mode is infrastructure it means connect
Dmitry Shmidt849734c2016-05-27 09:59:01 -0700873# to a PCP instead of AP. In this mode you can also specify 2 (don't care)
874# which means connect to either PCP or AP.
875# P2P_GO and P2P_GROUP_FORMATION modes must use PBSS in IEEE 802.11ad network.
Dmitry Shmidt57c2d392016-02-23 13:40:19 -0800876# For more details, see IEEE Std 802.11ad-2012.
877#
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800878# scan_freq: List of frequencies to scan
879# Space-separated list of frequencies in MHz to scan when searching for this
880# BSS. If the subset of channels used by the network is known, this option can
881# be used to optimize scanning to not occur on channels that the network does
882# not use. Example: scan_freq=2412 2437 2462
883#
884# freq_list: Array of allowed frequencies
885# Space-separated list of frequencies in MHz to allow for selecting the BSS. If
886# set, scan results that do not match any of the specified frequencies are not
887# considered when selecting a BSS.
888#
Dmitry Shmidt51b6ea82013-05-08 10:42:09 -0700889# This can also be set on the outside of the network block. In this case,
890# it limits the frequencies that will be scanned.
891#
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800892# bgscan: Background scanning
893# wpa_supplicant behavior for background scanning can be specified by
894# configuring a bgscan module. These modules are responsible for requesting
895# background scans for the purpose of roaming within an ESS (i.e., within a
896# single network block with all the APs using the same SSID). The bgscan
897# parameter uses following format: "<bgscan module name>:<module parameters>"
898# Following bgscan modules are available:
899# simple - Periodic background scans based on signal strength
900# bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>:
901# <long interval>"
902# bgscan="simple:30:-45:300"
903# learn - Learn channels used by the network and try to avoid bgscans on other
904# channels (experimental)
905# bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>:
906# <long interval>[:<database file name>]"
907# bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan"
Dmitry Shmidta38abf92014-03-06 13:38:44 -0800908# Explicitly disable bgscan by setting
909# bgscan=""
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -0800910#
Dmitry Shmidtb96dad42013-11-05 10:07:29 -0800911# This option can also be set outside of all network blocks for the bgscan
912# parameter to apply for all the networks that have no specific bgscan
913# parameter.
914#
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800915# proto: list of accepted protocols
916# WPA = WPA/IEEE 802.11i/D3.0
917# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
Hai Shalomce48b4a2018-09-05 11:41:35 -0700918# Note that RSN is used also for WPA3.
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800919# If not set, this defaults to: WPA RSN
920#
921# key_mgmt: list of accepted authenticated key management protocols
922# WPA-PSK = WPA pre-shared key (this requires 'psk' field)
923# WPA-EAP = WPA using EAP authentication
924# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
925# generated WEP keys
926# NONE = WPA is not used; plaintext or static WEP could be used
Dmitry Shmidt014a3ff2015-12-28 13:27:49 -0800927# WPA-NONE = WPA-None for IBSS (deprecated; use proto=RSN key_mgmt=WPA-PSK
928# instead)
929# FT-PSK = Fast BSS Transition (IEEE 802.11r) with pre-shared key
930# FT-EAP = Fast BSS Transition (IEEE 802.11r) with EAP authentication
Roshan Pius3a1667e2018-07-03 15:17:14 -0700931# FT-EAP-SHA384 = Fast BSS Transition (IEEE 802.11r) with EAP authentication
932# and using SHA384
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800933# WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
934# WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
Dmitry Shmidt014a3ff2015-12-28 13:27:49 -0800935# SAE = Simultaneous authentication of equals; pre-shared key/password -based
936# authentication with stronger security than WPA-PSK especially when using
Hai Shalomce48b4a2018-09-05 11:41:35 -0700937# not that strong password; a.k.a. WPA3-Personal
Dmitry Shmidt014a3ff2015-12-28 13:27:49 -0800938# FT-SAE = SAE with FT
939# WPA-EAP-SUITE-B = Suite B 128-bit level
940# WPA-EAP-SUITE-B-192 = Suite B 192-bit level
Dmitry Shmidtde47be72016-01-07 12:52:55 -0800941# OSEN = Hotspot 2.0 Rel 2 online signup connection
Dmitry Shmidt9839ecd2016-11-07 11:05:47 -0800942# FILS-SHA256 = Fast Initial Link Setup with SHA256
943# FILS-SHA384 = Fast Initial Link Setup with SHA384
944# FT-FILS-SHA256 = FT and Fast Initial Link Setup with SHA256
945# FT-FILS-SHA384 = FT and Fast Initial Link Setup with SHA384
Hai Shalomce48b4a2018-09-05 11:41:35 -0700946# OWE = Opportunistic Wireless Encryption (a.k.a. Enhanced Open)
947# DPP = Device Provisioning Protocol
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800948# If not set, this defaults to: WPA-PSK WPA-EAP
949#
Dmitry Shmidt04949592012-07-19 12:16:46 -0700950# ieee80211w: whether management frame protection is enabled
Dmitry Shmidtd5e49232012-12-03 15:08:10 -0800951# 0 = disabled (default unless changed with the global pmf parameter)
Dmitry Shmidt04949592012-07-19 12:16:46 -0700952# 1 = optional
953# 2 = required
954# The most common configuration options for this based on the PMF (protected
955# management frames) certification program are:
956# PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256
957# PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256
958# (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used)
959#
Hai Shalom74f70d42019-02-11 14:42:39 -0800960# ocv: whether operating channel validation is enabled
961# This is a countermeasure against multi-channel man-in-the-middle attacks.
962# Enabling this automatically also enables ieee80211w, if not yet enabled.
963# 0 = disabled (default)
964# 1 = enabled
965#ocv=1
966#
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800967# auth_alg: list of allowed IEEE 802.11 authentication algorithms
968# OPEN = Open System authentication (required for WPA/WPA2)
969# SHARED = Shared Key authentication (requires static WEP keys)
970# LEAP = LEAP/Network EAP (only used with LEAP)
971# If not set, automatic selection is used (Open System with LEAP enabled if
972# LEAP is allowed as one of the EAP methods).
973#
974# pairwise: list of accepted pairwise (unicast) ciphers for WPA
975# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
976# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
977# NONE = Use only Group Keys (deprecated, should not be included if APs support
978# pairwise keys)
979# If not set, this defaults to: CCMP TKIP
980#
981# group: list of accepted group (broadcast/multicast) ciphers for WPA
982# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
983# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
984# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
985# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
986# If not set, this defaults to: CCMP TKIP WEP104 WEP40
987#
Dmitry Shmidtd2986c22017-10-23 14:22:09 -0700988# group_mgmt: list of accepted group management ciphers for RSN (PMF)
989# AES-128-CMAC = BIP-CMAC-128
990# BIP-GMAC-128
991# BIP-GMAC-256
992# BIP-CMAC-256
993# If not set, no constraint on the cipher, i.e., accept whichever cipher the AP
994# indicates.
995#
Dmitry Shmidt30f94812012-02-21 17:02:48 -0800996# psk: WPA preshared key; 256-bit pre-shared key
997# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
998# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
999# generated using the passphrase and SSID). ASCII passphrase must be between
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001000# 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
1001# be used to indicate that the PSK/passphrase is stored in external storage.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001002# This field is not needed, if WPA-EAP is used.
1003# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
1004# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
1005# startup and reconfiguration time can be optimized by generating the PSK only
1006# only when the passphrase or SSID has actually changed.
1007#
Dmitry Shmidt912c6ec2015-03-30 13:16:51 -07001008# mem_only_psk: Whether to keep PSK/passphrase only in memory
1009# 0 = allow psk/passphrase to be stored to the configuration file
1010# 1 = do not store psk/passphrase to the configuration file
1011#mem_only_psk=0
1012#
Dmitry Shmidtd2986c22017-10-23 14:22:09 -07001013# sae_password: SAE password
1014# This parameter can be used to set a password for SAE. By default, the
Roshan Pius3a1667e2018-07-03 15:17:14 -07001015# passphrase from the psk parameter is used if this separate parameter is not
1016# used, but psk follows the WPA-PSK constraints (8..63 characters) even though
1017# SAE passwords do not have such constraints.
1018#
1019# sae_password_id: SAE password identifier
1020# This parameter can be used to set an identifier for the SAE password. By
1021# default, no such identifier is used. If set, the specified identifier value
1022# is used by the other peer to select which password to use for authentication.
Dmitry Shmidtd2986c22017-10-23 14:22:09 -07001023#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001024# eapol_flags: IEEE 802.1X/EAPOL options (bit field)
1025# Dynamic WEP key required for non-WPA mode
1026# bit0 (1): require dynamically generated unicast WEP key
1027# bit1 (2): require dynamically generated broadcast WEP key
1028# (3 = require both keys; default)
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001029# Note: When using wired authentication (including MACsec drivers),
Dmitry Shmidt5a1480c2014-05-12 09:46:02 -07001030# eapol_flags must be set to 0 for the authentication to be completed
1031# successfully.
1032#
1033# macsec_policy: IEEE 802.1X/MACsec options
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001034# This determines how sessions are secured with MACsec (only for MACsec
1035# drivers).
Dmitry Shmidt5a1480c2014-05-12 09:46:02 -07001036# 0: MACsec not in use (default)
1037# 1: MACsec enabled - Should secure, accept key server's advice to
1038# determine whether to use a secure session or not.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001039#
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001040# macsec_integ_only: IEEE 802.1X/MACsec transmit mode
1041# This setting applies only when MACsec is in use, i.e.,
1042# - macsec_policy is enabled
1043# - the key server has decided to enable MACsec
1044# 0: Encrypt traffic (default)
1045# 1: Integrity only
1046#
Hai Shalom74f70d42019-02-11 14:42:39 -08001047# macsec_replay_protect: IEEE 802.1X/MACsec replay protection
1048# This setting applies only when MACsec is in use, i.e.,
1049# - macsec_policy is enabled
1050# - the key server has decided to enable MACsec
1051# 0: Replay protection disabled (default)
1052# 1: Replay protection enabled
1053#
1054# macsec_replay_window: IEEE 802.1X/MACsec replay protection window
1055# This determines a window in which replay is tolerated, to allow receipt
1056# of frames that have been misordered by the network.
1057# This setting applies only when MACsec replay protection active, i.e.,
1058# - macsec_replay_protect is enabled
1059# - the key server has decided to enable MACsec
1060# 0: No replay window, strict check (default)
1061# 1..2^32-1: number of packets that could be misordered
1062#
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001063# macsec_port: IEEE 802.1X/MACsec port
1064# Port component of the SCI
1065# Range: 1-65534 (default: 1)
1066#
Dmitry Shmidt29333592017-01-09 12:27:11 -08001067# mka_cak, mka_ckn, and mka_priority: IEEE 802.1X/MACsec pre-shared key mode
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001068# This allows to configure MACsec with a pre-shared key using a (CAK,CKN) pair.
Dmitry Shmidt29333592017-01-09 12:27:11 -08001069# In this mode, instances of wpa_supplicant can act as MACsec peers. The peer
1070# with lower priority will become the key server and start distributing SAKs.
Hai Shalom74f70d42019-02-11 14:42:39 -08001071# mka_cak (CAK = Secure Connectivity Association Key) takes a 16-byte (128-bit)
1072# hex-string (32 hex-digits) or a 32-byte (256-bit) hex-string (64 hex-digits)
1073# mka_ckn (CKN = CAK Name) takes a 1..32-bytes (8..256 bit) hex-string
1074# (2..64 hex-digits)
Dmitry Shmidt29333592017-01-09 12:27:11 -08001075# mka_priority (Priority of MKA Actor) is in 0..255 range with 255 being
1076# default priority
Dmitry Shmidtabb90a32016-12-05 15:34:39 -08001077#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001078# mixed_cell: This option can be used to configure whether so called mixed
1079# cells, i.e., networks that use both plaintext and encryption in the same
Dmitry Shmidtc5ec7f52012-03-06 16:33:24 -08001080# SSID, are allowed when selecting a BSS from scan results.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001081# 0 = disabled (default)
1082# 1 = enabled
1083#
1084# proactive_key_caching:
1085# Enable/disable opportunistic PMKSA caching for WPA2.
Dmitry Shmidtd5e49232012-12-03 15:08:10 -08001086# 0 = disabled (default unless changed with the global okc parameter)
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001087# 1 = enabled
1088#
Hai Shalom81f62d82019-07-22 12:10:00 -07001089# ft_eap_pmksa_caching:
1090# Whether FT-EAP PMKSA caching is allowed
1091# 0 = do not try to use PMKSA caching with FT-EAP (default)
1092# 1 = try to use PMKSA caching with FT-EAP
1093# This controls whether to try to use PMKSA caching with FT-EAP for the
1094# FT initial mobility domain association.
1095#ft_eap_pmksa_caching=0
1096#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001097# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
1098# hex without quotation, e.g., 0102030405)
1099# wep_tx_keyidx: Default WEP key index (TX) (0..3)
1100#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001101# wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
1102# enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
1103#
Dmitry Shmidt7f2c7532016-08-15 09:48:12 -07001104# group_rekey: Group rekeying time in seconds. This value, if non-zero, is used
1105# as the dot11RSNAConfigGroupRekeyTime parameter when operating in
Paul Stewart092955c2017-02-06 09:13:09 -08001106# Authenticator role in IBSS, or in AP and mesh modes.
Dmitry Shmidt7f2c7532016-08-15 09:48:12 -07001107#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001108# Following fields are only used with internal EAP implementation.
1109# eap: space-separated list of accepted EAP methods
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001110# MD5 = EAP-MD5 (insecure and does not generate keying material ->
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001111# cannot be used with WPA; to be used as a Phase 2 method
1112# with EAP-PEAP or EAP-TTLS)
1113# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
1114# as a Phase 2 method with EAP-PEAP or EAP-TTLS)
1115# OTP = EAP-OTP (cannot be used separately with WPA; to be used
1116# as a Phase 2 method with EAP-PEAP or EAP-TTLS)
1117# GTC = EAP-GTC (cannot be used separately with WPA; to be used
1118# as a Phase 2 method with EAP-PEAP or EAP-TTLS)
1119# TLS = EAP-TLS (client and server certificate)
1120# PEAP = EAP-PEAP (with tunnelled EAP authentication)
1121# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
1122# authentication)
1123# If not set, all compiled in methods are allowed.
1124#
1125# identity: Identity string for EAP
1126# This field is also used to configure user NAI for
1127# EAP-PSK/PAX/SAKE/GPSK.
1128# anonymous_identity: Anonymous identity string for EAP (to be used as the
1129# unencrypted identity with EAP types that support different tunnelled
Dmitry Shmidt4530cfd2012-09-09 15:20:40 -07001130# identity, e.g., EAP-TTLS). This field can also be used with
1131# EAP-SIM/AKA/AKA' to store the pseudonym identity.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001132# password: Password string for EAP. This field can include either the
1133# plaintext password (using ASCII or hex string) or a NtPasswordHash
1134# (16-byte MD4 hash of password) in hash:<32 hex digits> format.
1135# NtPasswordHash can only be used when the password is for MSCHAPv2 or
1136# MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
1137# EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
1138# PSK) is also configured using this field. For EAP-GPSK, this is a
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001139# variable length PSK. ext:<name of external password field> format can
1140# be used to indicate that the password is stored in external storage.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001141# ca_cert: File path to CA certificate file (PEM/DER). This file can have one
1142# or more trusted CA certificates. If ca_cert and ca_path are not
1143# included, server certificate will not be verified. This is insecure and
1144# a trusted CA certificate should always be configured when using
1145# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
1146# change when wpa_supplicant is run in the background.
1147#
1148# Alternatively, this can be used to only perform matching of the server
1149# certificate (SHA-256 hash of the DER encoded X.509 certificate). In
1150# this case, the possible CA certificates in the server certificate chain
1151# are ignored and only the server certificate is verified. This is
1152# configured with the following format:
1153# hash:://server/sha256/cert_hash_in_hex
1154# For example: "hash://server/sha256/
1155# 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
1156#
1157# On Windows, trusted CA certificates can be loaded from the system
1158# certificate store by setting this to cert_store://<name>, e.g.,
1159# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
1160# Note that when running wpa_supplicant as an application, the user
1161# certificate store (My user account) is used, whereas computer store
1162# (Computer account) is used when running wpasvc as a service.
1163# ca_path: Directory path for CA certificate files (PEM). This path may
1164# contain multiple CA certificates in OpenSSL format. Common use for this
1165# is to point to system trusted CA list which is often installed into
1166# directory like /etc/ssl/certs. If configured, these certificates are
1167# added to the list of trusted CAs. ca_cert may also be included in that
1168# case, but it is not required.
1169# client_cert: File path to client certificate file (PEM/DER)
1170# Full path should be used since working directory may change when
1171# wpa_supplicant is run in the background.
1172# Alternatively, a named configuration blob can be used by setting this
1173# to blob://<blob name>.
1174# private_key: File path to client private key file (PEM/DER/PFX)
1175# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
1176# commented out. Both the private key and certificate will be read from
1177# the PKCS#12 file in this case. Full path should be used since working
1178# directory may change when wpa_supplicant is run in the background.
1179# Windows certificate store can be used by leaving client_cert out and
1180# configuring private_key in one of the following formats:
1181# cert://substring_to_match
1182# hash://certificate_thumbprint_in_hex
1183# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
1184# Note that when running wpa_supplicant as an application, the user
1185# certificate store (My user account) is used, whereas computer store
1186# (Computer account) is used when running wpasvc as a service.
1187# Alternatively, a named configuration blob can be used by setting this
1188# to blob://<blob name>.
1189# private_key_passwd: Password for private key file (if left out, this will be
1190# asked through control interface)
1191# dh_file: File path to DH/DSA parameters file (in PEM format)
1192# This is an optional configuration file for setting parameters for an
1193# ephemeral DH key exchange. In most cases, the default RSA
1194# authentication does not use this configuration. However, it is possible
1195# setup RSA to use ephemeral DH key exchange. In addition, ciphers with
1196# DSA keys always use ephemeral DH keys. This can be used to achieve
1197# forward secrecy. If the file is in DSA parameters format, it will be
1198# automatically converted into DH params.
1199# subject_match: Substring to be matched against the subject of the
1200# authentication server certificate. If this string is set, the server
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001201# certificate is only accepted if it contains this string in the subject.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001202# The subject string is in following format:
1203# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001204# Note: Since this is a substring match, this cannot be used securely to
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001205# do a suffix match against a possible domain name in the CN entry. For
Dmitry Shmidt2f74e362015-01-21 13:19:05 -08001206# such a use case, domain_suffix_match or domain_match should be used
1207# instead.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001208# altsubject_match: Semicolon separated string of entries to be matched against
1209# the alternative subject name of the authentication server certificate.
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001210# If this string is set, the server certificate is only accepted if it
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001211# contains one of the entries in an alternative subject name extension.
1212# altSubjectName string is in following format: TYPE:VALUE
1213# Example: EMAIL:server@example.com
1214# Example: DNS:server.example.com;DNS:server2.example.com
1215# Following types are supported: EMAIL, DNS, URI
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001216# domain_suffix_match: Constraint for server domain name. If set, this FQDN is
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001217# used as a suffix match requirement for the AAA server certificate in
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001218# SubjectAltName dNSName element(s). If a matching dNSName is found, this
1219# constraint is met. If no dNSName values are present, this constraint is
1220# matched against SubjectName CN using same suffix match comparison.
1221#
1222# Suffix match here means that the host/domain name is compared one label
1223# at a time starting from the top-level domain and all the labels in
1224# domain_suffix_match shall be included in the certificate. The
1225# certificate may include additional sub-level labels in addition to the
1226# required labels.
1227#
Hai Shalom021b0b52019-04-10 11:17:58 -07001228# More than one match string can be provided by using semicolons to
1229# separate the strings (e.g., example.org;example.com). When multiple
1230# strings are specified, a match with any one of the values is considered
1231# a sufficient match for the certificate, i.e., the conditions are ORed
1232# together.
1233#
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001234# For example, domain_suffix_match=example.com would match
1235# test.example.com but would not match test-example.com.
Dmitry Shmidt2f74e362015-01-21 13:19:05 -08001236# domain_match: Constraint for server domain name
1237# If set, this FQDN is used as a full match requirement for the
1238# server certificate in SubjectAltName dNSName element(s). If a
1239# matching dNSName is found, this constraint is met. If no dNSName
1240# values are present, this constraint is matched against SubjectName CN
1241# using same full match comparison. This behavior is similar to
1242# domain_suffix_match, but has the requirement of a full match, i.e.,
1243# no subdomains or wildcard matches are allowed. Case-insensitive
1244# comparison is used, so "Example.com" matches "example.com", but would
1245# not match "test.Example.com".
Hai Shalom021b0b52019-04-10 11:17:58 -07001246#
1247# More than one match string can be provided by using semicolons to
1248# separate the strings (e.g., example.org;example.com). When multiple
1249# strings are specified, a match with any one of the values is considered
1250# a sufficient match for the certificate, i.e., the conditions are ORed
1251# together.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001252# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
1253# (string with field-value pairs, e.g., "peapver=0" or
1254# "peapver=1 peaplabel=1")
1255# 'peapver' can be used to force which PEAP version (0 or 1) is used.
1256# 'peaplabel=1' can be used to force new label, "client PEAP encryption",
1257# to be used during key derivation when PEAPv1 or newer. Most existing
1258# PEAPv1 implementation seem to be using the old label, "client EAP
1259# encryption", and wpa_supplicant is now using that as the default value.
1260# Some servers, e.g., Radiator, may require peaplabel=1 configuration to
1261# interoperate with PEAPv1; see eap_testing.txt for more details.
1262# 'peap_outer_success=0' can be used to terminate PEAP authentication on
1263# tunneled EAP-Success. This is required with some RADIUS servers that
1264# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
1265# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
1266# include_tls_length=1 can be used to force wpa_supplicant to include
1267# TLS Message Length field in all TLS messages even if they are not
1268# fragmented.
1269# sim_min_num_chal=3 can be used to configure EAP-SIM to require three
1270# challenges (by default, it accepts 2 or 3)
1271# result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
1272# protected result indication.
1273# 'crypto_binding' option can be used to control PEAPv0 cryptobinding
1274# behavior:
1275# * 0 = do not use cryptobinding (default)
1276# * 1 = use cryptobinding if server supports it
1277# * 2 = require cryptobinding
1278# EAP-WSC (WPS) uses following options: pin=<Device Password> or
1279# pbc=1.
Dmitry Shmidt216983b2015-02-06 10:50:36 -08001280#
1281# For wired IEEE 802.1X authentication, "allow_canned_success=1" can be
1282# used to configure a mode that allows EAP-Success (and EAP-Failure)
1283# without going through authentication step. Some switches use such
1284# sequence when forcing the port to be authorized/unauthorized or as a
1285# fallback option if the authentication server is unreachable. By default,
1286# wpa_supplicant discards such frames to protect against potential attacks
1287# by rogue devices, but this option can be used to disable that protection
1288# for cases where the server/authenticator does not need to be
1289# authenticated.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001290# phase2: Phase2 (inner authentication with TLS tunnel) parameters
1291# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
Dmitry Shmidt216983b2015-02-06 10:50:36 -08001292# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS). "mschapv2_retry=0" can be
1293# used to disable MSCHAPv2 password retry in authentication failure cases.
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001294#
1295# TLS-based methods can use the following parameters to control TLS behavior
1296# (these are normally in the phase1 parameter, but can be used also in the
1297# phase2 parameter when EAP-TLS is used within the inner tunnel):
1298# tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the
1299# TLS library, these may be disabled by default to enforce stronger
1300# security)
1301# tls_disable_time_checks=1 - ignore certificate validity time (this requests
1302# the TLS library to accept certificates even if they are not currently
1303# valid, i.e., have expired or have not yet become valid; this should be
1304# used only for testing purposes)
1305# tls_disable_session_ticket=1 - disable TLS Session Ticket extension
1306# tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used
1307# Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS
1308# as a workaround for broken authentication server implementations unless
Dmitry Shmidtaf9da312015-04-03 10:03:11 -07001309# EAP workarounds are disabled with eap_workaround=0.
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001310# For EAP-FAST, this must be set to 0 (or left unconfigured for the
1311# default value to be used automatically).
Dmitry Shmidtd80a4012015-11-05 16:35:40 -08001312# tls_disable_tlsv1_0=1 - disable use of TLSv1.0
Hai Shalom74f70d42019-02-11 14:42:39 -08001313# tls_disable_tlsv1_0=0 - explicitly enable use of TLSv1.0 (this allows
1314# systemwide TLS policies to be overridden)
Dmitry Shmidt13ca8d82014-02-20 10:18:40 -08001315# tls_disable_tlsv1_1=1 - disable use of TLSv1.1 (a workaround for AAA servers
1316# that have issues interoperating with updated TLS version)
Hai Shalom74f70d42019-02-11 14:42:39 -08001317# tls_disable_tlsv1_1=0 - explicitly enable use of TLSv1.1 (this allows
1318# systemwide TLS policies to be overridden)
Dmitry Shmidt13ca8d82014-02-20 10:18:40 -08001319# tls_disable_tlsv1_2=1 - disable use of TLSv1.2 (a workaround for AAA servers
1320# that have issues interoperating with updated TLS version)
Hai Shalom74f70d42019-02-11 14:42:39 -08001321# tls_disable_tlsv1_2=0 - explicitly enable use of TLSv1.2 (this allows
1322# systemwide TLS policies to be overridden)
Roshan Pius3a1667e2018-07-03 15:17:14 -07001323# tls_disable_tlsv1_3=1 - disable use of TLSv1.3 (a workaround for AAA servers
1324# that have issues interoperating with updated TLS version)
Hai Shalom74f70d42019-02-11 14:42:39 -08001325# tls_disable_tlsv1_3=0 - enable TLSv1.3 (experimental - disabled by default)
Dmitry Shmidt55840ad2015-12-14 12:45:46 -08001326# tls_ext_cert_check=0 - No external server certificate validation (default)
1327# tls_ext_cert_check=1 - External server certificate validation enabled; this
1328# requires an external program doing validation of server certificate
1329# chain when receiving CTRL-RSP-EXT_CERT_CHECK event from the control
1330# interface and report the result of the validation with
1331# CTRL-RSP_EXT_CERT_CHECK.
Dmitry Shmidtd2986c22017-10-23 14:22:09 -07001332# tls_suiteb=0 - do not apply Suite B 192-bit constraints on TLS (default)
1333# tls_suiteb=1 - apply Suite B 192-bit constraints on TLS; this is used in
1334# particular when using Suite B with RSA keys of >= 3K (3072) bits
Dmitry Shmidt61d9df32012-08-29 16:22:06 -07001335#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001336# Following certificate/private key fields are used in inner Phase2
1337# authentication when using EAP-TTLS or EAP-PEAP.
1338# ca_cert2: File path to CA certificate file. This file can have one or more
1339# trusted CA certificates. If ca_cert2 and ca_path2 are not included,
1340# server certificate will not be verified. This is insecure and a trusted
1341# CA certificate should always be configured.
1342# ca_path2: Directory path for CA certificate files (PEM)
1343# client_cert2: File path to client certificate file
1344# private_key2: File path to client private key file
1345# private_key2_passwd: Password for private key file
1346# dh_file2: File path to DH/DSA parameters file (in PEM format)
1347# subject_match2: Substring to be matched against the subject of the
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001348# authentication server certificate. See subject_match for more details.
1349# altsubject_match2: Semicolon separated string of entries to be matched
1350# against the alternative subject name of the authentication server
1351# certificate. See altsubject_match documentation for more details.
1352# domain_suffix_match2: Constraint for server domain name. See
1353# domain_suffix_match for more details.
Hai Shalomc3565922019-10-28 11:58:20 -07001354# ocsp2: See ocsp for more details.
1355#
1356# Separate machine credentials can be configured for EAP-TEAP Phase 2 with
1357# "machine_" prefix (e.g., "machine_identity") in the configuration parameters.
1358# See the parameters without that prefix for more details on the meaning and
1359# format of each such parameter.
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001360#
1361# fragment_size: Maximum EAP fragment size in bytes (default 1398).
1362# This value limits the fragment size for EAP methods that support
1363# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
1364# small enough to make the EAP messages fit in MTU of the network
1365# interface used for EAPOL. The default value is suitable for most
1366# cases.
1367#
Dmitry Shmidt34af3062013-07-11 10:46:32 -07001368# ocsp: Whether to use/require OCSP to check server certificate
1369# 0 = do not use OCSP stapling (TLS certificate status extension)
1370# 1 = try to use OCSP stapling, but not require response
1371# 2 = require valid OCSP stapling response
Dmitry Shmidt014a3ff2015-12-28 13:27:49 -08001372# 3 = require valid OCSP stapling response for all not-trusted
1373# certificates in the server certificate chain
Dmitry Shmidt34af3062013-07-11 10:46:32 -07001374#
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -08001375# openssl_ciphers: OpenSSL specific cipher configuration
1376# This can be used to override the global openssl_ciphers configuration
1377# parameter (see above).
1378#
1379# erp: Whether EAP Re-authentication Protocol (ERP) is enabled
1380#
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001381# EAP-FAST variables:
1382# pac_file: File path for the PAC entries. wpa_supplicant will need to be able
1383# to create this file and write updates to it when PAC is being
1384# provisioned or refreshed. Full path to the file should be used since
1385# working directory may change when wpa_supplicant is run in the
1386# background. Alternatively, a named configuration blob can be used by
1387# setting this to blob://<blob name>
1388# phase1: fast_provisioning option can be used to enable in-line provisioning
1389# of EAP-FAST credentials (PAC):
1390# 0 = disabled,
1391# 1 = allow unauthenticated provisioning,
1392# 2 = allow authenticated provisioning,
1393# 3 = allow both unauthenticated and authenticated provisioning
1394# fast_max_pac_list_len=<num> option can be used to set the maximum
1395# number of PAC entries to store in a PAC list (default: 10)
1396# fast_pac_format=binary option can be used to select binary format for
1397# storing PAC entries in order to save some space (the default
1398# text format uses about 2.5 times the size of minimal binary
1399# format)
1400#
1401# wpa_supplicant supports number of "EAP workarounds" to work around
1402# interoperability issues with incorrectly behaving authentication servers.
1403# These are enabled by default because some of the issues are present in large
1404# number of authentication servers. Strict EAP conformance mode can be
1405# configured by disabling workarounds with eap_workaround=0.
1406
Dmitry Shmidtde47be72016-01-07 12:52:55 -08001407# update_identifier: PPS MO ID
1408# (Hotspot 2.0 PerProviderSubscription/UpdateIdentifier)
Roshan Pius3a1667e2018-07-03 15:17:14 -07001409#
1410# roaming_consortium_selection: Roaming Consortium Selection
1411# The matching Roaming Consortium OI that was used to generate this
1412# network profile.
Dmitry Shmidtde47be72016-01-07 12:52:55 -08001413
Dmitry Shmidt04949592012-07-19 12:16:46 -07001414# Station inactivity limit
1415#
1416# If a station does not send anything in ap_max_inactivity seconds, an
1417# empty data frame is sent to it in order to verify whether it is
1418# still in range. If this frame is not ACKed, the station will be
1419# disassociated and then deauthenticated. This feature is used to
1420# clear station table of old entries when the STAs move out of the
1421# range.
1422#
1423# The station can associate again with the AP if it is still in range;
1424# this inactivity poll is just used as a nicer way of verifying
1425# inactivity; i.e., client will not report broken connection because
1426# disassociation frame is not sent immediately without first polling
1427# the STA with a data frame.
1428# default: 300 (i.e., 5 minutes)
1429#ap_max_inactivity=300
1430
1431# DTIM period in Beacon intervals for AP mode (default: 2)
1432#dtim_period=2
1433
Dmitry Shmidt7a5e50a2013-03-05 12:37:16 -08001434# Beacon interval (default: 100 TU)
1435#beacon_int=100
1436
Dmitry Shmidt849734c2016-05-27 09:59:01 -07001437# WPS in AP mode
1438# 0 = WPS enabled and configured (default)
1439# 1 = WPS disabled
1440#wps_disabled=0
1441
Dmitry Shmidtd2986c22017-10-23 14:22:09 -07001442# FILS DH Group
1443# 0 = PFS disabled with FILS shared key authentication (default)
1444# 1-65535 = DH Group to use for FILS PFS
1445#fils_dh_group=0
1446
Dmitry Shmidt661b4f72014-09-29 14:58:27 -07001447# MAC address policy
1448# 0 = use permanent MAC address
1449# 1 = use random MAC address for each ESS connection
1450# 2 = like 1, but maintain OUI (with local admin bit set)
1451#mac_addr=0
1452
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001453# disable_ht: Whether HT (802.11n) should be disabled.
1454# 0 = HT enabled (if AP supports it)
1455# 1 = HT disabled
1456#
1457# disable_ht40: Whether HT-40 (802.11n) should be disabled.
1458# 0 = HT-40 enabled (if AP supports it)
1459# 1 = HT-40 disabled
1460#
1461# disable_sgi: Whether SGI (short guard interval) should be disabled.
1462# 0 = SGI enabled (if AP supports it)
1463# 1 = SGI disabled
1464#
Dmitry Shmidtdf5a7e42014-04-02 12:59:59 -07001465# disable_ldpc: Whether LDPC should be disabled.
1466# 0 = LDPC enabled (if AP supports it)
1467# 1 = LDPC disabled
1468#
Dmitry Shmidt61593f02014-04-21 16:27:35 -07001469# ht40_intolerant: Whether 40 MHz intolerant should be indicated.
1470# 0 = 40 MHz tolerant (default)
1471# 1 = 40 MHz intolerant
1472#
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001473# ht_mcs: Configure allowed MCS rates.
1474# Parsed as an array of bytes, in base-16 (ascii-hex)
1475# ht_mcs="" // Use all available (default)
1476# ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only
1477# ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only
1478#
1479# disable_max_amsdu: Whether MAX_AMSDU should be disabled.
1480# -1 = Do not make any changes.
1481# 0 = Enable MAX-AMSDU if hardware supports it.
1482# 1 = Disable AMSDU
1483#
Dmitry Shmidt7dba0e52014-04-14 10:49:15 -07001484# ampdu_factor: Maximum A-MPDU Length Exponent
1485# Value: 0-3, see 7.3.2.56.3 in IEEE Std 802.11n-2009.
1486#
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001487# ampdu_density: Allow overriding AMPDU density configuration.
1488# Treated as hint by the kernel.
1489# -1 = Do not make any changes.
1490# 0-3 = Set AMPDU density (aka factor) to specified value.
Hai Shalom74f70d42019-02-11 14:42:39 -08001491#
1492# tx_stbc: Allow overriding STBC support for TX streams
1493# Value: 0-1, see IEEE Std 802.11-2016, 9.4.2.56.2.
1494# -1 = Do not make any changes (default)
1495# 0 = Set if not supported
1496# 1 = Set if supported
1497#
1498# rx_stbc: Allow overriding STBC support for RX streams
1499# Value: 0-3, see IEEE Std 802.11-2016, 9.4.2.56.2.
1500# -1 = Do not make any changes (default)
1501# 0 = Set if not supported
1502# 1 = Set for support of one spatial stream
1503# 2 = Set for support of one and two spatial streams
1504# 3 = Set for support of one, two and three spatial streams
Dmitry Shmidta54fa5f2013-01-15 13:53:35 -08001505
Dmitry Shmidt2f023192013-03-12 12:44:17 -07001506# disable_vht: Whether VHT should be disabled.
1507# 0 = VHT enabled (if AP supports it)
1508# 1 = VHT disabled
1509#
1510# vht_capa: VHT capabilities to set in the override
1511# vht_capa_mask: mask of VHT capabilities
1512#
1513# vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8
1514# vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8
1515# 0: MCS 0-7
1516# 1: MCS 0-8
1517# 2: MCS 0-9
1518# 3: not supported
1519
Hai Shalom74f70d42019-02-11 14:42:39 -08001520# multi_ap_backhaul_sta: Multi-AP backhaul STA functionality
1521# 0 = normal STA (default)
1522# 1 = backhaul STA
1523# A backhaul STA sends the Multi-AP IE, fails to associate if the AP does not
1524# support Multi-AP, and sets 4-address mode if it does. Thus, the netdev can be
1525# added to a bridge to allow forwarding frames over this backhaul link.
1526
Dmitry Shmidtd80a4012015-11-05 16:35:40 -08001527##### Fast Session Transfer (FST) support #####################################
1528#
1529# The options in this section are only available when the build configuration
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001530# option CONFIG_FST is set while compiling wpa_supplicant. They allow this
1531# interface to be a part of FST setup.
Dmitry Shmidtd80a4012015-11-05 16:35:40 -08001532#
1533# FST is the transfer of a session from a channel to another channel, in the
1534# same or different frequency bands.
1535#
Dmitry Shmidtaca489e2016-09-28 15:44:14 -07001536# For details, see IEEE Std 802.11ad-2012.
Dmitry Shmidtd80a4012015-11-05 16:35:40 -08001537
1538# Identifier of an FST Group the interface belongs to.
1539#fst_group_id=bond0
1540
1541# Interface priority within the FST Group.
1542# Announcing a higher priority for an interface means declaring it more
1543# preferable for FST switch.
1544# fst_priority is in 1..255 range with 1 being the lowest priority.
1545#fst_priority=100
1546
1547# Default LLT value for this interface in milliseconds. The value used in case
1548# no value provided during session setup. Default is 50 msec.
1549# fst_llt is in 1..4294967 range (due to spec limitation, see 10.32.2.2
1550# Transitioning between states).
1551#fst_llt=100
1552
Hai Shalom81f62d82019-07-22 12:10:00 -07001553# BSS Transition Management
1554# disable_btm - Disable BSS transition management in STA
1555# Set to 0 to enable BSS transition management (default behavior)
1556# Set to 1 to disable BSS transition management
1557#disable_btm=0
1558
Hai Shalomc3565922019-10-28 11:58:20 -07001559# Enable EDMG capability in STA/AP mode, default value is false
1560#enable_edmg=1
1561
1562# This value is used to configure the channel bonding feature.
1563# Default value is 0.
1564# Relevant only if enable_edmg is true
1565# In AP mode it defines the EDMG channel to use for AP operation.
1566# In STA mode it defines the EDMG channel for connection (if supported by AP).
1567#edmg_channel=9
1568
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001569# Example blocks:
1570
1571# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
1572network={
1573 ssid="simple"
1574 psk="very secret passphrase"
1575 priority=5
1576}
1577
1578# Same as previous, but request SSID-specific scanning (for APs that reject
1579# broadcast SSID)
1580network={
1581 ssid="second ssid"
1582 scan_ssid=1
1583 psk="very secret passphrase"
1584 priority=2
1585}
1586
1587# Only WPA-PSK is used. Any valid cipher combination is accepted.
1588network={
1589 ssid="example"
1590 proto=WPA
1591 key_mgmt=WPA-PSK
1592 pairwise=CCMP TKIP
1593 group=CCMP TKIP WEP104 WEP40
1594 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1595 priority=2
1596}
1597
1598# WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
1599network={
1600 ssid="example"
1601 proto=WPA
1602 key_mgmt=WPA-PSK
1603 pairwise=TKIP
1604 group=TKIP
1605 psk="not so secure passphrase"
1606 wpa_ptk_rekey=600
1607}
1608
1609# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
1610# or WEP40 as the group cipher will not be accepted.
1611network={
1612 ssid="example"
1613 proto=RSN
1614 key_mgmt=WPA-EAP
1615 pairwise=CCMP TKIP
1616 group=CCMP TKIP
1617 eap=TLS
1618 identity="user@example.com"
1619 ca_cert="/etc/cert/ca.pem"
1620 client_cert="/etc/cert/user.pem"
1621 private_key="/etc/cert/user.prv"
1622 private_key_passwd="password"
1623 priority=1
1624}
1625
1626# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
1627# (e.g., Radiator)
1628network={
1629 ssid="example"
1630 key_mgmt=WPA-EAP
1631 eap=PEAP
1632 identity="user@example.com"
1633 password="foobar"
1634 ca_cert="/etc/cert/ca.pem"
1635 phase1="peaplabel=1"
1636 phase2="auth=MSCHAPV2"
1637 priority=10
1638}
1639
1640# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
1641# unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
1642network={
1643 ssid="example"
1644 key_mgmt=WPA-EAP
1645 eap=TTLS
1646 identity="user@example.com"
1647 anonymous_identity="anonymous@example.com"
1648 password="foobar"
1649 ca_cert="/etc/cert/ca.pem"
1650 priority=2
1651}
1652
1653# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
1654# use. Real identity is sent only within an encrypted TLS tunnel.
1655network={
1656 ssid="example"
1657 key_mgmt=WPA-EAP
1658 eap=TTLS
1659 identity="user@example.com"
1660 anonymous_identity="anonymous@example.com"
1661 password="foobar"
1662 ca_cert="/etc/cert/ca.pem"
1663 phase2="auth=MSCHAPV2"
1664}
1665
1666# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
1667# authentication.
1668network={
1669 ssid="example"
1670 key_mgmt=WPA-EAP
1671 eap=TTLS
1672 # Phase1 / outer authentication
1673 anonymous_identity="anonymous@example.com"
1674 ca_cert="/etc/cert/ca.pem"
1675 # Phase 2 / inner authentication
1676 phase2="autheap=TLS"
1677 ca_cert2="/etc/cert/ca2.pem"
1678 client_cert2="/etc/cer/user.pem"
1679 private_key2="/etc/cer/user.prv"
1680 private_key2_passwd="password"
1681 priority=2
1682}
1683
1684# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
1685# group cipher.
1686network={
1687 ssid="example"
1688 bssid=00:11:22:33:44:55
1689 proto=WPA RSN
1690 key_mgmt=WPA-PSK WPA-EAP
1691 pairwise=CCMP
1692 group=CCMP
1693 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1694}
1695
1696# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
1697# and all valid ciphers.
1698network={
1699 ssid=00010203
1700 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
1701}
1702
1703
1704# EAP-SIM with a GSM SIM or USIM
1705network={
1706 ssid="eap-sim-test"
1707 key_mgmt=WPA-EAP
1708 eap=SIM
1709 pin="1234"
1710 pcsc=""
1711}
1712
1713
1714# EAP-PSK
1715network={
1716 ssid="eap-psk-test"
1717 key_mgmt=WPA-EAP
1718 eap=PSK
1719 anonymous_identity="eap_psk_user"
1720 password=06b4be19da289f475aa46a33cb793029
1721 identity="eap_psk_user@example.com"
1722}
1723
1724
1725# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
1726# EAP-TLS for authentication and key generation; require both unicast and
1727# broadcast WEP keys.
1728network={
1729 ssid="1x-test"
1730 key_mgmt=IEEE8021X
1731 eap=TLS
1732 identity="user@example.com"
1733 ca_cert="/etc/cert/ca.pem"
1734 client_cert="/etc/cert/user.pem"
1735 private_key="/etc/cert/user.prv"
1736 private_key_passwd="password"
1737 eapol_flags=3
1738}
1739
1740
1741# LEAP with dynamic WEP keys
1742network={
1743 ssid="leap-example"
1744 key_mgmt=IEEE8021X
1745 eap=LEAP
1746 identity="user"
1747 password="foobar"
1748}
1749
1750# EAP-IKEv2 using shared secrets for both server and peer authentication
1751network={
1752 ssid="ikev2-example"
1753 key_mgmt=WPA-EAP
1754 eap=IKEV2
1755 identity="user"
1756 password="foobar"
1757}
1758
1759# EAP-FAST with WPA (WPA or WPA2)
1760network={
1761 ssid="eap-fast-test"
1762 key_mgmt=WPA-EAP
1763 eap=FAST
1764 anonymous_identity="FAST-000102030405"
1765 identity="username"
1766 password="password"
1767 phase1="fast_provisioning=1"
1768 pac_file="/etc/wpa_supplicant.eap-fast-pac"
1769}
1770
1771network={
1772 ssid="eap-fast-test"
1773 key_mgmt=WPA-EAP
1774 eap=FAST
1775 anonymous_identity="FAST-000102030405"
1776 identity="username"
1777 password="password"
1778 phase1="fast_provisioning=1"
1779 pac_file="blob://eap-fast-pac"
1780}
1781
1782# Plaintext connection (no WPA, no IEEE 802.1X)
1783network={
1784 ssid="plaintext-test"
1785 key_mgmt=NONE
1786}
1787
1788
1789# Shared WEP key connection (no WPA, no IEEE 802.1X)
1790network={
1791 ssid="static-wep-test"
1792 key_mgmt=NONE
1793 wep_key0="abcde"
1794 wep_key1=0102030405
1795 wep_key2="1234567890123"
1796 wep_tx_keyidx=0
1797 priority=5
1798}
1799
1800
1801# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
1802# IEEE 802.11 authentication
1803network={
1804 ssid="static-wep-test2"
1805 key_mgmt=NONE
1806 wep_key0="abcde"
1807 wep_key1=0102030405
1808 wep_key2="1234567890123"
1809 wep_tx_keyidx=0
1810 priority=5
1811 auth_alg=SHARED
1812}
1813
1814
Dmitry Shmidtfb79edc2014-01-10 10:45:54 -08001815# IBSS/ad-hoc network with RSN
1816network={
1817 ssid="ibss-rsn"
1818 key_mgmt=WPA-PSK
1819 proto=RSN
1820 psk="12345678"
1821 mode=1
1822 frequency=2412
1823 pairwise=CCMP
1824 group=CCMP
1825}
1826
1827# IBSS/ad-hoc network with WPA-None/TKIP (deprecated)
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001828network={
1829 ssid="test adhoc"
1830 mode=1
1831 frequency=2412
1832 proto=WPA
1833 key_mgmt=WPA-NONE
1834 pairwise=NONE
1835 group=TKIP
1836 psk="secret passphrase"
1837}
1838
Dmitry Shmidt6c0da2b2015-01-05 13:08:17 -08001839# open mesh network
1840network={
1841 ssid="test mesh"
1842 mode=5
1843 frequency=2437
1844 key_mgmt=NONE
1845}
1846
1847# secure (SAE + AMPE) network
1848network={
1849 ssid="secure mesh"
1850 mode=5
1851 frequency=2437
1852 key_mgmt=SAE
1853 psk="very secret passphrase"
1854}
1855
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001856
1857# Catch all example that allows more or less all configuration modes
1858network={
1859 ssid="example"
1860 scan_ssid=1
1861 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
1862 pairwise=CCMP TKIP
1863 group=CCMP TKIP WEP104 WEP40
1864 psk="very secret passphrase"
1865 eap=TTLS PEAP TLS
1866 identity="user@example.com"
1867 password="foobar"
1868 ca_cert="/etc/cert/ca.pem"
1869 client_cert="/etc/cert/user.pem"
1870 private_key="/etc/cert/user.prv"
1871 private_key_passwd="password"
1872 phase1="peaplabel=0"
1873}
1874
1875# Example of EAP-TLS with smartcard (openssl engine)
1876network={
1877 ssid="example"
1878 key_mgmt=WPA-EAP
1879 eap=TLS
1880 proto=RSN
1881 pairwise=CCMP TKIP
1882 group=CCMP TKIP
1883 identity="user@example.com"
1884 ca_cert="/etc/cert/ca.pem"
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001885
Dmitry Shmidtd5ab1b52016-06-21 12:38:41 -07001886 # Certificate and/or key identified by PKCS#11 URI (RFC7512)
1887 client_cert="pkcs11:manufacturer=piv_II;id=%01"
1888 private_key="pkcs11:manufacturer=piv_II;id=%01"
Dmitry Shmidt30f94812012-02-21 17:02:48 -08001889
1890 # Optional PIN configuration; this can be left out and PIN will be
1891 # asked through the control interface
1892 pin="1234"
1893}
1894
1895# Example configuration showing how to use an inlined blob as a CA certificate
1896# data instead of using external file
1897network={
1898 ssid="example"
1899 key_mgmt=WPA-EAP
1900 eap=TTLS
1901 identity="user@example.com"
1902 anonymous_identity="anonymous@example.com"
1903 password="foobar"
1904 ca_cert="blob://exampleblob"
1905 priority=20
1906}
1907
1908blob-base64-exampleblob={
1909SGVsbG8gV29ybGQhCg==
1910}
1911
1912
1913# Wildcard match for SSID (plaintext APs only). This example select any
1914# open AP regardless of its SSID.
1915network={
1916 key_mgmt=NONE
1917}
Dmitry Shmidt51b6ea82013-05-08 10:42:09 -07001918
Dmitry Shmidtff787d52015-01-12 13:01:47 -08001919# Example configuration blacklisting two APs - these will be ignored
1920# for this network.
1921network={
1922 ssid="example"
1923 psk="very secret passphrase"
1924 bssid_blacklist=02:11:22:33:44:55 02:22:aa:44:55:66
1925}
1926
1927# Example configuration limiting AP selection to a specific set of APs;
1928# any other AP not matching the masked address will be ignored.
1929network={
1930 ssid="example"
1931 psk="very secret passphrase"
1932 bssid_whitelist=02:55:ae:bc:00:00/ff:ff:ff:ff:00:00 00:00:77:66:55:44/00:00:ff:ff:ff:ff
1933}
Dmitry Shmidt51b6ea82013-05-08 10:42:09 -07001934
1935# Example config file that will only scan on channel 36.
1936freq_list=5180
1937network={
1938 key_mgmt=NONE
1939}
Dmitry Shmidt5a1480c2014-05-12 09:46:02 -07001940
1941
Roshan Pius3a1667e2018-07-03 15:17:14 -07001942# Example configuration using EAP-TTLS for authentication and key
1943# generation for MACsec
1944network={
1945 key_mgmt=IEEE8021X
1946 eap=TTLS
1947 phase2="auth=PAP"
1948 anonymous_identity="anonymous@example.com"
1949 identity="user@example.com"
1950 password="secretr"
1951 ca_cert="/etc/cert/ca.pem"
1952 eapol_flags=0
1953 macsec_policy=1
1954}
1955
1956# Example configuration for MACsec with preshared key
1957network={
1958 key_mgmt=NONE
1959 eapol_flags=0
1960 macsec_policy=1
1961 mka_cak=0123456789ABCDEF0123456789ABCDEF
1962 mka_ckn=6162636465666768696A6B6C6D6E6F707172737475767778797A303132333435
1963 mka_priority=128
1964}