1 ##### Example wpa_supplicant configuration file ###############################
3 # ***** Please check wpa_supplicant.conf(5) for details on these options *****
5 # This file describes configuration file format and lists all available option.
6 # Please also take a look at simpler configuration examples in 'examples'
9 # Empty lines and lines starting with # are ignored
11 # NOTE! This file may contain password information and should probably be made
12 # readable only by root user on multiuser systems.
14 # Note: All file paths in this configuration file should use full (absolute,
15 # not relative to working directory) path in order to allow working directory
16 # to be changed. This can happen if wpa_supplicant is run in the background.
18 # Whether to allow wpa_supplicant to update (overwrite) configuration
20 # This option can be used to allow wpa_supplicant to overwrite configuration
21 # file whenever configuration is changed (e.g., new network block is added with
22 # wpa_cli or wpa_gui, or a password is changed). This is required for
23 # wpa_cli/wpa_gui to be able to store the configuration changes permanently.
24 # Please note that overwriting configuration file will remove the comments from
28 # global configuration (shared by all network blocks)
30 # Parameters for the control interface. If this is specified, wpa_supplicant
31 # will open a control interface that is available for external programs to
32 # manage wpa_supplicant. The meaning of this string depends on which control
33 # interface mechanism is used. For all cases, the existance of this parameter
34 # in configuration is used to determine whether the control interface is
37 # For UNIX domain sockets (default on Linux and BSD): This is a directory that
38 # will be created for UNIX domain sockets for listening to requests from
39 # external programs (CLI/GUI, etc.) for status information and configuration.
40 # The socket file will be named based on the interface name, so multiple
41 # wpa_supplicant processes can be run at the same time if more than one
43 # /var/run/wpa_supplicant is the recommended directory for sockets and by
44 # default, wpa_cli will use it when trying to connect with wpa_supplicant.
46 # Access control for the control interface can be configured by setting the
47 # directory to allow only members of a group to use sockets. This way, it is
48 # possible to run wpa_supplicant as root (since it needs to change network
49 # configuration and open raw sockets) and still allow GUI/CLI components to be
50 # run as non-root users. However, since the control interface can be used to
51 # change the network configuration, this access needs to be protected in many
52 # cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
53 # want to allow non-root users to use the control interface, add a new group
54 # and change this value to match with that group. Add users that should have
55 # control interface access to this group. If this variable is commented out or
56 # not included in the configuration file, group will not be changed from the
57 # value it got by default when the directory or socket was created.
59 # When configuring both the directory and group, use following format:
60 # DIR=/var/run/wpa_supplicant GROUP=wheel
61 # DIR=/var/run/wpa_supplicant GROUP=0
62 # (group can be either group name or gid)
64 ctrl_interface=/var/run/wpa_supplicant
66 # IEEE 802.1X/EAPOL version
67 # wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
68 # EAPOL version 2. However, there are many APs that do not handle the new
69 # version number correctly (they seem to drop the frames completely). In order
70 # to make wpa_supplicant interoperate with these APs, the version number is set
71 # to 1 by default. This configuration value can be used to set it to the new
75 # AP scanning/selection
76 # By default, wpa_supplicant requests driver to perform AP scanning and then
77 # uses the scan results to select a suitable AP. Another alternative is to
78 # allow the driver to take care of AP scanning and selection and use
79 # wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
80 # information from the driver.
81 # 1: wpa_supplicant initiates scanning and AP selection
82 # 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
83 # parameters (e.g., WPA IE generation); this mode can also be used with
84 # non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
85 # APs (i.e., external program needs to control association). This mode must
86 # also be used when using wired Ethernet drivers.
87 # 2: like 0, but associate with APs using security policy and SSID (but not
88 # BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
89 # enable operation with hidden SSIDs and optimized roaming; in this mode,
90 # the network blocks in the configuration file are tried one by one until
91 # the driver reports successful association; each network block should have
92 # explicit security policy (i.e., only one option in the lists) for
93 # key_mgmt, pairwise, group, proto variables
95 # For use in FreeBSD with the wlan module ap_scan must be set to 1.
98 # EAP fast re-authentication
99 # By default, fast re-authentication is enabled for all EAP methods that
100 # support it. This variable can be used to disable fast re-authentication.
101 # Normally, there is no need to disable this.
104 # OpenSSL Engine support
105 # These options can be used to load OpenSSL engines.
106 # The two engines that are supported currently are shown below:
107 # They are both from the opensc project (http://www.opensc.org/)
108 # By default no engines are loaded.
109 # make the opensc engine available
110 #opensc_engine_path=/usr/lib/opensc/engine_opensc.so
111 # make the pkcs11 engine available
112 #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
113 # configure the path to the pkcs11 module required by the pkcs11 engine
114 #pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
116 # Dynamic EAP methods
117 # If EAP methods were built dynamically as shared object files, they need to be
118 # loaded here before being used in the network blocks. By default, EAP methods
119 # are included statically in the build, so these lines are not needed
120 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
121 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
123 # Driver interface parameters
124 # This field can be used to configure arbitrary driver interace parameters. The
125 # format is specific to the selected driver interface. This field is not used
127 #driver_param="field=value"
130 # The ISO/IEC alpha2 country code for the country in which this device is
131 # currently operating.
134 # Maximum lifetime for PMKSA in seconds; default 43200
135 #dot11RSNAConfigPMKLifetime=43200
136 # Threshold for reauthentication (percentage of PMK lifetime); default 70
137 #dot11RSNAConfigPMKReauthThreshold=70
138 # Timeout for security association negotiation in seconds; default 60
139 #dot11RSNAConfigSATimeout=60
141 # Wi-Fi Protected Setup (WPS) parameters
143 # Universally Unique IDentifier (UUID; see RFC 4122) of the device
144 # If not configured, UUID will be generated based on the local MAC address.
145 #uuid=12345678-9abc-def0-1234-56789abcdef0
148 # User-friendly description of device; up to 32 octets encoded in UTF-8
149 #device_name=Wireless Client
152 # The manufacturer of the device (up to 64 ASCII characters)
153 #manufacturer=Company
156 # Model of the device (up to 32 ASCII characters)
160 # Additional device description (up to 32 ASCII characters)
164 # Serial number of the device (up to 32 characters)
167 # Primary Device Type
168 # Used format: <categ>-<OUI>-<subcateg>
169 # categ = Category as an integer value
170 # OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
172 # subcateg = OUI-specific Sub Category as an integer value
174 # 1-0050F204-1 (Computer / PC)
175 # 1-0050F204-2 (Computer / Server)
176 # 5-0050F204-1 (Storage / NAS)
177 # 6-0050F204-1 (Network Infrastructure / AP)
178 #device_type=1-0050F204-1
181 # 4-octet operating system version number (hex string)
184 # Credential processing
185 # 0 = process received credentials internally (default)
186 # 1 = do not process received credentials; just pass them over ctrl_iface to
187 # external program(s)
188 # 2 = process received credentials internally and pass them over ctrl_iface
189 # to external program(s)
190 #wps_cred_processing=0
194 # Each network (usually AP's sharing the same SSID) is configured as a separate
195 # block in this configuration file. The network blocks are in preference order
196 # (the first match is used).
198 # network block fields:
201 # 0 = this network can be used (default)
202 # 1 = this network block is disabled (can be enabled through ctrl_iface,
203 # e.g., with wpa_cli or wpa_gui)
205 # id_str: Network identifier string for external scripts. This value is passed
206 # to external action script through wpa_cli as WPA_ID_STR environment
207 # variable to make it easier to do network specific configuration.
209 # ssid: SSID (mandatory); either as an ASCII string with double quotation or
210 # as hex string; network name
213 # 0 = do not scan this SSID with specific Probe Request frames (default)
214 # 1 = scan with SSID-specific Probe Request frames (this can be used to
215 # find APs that hide (do not broadcast) SSID or use multiple SSIDs;
216 # this will add latency to scanning, so enable this only when needed)
218 # bssid: BSSID (optional); if set, this network block is used only when
219 # associating with the AP using the configured BSSID
221 # priority: priority group (integer)
222 # By default, all networks will get same priority group (0). If some of the
223 # networks are more desirable, this field can be used to change the order in
224 # which wpa_supplicant goes through the networks when selecting a BSS. The
225 # priority groups will be iterated in decreasing priority (i.e., the larger the
226 # priority value, the sooner the network is matched against the scan results).
227 # Within each priority group, networks will be selected based on security
228 # policy, signal strength, etc.
229 # Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
230 # using this priority to select the order for scanning. Instead, they try the
231 # networks in the order that they are listed in the configuration file.
233 # mode: IEEE 802.11 operation mode
234 # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
235 # 1 = IBSS (ad-hoc, peer-to-peer)
236 # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
237 # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
238 # to be set to 2 for IBSS. WPA-None requires following network block options:
239 # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
240 # both), and psk must also be set.
242 # frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
243 # 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
244 # channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
245 # In addition, this value is only used by the station that creates the IBSS. If
246 # an IBSS network with the configured SSID is already present, the frequency of
247 # the network will be used instead of this configured value.
249 # proto: list of accepted protocols
250 # WPA = WPA/IEEE 802.11i/D3.0
251 # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
252 # If not set, this defaults to: WPA RSN
254 # key_mgmt: list of accepted authenticated key management protocols
255 # WPA-PSK = WPA pre-shared key (this requires 'psk' field)
256 # WPA-EAP = WPA using EAP authentication
257 # IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
259 # NONE = WPA is not used; plaintext or static WEP could be used
260 # WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
261 # WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
262 # If not set, this defaults to: WPA-PSK WPA-EAP
264 # auth_alg: list of allowed IEEE 802.11 authentication algorithms
265 # OPEN = Open System authentication (required for WPA/WPA2)
266 # SHARED = Shared Key authentication (requires static WEP keys)
267 # LEAP = LEAP/Network EAP (only used with LEAP)
268 # If not set, automatic selection is used (Open System with LEAP enabled if
269 # LEAP is allowed as one of the EAP methods).
271 # pairwise: list of accepted pairwise (unicast) ciphers for WPA
272 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
273 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
274 # NONE = Use only Group Keys (deprecated, should not be included if APs support
276 # If not set, this defaults to: CCMP TKIP
278 # group: list of accepted group (broadcast/multicast) ciphers for WPA
279 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
280 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
281 # WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
282 # WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
283 # If not set, this defaults to: CCMP TKIP WEP104 WEP40
285 # psk: WPA preshared key; 256-bit pre-shared key
286 # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
287 # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
288 # generated using the passphrase and SSID). ASCII passphrase must be between
289 # 8 and 63 characters (inclusive).
290 # This field is not needed, if WPA-EAP is used.
291 # Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
292 # from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
293 # startup and reconfiguration time can be optimized by generating the PSK only
294 # only when the passphrase or SSID has actually changed.
296 # eapol_flags: IEEE 802.1X/EAPOL options (bit field)
297 # Dynamic WEP key required for non-WPA mode
298 # bit0 (1): require dynamically generated unicast WEP key
299 # bit1 (2): require dynamically generated broadcast WEP key
300 # (3 = require both keys; default)
301 # Note: When using wired authentication, eapol_flags must be set to 0 for the
302 # authentication to be completed successfully.
304 # mixed_cell: This option can be used to configure whether so called mixed
305 # cells, i.e., networks that use both plaintext and encryption in the same
306 # SSID, are allowed when selecting a BSS form scan results.
307 # 0 = disabled (default)
310 # proactive_key_caching:
311 # Enable/disable opportunistic PMKSA caching for WPA2.
312 # 0 = disabled (default)
315 # wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
316 # hex without quotation, e.g., 0102030405)
317 # wep_tx_keyidx: Default WEP key index (TX) (0..3)
319 # peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
320 # allowed. This is only used with RSN/WPA2.
321 # 0 = disabled (default)
325 # wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
326 # enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
328 # Following fields are only used with internal EAP implementation.
329 # eap: space-separated list of accepted EAP methods
330 # MD5 = EAP-MD5 (unsecure and does not generate keying material ->
331 # cannot be used with WPA; to be used as a Phase 2 method
332 # with EAP-PEAP or EAP-TTLS)
333 # MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
334 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
335 # OTP = EAP-OTP (cannot be used separately with WPA; to be used
336 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
337 # GTC = EAP-GTC (cannot be used separately with WPA; to be used
338 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
339 # TLS = EAP-TLS (client and server certificate)
340 # PEAP = EAP-PEAP (with tunnelled EAP authentication)
341 # TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
343 # If not set, all compiled in methods are allowed.
345 # identity: Identity string for EAP
346 # This field is also used to configure user NAI for
347 # EAP-PSK/PAX/SAKE/GPSK.
348 # anonymous_identity: Anonymous identity string for EAP (to be used as the
349 # unencrypted identity with EAP types that support different tunnelled
350 # identity, e.g., EAP-TTLS)
351 # password: Password string for EAP. This field can include either the
352 # plaintext password (using ASCII or hex string) or a NtPasswordHash
353 # (16-byte MD4 hash of password) in hash:<32 hex digits> format.
354 # NtPasswordHash can only be used when the password is for MSCHAPv2 or
355 # MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
356 # EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
357 # PSK) is also configured using this field. For EAP-GPSK, this is a
358 # variable length PSK.
359 # ca_cert: File path to CA certificate file (PEM/DER). This file can have one
360 # or more trusted CA certificates. If ca_cert and ca_path are not
361 # included, server certificate will not be verified. This is insecure and
362 # a trusted CA certificate should always be configured when using
363 # EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
364 # change when wpa_supplicant is run in the background.
365 # On Windows, trusted CA certificates can be loaded from the system
366 # certificate store by setting this to cert_store://<name>, e.g.,
367 # ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
368 # Note that when running wpa_supplicant as an application, the user
369 # certificate store (My user account) is used, whereas computer store
370 # (Computer account) is used when running wpasvc as a service.
371 # ca_path: Directory path for CA certificate files (PEM). This path may
372 # contain multiple CA certificates in OpenSSL format. Common use for this
373 # is to point to system trusted CA list which is often installed into
374 # directory like /etc/ssl/certs. If configured, these certificates are
375 # added to the list of trusted CAs. ca_cert may also be included in that
376 # case, but it is not required.
377 # client_cert: File path to client certificate file (PEM/DER)
378 # Full path should be used since working directory may change when
379 # wpa_supplicant is run in the background.
380 # Alternatively, a named configuration blob can be used by setting this
381 # to blob://<blob name>.
382 # private_key: File path to client private key file (PEM/DER/PFX)
383 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
384 # commented out. Both the private key and certificate will be read from
385 # the PKCS#12 file in this case. Full path should be used since working
386 # directory may change when wpa_supplicant is run in the background.
387 # Windows certificate store can be used by leaving client_cert out and
388 # configuring private_key in one of the following formats:
389 # cert://substring_to_match
390 # hash://certificate_thumbprint_in_hex
391 # for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
392 # Note that when running wpa_supplicant as an application, the user
393 # certificate store (My user account) is used, whereas computer store
394 # (Computer account) is used when running wpasvc as a service.
395 # Alternatively, a named configuration blob can be used by setting this
396 # to blob://<blob name>.
397 # private_key_passwd: Password for private key file (if left out, this will be
398 # asked through control interface)
399 # dh_file: File path to DH/DSA parameters file (in PEM format)
400 # This is an optional configuration file for setting parameters for an
401 # ephemeral DH key exchange. In most cases, the default RSA
402 # authentication does not use this configuration. However, it is possible
403 # setup RSA to use ephemeral DH key exchange. In addition, ciphers with
404 # DSA keys always use ephemeral DH keys. This can be used to achieve
405 # forward secrecy. If the file is in DSA parameters format, it will be
406 # automatically converted into DH params.
407 # subject_match: Substring to be matched against the subject of the
408 # authentication server certificate. If this string is set, the server
409 # sertificate is only accepted if it contains this string in the subject.
410 # The subject string is in following format:
411 # /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
412 # altsubject_match: Semicolon separated string of entries to be matched against
413 # the alternative subject name of the authentication server certificate.
414 # If this string is set, the server sertificate is only accepted if it
415 # contains one of the entries in an alternative subject name extension.
416 # altSubjectName string is in following format: TYPE:VALUE
417 # Example: EMAIL:server@example.com
418 # Example: DNS:server.example.com;DNS:server2.example.com
419 # Following types are supported: EMAIL, DNS, URI
420 # phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
421 # (string with field-value pairs, e.g., "peapver=0" or
422 # "peapver=1 peaplabel=1")
423 # 'peapver' can be used to force which PEAP version (0 or 1) is used.
424 # 'peaplabel=1' can be used to force new label, "client PEAP encryption",
425 # to be used during key derivation when PEAPv1 or newer. Most existing
426 # PEAPv1 implementation seem to be using the old label, "client EAP
427 # encryption", and wpa_supplicant is now using that as the default value.
428 # Some servers, e.g., Radiator, may require peaplabel=1 configuration to
429 # interoperate with PEAPv1; see eap_testing.txt for more details.
430 # 'peap_outer_success=0' can be used to terminate PEAP authentication on
431 # tunneled EAP-Success. This is required with some RADIUS servers that
432 # implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
433 # Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
434 # include_tls_length=1 can be used to force wpa_supplicant to include
435 # TLS Message Length field in all TLS messages even if they are not
437 # sim_min_num_chal=3 can be used to configure EAP-SIM to require three
438 # challenges (by default, it accepts 2 or 3)
439 # result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
440 # protected result indication.
441 # 'crypto_binding' option can be used to control PEAPv0 cryptobinding
443 # * 0 = do not use cryptobinding (default)
444 # * 1 = use cryptobinding if server supports it
445 # * 2 = require cryptobinding
446 # EAP-WSC (WPS) uses following options: pin=<Device Password> or
448 # phase2: Phase2 (inner authentication with TLS tunnel) parameters
449 # (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
450 # "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
451 # Following certificate/private key fields are used in inner Phase2
452 # authentication when using EAP-TTLS or EAP-PEAP.
453 # ca_cert2: File path to CA certificate file. This file can have one or more
454 # trusted CA certificates. If ca_cert2 and ca_path2 are not included,
455 # server certificate will not be verified. This is insecure and a trusted
456 # CA certificate should always be configured.
457 # ca_path2: Directory path for CA certificate files (PEM)
458 # client_cert2: File path to client certificate file
459 # private_key2: File path to client private key file
460 # private_key2_passwd: Password for private key file
461 # dh_file2: File path to DH/DSA parameters file (in PEM format)
462 # subject_match2: Substring to be matched against the subject of the
463 # authentication server certificate.
464 # altsubject_match2: Substring to be matched against the alternative subject
465 # name of the authentication server certificate.
467 # fragment_size: Maximum EAP fragment size in bytes (default 1398).
468 # This value limits the fragment size for EAP methods that support
469 # fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
470 # small enough to make the EAP messages fit in MTU of the network
471 # interface used for EAPOL. The default value is suitable for most
474 # EAP-FAST variables:
475 # pac_file: File path for the PAC entries. wpa_supplicant will need to be able
476 # to create this file and write updates to it when PAC is being
477 # provisioned or refreshed. Full path to the file should be used since
478 # working directory may change when wpa_supplicant is run in the
479 # background. Alternatively, a named configuration blob can be used by
480 # setting this to blob://<blob name>
481 # phase1: fast_provisioning option can be used to enable in-line provisioning
482 # of EAP-FAST credentials (PAC):
484 # 1 = allow unauthenticated provisioning,
485 # 2 = allow authenticated provisioning,
486 # 3 = allow both unauthenticated and authenticated provisioning
487 # fast_max_pac_list_len=<num> option can be used to set the maximum
488 # number of PAC entries to store in a PAC list (default: 10)
489 # fast_pac_format=binary option can be used to select binary format for
490 # storing PAC entries in order to save some space (the default
491 # text format uses about 2.5 times the size of minimal binary
494 # wpa_supplicant supports number of "EAP workarounds" to work around
495 # interoperability issues with incorrectly behaving authentication servers.
496 # These are enabled by default because some of the issues are present in large
497 # number of authentication servers. Strict EAP conformance mode can be
498 # configured by disabling workarounds with eap_workaround=0.
502 # Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
505 psk="very secret passphrase"
509 # Same as previous, but request SSID-specific scanning (for APs that reject
514 psk="very secret passphrase"
518 # Only WPA-PSK is used. Any valid cipher combination is accepted.
524 group=CCMP TKIP WEP104 WEP40
525 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
529 # WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
536 psk="not so secure passphrase"
540 # Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
541 # or WEP40 as the group cipher will not be accepted.
549 identity="user@example.com"
550 ca_cert="/etc/cert/ca.pem"
551 client_cert="/etc/cert/user.pem"
552 private_key="/etc/cert/user.prv"
553 private_key_passwd="password"
557 # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
563 identity="user@example.com"
565 ca_cert="/etc/cert/ca.pem"
567 phase2="auth=MSCHAPV2"
571 # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
572 # unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
577 identity="user@example.com"
578 anonymous_identity="anonymous@example.com"
580 ca_cert="/etc/cert/ca.pem"
584 # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
585 # use. Real identity is sent only within an encrypted TLS tunnel.
590 identity="user@example.com"
591 anonymous_identity="anonymous@example.com"
593 ca_cert="/etc/cert/ca.pem"
594 phase2="auth=MSCHAPV2"
597 # WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
603 # Phase1 / outer authentication
604 anonymous_identity="anonymous@example.com"
605 ca_cert="/etc/cert/ca.pem"
606 # Phase 2 / inner authentication
608 ca_cert2="/etc/cert/ca2.pem"
609 client_cert2="/etc/cer/user.pem"
610 private_key2="/etc/cer/user.prv"
611 private_key2_passwd="password"
615 # Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
619 bssid=00:11:22:33:44:55
621 key_mgmt=WPA-PSK WPA-EAP
624 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
627 # Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
628 # and all valid ciphers.
631 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
635 # EAP-SIM with a GSM SIM or USIM
650 anonymous_identity="eap_psk_user"
651 password=06b4be19da289f475aa46a33cb793029
652 identity="eap_psk_user@example.com"
656 # IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
657 # EAP-TLS for authentication and key generation; require both unicast and
658 # broadcast WEP keys.
663 identity="user@example.com"
664 ca_cert="/etc/cert/ca.pem"
665 client_cert="/etc/cert/user.pem"
666 private_key="/etc/cert/user.prv"
667 private_key_passwd="password"
672 # LEAP with dynamic WEP keys
681 # EAP-IKEv2 using shared secrets for both server and peer authentication
690 # EAP-FAST with WPA (WPA or WPA2)
695 anonymous_identity="FAST-000102030405"
698 phase1="fast_provisioning=1"
699 pac_file="/etc/wpa_supplicant.eap-fast-pac"
706 anonymous_identity="FAST-000102030405"
709 phase1="fast_provisioning=1"
710 pac_file="blob://eap-fast-pac"
713 # Plaintext connection (no WPA, no IEEE 802.1X)
715 ssid="plaintext-test"
720 # Shared WEP key connection (no WPA, no IEEE 802.1X)
722 ssid="static-wep-test"
726 wep_key2="1234567890123"
732 # Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
733 # IEEE 802.11 authentication
735 ssid="static-wep-test2"
739 wep_key2="1234567890123"
746 # IBSS/ad-hoc network with WPA-None/TKIP.
755 psk="secret passphrase"
759 # Catch all example that allows more or less all configuration modes
763 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
765 group=CCMP TKIP WEP104 WEP40
766 psk="very secret passphrase"
768 identity="user@example.com"
770 ca_cert="/etc/cert/ca.pem"
771 client_cert="/etc/cert/user.pem"
772 private_key="/etc/cert/user.prv"
773 private_key_passwd="password"
777 # Example of EAP-TLS with smartcard (openssl engine)
785 identity="user@example.com"
786 ca_cert="/etc/cert/ca.pem"
787 client_cert="/etc/cert/user.pem"
791 # The engine configured here must be available. Look at
792 # OpenSSL engine support in the global section.
793 # The key available through the engine must be the private key
794 # matching the client certificate configured above.
796 # use the opensc engine
800 # use the pkcs11 engine
804 # Optional PIN configuration; this can be left out and PIN will be
805 # asked through the control interface
809 # Example configuration showing how to use an inlined blob as a CA certificate
810 # data instead of using external file
815 identity="user@example.com"
816 anonymous_identity="anonymous@example.com"
818 ca_cert="blob://exampleblob"
822 blob-base64-exampleblob={
827 # Wildcard match for SSID (plaintext APs only). This example select any
828 # open AP regardless of its SSID.