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 # When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
112 # created immediately regardless of scan results. ap_scan=1 mode will first try
113 # to scan for existing networks and only if no matches with the enabled
114 # networks are found, a new IBSS or AP mode network is created.
117 # EAP fast re-authentication
118 # By default, fast re-authentication is enabled for all EAP methods that
119 # support it. This variable can be used to disable fast re-authentication.
120 # Normally, there is no need to disable this.
123 # OpenSSL Engine support
124 # These options can be used to load OpenSSL engines.
125 # The two engines that are supported currently are shown below:
126 # They are both from the opensc project (http://www.opensc.org/)
127 # By default no engines are loaded.
128 # make the opensc engine available
129 #opensc_engine_path=/usr/lib/opensc/engine_opensc.so
130 # make the pkcs11 engine available
131 #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
132 # configure the path to the pkcs11 module required by the pkcs11 engine
133 #pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
135 # OpenSSL cipher string
137 # This is an OpenSSL specific configuration option for configuring the default
138 # ciphers. If not set, "DEFAULT:!EXP:!LOW" is used as the default.
139 # See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation
140 # on cipher suite configuration. This is applicable only if wpa_supplicant is
141 # built to use OpenSSL.
142 #openssl_ciphers=DEFAULT:!EXP:!LOW
145 # Dynamic EAP methods
146 # If EAP methods were built dynamically as shared object files, they need to be
147 # loaded here before being used in the network blocks. By default, EAP methods
148 # are included statically in the build, so these lines are not needed
149 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
150 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
152 # Driver interface parameters
153 # This field can be used to configure arbitrary driver interace parameters. The
154 # format is specific to the selected driver interface. This field is not used
156 #driver_param="field=value"
159 # The ISO/IEC alpha2 country code for the country in which this device is
160 # currently operating.
163 # Maximum lifetime for PMKSA in seconds; default 43200
164 #dot11RSNAConfigPMKLifetime=43200
165 # Threshold for reauthentication (percentage of PMK lifetime); default 70
166 #dot11RSNAConfigPMKReauthThreshold=70
167 # Timeout for security association negotiation in seconds; default 60
168 #dot11RSNAConfigSATimeout=60
170 # Wi-Fi Protected Setup (WPS) parameters
172 # Universally Unique IDentifier (UUID; see RFC 4122) of the device
173 # If not configured, UUID will be generated based on the local MAC address.
174 #uuid=12345678-9abc-def0-1234-56789abcdef0
177 # User-friendly description of device; up to 32 octets encoded in UTF-8
178 #device_name=Wireless Client
181 # The manufacturer of the device (up to 64 ASCII characters)
182 #manufacturer=Company
185 # Model of the device (up to 32 ASCII characters)
189 # Additional device description (up to 32 ASCII characters)
193 # Serial number of the device (up to 32 characters)
196 # Primary Device Type
197 # Used format: <categ>-<OUI>-<subcateg>
198 # categ = Category as an integer value
199 # OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
201 # subcateg = OUI-specific Sub Category as an integer value
203 # 1-0050F204-1 (Computer / PC)
204 # 1-0050F204-2 (Computer / Server)
205 # 5-0050F204-1 (Storage / NAS)
206 # 6-0050F204-1 (Network Infrastructure / AP)
207 #device_type=1-0050F204-1
210 # 4-octet operating system version number (hex string)
214 # List of the supported configuration methods
215 # Available methods: usba ethernet label display ext_nfc_token int_nfc_token
216 # nfc_interface push_button keypad virtual_display physical_display
217 # virtual_push_button physical_push_button
219 #config_methods=label display push_button keypad
221 #config_methods=label virtual_display virtual_push_button keypad
223 # Credential processing
224 # 0 = process received credentials internally (default)
225 # 1 = do not process received credentials; just pass them over ctrl_iface to
226 # external program(s)
227 # 2 = process received credentials internally and pass them over ctrl_iface
228 # to external program(s)
229 #wps_cred_processing=0
231 # Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing
232 # The vendor attribute contents to be added in M1 (hex string)
233 #wps_vendor_ext_m1=000137100100020001
235 # NFC password token for WPS
236 # These parameters can be used to configure a fixed NFC password token for the
237 # station. This can be generated, e.g., with nfc_pw_token. When these
238 # parameters are used, the station is assumed to be deployed with a NFC tag
239 # that includes the matching NFC password token (e.g., written based on the
240 # NDEF record from nfc_pw_token).
242 #wps_nfc_dev_pw_id: Device Password ID (16..65535)
243 #wps_nfc_dh_pubkey: Hexdump of DH Public Key
244 #wps_nfc_dh_privkey: Hexdump of DH Private Key
245 #wps_nfc_dev_pw: Hexdump of Device Password
247 # Maximum number of BSS entries to keep in memory
249 # This can be used to limit memory use on the BSS entries (cached scan
250 # results). A larger value may be needed in environments that have huge number
251 # of APs when using ap_scan=1 mode.
255 # This is an optional set of parameters for automatic scanning
256 # within an interface in following format:
257 #autoscan=<autoscan module name>:<module parameters>
258 # autoscan is like bgscan but on disconnected or inactive state.
259 # For instance, on exponential module parameters would be <base>:<limit>
260 #autoscan=exponential:3:300
261 # Which means a delay between scans on a base exponential of 3,
262 # up to the limit of 300 seconds (3, 9, 27 ... 300)
263 # For periodic module, parameters would be <fixed interval>
264 #autoscan=periodic:30
265 # So a delay of 30 seconds will be applied between each scan
267 # filter_ssids - SSID-based scan result filtering
268 # 0 = do not filter scan results (default)
269 # 1 = only include configured SSIDs in scan results/BSS table
272 # Password (and passphrase, etc.) backend for external storage
273 # format: <backend name>[:<optional backend parameters>]
274 #ext_password_backend=test:pw1=password|pw2=testing
276 # Timeout in seconds to detect STA inactivity (default: 300 seconds)
278 # This timeout value is used in P2P GO mode to clean up
280 #p2p_go_max_inactivity=300
282 # Passphrase length (8..63) for P2P GO
284 # This parameter controls the length of the random passphrase that is
285 # generated at the GO. Default: 8.
286 #p2p_passphrase_len=8
288 # Extra delay between concurrent P2P search iterations
290 # This value adds extra delay in milliseconds between concurrent search
291 # iterations to make p2p_find friendlier to concurrent operations by avoiding
292 # it from taking 100% of radio resources. The default value is 500 ms.
293 #p2p_search_delay=500
295 # Opportunistic Key Caching (also known as Proactive Key Caching) default
296 # This parameter can be used to set the default behavior for the
297 # proactive_key_caching parameter. By default, OKC is disabled unless enabled
298 # with the global okc=1 parameter or with the per-network
299 # proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but
300 # can be disabled with per-network proactive_key_caching=0 parameter.
303 # Protected Management Frames default
304 # This parameter can be used to set the default behavior for the ieee80211w
305 # parameter. By default, PMF is disabled unless enabled with the global pmf=1/2
306 # parameter or with the per-network ieee80211w=1/2 parameter. With pmf=1/2, PMF
307 # is enabled/required by default, but can be disabled with the per-network
308 # ieee80211w parameter.
311 # Enabled SAE finite cyclic groups in preference order
312 # By default (if this parameter is not set), the mandatory group 19 (ECC group
313 # defined over a 256-bit prime order field) is preferred, but other groups are
314 # also enabled. If this parameter is set, the groups will be tried in the
315 # indicated order. The group values are listed in the IANA registry:
316 # http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
317 #sae_groups=21 20 19 26 25
319 # Default value for DTIM period (if not overridden in network block)
322 # Default value for Beacon interval (if not overridden in network block)
325 # Additional vendor specific elements for Beacon and Probe Response frames
326 # This parameter can be used to add additional vendor specific element(s) into
327 # the end of the Beacon and Probe Response frames. The format for these
328 # element(s) is a hexdump of the raw information elements (id+len+payload for
329 # one or more elements). This is used in AP and P2P GO modes.
330 #ap_vendor_elements=dd0411223301
332 # Ignore scan results older than request
334 # The driver may have a cache of scan results that makes it return
335 # information that is older than our scan trigger. This parameter can
336 # be used to configure such old information to be ignored instead of
337 # allowing it to update the internal BSS table.
338 #ignore_old_scan_res=0
340 # scan_cur_freq: Whether to scan only the current frequency
341 # 0: Scan all available frequencies. (Default)
342 # 1: Scan current operating frequency if another VIF on the same radio
343 # is already associated.
345 # MAC address policy default
346 # 0 = use permanent MAC address
347 # 1 = use random MAC address for each ESS connection
348 # 2 = like 1, but maintain OUI (with local admin bit set)
350 # By default, permanent MAC address is used unless policy is changed by
351 # the per-network mac_addr parameter. Global mac_addr=1 can be used to
352 # change this default behavior.
355 # Lifetime of random MAC address in seconds (default: 60)
356 #rand_addr_lifetime=60
358 # MAC address policy for pre-association operations (scanning, ANQP)
359 # 0 = use permanent MAC address
360 # 1 = use random MAC address
361 # 2 = like 1, but maintain OUI (with local admin bit set)
364 # Interworking (IEEE 802.11u)
366 # Enable Interworking
369 # Homogenous ESS identifier
370 # If this is set, scans will be used to request response only from BSSes
371 # belonging to the specified Homogeneous ESS. This is used only if interworking
373 # hessid=00:11:22:33:44:55
375 # Automatic network selection behavior
376 # 0 = do not automatically go through Interworking network selection
377 # (i.e., require explicit interworking_select command for this; default)
378 # 1 = perform Interworking network selection if one or more
379 # credentials have been configured and scan did not find a
380 # matching network block
385 # Each credential used for automatic network selection is configured as a set
386 # of parameters that are compared to the information advertised by the APs when
387 # interworking_select and interworking_connect commands are used.
391 # temporary: Whether this credential is temporary and not to be saved
393 # priority: Priority group
394 # By default, all networks and credentials get the same priority group
395 # (0). This field can be used to give higher priority for credentials
396 # (and similarly in struct wpa_ssid for network blocks) to change the
397 # Interworking automatic networking selection behavior. The matching
398 # network (based on either an enabled network block or a credential)
399 # with the highest priority value will be selected.
401 # pcsc: Use PC/SC and SIM/USIM card
403 # realm: Home Realm for Interworking
405 # username: Username for Interworking network selection
407 # password: Password for Interworking network selection
409 # ca_cert: CA certificate for Interworking network selection
411 # client_cert: File path to client certificate file (PEM/DER)
412 # This field is used with Interworking networking selection for a case
413 # where client certificate/private key is used for authentication
414 # (EAP-TLS). Full path to the file should be used since working
415 # directory may change when wpa_supplicant is run in the background.
417 # Alternatively, a named configuration blob can be used by setting
418 # this to blob://blob_name.
420 # private_key: File path to client private key file (PEM/DER/PFX)
421 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
422 # commented out. Both the private key and certificate will be read
423 # from the PKCS#12 file in this case. Full path to the file should be
424 # used since working directory may change when wpa_supplicant is run
427 # Windows certificate store can be used by leaving client_cert out and
428 # configuring private_key in one of the following formats:
430 # cert://substring_to_match
432 # hash://certificate_thumbprint_in_hex
434 # For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
436 # Note that when running wpa_supplicant as an application, the user
437 # certificate store (My user account) is used, whereas computer store
438 # (Computer account) is used when running wpasvc as a service.
440 # Alternatively, a named configuration blob can be used by setting
441 # this to blob://blob_name.
443 # private_key_passwd: Password for private key file
445 # imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format
447 # milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN>
450 # domain: Home service provider FQDN(s)
451 # This is used to compare against the Domain Name List to figure out
452 # whether the AP is operated by the Home SP. Multiple domain entries can
453 # be used to configure alternative FQDNs that will be considered home
456 # roaming_consortium: Roaming Consortium OI
457 # If roaming_consortium_len is non-zero, this field contains the
458 # Roaming Consortium OI that can be used to determine which access
459 # points support authentication with this credential. This is an
460 # alternative to the use of the realm parameter. When using Roaming
461 # Consortium to match the network, the EAP parameters need to be
462 # pre-configured with the credential since the NAI Realm information
463 # may not be available or fetched.
465 # eap: Pre-configured EAP method
466 # This optional field can be used to specify which EAP method will be
467 # used with this credential. If not set, the EAP method is selected
468 # automatically based on ANQP information (e.g., NAI Realm).
470 # phase1: Pre-configure Phase 1 (outer authentication) parameters
471 # This optional field is used with like the 'eap' parameter.
473 # phase2: Pre-configure Phase 2 (inner authentication) parameters
474 # This optional field is used with like the 'eap' parameter.
476 # excluded_ssid: Excluded SSID
477 # This optional field can be used to excluded specific SSID(s) from
478 # matching with the network. Multiple entries can be used to specify more
481 # roaming_partner: Roaming partner information
482 # This optional field can be used to configure preferences between roaming
483 # partners. The field is a string in following format:
484 # <FQDN>,<0/1 exact match>,<priority>,<* or country code>
485 # (non-exact match means any subdomain matches the entry; priority is in
486 # 0..255 range with 0 being the highest priority)
488 # update_identifier: PPS MO ID
489 # (Hotspot 2.0 PerProviderSubscription/UpdateIdentifier)
491 # provisioning_sp: FQDN of the SP that provisioned the credential
492 # This optional field can be used to keep track of the SP that provisioned
493 # the credential to find the PPS MO (./Wi-Fi/<provisioning_sp>).
495 # Minimum backhaul threshold (PPS/<X+>/Policy/MinBackhauldThreshold/*)
496 # These fields can be used to specify minimum download/upload backhaul
497 # bandwidth that is preferred for the credential. This constraint is
498 # ignored if the AP does not advertise WAN Metrics information or if the
499 # limit would prevent any connection. Values are in kilobits per second.
500 # min_dl_bandwidth_home
501 # min_ul_bandwidth_home
502 # min_dl_bandwidth_roaming
503 # min_ul_bandwidth_roaming
505 # max_bss_load: Maximum BSS Load Channel Utilization (1..255)
506 # (PPS/<X+>/Policy/MaximumBSSLoadValue)
507 # This value is used as the maximum channel utilization for network
508 # selection purposes for home networks. If the AP does not advertise
509 # BSS Load or if the limit would prevent any connection, this constraint
512 # req_conn_capab: Required connection capability
513 # (PPS/<X+>/Policy/RequiredProtoPortTuple)
514 # This value is used to configure set of required protocol/port pairs that
515 # a roaming network shall support (include explicitly in Connection
516 # Capability ANQP element). This constraint is ignored if the AP does not
517 # advertise Connection Capability or if this constraint would prevent any
518 # network connection. This policy is not used in home networks.
519 # Format: <protocol>[:<comma-separated list of ports]
520 # Multiple entries can be used to list multiple requirements.
521 # For example, number of common TCP protocols:
522 # req_conn_capab=6,22,80,443
523 # For example, IPSec/IKE:
524 # req_conn_capab=17:500
527 # ocsp: Whether to use/require OCSP to check server certificate
528 # 0 = do not use OCSP stapling (TLS certificate status extension)
529 # 1 = try to use OCSP stapling, but not require response
530 # 2 = require valid OCSP stapling response
532 # sim_num: Identifier for which SIM to use in multi-SIM devices
537 # realm="example.com"
538 # username="user@example.com"
539 # password="password"
540 # ca_cert="/etc/wpa_supplicant/ca.pem"
541 # domain="example.com"
545 # imsi="310026-000000000"
546 # milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82"
550 # realm="example.com"
552 # password="password"
553 # ca_cert="/etc/wpa_supplicant/ca.pem"
554 # domain="example.com"
555 # roaming_consortium=223344
557 # phase2="auth=MSCHAPV2"
565 # Each network (usually AP's sharing the same SSID) is configured as a separate
566 # block in this configuration file. The network blocks are in preference order
567 # (the first match is used).
569 # network block fields:
572 # 0 = this network can be used (default)
573 # 1 = this network block is disabled (can be enabled through ctrl_iface,
574 # e.g., with wpa_cli or wpa_gui)
576 # id_str: Network identifier string for external scripts. This value is passed
577 # to external action script through wpa_cli as WPA_ID_STR environment
578 # variable to make it easier to do network specific configuration.
580 # ssid: SSID (mandatory); network name in one of the optional formats:
581 # - an ASCII string with double quotation
582 # - a hex string (two characters per octet of SSID)
583 # - a printf-escaped ASCII string P"<escaped string>"
586 # 0 = do not scan this SSID with specific Probe Request frames (default)
587 # 1 = scan with SSID-specific Probe Request frames (this can be used to
588 # find APs that do not accept broadcast SSID or use multiple SSIDs;
589 # this will add latency to scanning, so enable this only when needed)
591 # bssid: BSSID (optional); if set, this network block is used only when
592 # associating with the AP using the configured BSSID
594 # priority: priority group (integer)
595 # By default, all networks will get same priority group (0). If some of the
596 # networks are more desirable, this field can be used to change the order in
597 # which wpa_supplicant goes through the networks when selecting a BSS. The
598 # priority groups will be iterated in decreasing priority (i.e., the larger the
599 # priority value, the sooner the network is matched against the scan results).
600 # Within each priority group, networks will be selected based on security
601 # policy, signal strength, etc.
602 # Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
603 # using this priority to select the order for scanning. Instead, they try the
604 # networks in the order that used in the configuration file.
606 # mode: IEEE 802.11 operation mode
607 # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
608 # 1 = IBSS (ad-hoc, peer-to-peer)
609 # 2 = AP (access point)
610 # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) and
611 # WPA-PSK (with proto=RSN). In addition, key_mgmt=WPA-NONE (fixed group key
612 # TKIP/CCMP) is available for backwards compatibility, but its use is
613 # deprecated. WPA-None requires following network block options:
614 # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
615 # both), and psk must also be set.
617 # frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
618 # 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
619 # channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
620 # In addition, this value is only used by the station that creates the IBSS. If
621 # an IBSS network with the configured SSID is already present, the frequency of
622 # the network will be used instead of this configured value.
624 # scan_freq: List of frequencies to scan
625 # Space-separated list of frequencies in MHz to scan when searching for this
626 # BSS. If the subset of channels used by the network is known, this option can
627 # be used to optimize scanning to not occur on channels that the network does
628 # not use. Example: scan_freq=2412 2437 2462
630 # freq_list: Array of allowed frequencies
631 # Space-separated list of frequencies in MHz to allow for selecting the BSS. If
632 # set, scan results that do not match any of the specified frequencies are not
633 # considered when selecting a BSS.
635 # This can also be set on the outside of the network block. In this case,
636 # it limits the frequencies that will be scanned.
638 # bgscan: Background scanning
639 # wpa_supplicant behavior for background scanning can be specified by
640 # configuring a bgscan module. These modules are responsible for requesting
641 # background scans for the purpose of roaming within an ESS (i.e., within a
642 # single network block with all the APs using the same SSID). The bgscan
643 # parameter uses following format: "<bgscan module name>:<module parameters>"
644 # Following bgscan modules are available:
645 # simple - Periodic background scans based on signal strength
646 # bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>:
648 # bgscan="simple:30:-45:300"
649 # learn - Learn channels used by the network and try to avoid bgscans on other
650 # channels (experimental)
651 # bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>:
652 # <long interval>[:<database file name>]"
653 # bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan"
654 # Explicitly disable bgscan by setting
657 # This option can also be set outside of all network blocks for the bgscan
658 # parameter to apply for all the networks that have no specific bgscan
661 # proto: list of accepted protocols
662 # WPA = WPA/IEEE 802.11i/D3.0
663 # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
664 # If not set, this defaults to: WPA RSN
666 # key_mgmt: list of accepted authenticated key management protocols
667 # WPA-PSK = WPA pre-shared key (this requires 'psk' field)
668 # WPA-EAP = WPA using EAP authentication
669 # IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
671 # NONE = WPA is not used; plaintext or static WEP could be used
672 # WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
673 # WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
674 # If not set, this defaults to: WPA-PSK WPA-EAP
676 # ieee80211w: whether management frame protection is enabled
677 # 0 = disabled (default unless changed with the global pmf parameter)
680 # The most common configuration options for this based on the PMF (protected
681 # management frames) certification program are:
682 # PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256
683 # PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256
684 # (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used)
686 # auth_alg: list of allowed IEEE 802.11 authentication algorithms
687 # OPEN = Open System authentication (required for WPA/WPA2)
688 # SHARED = Shared Key authentication (requires static WEP keys)
689 # LEAP = LEAP/Network EAP (only used with LEAP)
690 # If not set, automatic selection is used (Open System with LEAP enabled if
691 # LEAP is allowed as one of the EAP methods).
693 # pairwise: list of accepted pairwise (unicast) ciphers for WPA
694 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
695 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
696 # NONE = Use only Group Keys (deprecated, should not be included if APs support
698 # If not set, this defaults to: CCMP TKIP
700 # group: list of accepted group (broadcast/multicast) ciphers for WPA
701 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
702 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
703 # WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
704 # WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
705 # If not set, this defaults to: CCMP TKIP WEP104 WEP40
707 # psk: WPA preshared key; 256-bit pre-shared key
708 # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
709 # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
710 # generated using the passphrase and SSID). ASCII passphrase must be between
711 # 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
712 # be used to indicate that the PSK/passphrase is stored in external storage.
713 # This field is not needed, if WPA-EAP is used.
714 # Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
715 # from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
716 # startup and reconfiguration time can be optimized by generating the PSK only
717 # only when the passphrase or SSID has actually changed.
719 # eapol_flags: IEEE 802.1X/EAPOL options (bit field)
720 # Dynamic WEP key required for non-WPA mode
721 # bit0 (1): require dynamically generated unicast WEP key
722 # bit1 (2): require dynamically generated broadcast WEP key
723 # (3 = require both keys; default)
724 # Note: When using wired authentication (including macsec_qca driver),
725 # eapol_flags must be set to 0 for the authentication to be completed
728 # macsec_policy: IEEE 802.1X/MACsec options
729 # This determines how sessions are secured with MACsec. It is currently
730 # applicable only when using the macsec_qca driver interface.
731 # 0: MACsec not in use (default)
732 # 1: MACsec enabled - Should secure, accept key server's advice to
733 # determine whether to use a secure session or not.
735 # mixed_cell: This option can be used to configure whether so called mixed
736 # cells, i.e., networks that use both plaintext and encryption in the same
737 # SSID, are allowed when selecting a BSS from scan results.
738 # 0 = disabled (default)
741 # proactive_key_caching:
742 # Enable/disable opportunistic PMKSA caching for WPA2.
743 # 0 = disabled (default unless changed with the global okc parameter)
746 # wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
747 # hex without quotation, e.g., 0102030405)
748 # wep_tx_keyidx: Default WEP key index (TX) (0..3)
750 # peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
751 # allowed. This is only used with RSN/WPA2.
752 # 0 = disabled (default)
756 # wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
757 # enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
759 # Following fields are only used with internal EAP implementation.
760 # eap: space-separated list of accepted EAP methods
761 # MD5 = EAP-MD5 (unsecure and does not generate keying material ->
762 # cannot be used with WPA; to be used as a Phase 2 method
763 # with EAP-PEAP or EAP-TTLS)
764 # MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
765 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
766 # OTP = EAP-OTP (cannot be used separately with WPA; to be used
767 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
768 # GTC = EAP-GTC (cannot be used separately with WPA; to be used
769 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
770 # TLS = EAP-TLS (client and server certificate)
771 # PEAP = EAP-PEAP (with tunnelled EAP authentication)
772 # TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
774 # If not set, all compiled in methods are allowed.
776 # identity: Identity string for EAP
777 # This field is also used to configure user NAI for
778 # EAP-PSK/PAX/SAKE/GPSK.
779 # anonymous_identity: Anonymous identity string for EAP (to be used as the
780 # unencrypted identity with EAP types that support different tunnelled
781 # identity, e.g., EAP-TTLS). This field can also be used with
782 # EAP-SIM/AKA/AKA' to store the pseudonym identity.
783 # password: Password string for EAP. This field can include either the
784 # plaintext password (using ASCII or hex string) or a NtPasswordHash
785 # (16-byte MD4 hash of password) in hash:<32 hex digits> format.
786 # NtPasswordHash can only be used when the password is for MSCHAPv2 or
787 # MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
788 # EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
789 # PSK) is also configured using this field. For EAP-GPSK, this is a
790 # variable length PSK. ext:<name of external password field> format can
791 # be used to indicate that the password is stored in external storage.
792 # ca_cert: File path to CA certificate file (PEM/DER). This file can have one
793 # or more trusted CA certificates. If ca_cert and ca_path are not
794 # included, server certificate will not be verified. This is insecure and
795 # a trusted CA certificate should always be configured when using
796 # EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
797 # change when wpa_supplicant is run in the background.
799 # Alternatively, this can be used to only perform matching of the server
800 # certificate (SHA-256 hash of the DER encoded X.509 certificate). In
801 # this case, the possible CA certificates in the server certificate chain
802 # are ignored and only the server certificate is verified. This is
803 # configured with the following format:
804 # hash:://server/sha256/cert_hash_in_hex
805 # For example: "hash://server/sha256/
806 # 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
808 # On Windows, trusted CA certificates can be loaded from the system
809 # certificate store by setting this to cert_store://<name>, e.g.,
810 # ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
811 # Note that when running wpa_supplicant as an application, the user
812 # certificate store (My user account) is used, whereas computer store
813 # (Computer account) is used when running wpasvc as a service.
814 # ca_path: Directory path for CA certificate files (PEM). This path may
815 # contain multiple CA certificates in OpenSSL format. Common use for this
816 # is to point to system trusted CA list which is often installed into
817 # directory like /etc/ssl/certs. If configured, these certificates are
818 # added to the list of trusted CAs. ca_cert may also be included in that
819 # case, but it is not required.
820 # client_cert: File path to client certificate file (PEM/DER)
821 # Full path should be used since working directory may change when
822 # wpa_supplicant is run in the background.
823 # Alternatively, a named configuration blob can be used by setting this
824 # to blob://<blob name>.
825 # private_key: File path to client private key file (PEM/DER/PFX)
826 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
827 # commented out. Both the private key and certificate will be read from
828 # the PKCS#12 file in this case. Full path should be used since working
829 # directory may change when wpa_supplicant is run in the background.
830 # Windows certificate store can be used by leaving client_cert out and
831 # configuring private_key in one of the following formats:
832 # cert://substring_to_match
833 # hash://certificate_thumbprint_in_hex
834 # for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
835 # Note that when running wpa_supplicant as an application, the user
836 # certificate store (My user account) is used, whereas computer store
837 # (Computer account) is used when running wpasvc as a service.
838 # Alternatively, a named configuration blob can be used by setting this
839 # to blob://<blob name>.
840 # private_key_passwd: Password for private key file (if left out, this will be
841 # asked through control interface)
842 # dh_file: File path to DH/DSA parameters file (in PEM format)
843 # This is an optional configuration file for setting parameters for an
844 # ephemeral DH key exchange. In most cases, the default RSA
845 # authentication does not use this configuration. However, it is possible
846 # setup RSA to use ephemeral DH key exchange. In addition, ciphers with
847 # DSA keys always use ephemeral DH keys. This can be used to achieve
848 # forward secrecy. If the file is in DSA parameters format, it will be
849 # automatically converted into DH params.
850 # subject_match: Substring to be matched against the subject of the
851 # authentication server certificate. If this string is set, the server
852 # sertificate is only accepted if it contains this string in the subject.
853 # The subject string is in following format:
854 # /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
855 # altsubject_match: Semicolon separated string of entries to be matched against
856 # the alternative subject name of the authentication server certificate.
857 # If this string is set, the server sertificate is only accepted if it
858 # contains one of the entries in an alternative subject name extension.
859 # altSubjectName string is in following format: TYPE:VALUE
860 # Example: EMAIL:server@example.com
861 # Example: DNS:server.example.com;DNS:server2.example.com
862 # Following types are supported: EMAIL, DNS, URI
863 # phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
864 # (string with field-value pairs, e.g., "peapver=0" or
865 # "peapver=1 peaplabel=1")
866 # 'peapver' can be used to force which PEAP version (0 or 1) is used.
867 # 'peaplabel=1' can be used to force new label, "client PEAP encryption",
868 # to be used during key derivation when PEAPv1 or newer. Most existing
869 # PEAPv1 implementation seem to be using the old label, "client EAP
870 # encryption", and wpa_supplicant is now using that as the default value.
871 # Some servers, e.g., Radiator, may require peaplabel=1 configuration to
872 # interoperate with PEAPv1; see eap_testing.txt for more details.
873 # 'peap_outer_success=0' can be used to terminate PEAP authentication on
874 # tunneled EAP-Success. This is required with some RADIUS servers that
875 # implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
876 # Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
877 # include_tls_length=1 can be used to force wpa_supplicant to include
878 # TLS Message Length field in all TLS messages even if they are not
880 # sim_min_num_chal=3 can be used to configure EAP-SIM to require three
881 # challenges (by default, it accepts 2 or 3)
882 # result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
883 # protected result indication.
884 # 'crypto_binding' option can be used to control PEAPv0 cryptobinding
886 # * 0 = do not use cryptobinding (default)
887 # * 1 = use cryptobinding if server supports it
888 # * 2 = require cryptobinding
889 # EAP-WSC (WPS) uses following options: pin=<Device Password> or
891 # phase2: Phase2 (inner authentication with TLS tunnel) parameters
892 # (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
893 # "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
895 # TLS-based methods can use the following parameters to control TLS behavior
896 # (these are normally in the phase1 parameter, but can be used also in the
897 # phase2 parameter when EAP-TLS is used within the inner tunnel):
898 # tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the
899 # TLS library, these may be disabled by default to enforce stronger
901 # tls_disable_time_checks=1 - ignore certificate validity time (this requests
902 # the TLS library to accept certificates even if they are not currently
903 # valid, i.e., have expired or have not yet become valid; this should be
904 # used only for testing purposes)
905 # tls_disable_session_ticket=1 - disable TLS Session Ticket extension
906 # tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used
907 # Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS
908 # as a workaround for broken authentication server implementations unless
909 # EAP workarounds are disabled with eap_workarounds=0.
910 # For EAP-FAST, this must be set to 0 (or left unconfigured for the
911 # default value to be used automatically).
912 # tls_disable_tlsv1_1=1 - disable use of TLSv1.1 (a workaround for AAA servers
913 # that have issues interoperating with updated TLS version)
914 # tls_disable_tlsv1_2=1 - disable use of TLSv1.2 (a workaround for AAA servers
915 # that have issues interoperating with updated TLS version)
917 # Following certificate/private key fields are used in inner Phase2
918 # authentication when using EAP-TTLS or EAP-PEAP.
919 # ca_cert2: File path to CA certificate file. This file can have one or more
920 # trusted CA certificates. If ca_cert2 and ca_path2 are not included,
921 # server certificate will not be verified. This is insecure and a trusted
922 # CA certificate should always be configured.
923 # ca_path2: Directory path for CA certificate files (PEM)
924 # client_cert2: File path to client certificate file
925 # private_key2: File path to client private key file
926 # private_key2_passwd: Password for private key file
927 # dh_file2: File path to DH/DSA parameters file (in PEM format)
928 # subject_match2: Substring to be matched against the subject of the
929 # authentication server certificate.
930 # altsubject_match2: Substring to be matched against the alternative subject
931 # name of the authentication server certificate.
933 # fragment_size: Maximum EAP fragment size in bytes (default 1398).
934 # This value limits the fragment size for EAP methods that support
935 # fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
936 # small enough to make the EAP messages fit in MTU of the network
937 # interface used for EAPOL. The default value is suitable for most
940 # ocsp: Whether to use/require OCSP to check server certificate
941 # 0 = do not use OCSP stapling (TLS certificate status extension)
942 # 1 = try to use OCSP stapling, but not require response
943 # 2 = require valid OCSP stapling response
945 # openssl_ciphers: OpenSSL specific cipher configuration
946 # This can be used to override the global openssl_ciphers configuration
947 # parameter (see above).
949 # EAP-FAST variables:
950 # pac_file: File path for the PAC entries. wpa_supplicant will need to be able
951 # to create this file and write updates to it when PAC is being
952 # provisioned or refreshed. Full path to the file should be used since
953 # working directory may change when wpa_supplicant is run in the
954 # background. Alternatively, a named configuration blob can be used by
955 # setting this to blob://<blob name>
956 # phase1: fast_provisioning option can be used to enable in-line provisioning
957 # of EAP-FAST credentials (PAC):
959 # 1 = allow unauthenticated provisioning,
960 # 2 = allow authenticated provisioning,
961 # 3 = allow both unauthenticated and authenticated provisioning
962 # fast_max_pac_list_len=<num> option can be used to set the maximum
963 # number of PAC entries to store in a PAC list (default: 10)
964 # fast_pac_format=binary option can be used to select binary format for
965 # storing PAC entries in order to save some space (the default
966 # text format uses about 2.5 times the size of minimal binary
969 # wpa_supplicant supports number of "EAP workarounds" to work around
970 # interoperability issues with incorrectly behaving authentication servers.
971 # These are enabled by default because some of the issues are present in large
972 # number of authentication servers. Strict EAP conformance mode can be
973 # configured by disabling workarounds with eap_workaround=0.
975 # Station inactivity limit
977 # If a station does not send anything in ap_max_inactivity seconds, an
978 # empty data frame is sent to it in order to verify whether it is
979 # still in range. If this frame is not ACKed, the station will be
980 # disassociated and then deauthenticated. This feature is used to
981 # clear station table of old entries when the STAs move out of the
984 # The station can associate again with the AP if it is still in range;
985 # this inactivity poll is just used as a nicer way of verifying
986 # inactivity; i.e., client will not report broken connection because
987 # disassociation frame is not sent immediately without first polling
988 # the STA with a data frame.
989 # default: 300 (i.e., 5 minutes)
990 #ap_max_inactivity=300
992 # DTIM period in Beacon intervals for AP mode (default: 2)
995 # Beacon interval (default: 100 TU)
999 # 0 = use permanent MAC address
1000 # 1 = use random MAC address for each ESS connection
1001 # 2 = like 1, but maintain OUI (with local admin bit set)
1004 # disable_ht: Whether HT (802.11n) should be disabled.
1005 # 0 = HT enabled (if AP supports it)
1008 # disable_ht40: Whether HT-40 (802.11n) should be disabled.
1009 # 0 = HT-40 enabled (if AP supports it)
1010 # 1 = HT-40 disabled
1012 # disable_sgi: Whether SGI (short guard interval) should be disabled.
1013 # 0 = SGI enabled (if AP supports it)
1016 # disable_ldpc: Whether LDPC should be disabled.
1017 # 0 = LDPC enabled (if AP supports it)
1020 # ht40_intolerant: Whether 40 MHz intolerant should be indicated.
1021 # 0 = 40 MHz tolerant (default)
1022 # 1 = 40 MHz intolerant
1024 # ht_mcs: Configure allowed MCS rates.
1025 # Parsed as an array of bytes, in base-16 (ascii-hex)
1026 # ht_mcs="" // Use all available (default)
1027 # ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only
1028 # ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only
1030 # disable_max_amsdu: Whether MAX_AMSDU should be disabled.
1031 # -1 = Do not make any changes.
1032 # 0 = Enable MAX-AMSDU if hardware supports it.
1035 # ampdu_factor: Maximum A-MPDU Length Exponent
1036 # Value: 0-3, see 7.3.2.56.3 in IEEE Std 802.11n-2009.
1038 # ampdu_density: Allow overriding AMPDU density configuration.
1039 # Treated as hint by the kernel.
1040 # -1 = Do not make any changes.
1041 # 0-3 = Set AMPDU density (aka factor) to specified value.
1043 # disable_vht: Whether VHT should be disabled.
1044 # 0 = VHT enabled (if AP supports it)
1047 # vht_capa: VHT capabilities to set in the override
1048 # vht_capa_mask: mask of VHT capabilities
1050 # vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8
1051 # vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8
1059 # Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
1062 psk="very secret passphrase"
1066 # Same as previous, but request SSID-specific scanning (for APs that reject
1071 psk="very secret passphrase"
1075 # Only WPA-PSK is used. Any valid cipher combination is accepted.
1081 group=CCMP TKIP WEP104 WEP40
1082 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1086 # WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
1093 psk="not so secure passphrase"
1097 # Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
1098 # or WEP40 as the group cipher will not be accepted.
1106 identity="user@example.com"
1107 ca_cert="/etc/cert/ca.pem"
1108 client_cert="/etc/cert/user.pem"
1109 private_key="/etc/cert/user.prv"
1110 private_key_passwd="password"
1114 # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
1120 identity="user@example.com"
1122 ca_cert="/etc/cert/ca.pem"
1123 phase1="peaplabel=1"
1124 phase2="auth=MSCHAPV2"
1128 # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
1129 # unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
1134 identity="user@example.com"
1135 anonymous_identity="anonymous@example.com"
1137 ca_cert="/etc/cert/ca.pem"
1141 # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
1142 # use. Real identity is sent only within an encrypted TLS tunnel.
1147 identity="user@example.com"
1148 anonymous_identity="anonymous@example.com"
1150 ca_cert="/etc/cert/ca.pem"
1151 phase2="auth=MSCHAPV2"
1154 # WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
1160 # Phase1 / outer authentication
1161 anonymous_identity="anonymous@example.com"
1162 ca_cert="/etc/cert/ca.pem"
1163 # Phase 2 / inner authentication
1164 phase2="autheap=TLS"
1165 ca_cert2="/etc/cert/ca2.pem"
1166 client_cert2="/etc/cer/user.pem"
1167 private_key2="/etc/cer/user.prv"
1168 private_key2_passwd="password"
1172 # Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
1176 bssid=00:11:22:33:44:55
1178 key_mgmt=WPA-PSK WPA-EAP
1181 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
1184 # Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
1185 # and all valid ciphers.
1188 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
1192 # EAP-SIM with a GSM SIM or USIM
1207 anonymous_identity="eap_psk_user"
1208 password=06b4be19da289f475aa46a33cb793029
1209 identity="eap_psk_user@example.com"
1213 # IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
1214 # EAP-TLS for authentication and key generation; require both unicast and
1215 # broadcast WEP keys.
1220 identity="user@example.com"
1221 ca_cert="/etc/cert/ca.pem"
1222 client_cert="/etc/cert/user.pem"
1223 private_key="/etc/cert/user.prv"
1224 private_key_passwd="password"
1229 # LEAP with dynamic WEP keys
1238 # EAP-IKEv2 using shared secrets for both server and peer authentication
1240 ssid="ikev2-example"
1247 # EAP-FAST with WPA (WPA or WPA2)
1249 ssid="eap-fast-test"
1252 anonymous_identity="FAST-000102030405"
1255 phase1="fast_provisioning=1"
1256 pac_file="/etc/wpa_supplicant.eap-fast-pac"
1260 ssid="eap-fast-test"
1263 anonymous_identity="FAST-000102030405"
1266 phase1="fast_provisioning=1"
1267 pac_file="blob://eap-fast-pac"
1270 # Plaintext connection (no WPA, no IEEE 802.1X)
1272 ssid="plaintext-test"
1277 # Shared WEP key connection (no WPA, no IEEE 802.1X)
1279 ssid="static-wep-test"
1283 wep_key2="1234567890123"
1289 # Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
1290 # IEEE 802.11 authentication
1292 ssid="static-wep-test2"
1296 wep_key2="1234567890123"
1303 # IBSS/ad-hoc network with RSN
1315 # IBSS/ad-hoc network with WPA-None/TKIP (deprecated)
1324 psk="secret passphrase"
1328 # Catch all example that allows more or less all configuration modes
1332 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
1334 group=CCMP TKIP WEP104 WEP40
1335 psk="very secret passphrase"
1337 identity="user@example.com"
1339 ca_cert="/etc/cert/ca.pem"
1340 client_cert="/etc/cert/user.pem"
1341 private_key="/etc/cert/user.prv"
1342 private_key_passwd="password"
1343 phase1="peaplabel=0"
1346 # Example of EAP-TLS with smartcard (openssl engine)
1354 identity="user@example.com"
1355 ca_cert="/etc/cert/ca.pem"
1356 client_cert="/etc/cert/user.pem"
1360 # The engine configured here must be available. Look at
1361 # OpenSSL engine support in the global section.
1362 # The key available through the engine must be the private key
1363 # matching the client certificate configured above.
1365 # use the opensc engine
1369 # use the pkcs11 engine
1373 # Optional PIN configuration; this can be left out and PIN will be
1374 # asked through the control interface
1378 # Example configuration showing how to use an inlined blob as a CA certificate
1379 # data instead of using external file
1384 identity="user@example.com"
1385 anonymous_identity="anonymous@example.com"
1387 ca_cert="blob://exampleblob"
1391 blob-base64-exampleblob={
1392 SGVsbG8gV29ybGQhCg==
1396 # Wildcard match for SSID (plaintext APs only). This example select any
1397 # open AP regardless of its SSID.
1403 # Example config file that will only scan on channel 36.
1410 # Example MACsec configuration
1412 # key_mgmt=IEEE8021X
1415 # anonymous_identity="anonymous@example.com"
1416 # identity="user@example.com"
1417 # password="secretr"
1418 # ca_cert="/etc/cert/ca.pem"