1 ##### Example wpa_supplicant configuration file ###############################
3 # This file describes configuration file format and lists all available option.
4 # Please also take a look at simpler configuration examples in 'examples'
7 # Empty lines and lines starting with # are ignored
9 # NOTE! This file may contain password information and should probably be made
10 # readable only by root user on multiuser systems.
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.
16 # Whether to allow wpa_supplicant to update (overwrite) configuration
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
26 # global configuration (shared by all network blocks)
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
31 # interface mechanism is used. For all cases, the existence of this parameter
32 # in configuration is used to determine whether the control interface is
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
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.
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.
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)
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)
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.
75 ctrl_interface=/var/run/wpa_supplicant
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
84 # Note: When using MACsec, eapol_version shall be set to 3, which is
85 # defined in IEEE Std 802.1X-2010.
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
101 # also be used when using wired Ethernet drivers.
102 # Note: macsec_qca driver is one type of Ethernet driver which implements
104 # 2: like 0, but associate with APs using security policy and SSID (but not
105 # BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
106 # enable operation with hidden SSIDs and optimized roaming; in this mode,
107 # the network blocks in the configuration file are tried one by one until
108 # the driver reports successful association; each network block should have
109 # explicit security policy (i.e., only one option in the lists) for
110 # key_mgmt, pairwise, group, proto variables
111 # Note: ap_scan=2 should not be used with the nl80211 driver interface (the
112 # current Linux interface). ap_scan=1 is optimized work working with nl80211.
113 # For finding networks using hidden SSID, scan_ssid=1 in the network block can
114 # be used with nl80211.
115 # When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
116 # created immediately regardless of scan results. ap_scan=1 mode will first try
117 # to scan for existing networks and only if no matches with the enabled
118 # networks are found, a new IBSS or AP mode network is created.
121 # Whether to force passive scan for network connection
123 # By default, scans will send out Probe Request frames on channels that allow
124 # active scanning. This advertise the local station to the world. Normally this
125 # is fine, but users may wish to do passive scanning where the radio should only
126 # listen quietly for Beacon frames and not send any Probe Request frames. Actual
127 # functionality may be driver dependent.
129 # This parameter can be used to force only passive scanning to be used
130 # for network connection cases. It should be noted that this will slow
131 # down scan operations and reduce likelihood of finding the AP. In
132 # addition, some use cases will override this due to functional
133 # requirements, e.g., for finding an AP that uses hidden SSID
134 # (scan_ssid=1) or P2P device discovery.
136 # 0: Do normal scans (allow active scans) (default)
137 # 1: Do passive scans.
141 # By default, wpa_supplicant implements the mesh peering manager (MPM) for an
142 # open mesh. However, if the driver can implement the MPM, you may set this to
143 # 0 to use the driver version. When AMPE is enabled, the wpa_supplicant MPM is
145 # 0: MPM lives in the driver
146 # 1: wpa_supplicant provides an MPM which handles peering (default)
149 # Maximum number of peer links (0-255; default: 99)
150 # Maximum number of mesh peering currently maintained by the STA.
153 # Timeout in seconds to detect STA inactivity (default: 300 seconds)
155 # This timeout value is used in mesh STA to clean up inactive stations.
156 #mesh_max_inactivity=300
158 # cert_in_cb - Whether to include a peer certificate dump in events
159 # This controls whether peer certificates for authentication server and
160 # its certificate chain are included in EAP peer certificate events. This is
161 # enabled by default.
164 # EAP fast re-authentication
165 # By default, fast re-authentication is enabled for all EAP methods that
166 # support it. This variable can be used to disable fast re-authentication.
167 # Normally, there is no need to disable this.
170 # OpenSSL Engine support
171 # These options can be used to load OpenSSL engines.
172 # The two engines that are supported currently are shown below:
173 # They are both from the opensc project (http://www.opensc.org/)
174 # By default no engines are loaded.
175 # make the opensc engine available
176 #opensc_engine_path=/usr/lib/opensc/engine_opensc.so
177 # make the pkcs11 engine available
178 #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
179 # configure the path to the pkcs11 module required by the pkcs11 engine
180 #pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
182 # OpenSSL cipher string
184 # This is an OpenSSL specific configuration option for configuring the default
185 # ciphers. If not set, "DEFAULT:!EXP:!LOW" is used as the default.
186 # See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation
187 # on cipher suite configuration. This is applicable only if wpa_supplicant is
188 # built to use OpenSSL.
189 #openssl_ciphers=DEFAULT:!EXP:!LOW
192 # Dynamic EAP methods
193 # If EAP methods were built dynamically as shared object files, they need to be
194 # loaded here before being used in the network blocks. By default, EAP methods
195 # are included statically in the build, so these lines are not needed
196 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
197 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
199 # Driver interface parameters
200 # This field can be used to configure arbitrary driver interace parameters. The
201 # format is specific to the selected driver interface. This field is not used
203 #driver_param="field=value"
206 # The ISO/IEC alpha2 country code for the country in which this device is
207 # currently operating.
210 # Maximum lifetime for PMKSA in seconds; default 43200
211 #dot11RSNAConfigPMKLifetime=43200
212 # Threshold for reauthentication (percentage of PMK lifetime); default 70
213 #dot11RSNAConfigPMKReauthThreshold=70
214 # Timeout for security association negotiation in seconds; default 60
215 #dot11RSNAConfigSATimeout=60
217 # Wi-Fi Protected Setup (WPS) parameters
219 # Universally Unique IDentifier (UUID; see RFC 4122) of the device
220 # If not configured, UUID will be generated based on the local MAC address.
221 #uuid=12345678-9abc-def0-1234-56789abcdef0
224 # User-friendly description of device; up to 32 octets encoded in UTF-8
225 #device_name=Wireless Client
228 # The manufacturer of the device (up to 64 ASCII characters)
229 #manufacturer=Company
232 # Model of the device (up to 32 ASCII characters)
236 # Additional device description (up to 32 ASCII characters)
240 # Serial number of the device (up to 32 characters)
243 # Primary Device Type
244 # Used format: <categ>-<OUI>-<subcateg>
245 # categ = Category as an integer value
246 # OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
248 # subcateg = OUI-specific Sub Category as an integer value
250 # 1-0050F204-1 (Computer / PC)
251 # 1-0050F204-2 (Computer / Server)
252 # 5-0050F204-1 (Storage / NAS)
253 # 6-0050F204-1 (Network Infrastructure / AP)
254 #device_type=1-0050F204-1
257 # 4-octet operating system version number (hex string)
261 # List of the supported configuration methods
262 # Available methods: usba ethernet label display ext_nfc_token int_nfc_token
263 # nfc_interface push_button keypad virtual_display physical_display
264 # virtual_push_button physical_push_button
266 #config_methods=label display push_button keypad
268 #config_methods=label virtual_display virtual_push_button keypad
270 # Credential processing
271 # 0 = process received credentials internally (default)
272 # 1 = do not process received credentials; just pass them over ctrl_iface to
273 # external program(s)
274 # 2 = process received credentials internally and pass them over ctrl_iface
275 # to external program(s)
276 #wps_cred_processing=0
278 # Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing
279 # The vendor attribute contents to be added in M1 (hex string)
280 #wps_vendor_ext_m1=000137100100020001
282 # NFC password token for WPS
283 # These parameters can be used to configure a fixed NFC password token for the
284 # station. This can be generated, e.g., with nfc_pw_token. When these
285 # parameters are used, the station is assumed to be deployed with a NFC tag
286 # that includes the matching NFC password token (e.g., written based on the
287 # NDEF record from nfc_pw_token).
289 #wps_nfc_dev_pw_id: Device Password ID (16..65535)
290 #wps_nfc_dh_pubkey: Hexdump of DH Public Key
291 #wps_nfc_dh_privkey: Hexdump of DH Private Key
292 #wps_nfc_dev_pw: Hexdump of Device Password
294 # Priority for the networks added through WPS
295 # This priority value will be set to each network profile that is added
296 # by executing the WPS protocol.
299 # Maximum number of BSS entries to keep in memory
301 # This can be used to limit memory use on the BSS entries (cached scan
302 # results). A larger value may be needed in environments that have huge number
303 # of APs when using ap_scan=1 mode.
307 # This is an optional set of parameters for automatic scanning
308 # within an interface in following format:
309 #autoscan=<autoscan module name>:<module parameters>
310 # autoscan is like bgscan but on disconnected or inactive state.
311 # For instance, on exponential module parameters would be <base>:<limit>
312 #autoscan=exponential:3:300
313 # Which means a delay between scans on a base exponential of 3,
314 # up to the limit of 300 seconds (3, 9, 27 ... 300)
315 # For periodic module, parameters would be <fixed interval>
316 #autoscan=periodic:30
317 # So a delay of 30 seconds will be applied between each scan
319 # filter_ssids - SSID-based scan result filtering
320 # 0 = do not filter scan results (default)
321 # 1 = only include configured SSIDs in scan results/BSS table
324 # Password (and passphrase, etc.) backend for external storage
325 # format: <backend name>[:<optional backend parameters>]
326 #ext_password_backend=test:pw1=password|pw2=testing
329 # Disable P2P functionality
332 # Timeout in seconds to detect STA inactivity (default: 300 seconds)
334 # This timeout value is used in P2P GO mode to clean up
336 #p2p_go_max_inactivity=300
338 # Passphrase length (8..63) for P2P GO
340 # This parameter controls the length of the random passphrase that is
341 # generated at the GO. Default: 8.
342 #p2p_passphrase_len=8
344 # Extra delay between concurrent P2P search iterations
346 # This value adds extra delay in milliseconds between concurrent search
347 # iterations to make p2p_find friendlier to concurrent operations by avoiding
348 # it from taking 100% of radio resources. The default value is 500 ms.
349 #p2p_search_delay=500
351 # Opportunistic Key Caching (also known as Proactive Key Caching) default
352 # This parameter can be used to set the default behavior for the
353 # proactive_key_caching parameter. By default, OKC is disabled unless enabled
354 # with the global okc=1 parameter or with the per-network
355 # proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but
356 # can be disabled with per-network proactive_key_caching=0 parameter.
359 # Protected Management Frames default
360 # This parameter can be used to set the default behavior for the ieee80211w
361 # parameter. By default, PMF is disabled unless enabled with the global pmf=1/2
362 # parameter or with the per-network ieee80211w=1/2 parameter. With pmf=1/2, PMF
363 # is enabled/required by default, but can be disabled with the per-network
364 # ieee80211w parameter.
367 # Enabled SAE finite cyclic groups in preference order
368 # By default (if this parameter is not set), the mandatory group 19 (ECC group
369 # defined over a 256-bit prime order field) is preferred, but other groups are
370 # also enabled. If this parameter is set, the groups will be tried in the
371 # indicated order. The group values are listed in the IANA registry:
372 # http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
373 #sae_groups=21 20 19 26 25
375 # Default value for DTIM period (if not overridden in network block)
378 # Default value for Beacon interval (if not overridden in network block)
381 # Additional vendor specific elements for Beacon and Probe Response frames
382 # This parameter can be used to add additional vendor specific element(s) into
383 # the end of the Beacon and Probe Response frames. The format for these
384 # element(s) is a hexdump of the raw information elements (id+len+payload for
385 # one or more elements). This is used in AP and P2P GO modes.
386 #ap_vendor_elements=dd0411223301
388 # Ignore scan results older than request
390 # The driver may have a cache of scan results that makes it return
391 # information that is older than our scan trigger. This parameter can
392 # be used to configure such old information to be ignored instead of
393 # allowing it to update the internal BSS table.
394 #ignore_old_scan_res=0
396 # scan_cur_freq: Whether to scan only the current frequency
397 # 0: Scan all available frequencies. (Default)
398 # 1: Scan current operating frequency if another VIF on the same radio
399 # is already associated.
401 # MAC address policy default
402 # 0 = use permanent MAC address
403 # 1 = use random MAC address for each ESS connection
404 # 2 = like 1, but maintain OUI (with local admin bit set)
406 # By default, permanent MAC address is used unless policy is changed by
407 # the per-network mac_addr parameter. Global mac_addr=1 can be used to
408 # change this default behavior.
411 # Lifetime of random MAC address in seconds (default: 60)
412 #rand_addr_lifetime=60
414 # MAC address policy for pre-association operations (scanning, ANQP)
415 # 0 = use permanent MAC address
416 # 1 = use random MAC address
417 # 2 = like 1, but maintain OUI (with local admin bit set)
420 # Interworking (IEEE 802.11u)
422 # Enable Interworking
425 # Homogenous ESS identifier
426 # If this is set, scans will be used to request response only from BSSes
427 # belonging to the specified Homogeneous ESS. This is used only if interworking
429 # hessid=00:11:22:33:44:55
431 # Automatic network selection behavior
432 # 0 = do not automatically go through Interworking network selection
433 # (i.e., require explicit interworking_select command for this; default)
434 # 1 = perform Interworking network selection if one or more
435 # credentials have been configured and scan did not find a
436 # matching network block
441 # Each credential used for automatic network selection is configured as a set
442 # of parameters that are compared to the information advertised by the APs when
443 # interworking_select and interworking_connect commands are used.
447 # temporary: Whether this credential is temporary and not to be saved
449 # priority: Priority group
450 # By default, all networks and credentials get the same priority group
451 # (0). This field can be used to give higher priority for credentials
452 # (and similarly in struct wpa_ssid for network blocks) to change the
453 # Interworking automatic networking selection behavior. The matching
454 # network (based on either an enabled network block or a credential)
455 # with the highest priority value will be selected.
457 # pcsc: Use PC/SC and SIM/USIM card
459 # realm: Home Realm for Interworking
461 # username: Username for Interworking network selection
463 # password: Password for Interworking network selection
465 # ca_cert: CA certificate for Interworking network selection
467 # client_cert: File path to client certificate file (PEM/DER)
468 # This field is used with Interworking networking selection for a case
469 # where client certificate/private key is used for authentication
470 # (EAP-TLS). Full path to the file should be used since working
471 # directory may change when wpa_supplicant is run in the background.
473 # Alternatively, a named configuration blob can be used by setting
474 # this to blob://blob_name.
476 # private_key: File path to client private key file (PEM/DER/PFX)
477 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
478 # commented out. Both the private key and certificate will be read
479 # from the PKCS#12 file in this case. Full path to the file should be
480 # used since working directory may change when wpa_supplicant is run
483 # Windows certificate store can be used by leaving client_cert out and
484 # configuring private_key in one of the following formats:
486 # cert://substring_to_match
488 # hash://certificate_thumbprint_in_hex
490 # For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
492 # Note that when running wpa_supplicant as an application, the user
493 # certificate store (My user account) is used, whereas computer store
494 # (Computer account) is used when running wpasvc as a service.
496 # Alternatively, a named configuration blob can be used by setting
497 # this to blob://blob_name.
499 # private_key_passwd: Password for private key file
501 # imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format
503 # milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN>
506 # domain: Home service provider FQDN(s)
507 # This is used to compare against the Domain Name List to figure out
508 # whether the AP is operated by the Home SP. Multiple domain entries can
509 # be used to configure alternative FQDNs that will be considered home
512 # roaming_consortium: Roaming Consortium OI
513 # If roaming_consortium_len is non-zero, this field contains the
514 # Roaming Consortium OI that can be used to determine which access
515 # points support authentication with this credential. This is an
516 # alternative to the use of the realm parameter. When using Roaming
517 # Consortium to match the network, the EAP parameters need to be
518 # pre-configured with the credential since the NAI Realm information
519 # may not be available or fetched.
521 # eap: Pre-configured EAP method
522 # This optional field can be used to specify which EAP method will be
523 # used with this credential. If not set, the EAP method is selected
524 # automatically based on ANQP information (e.g., NAI Realm).
526 # phase1: Pre-configure Phase 1 (outer authentication) parameters
527 # This optional field is used with like the 'eap' parameter.
529 # phase2: Pre-configure Phase 2 (inner authentication) parameters
530 # This optional field is used with like the 'eap' parameter.
532 # excluded_ssid: Excluded SSID
533 # This optional field can be used to excluded specific SSID(s) from
534 # matching with the network. Multiple entries can be used to specify more
537 # roaming_partner: Roaming partner information
538 # This optional field can be used to configure preferences between roaming
539 # partners. The field is a string in following format:
540 # <FQDN>,<0/1 exact match>,<priority>,<* or country code>
541 # (non-exact match means any subdomain matches the entry; priority is in
542 # 0..255 range with 0 being the highest priority)
544 # update_identifier: PPS MO ID
545 # (Hotspot 2.0 PerProviderSubscription/UpdateIdentifier)
547 # provisioning_sp: FQDN of the SP that provisioned the credential
548 # This optional field can be used to keep track of the SP that provisioned
549 # the credential to find the PPS MO (./Wi-Fi/<provisioning_sp>).
551 # Minimum backhaul threshold (PPS/<X+>/Policy/MinBackhauldThreshold/*)
552 # These fields can be used to specify minimum download/upload backhaul
553 # bandwidth that is preferred for the credential. This constraint is
554 # ignored if the AP does not advertise WAN Metrics information or if the
555 # limit would prevent any connection. Values are in kilobits per second.
556 # min_dl_bandwidth_home
557 # min_ul_bandwidth_home
558 # min_dl_bandwidth_roaming
559 # min_ul_bandwidth_roaming
561 # max_bss_load: Maximum BSS Load Channel Utilization (1..255)
562 # (PPS/<X+>/Policy/MaximumBSSLoadValue)
563 # This value is used as the maximum channel utilization for network
564 # selection purposes for home networks. If the AP does not advertise
565 # BSS Load or if the limit would prevent any connection, this constraint
568 # req_conn_capab: Required connection capability
569 # (PPS/<X+>/Policy/RequiredProtoPortTuple)
570 # This value is used to configure set of required protocol/port pairs that
571 # a roaming network shall support (include explicitly in Connection
572 # Capability ANQP element). This constraint is ignored if the AP does not
573 # advertise Connection Capability or if this constraint would prevent any
574 # network connection. This policy is not used in home networks.
575 # Format: <protocol>[:<comma-separated list of ports]
576 # Multiple entries can be used to list multiple requirements.
577 # For example, number of common TCP protocols:
578 # req_conn_capab=6,22,80,443
579 # For example, IPSec/IKE:
580 # req_conn_capab=17:500
583 # ocsp: Whether to use/require OCSP to check server certificate
584 # 0 = do not use OCSP stapling (TLS certificate status extension)
585 # 1 = try to use OCSP stapling, but not require response
586 # 2 = require valid OCSP stapling response
588 # sim_num: Identifier for which SIM to use in multi-SIM devices
593 # realm="example.com"
594 # username="user@example.com"
595 # password="password"
596 # ca_cert="/etc/wpa_supplicant/ca.pem"
597 # domain="example.com"
601 # imsi="310026-000000000"
602 # milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82"
606 # realm="example.com"
608 # password="password"
609 # ca_cert="/etc/wpa_supplicant/ca.pem"
610 # domain="example.com"
611 # roaming_consortium=223344
613 # phase2="auth=MSCHAPV2"
621 # Each network (usually AP's sharing the same SSID) is configured as a separate
622 # block in this configuration file. The network blocks are in preference order
623 # (the first match is used).
625 # network block fields:
628 # 0 = this network can be used (default)
629 # 1 = this network block is disabled (can be enabled through ctrl_iface,
630 # e.g., with wpa_cli or wpa_gui)
632 # id_str: Network identifier string for external scripts. This value is passed
633 # to external action script through wpa_cli as WPA_ID_STR environment
634 # variable to make it easier to do network specific configuration.
636 # ssid: SSID (mandatory); network name in one of the optional formats:
637 # - an ASCII string with double quotation
638 # - a hex string (two characters per octet of SSID)
639 # - a printf-escaped ASCII string P"<escaped string>"
642 # 0 = do not scan this SSID with specific Probe Request frames (default)
643 # 1 = scan with SSID-specific Probe Request frames (this can be used to
644 # find APs that do not accept broadcast SSID or use multiple SSIDs;
645 # this will add latency to scanning, so enable this only when needed)
647 # bssid: BSSID (optional); if set, this network block is used only when
648 # associating with the AP using the configured BSSID
650 # priority: priority group (integer)
651 # By default, all networks will get same priority group (0). If some of the
652 # networks are more desirable, this field can be used to change the order in
653 # which wpa_supplicant goes through the networks when selecting a BSS. The
654 # priority groups will be iterated in decreasing priority (i.e., the larger the
655 # priority value, the sooner the network is matched against the scan results).
656 # Within each priority group, networks will be selected based on security
657 # policy, signal strength, etc.
658 # Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
659 # using this priority to select the order for scanning. Instead, they try the
660 # networks in the order that used in the configuration file.
662 # mode: IEEE 802.11 operation mode
663 # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
664 # 1 = IBSS (ad-hoc, peer-to-peer)
665 # 2 = AP (access point)
666 # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) and
667 # WPA-PSK (with proto=RSN). In addition, key_mgmt=WPA-NONE (fixed group key
668 # TKIP/CCMP) is available for backwards compatibility, but its use is
669 # deprecated. WPA-None requires following network block options:
670 # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
671 # both), and psk must also be set.
673 # frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
674 # 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
675 # channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
676 # In addition, this value is only used by the station that creates the IBSS. If
677 # an IBSS network with the configured SSID is already present, the frequency of
678 # the network will be used instead of this configured value.
680 # scan_freq: List of frequencies to scan
681 # Space-separated list of frequencies in MHz to scan when searching for this
682 # BSS. If the subset of channels used by the network is known, this option can
683 # be used to optimize scanning to not occur on channels that the network does
684 # not use. Example: scan_freq=2412 2437 2462
686 # freq_list: Array of allowed frequencies
687 # Space-separated list of frequencies in MHz to allow for selecting the BSS. If
688 # set, scan results that do not match any of the specified frequencies are not
689 # considered when selecting a BSS.
691 # This can also be set on the outside of the network block. In this case,
692 # it limits the frequencies that will be scanned.
694 # bgscan: Background scanning
695 # wpa_supplicant behavior for background scanning can be specified by
696 # configuring a bgscan module. These modules are responsible for requesting
697 # background scans for the purpose of roaming within an ESS (i.e., within a
698 # single network block with all the APs using the same SSID). The bgscan
699 # parameter uses following format: "<bgscan module name>:<module parameters>"
700 # Following bgscan modules are available:
701 # simple - Periodic background scans based on signal strength
702 # bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>:
704 # bgscan="simple:30:-45:300"
705 # learn - Learn channels used by the network and try to avoid bgscans on other
706 # channels (experimental)
707 # bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>:
708 # <long interval>[:<database file name>]"
709 # bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan"
710 # Explicitly disable bgscan by setting
713 # This option can also be set outside of all network blocks for the bgscan
714 # parameter to apply for all the networks that have no specific bgscan
717 # proto: list of accepted protocols
718 # WPA = WPA/IEEE 802.11i/D3.0
719 # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
720 # If not set, this defaults to: WPA RSN
722 # key_mgmt: list of accepted authenticated key management protocols
723 # WPA-PSK = WPA pre-shared key (this requires 'psk' field)
724 # WPA-EAP = WPA using EAP authentication
725 # IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
727 # NONE = WPA is not used; plaintext or static WEP could be used
728 # WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
729 # WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
730 # If not set, this defaults to: WPA-PSK WPA-EAP
732 # ieee80211w: whether management frame protection is enabled
733 # 0 = disabled (default unless changed with the global pmf parameter)
736 # The most common configuration options for this based on the PMF (protected
737 # management frames) certification program are:
738 # PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256
739 # PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256
740 # (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used)
742 # auth_alg: list of allowed IEEE 802.11 authentication algorithms
743 # OPEN = Open System authentication (required for WPA/WPA2)
744 # SHARED = Shared Key authentication (requires static WEP keys)
745 # LEAP = LEAP/Network EAP (only used with LEAP)
746 # If not set, automatic selection is used (Open System with LEAP enabled if
747 # LEAP is allowed as one of the EAP methods).
749 # pairwise: list of accepted pairwise (unicast) ciphers for WPA
750 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
751 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
752 # NONE = Use only Group Keys (deprecated, should not be included if APs support
754 # If not set, this defaults to: CCMP TKIP
756 # group: list of accepted group (broadcast/multicast) ciphers for WPA
757 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
758 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
759 # WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
760 # WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
761 # If not set, this defaults to: CCMP TKIP WEP104 WEP40
763 # psk: WPA preshared key; 256-bit pre-shared key
764 # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
765 # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
766 # generated using the passphrase and SSID). ASCII passphrase must be between
767 # 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
768 # be used to indicate that the PSK/passphrase is stored in external storage.
769 # This field is not needed, if WPA-EAP is used.
770 # Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
771 # from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
772 # startup and reconfiguration time can be optimized by generating the PSK only
773 # only when the passphrase or SSID has actually changed.
775 # mem_only_psk: Whether to keep PSK/passphrase only in memory
776 # 0 = allow psk/passphrase to be stored to the configuration file
777 # 1 = do not store psk/passphrase to the configuration file
780 # eapol_flags: IEEE 802.1X/EAPOL options (bit field)
781 # Dynamic WEP key required for non-WPA mode
782 # bit0 (1): require dynamically generated unicast WEP key
783 # bit1 (2): require dynamically generated broadcast WEP key
784 # (3 = require both keys; default)
785 # Note: When using wired authentication (including macsec_qca driver),
786 # eapol_flags must be set to 0 for the authentication to be completed
789 # macsec_policy: IEEE 802.1X/MACsec options
790 # This determines how sessions are secured with MACsec. It is currently
791 # applicable only when using the macsec_qca driver interface.
792 # 0: MACsec not in use (default)
793 # 1: MACsec enabled - Should secure, accept key server's advice to
794 # determine whether to use a secure session or not.
796 # mixed_cell: This option can be used to configure whether so called mixed
797 # cells, i.e., networks that use both plaintext and encryption in the same
798 # SSID, are allowed when selecting a BSS from scan results.
799 # 0 = disabled (default)
802 # proactive_key_caching:
803 # Enable/disable opportunistic PMKSA caching for WPA2.
804 # 0 = disabled (default unless changed with the global okc parameter)
807 # wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
808 # hex without quotation, e.g., 0102030405)
809 # wep_tx_keyidx: Default WEP key index (TX) (0..3)
811 # peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
812 # allowed. This is only used with RSN/WPA2.
813 # 0 = disabled (default)
817 # wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
818 # enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
820 # Following fields are only used with internal EAP implementation.
821 # eap: space-separated list of accepted EAP methods
822 # MD5 = EAP-MD5 (unsecure and does not generate keying material ->
823 # cannot be used with WPA; to be used as a Phase 2 method
824 # with EAP-PEAP or EAP-TTLS)
825 # MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
826 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
827 # OTP = EAP-OTP (cannot be used separately with WPA; to be used
828 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
829 # GTC = EAP-GTC (cannot be used separately with WPA; to be used
830 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
831 # TLS = EAP-TLS (client and server certificate)
832 # PEAP = EAP-PEAP (with tunnelled EAP authentication)
833 # TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
835 # If not set, all compiled in methods are allowed.
837 # identity: Identity string for EAP
838 # This field is also used to configure user NAI for
839 # EAP-PSK/PAX/SAKE/GPSK.
840 # anonymous_identity: Anonymous identity string for EAP (to be used as the
841 # unencrypted identity with EAP types that support different tunnelled
842 # identity, e.g., EAP-TTLS). This field can also be used with
843 # EAP-SIM/AKA/AKA' to store the pseudonym identity.
844 # password: Password string for EAP. This field can include either the
845 # plaintext password (using ASCII or hex string) or a NtPasswordHash
846 # (16-byte MD4 hash of password) in hash:<32 hex digits> format.
847 # NtPasswordHash can only be used when the password is for MSCHAPv2 or
848 # MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
849 # EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
850 # PSK) is also configured using this field. For EAP-GPSK, this is a
851 # variable length PSK. ext:<name of external password field> format can
852 # be used to indicate that the password is stored in external storage.
853 # ca_cert: File path to CA certificate file (PEM/DER). This file can have one
854 # or more trusted CA certificates. If ca_cert and ca_path are not
855 # included, server certificate will not be verified. This is insecure and
856 # a trusted CA certificate should always be configured when using
857 # EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
858 # change when wpa_supplicant is run in the background.
860 # Alternatively, this can be used to only perform matching of the server
861 # certificate (SHA-256 hash of the DER encoded X.509 certificate). In
862 # this case, the possible CA certificates in the server certificate chain
863 # are ignored and only the server certificate is verified. This is
864 # configured with the following format:
865 # hash:://server/sha256/cert_hash_in_hex
866 # For example: "hash://server/sha256/
867 # 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
869 # On Windows, trusted CA certificates can be loaded from the system
870 # certificate store by setting this to cert_store://<name>, e.g.,
871 # ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
872 # Note that when running wpa_supplicant as an application, the user
873 # certificate store (My user account) is used, whereas computer store
874 # (Computer account) is used when running wpasvc as a service.
875 # ca_path: Directory path for CA certificate files (PEM). This path may
876 # contain multiple CA certificates in OpenSSL format. Common use for this
877 # is to point to system trusted CA list which is often installed into
878 # directory like /etc/ssl/certs. If configured, these certificates are
879 # added to the list of trusted CAs. ca_cert may also be included in that
880 # case, but it is not required.
881 # client_cert: File path to client certificate file (PEM/DER)
882 # Full path should be used since working directory may change when
883 # wpa_supplicant is run in the background.
884 # Alternatively, a named configuration blob can be used by setting this
885 # to blob://<blob name>.
886 # private_key: File path to client private key file (PEM/DER/PFX)
887 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
888 # commented out. Both the private key and certificate will be read from
889 # the PKCS#12 file in this case. Full path should be used since working
890 # directory may change when wpa_supplicant is run in the background.
891 # Windows certificate store can be used by leaving client_cert out and
892 # configuring private_key in one of the following formats:
893 # cert://substring_to_match
894 # hash://certificate_thumbprint_in_hex
895 # for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
896 # Note that when running wpa_supplicant as an application, the user
897 # certificate store (My user account) is used, whereas computer store
898 # (Computer account) is used when running wpasvc as a service.
899 # Alternatively, a named configuration blob can be used by setting this
900 # to blob://<blob name>.
901 # private_key_passwd: Password for private key file (if left out, this will be
902 # asked through control interface)
903 # dh_file: File path to DH/DSA parameters file (in PEM format)
904 # This is an optional configuration file for setting parameters for an
905 # ephemeral DH key exchange. In most cases, the default RSA
906 # authentication does not use this configuration. However, it is possible
907 # setup RSA to use ephemeral DH key exchange. In addition, ciphers with
908 # DSA keys always use ephemeral DH keys. This can be used to achieve
909 # forward secrecy. If the file is in DSA parameters format, it will be
910 # automatically converted into DH params.
911 # subject_match: Substring to be matched against the subject of the
912 # authentication server certificate. If this string is set, the server
913 # sertificate is only accepted if it contains this string in the subject.
914 # The subject string is in following format:
915 # /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
916 # Note: Since this is a substring match, this cannot be used securily to
917 # do a suffix match against a possible domain name in the CN entry. For
918 # such a use case, domain_suffix_match or domain_match should be used
920 # altsubject_match: Semicolon separated string of entries to be matched against
921 # the alternative subject name of the authentication server certificate.
922 # If this string is set, the server sertificate is only accepted if it
923 # contains one of the entries in an alternative subject name extension.
924 # altSubjectName string is in following format: TYPE:VALUE
925 # Example: EMAIL:server@example.com
926 # Example: DNS:server.example.com;DNS:server2.example.com
927 # Following types are supported: EMAIL, DNS, URI
928 # domain_suffix_match: Constraint for server domain name. If set, this FQDN is
929 # used as a suffix match requirement for the AAAserver certificate in
930 # SubjectAltName dNSName element(s). If a matching dNSName is found, this
931 # constraint is met. If no dNSName values are present, this constraint is
932 # matched against SubjectName CN using same suffix match comparison.
934 # Suffix match here means that the host/domain name is compared one label
935 # at a time starting from the top-level domain and all the labels in
936 # domain_suffix_match shall be included in the certificate. The
937 # certificate may include additional sub-level labels in addition to the
940 # For example, domain_suffix_match=example.com would match
941 # test.example.com but would not match test-example.com.
942 # domain_match: Constraint for server domain name
943 # If set, this FQDN is used as a full match requirement for the
944 # server certificate in SubjectAltName dNSName element(s). If a
945 # matching dNSName is found, this constraint is met. If no dNSName
946 # values are present, this constraint is matched against SubjectName CN
947 # using same full match comparison. This behavior is similar to
948 # domain_suffix_match, but has the requirement of a full match, i.e.,
949 # no subdomains or wildcard matches are allowed. Case-insensitive
950 # comparison is used, so "Example.com" matches "example.com", but would
951 # not match "test.Example.com".
952 # phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
953 # (string with field-value pairs, e.g., "peapver=0" or
954 # "peapver=1 peaplabel=1")
955 # 'peapver' can be used to force which PEAP version (0 or 1) is used.
956 # 'peaplabel=1' can be used to force new label, "client PEAP encryption",
957 # to be used during key derivation when PEAPv1 or newer. Most existing
958 # PEAPv1 implementation seem to be using the old label, "client EAP
959 # encryption", and wpa_supplicant is now using that as the default value.
960 # Some servers, e.g., Radiator, may require peaplabel=1 configuration to
961 # interoperate with PEAPv1; see eap_testing.txt for more details.
962 # 'peap_outer_success=0' can be used to terminate PEAP authentication on
963 # tunneled EAP-Success. This is required with some RADIUS servers that
964 # implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
965 # Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
966 # include_tls_length=1 can be used to force wpa_supplicant to include
967 # TLS Message Length field in all TLS messages even if they are not
969 # sim_min_num_chal=3 can be used to configure EAP-SIM to require three
970 # challenges (by default, it accepts 2 or 3)
971 # result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
972 # protected result indication.
973 # 'crypto_binding' option can be used to control PEAPv0 cryptobinding
975 # * 0 = do not use cryptobinding (default)
976 # * 1 = use cryptobinding if server supports it
977 # * 2 = require cryptobinding
978 # EAP-WSC (WPS) uses following options: pin=<Device Password> or
981 # For wired IEEE 802.1X authentication, "allow_canned_success=1" can be
982 # used to configure a mode that allows EAP-Success (and EAP-Failure)
983 # without going through authentication step. Some switches use such
984 # sequence when forcing the port to be authorized/unauthorized or as a
985 # fallback option if the authentication server is unreachable. By default,
986 # wpa_supplicant discards such frames to protect against potential attacks
987 # by rogue devices, but this option can be used to disable that protection
988 # for cases where the server/authenticator does not need to be
990 # phase2: Phase2 (inner authentication with TLS tunnel) parameters
991 # (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
992 # "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS). "mschapv2_retry=0" can be
993 # used to disable MSCHAPv2 password retry in authentication failure cases.
995 # TLS-based methods can use the following parameters to control TLS behavior
996 # (these are normally in the phase1 parameter, but can be used also in the
997 # phase2 parameter when EAP-TLS is used within the inner tunnel):
998 # tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the
999 # TLS library, these may be disabled by default to enforce stronger
1001 # tls_disable_time_checks=1 - ignore certificate validity time (this requests
1002 # the TLS library to accept certificates even if they are not currently
1003 # valid, i.e., have expired or have not yet become valid; this should be
1004 # used only for testing purposes)
1005 # tls_disable_session_ticket=1 - disable TLS Session Ticket extension
1006 # tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used
1007 # Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS
1008 # as a workaround for broken authentication server implementations unless
1009 # EAP workarounds are disabled with eap_workaround=0.
1010 # For EAP-FAST, this must be set to 0 (or left unconfigured for the
1011 # default value to be used automatically).
1012 # tls_disable_tlsv1_0=1 - disable use of TLSv1.0
1013 # tls_disable_tlsv1_1=1 - disable use of TLSv1.1 (a workaround for AAA servers
1014 # that have issues interoperating with updated TLS version)
1015 # tls_disable_tlsv1_2=1 - disable use of TLSv1.2 (a workaround for AAA servers
1016 # that have issues interoperating with updated TLS version)
1018 # Following certificate/private key fields are used in inner Phase2
1019 # authentication when using EAP-TTLS or EAP-PEAP.
1020 # ca_cert2: File path to CA certificate file. This file can have one or more
1021 # trusted CA certificates. If ca_cert2 and ca_path2 are not included,
1022 # server certificate will not be verified. This is insecure and a trusted
1023 # CA certificate should always be configured.
1024 # ca_path2: Directory path for CA certificate files (PEM)
1025 # client_cert2: File path to client certificate file
1026 # private_key2: File path to client private key file
1027 # private_key2_passwd: Password for private key file
1028 # dh_file2: File path to DH/DSA parameters file (in PEM format)
1029 # subject_match2: Substring to be matched against the subject of the
1030 # authentication server certificate. See subject_match for more details.
1031 # altsubject_match2: Semicolon separated string of entries to be matched
1032 # against the alternative subject name of the authentication server
1033 # certificate. See altsubject_match documentation for more details.
1034 # domain_suffix_match2: Constraint for server domain name. See
1035 # domain_suffix_match for more details.
1037 # fragment_size: Maximum EAP fragment size in bytes (default 1398).
1038 # This value limits the fragment size for EAP methods that support
1039 # fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
1040 # small enough to make the EAP messages fit in MTU of the network
1041 # interface used for EAPOL. The default value is suitable for most
1044 # ocsp: Whether to use/require OCSP to check server certificate
1045 # 0 = do not use OCSP stapling (TLS certificate status extension)
1046 # 1 = try to use OCSP stapling, but not require response
1047 # 2 = require valid OCSP stapling response
1049 # openssl_ciphers: OpenSSL specific cipher configuration
1050 # This can be used to override the global openssl_ciphers configuration
1051 # parameter (see above).
1053 # erp: Whether EAP Re-authentication Protocol (ERP) is enabled
1055 # EAP-FAST variables:
1056 # pac_file: File path for the PAC entries. wpa_supplicant will need to be able
1057 # to create this file and write updates to it when PAC is being
1058 # provisioned or refreshed. Full path to the file should be used since
1059 # working directory may change when wpa_supplicant is run in the
1060 # background. Alternatively, a named configuration blob can be used by
1061 # setting this to blob://<blob name>
1062 # phase1: fast_provisioning option can be used to enable in-line provisioning
1063 # of EAP-FAST credentials (PAC):
1065 # 1 = allow unauthenticated provisioning,
1066 # 2 = allow authenticated provisioning,
1067 # 3 = allow both unauthenticated and authenticated provisioning
1068 # fast_max_pac_list_len=<num> option can be used to set the maximum
1069 # number of PAC entries to store in a PAC list (default: 10)
1070 # fast_pac_format=binary option can be used to select binary format for
1071 # storing PAC entries in order to save some space (the default
1072 # text format uses about 2.5 times the size of minimal binary
1075 # wpa_supplicant supports number of "EAP workarounds" to work around
1076 # interoperability issues with incorrectly behaving authentication servers.
1077 # These are enabled by default because some of the issues are present in large
1078 # number of authentication servers. Strict EAP conformance mode can be
1079 # configured by disabling workarounds with eap_workaround=0.
1081 # Station inactivity limit
1083 # If a station does not send anything in ap_max_inactivity seconds, an
1084 # empty data frame is sent to it in order to verify whether it is
1085 # still in range. If this frame is not ACKed, the station will be
1086 # disassociated and then deauthenticated. This feature is used to
1087 # clear station table of old entries when the STAs move out of the
1090 # The station can associate again with the AP if it is still in range;
1091 # this inactivity poll is just used as a nicer way of verifying
1092 # inactivity; i.e., client will not report broken connection because
1093 # disassociation frame is not sent immediately without first polling
1094 # the STA with a data frame.
1095 # default: 300 (i.e., 5 minutes)
1096 #ap_max_inactivity=300
1098 # DTIM period in Beacon intervals for AP mode (default: 2)
1101 # Beacon interval (default: 100 TU)
1104 # MAC address policy
1105 # 0 = use permanent MAC address
1106 # 1 = use random MAC address for each ESS connection
1107 # 2 = like 1, but maintain OUI (with local admin bit set)
1110 # disable_ht: Whether HT (802.11n) should be disabled.
1111 # 0 = HT enabled (if AP supports it)
1114 # disable_ht40: Whether HT-40 (802.11n) should be disabled.
1115 # 0 = HT-40 enabled (if AP supports it)
1116 # 1 = HT-40 disabled
1118 # disable_sgi: Whether SGI (short guard interval) should be disabled.
1119 # 0 = SGI enabled (if AP supports it)
1122 # disable_ldpc: Whether LDPC should be disabled.
1123 # 0 = LDPC enabled (if AP supports it)
1126 # ht40_intolerant: Whether 40 MHz intolerant should be indicated.
1127 # 0 = 40 MHz tolerant (default)
1128 # 1 = 40 MHz intolerant
1130 # ht_mcs: Configure allowed MCS rates.
1131 # Parsed as an array of bytes, in base-16 (ascii-hex)
1132 # ht_mcs="" // Use all available (default)
1133 # ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only
1134 # ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only
1136 # disable_max_amsdu: Whether MAX_AMSDU should be disabled.
1137 # -1 = Do not make any changes.
1138 # 0 = Enable MAX-AMSDU if hardware supports it.
1141 # ampdu_factor: Maximum A-MPDU Length Exponent
1142 # Value: 0-3, see 7.3.2.56.3 in IEEE Std 802.11n-2009.
1144 # ampdu_density: Allow overriding AMPDU density configuration.
1145 # Treated as hint by the kernel.
1146 # -1 = Do not make any changes.
1147 # 0-3 = Set AMPDU density (aka factor) to specified value.
1149 # disable_vht: Whether VHT should be disabled.
1150 # 0 = VHT enabled (if AP supports it)
1153 # vht_capa: VHT capabilities to set in the override
1154 # vht_capa_mask: mask of VHT capabilities
1156 # vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8
1157 # vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8
1163 ##### Fast Session Transfer (FST) support #####################################
1165 # The options in this section are only available when the build configuration
1166 # option CONFIG_FST is set while compiling hostapd. They allow this interface
1167 # to be a part of FST setup.
1169 # FST is the transfer of a session from a channel to another channel, in the
1170 # same or different frequency bands.
1172 # For detals, see IEEE Std 802.11ad-2012.
1174 # Identifier of an FST Group the interface belongs to.
1177 # Interface priority within the FST Group.
1178 # Announcing a higher priority for an interface means declaring it more
1179 # preferable for FST switch.
1180 # fst_priority is in 1..255 range with 1 being the lowest priority.
1183 # Default LLT value for this interface in milliseconds. The value used in case
1184 # no value provided during session setup. Default is 50 msec.
1185 # fst_llt is in 1..4294967 range (due to spec limitation, see 10.32.2.2
1186 # Transitioning between states).
1191 # Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
1194 psk="very secret passphrase"
1198 # Same as previous, but request SSID-specific scanning (for APs that reject
1203 psk="very secret passphrase"
1207 # Only WPA-PSK is used. Any valid cipher combination is accepted.
1213 group=CCMP TKIP WEP104 WEP40
1214 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1218 # WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
1225 psk="not so secure passphrase"
1229 # Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
1230 # or WEP40 as the group cipher will not be accepted.
1238 identity="user@example.com"
1239 ca_cert="/etc/cert/ca.pem"
1240 client_cert="/etc/cert/user.pem"
1241 private_key="/etc/cert/user.prv"
1242 private_key_passwd="password"
1246 # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
1252 identity="user@example.com"
1254 ca_cert="/etc/cert/ca.pem"
1255 phase1="peaplabel=1"
1256 phase2="auth=MSCHAPV2"
1260 # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
1261 # unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
1266 identity="user@example.com"
1267 anonymous_identity="anonymous@example.com"
1269 ca_cert="/etc/cert/ca.pem"
1273 # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
1274 # use. Real identity is sent only within an encrypted TLS tunnel.
1279 identity="user@example.com"
1280 anonymous_identity="anonymous@example.com"
1282 ca_cert="/etc/cert/ca.pem"
1283 phase2="auth=MSCHAPV2"
1286 # WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
1292 # Phase1 / outer authentication
1293 anonymous_identity="anonymous@example.com"
1294 ca_cert="/etc/cert/ca.pem"
1295 # Phase 2 / inner authentication
1296 phase2="autheap=TLS"
1297 ca_cert2="/etc/cert/ca2.pem"
1298 client_cert2="/etc/cer/user.pem"
1299 private_key2="/etc/cer/user.prv"
1300 private_key2_passwd="password"
1304 # Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
1308 bssid=00:11:22:33:44:55
1310 key_mgmt=WPA-PSK WPA-EAP
1313 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1316 # Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
1317 # and all valid ciphers.
1320 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
1324 # EAP-SIM with a GSM SIM or USIM
1339 anonymous_identity="eap_psk_user"
1340 password=06b4be19da289f475aa46a33cb793029
1341 identity="eap_psk_user@example.com"
1345 # IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
1346 # EAP-TLS for authentication and key generation; require both unicast and
1347 # broadcast WEP keys.
1352 identity="user@example.com"
1353 ca_cert="/etc/cert/ca.pem"
1354 client_cert="/etc/cert/user.pem"
1355 private_key="/etc/cert/user.prv"
1356 private_key_passwd="password"
1361 # LEAP with dynamic WEP keys
1370 # EAP-IKEv2 using shared secrets for both server and peer authentication
1372 ssid="ikev2-example"
1379 # EAP-FAST with WPA (WPA or WPA2)
1381 ssid="eap-fast-test"
1384 anonymous_identity="FAST-000102030405"
1387 phase1="fast_provisioning=1"
1388 pac_file="/etc/wpa_supplicant.eap-fast-pac"
1392 ssid="eap-fast-test"
1395 anonymous_identity="FAST-000102030405"
1398 phase1="fast_provisioning=1"
1399 pac_file="blob://eap-fast-pac"
1402 # Plaintext connection (no WPA, no IEEE 802.1X)
1404 ssid="plaintext-test"
1409 # Shared WEP key connection (no WPA, no IEEE 802.1X)
1411 ssid="static-wep-test"
1415 wep_key2="1234567890123"
1421 # Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
1422 # IEEE 802.11 authentication
1424 ssid="static-wep-test2"
1428 wep_key2="1234567890123"
1435 # IBSS/ad-hoc network with RSN
1447 # IBSS/ad-hoc network with WPA-None/TKIP (deprecated)
1456 psk="secret passphrase"
1467 # secure (SAE + AMPE) network
1473 psk="very secret passphrase"
1477 # Catch all example that allows more or less all configuration modes
1481 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
1483 group=CCMP TKIP WEP104 WEP40
1484 psk="very secret passphrase"
1486 identity="user@example.com"
1488 ca_cert="/etc/cert/ca.pem"
1489 client_cert="/etc/cert/user.pem"
1490 private_key="/etc/cert/user.prv"
1491 private_key_passwd="password"
1492 phase1="peaplabel=0"
1495 # Example of EAP-TLS with smartcard (openssl engine)
1503 identity="user@example.com"
1504 ca_cert="/etc/cert/ca.pem"
1505 client_cert="/etc/cert/user.pem"
1509 # The engine configured here must be available. Look at
1510 # OpenSSL engine support in the global section.
1511 # The key available through the engine must be the private key
1512 # matching the client certificate configured above.
1514 # use the opensc engine
1518 # use the pkcs11 engine
1522 # Optional PIN configuration; this can be left out and PIN will be
1523 # asked through the control interface
1527 # Example configuration showing how to use an inlined blob as a CA certificate
1528 # data instead of using external file
1533 identity="user@example.com"
1534 anonymous_identity="anonymous@example.com"
1536 ca_cert="blob://exampleblob"
1540 blob-base64-exampleblob={
1541 SGVsbG8gV29ybGQhCg==
1545 # Wildcard match for SSID (plaintext APs only). This example select any
1546 # open AP regardless of its SSID.
1551 # Example configuration blacklisting two APs - these will be ignored
1555 psk="very secret passphrase"
1556 bssid_blacklist=02:11:22:33:44:55 02:22:aa:44:55:66
1559 # Example configuration limiting AP selection to a specific set of APs;
1560 # any other AP not matching the masked address will be ignored.
1563 psk="very secret passphrase"
1564 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
1567 # Example config file that will only scan on channel 36.
1574 # Example MACsec configuration
1576 # key_mgmt=IEEE8021X
1579 # anonymous_identity="anonymous@example.com"
1580 # identity="user@example.com"
1581 # password="secretr"
1582 # ca_cert="/etc/cert/ca.pem"