1##### Example wpa_supplicant configuration file ############################### 2# 3# This file describes configuration file format and lists all available option. 4# Please also take a look at simpler configuration examples in 'examples' 5# subdirectory. 6# 7# Empty lines and lines starting with # are ignored 8 9# NOTE! This file may contain password information and should probably be made 10# readable only by root user on multiuser systems. 11 12# Note: All file paths in this configuration file should use full (absolute, 13# not relative to working directory) path in order to allow working directory 14# to be changed. This can happen if wpa_supplicant is run in the background. 15 16# Whether to allow wpa_supplicant to update (overwrite) configuration 17# 18# This option can be used to allow wpa_supplicant to overwrite configuration 19# file whenever configuration is changed (e.g., new network block is added with 20# wpa_cli or wpa_gui, or a password is changed). This is required for 21# wpa_cli/wpa_gui to be able to store the configuration changes permanently. 22# Please note that overwriting configuration file will remove the comments from 23# it. 24update_config=1 25 26# global configuration (shared by all network blocks) 27# 28# Parameters for the control interface. If this is specified, wpa_supplicant 29# will open a control interface that is available for external programs to 30# manage wpa_supplicant. The meaning of this string depends on which control 31# interface mechanism is used. For all cases, the existance of this parameter 32# in configuration is used to determine whether the control interface is 33# enabled. 34# 35# For UNIX domain sockets (default on Linux and BSD): This is a directory that 36# will be created for UNIX domain sockets for listening to requests from 37# external programs (CLI/GUI, etc.) for status information and configuration. 38# The socket file will be named based on the interface name, so multiple 39# wpa_supplicant processes can be run at the same time if more than one 40# interface is used. 41# /var/run/wpa_supplicant is the recommended directory for sockets and by 42# default, wpa_cli will use it when trying to connect with wpa_supplicant. 43# 44# Access control for the control interface can be configured by setting the 45# directory to allow only members of a group to use sockets. This way, it is 46# possible to run wpa_supplicant as root (since it needs to change network 47# configuration and open raw sockets) and still allow GUI/CLI components to be 48# run as non-root users. However, since the control interface can be used to 49# change the network configuration, this access needs to be protected in many 50# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you 51# want to allow non-root users to use the control interface, add a new group 52# and change this value to match with that group. Add users that should have 53# control interface access to this group. If this variable is commented out or 54# not included in the configuration file, group will not be changed from the 55# value it got by default when the directory or socket was created. 56# 57# When configuring both the directory and group, use following format: 58# DIR=/var/run/wpa_supplicant GROUP=wheel 59# DIR=/var/run/wpa_supplicant GROUP=0 60# (group can be either group name or gid) 61# 62# For UDP connections (default on Windows): The value will be ignored. This 63# variable is just used to select that the control interface is to be created. 64# The value can be set to, e.g., udp (ctrl_interface=udp) 65# 66# For Windows Named Pipe: This value can be used to set the security descriptor 67# for controlling access to the control interface. Security descriptor can be 68# set using Security Descriptor String Format (see http://msdn.microsoft.com/ 69# library/default.asp?url=/library/en-us/secauthz/security/ 70# security_descriptor_string_format.asp). The descriptor string needs to be 71# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty 72# DACL (which will reject all connections). See README-Windows.txt for more 73# information about SDDL string format. 74# 75ctrl_interface=wlan0 76 77# IEEE 802.1X/EAPOL version 78# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines 79# EAPOL version 2. However, there are many APs that do not handle the new 80# version number correctly (they seem to drop the frames completely). In order 81# to make wpa_supplicant interoperate with these APs, the version number is set 82# to 1 by default. This configuration value can be used to set it to the new 83# version (2). 84eapol_version=1 85 86# AP scanning/selection 87# By default, wpa_supplicant requests driver to perform AP scanning and then 88# uses the scan results to select a suitable AP. Another alternative is to 89# allow the driver to take care of AP scanning and selection and use 90# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association 91# information from the driver. 92# 1: wpa_supplicant initiates scanning and AP selection 93# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association 94# parameters (e.g., WPA IE generation); this mode can also be used with 95# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with 96# APs (i.e., external program needs to control association). This mode must 97# also be used when using wired Ethernet drivers. 98# 2: like 0, but associate with APs using security policy and SSID (but not 99# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to 100# enable operation with hidden SSIDs and optimized roaming; in this mode, 101# the network blocks in the configuration file are tried one by one until 102# the driver reports successful association; each network block should have 103# explicit security policy (i.e., only one option in the lists) for 104# key_mgmt, pairwise, group, proto variables 105ap_scan=1 106 107# EAP fast re-authentication 108# By default, fast re-authentication is enabled for all EAP methods that 109# support it. This variable can be used to disable fast re-authentication. 110# Normally, there is no need to disable this. 111fast_reauth=1 112 113# OpenSSL Engine support 114# These options can be used to load OpenSSL engines. 115# The two engines that are supported currently are shown below: 116# They are both from the opensc project (http://www.opensc.org/) 117# By default no engines are loaded. 118# make the opensc engine available 119#opensc_engine_path=/usr/lib/opensc/engine_opensc.so 120# make the pkcs11 engine available 121#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so 122# configure the path to the pkcs11 module required by the pkcs11 engine 123#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so 124 125# Dynamic EAP methods 126# If EAP methods were built dynamically as shared object files, they need to be 127# loaded here before being used in the network blocks. By default, EAP methods 128# are included statically in the build, so these lines are not needed 129#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so 130#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so 131 132# Driver interface parameters 133# This field can be used to configure arbitrary driver interace parameters. The 134# format is specific to the selected driver interface. This field is not used 135# in most cases. 136#driver_param="field=value" 137 138# Maximum lifetime for PMKSA in seconds; default 43200 139#dot11RSNAConfigPMKLifetime=43200 140# Threshold for reauthentication (percentage of PMK lifetime); default 70 141#dot11RSNAConfigPMKReauthThreshold=70 142# Timeout for security association negotiation in seconds; default 60 143#dot11RSNAConfigSATimeout=60 144 145# network block 146# 147# Each network (usually AP's sharing the same SSID) is configured as a separate 148# block in this configuration file. The network blocks are in preference order 149# (the first match is used). 150# 151# network block fields: 152# 153# disabled: 154# 0 = this network can be used (default) 155# 1 = this network block is disabled (can be enabled through ctrl_iface, 156# e.g., with wpa_cli or wpa_gui) 157# 158# id_str: Network identifier string for external scripts. This value is passed 159# to external action script through wpa_cli as WPA_ID_STR environment 160# variable to make it easier to do network specific configuration. 161# 162# ssid: SSID (mandatory); either as an ASCII string with double quotation or 163# as hex string; network name 164# 165# scan_ssid: 166# 0 = do not scan this SSID with specific Probe Request frames (default) 167# 1 = scan with SSID-specific Probe Request frames (this can be used to 168# find APs that do not accept broadcast SSID or use multiple SSIDs; 169# this will add latency to scanning, so enable this only when needed) 170# 171# bssid: BSSID (optional); if set, this network block is used only when 172# associating with the AP using the configured BSSID 173# 174# priority: priority group (integer) 175# By default, all networks will get same priority group (0). If some of the 176# networks are more desirable, this field can be used to change the order in 177# which wpa_supplicant goes through the networks when selecting a BSS. The 178# priority groups will be iterated in decreasing priority (i.e., the larger the 179# priority value, the sooner the network is matched against the scan results). 180# Within each priority group, networks will be selected based on security 181# policy, signal strength, etc. 182# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not 183# using this priority to select the order for scanning. Instead, they try the 184# networks in the order that used in the configuration file. 185# 186# mode: IEEE 802.11 operation mode 187# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default) 188# 1 = IBSS (ad-hoc, peer-to-peer) 189# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) 190# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has 191# to be set to 2 for IBSS. WPA-None requires following network block options: 192# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not 193# both), and psk must also be set. 194# 195# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g., 196# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial 197# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode. 198# In addition, this value is only used by the station that creates the IBSS. If 199# an IBSS network with the configured SSID is already present, the frequency of 200# the network will be used instead of this configured value. 201# 202# proto: list of accepted protocols 203# WPA = WPA/IEEE 802.11i/D3.0 204# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN) 205# If not set, this defaults to: WPA RSN 206# 207# key_mgmt: list of accepted authenticated key management protocols 208# WPA-PSK = WPA pre-shared key (this requires 'psk' field) 209# WPA-EAP = WPA using EAP authentication (this can use an external 210# program, e.g., Xsupplicant, for IEEE 802.1X EAP Authentication 211# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically 212# generated WEP keys 213# NONE = WPA is not used; plaintext or static WEP could be used 214# If not set, this defaults to: WPA-PSK WPA-EAP 215# 216# auth_alg: list of allowed IEEE 802.11 authentication algorithms 217# OPEN = Open System authentication (required for WPA/WPA2) 218# SHARED = Shared Key authentication (requires static WEP keys) 219# LEAP = LEAP/Network EAP (only used with LEAP) 220# If not set, automatic selection is used (Open System with LEAP enabled if 221# LEAP is allowed as one of the EAP methods). 222# 223# pairwise: list of accepted pairwise (unicast) ciphers for WPA 224# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 225# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 226# NONE = Use only Group Keys (deprecated, should not be included if APs support 227# pairwise keys) 228# If not set, this defaults to: CCMP TKIP 229# 230# group: list of accepted group (broadcast/multicast) ciphers for WPA 231# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 232# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 233# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key 234# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11] 235# If not set, this defaults to: CCMP TKIP WEP104 WEP40 236# 237# psk: WPA preshared key; 256-bit pre-shared key 238# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., 239# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be 240# generated using the passphrase and SSID). ASCII passphrase must be between 241# 8 and 63 characters (inclusive). 242# This field is not needed, if WPA-EAP is used. 243# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys 244# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant 245# startup and reconfiguration time can be optimized by generating the PSK only 246# only when the passphrase or SSID has actually changed. 247# 248# eapol_flags: IEEE 802.1X/EAPOL options (bit field) 249# Dynamic WEP key required for non-WPA mode 250# bit0 (1): require dynamically generated unicast WEP key 251# bit1 (2): require dynamically generated broadcast WEP key 252# (3 = require both keys; default) 253# Note: When using wired authentication, eapol_flags must be set to 0 for the 254# authentication to be completed successfully. 255# 256# mixed_cell: This option can be used to configure whether so called mixed 257# cells, i.e., networks that use both plaintext and encryption in the same 258# SSID, are allowed when selecting a BSS form scan results. 259# 0 = disabled (default) 260# 1 = enabled 261# 262# proactive_key_caching: 263# Enable/disable opportunistic PMKSA caching for WPA2. 264# 0 = disabled (default) 265# 1 = enabled 266# 267# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or 268# hex without quotation, e.g., 0102030405) 269# wep_tx_keyidx: Default WEP key index (TX) (0..3) 270# 271# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is 272# allowed. This is only used with RSN/WPA2. 273# 0 = disabled (default) 274# 1 = enabled 275#peerkey=1 276# 277# Following fields are only used with internal EAP implementation. 278# eap: space-separated list of accepted EAP methods 279# MD5 = EAP-MD5 (unsecure and does not generate keying material -> 280# cannot be used with WPA; to be used as a Phase 2 method 281# with EAP-PEAP or EAP-TTLS) 282# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used 283# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 284# OTP = EAP-OTP (cannot be used separately with WPA; to be used 285# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 286# GTC = EAP-GTC (cannot be used separately with WPA; to be used 287# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 288# TLS = EAP-TLS (client and server certificate) 289# PEAP = EAP-PEAP (with tunnelled EAP authentication) 290# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2 291# authentication) 292# If not set, all compiled in methods are allowed. 293# 294# identity: Identity string for EAP 295# anonymous_identity: Anonymous identity string for EAP (to be used as the 296# unencrypted identity with EAP types that support different tunnelled 297# identity, e.g., EAP-TTLS) 298# password: Password string for EAP 299# ca_cert: File path to CA certificate file (PEM/DER). This file can have one 300# or more trusted CA certificates. If ca_cert and ca_path are not 301# included, server certificate will not be verified. This is insecure and 302# a trusted CA certificate should always be configured when using 303# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may 304# change when wpa_supplicant is run in the background. 305# On Windows, trusted CA certificates can be loaded from the system 306# certificate store by setting this to cert_store://<name>, e.g., 307# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 308# Note that when running wpa_supplicant as an application, the user 309# certificate store (My user account) is used, whereas computer store 310# (Computer account) is used when running wpasvc as a service. 311# ca_path: Directory path for CA certificate files (PEM). This path may 312# contain multiple CA certificates in OpenSSL format. Common use for this 313# is to point to system trusted CA list which is often installed into 314# directory like /etc/ssl/certs. If configured, these certificates are 315# added to the list of trusted CAs. ca_cert may also be included in that 316# case, but it is not required. 317# client_cert: File path to client certificate file (PEM/DER) 318# Full path should be used since working directory may change when 319# wpa_supplicant is run in the background. 320# Alternatively, a named configuration blob can be used by setting this 321# to blob://<blob name>. 322# private_key: File path to client private key file (PEM/DER/PFX) 323# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 324# commented out. Both the private key and certificate will be read from 325# the PKCS#12 file in this case. Full path should be used since working 326# directory may change when wpa_supplicant is run in the background. 327# Windows certificate store can be used by leaving client_cert out and 328# configuring private_key in one of the following formats: 329# cert://substring_to_match 330# hash://certificate_thumbprint_in_hex 331# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 332# Note that when running wpa_supplicant as an application, the user 333# certificate store (My user account) is used, whereas computer store 334# (Computer account) is used when running wpasvc as a service. 335# Alternatively, a named configuration blob can be used by setting this 336# to blob://<blob name>. 337# private_key_passwd: Password for private key file (if left out, this will be 338# asked through control interface) 339# dh_file: File path to DH/DSA parameters file (in PEM format) 340# This is an optional configuration file for setting parameters for an 341# ephemeral DH key exchange. In most cases, the default RSA 342# authentication does not use this configuration. However, it is possible 343# setup RSA to use ephemeral DH key exchange. In addition, ciphers with 344# DSA keys always use ephemeral DH keys. This can be used to achieve 345# forward secrecy. If the file is in DSA parameters format, it will be 346# automatically converted into DH params. 347# subject_match: Substring to be matched against the subject of the 348# authentication server certificate. If this string is set, the server 349# sertificate is only accepted if it contains this string in the subject. 350# The subject string is in following format: 351# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com 352# altsubject_match: Semicolon separated string of entries to be matched against 353# the alternative subject name of the authentication server certificate. 354# If this string is set, the server sertificate is only accepted if it 355# contains one of the entries in an alternative subject name extension. 356# altSubjectName string is in following format: TYPE:VALUE 357# Example: EMAIL:server@example.com 358# Example: DNS:server.example.com;DNS:server2.example.com 359# Following types are supported: EMAIL, DNS, URI 360# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters 361# (string with field-value pairs, e.g., "peapver=0" or 362# "peapver=1 peaplabel=1") 363# 'peapver' can be used to force which PEAP version (0 or 1) is used. 364# 'peaplabel=1' can be used to force new label, "client PEAP encryption", 365# to be used during key derivation when PEAPv1 or newer. Most existing 366# PEAPv1 implementation seem to be using the old label, "client EAP 367# encryption", and wpa_supplicant is now using that as the default value. 368# Some servers, e.g., Radiator, may require peaplabel=1 configuration to 369# interoperate with PEAPv1; see eap_testing.txt for more details. 370# 'peap_outer_success=0' can be used to terminate PEAP authentication on 371# tunneled EAP-Success. This is required with some RADIUS servers that 372# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 373# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode) 374# include_tls_length=1 can be used to force wpa_supplicant to include 375# TLS Message Length field in all TLS messages even if they are not 376# fragmented. 377# sim_min_num_chal=3 can be used to configure EAP-SIM to require three 378# challenges (by default, it accepts 2 or 3) 379# phase2: Phase2 (inner authentication with TLS tunnel) parameters 380# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 381# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS) 382# Following certificate/private key fields are used in inner Phase2 383# authentication when using EAP-TTLS or EAP-PEAP. 384# ca_cert2: File path to CA certificate file. This file can have one or more 385# trusted CA certificates. If ca_cert2 and ca_path2 are not included, 386# server certificate will not be verified. This is insecure and a trusted 387# CA certificate should always be configured. 388# ca_path2: Directory path for CA certificate files (PEM) 389# client_cert2: File path to client certificate file 390# private_key2: File path to client private key file 391# private_key2_passwd: Password for private key file 392# dh_file2: File path to DH/DSA parameters file (in PEM format) 393# subject_match2: Substring to be matched against the subject of the 394# authentication server certificate. 395# altsubject_match2: Substring to be matched against the alternative subject 396# name of the authentication server certificate. 397# 398# fragment_size: Maximum EAP fragment size in bytes (default 1398). 399# This value limits the fragment size for EAP methods that support 400# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 401# small enough to make the EAP messages fit in MTU of the network 402# interface used for EAPOL. The default value is suitable for most 403# cases. 404# 405# EAP-PSK variables: 406# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 407# nai: user NAI 408# 409# EAP-PAX variables: 410# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 411# 412# EAP-SAKE variables: 413# eappsk: 32-byte (256-bit, 64 hex digits) pre-shared key in hex format 414# (this is concatenation of Root-Secret-A and Root-Secret-B) 415# nai: user NAI (PEERID) 416# 417# EAP-GPSK variables: 418# eappsk: Pre-shared key in hex format (at least 128 bits, i.e., 32 hex digits) 419# nai: user NAI (ID_Client) 420# 421# EAP-FAST variables: 422# pac_file: File path for the PAC entries. wpa_supplicant will need to be able 423# to create this file and write updates to it when PAC is being 424# provisioned or refreshed. Full path to the file should be used since 425# working directory may change when wpa_supplicant is run in the 426# background. Alternatively, a named configuration blob can be used by 427# setting this to blob://<blob name> 428# phase1: fast_provisioning=1 option enables in-line provisioning of EAP-FAST 429# credentials (PAC) 430# 431# wpa_supplicant supports number of "EAP workarounds" to work around 432# interoperability issues with incorrectly behaving authentication servers. 433# These are enabled by default because some of the issues are present in large 434# number of authentication servers. Strict EAP conformance mode can be 435# configured by disabling workarounds with eap_workaround=0. 436 437# Example blocks: 438 439# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers 440#network={ 441# ssid="simple" 442# psk="very secret passphrase" 443# priority=5 444#} 445 446# Same as previous, but request SSID-specific scanning (for APs that reject 447# broadcast SSID) 448#network={ 449# ssid="second ssid" 450# scan_ssid=1 451# psk="very secret passphrase" 452# priority=2 453#} 454 455# Only WPA-PSK is used. Any valid cipher combination is accepted. 456#network={ 457# ssid="example" 458# proto=WPA 459# key_mgmt=WPA-PSK 460# pairwise=CCMP TKIP 461# group=CCMP TKIP WEP104 WEP40 462# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 463# priority=2 464#} 465 466# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104 467# or WEP40 as the group cipher will not be accepted. 468#network={ 469# ssid="example" 470# proto=RSN 471# key_mgmt=WPA-EAP 472# pairwise=CCMP TKIP 473# group=CCMP TKIP 474# eap=TLS 475# identity="user@example.com" 476# ca_cert="/etc/cert/ca.pem" 477# client_cert="/etc/cert/user.pem" 478# private_key="/etc/cert/user.prv" 479# private_key_passwd="password" 480# priority=1 481#} 482 483# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel 484# (e.g., Radiator) 485#network={ 486# ssid="example" 487# key_mgmt=WPA-EAP 488# eap=PEAP 489# identity="user@example.com" 490# password="foobar" 491# ca_cert="/etc/cert/ca.pem" 492# phase1="peaplabel=1" 493# phase2="auth=MSCHAPV2" 494# priority=10 495#} 496 497# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the 498# unencrypted use. Real identity is sent only within an encrypted TLS tunnel. 499#network={ 500# ssid="example" 501# key_mgmt=WPA-EAP 502# eap=TTLS 503# identity="user@example.com" 504# anonymous_identity="anonymous@example.com" 505# password="foobar" 506# ca_cert="/etc/cert/ca.pem" 507# priority=2 508#} 509 510# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted 511# use. Real identity is sent only within an encrypted TLS tunnel. 512#network={ 513# ssid="example" 514# key_mgmt=WPA-EAP 515# eap=TTLS 516# identity="user@example.com" 517# anonymous_identity="anonymous@example.com" 518# password="foobar" 519# ca_cert="/etc/cert/ca.pem" 520# phase2="auth=MSCHAPV2" 521#} 522 523# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner 524# authentication. 525#network={ 526# ssid="example" 527# key_mgmt=WPA-EAP 528# eap=TTLS 529# # Phase1 / outer authentication 530# anonymous_identity="anonymous@example.com" 531# ca_cert="/etc/cert/ca.pem" 532# # Phase 2 / inner authentication 533# phase2="autheap=TLS" 534# ca_cert2="/etc/cert/ca2.pem" 535# client_cert2="/etc/cer/user.pem" 536# private_key2="/etc/cer/user.prv" 537# private_key2_passwd="password" 538# priority=2 539#} 540 541# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and 542# group cipher. 543#network={ 544# ssid="example" 545# bssid=00:11:22:33:44:55 546# proto=WPA RSN 547# key_mgmt=WPA-PSK WPA-EAP 548# pairwise=CCMP 549# group=CCMP 550# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 551#} 552 553# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP 554# and all valid ciphers. 555#network={ 556# ssid=00010203 557# psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 558#} 559 560 561# EAP-SIM with a GSM SIM or USIM 562#network={ 563# ssid="eap-sim-test" 564# key_mgmt=WPA-EAP 565# eap=SIM 566# pin="1234" 567# pcsc="" 568#} 569 570 571# EAP-PSK 572#network={ 573# ssid="eap-psk-test" 574# key_mgmt=WPA-EAP 575# eap=PSK 576# identity="eap_psk_user" 577# eappsk=06b4be19da289f475aa46a33cb793029 578# nai="eap_psk_user@example.com" 579#} 580 581 582# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using 583# EAP-TLS for authentication and key generation; require both unicast and 584# broadcast WEP keys. 585#network={ 586# ssid="1x-test" 587# key_mgmt=IEEE8021X 588# eap=TLS 589# identity="user@example.com" 590# ca_cert="/etc/cert/ca.pem" 591# client_cert="/etc/cert/user.pem" 592# private_key="/etc/cert/user.prv" 593# private_key_passwd="password" 594# eapol_flags=3 595#} 596 597 598# LEAP with dynamic WEP keys 599#network={ 600# ssid="leap-example" 601# key_mgmt=IEEE8021X 602# eap=LEAP 603# identity="user" 604# password="foobar" 605#} 606 607# EAP-FAST with WPA (WPA or WPA2) 608#network={ 609# ssid="eap-fast-test" 610# key_mgmt=WPA-EAP 611# eap=FAST 612# anonymous_identity="FAST-000102030405" 613# identity="username" 614# password="password" 615# phase1="fast_provisioning=1" 616# pac_file="/etc/wpa_supplicant.eap-fast-pac" 617#} 618 619#network={ 620# ssid="eap-fast-test" 621# key_mgmt=WPA-EAP 622# eap=FAST 623# anonymous_identity="FAST-000102030405" 624# identity="username" 625# password="password" 626# phase1="fast_provisioning=1" 627# pac_file="blob://eap-fast-pac" 628#} 629 630# Plaintext connection (no WPA, no IEEE 802.1X) 631#network={ 632# ssid="plaintext-test" 633# key_mgmt=NONE 634#} 635 636 637# Shared WEP key connection (no WPA, no IEEE 802.1X) 638#network={ 639# ssid="static-wep-test" 640# key_mgmt=NONE 641# wep_key0="abcde" 642# wep_key1=0102030405 643# wep_key2="1234567890123" 644# wep_tx_keyidx=0 645# priority=5 646#} 647 648 649# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key 650# IEEE 802.11 authentication 651#network={ 652# ssid="static-wep-test2" 653# key_mgmt=NONE 654# wep_key0="abcde" 655# wep_key1=0102030405 656# wep_key2="1234567890123" 657# wep_tx_keyidx=0 658# priority=5 659# auth_alg=SHARED 660#} 661 662 663# IBSS/ad-hoc network with WPA-None/TKIP. 664#network={ 665# ssid="test adhoc" 666# mode=1 667# frequency=2412 668# proto=WPA 669# key_mgmt=WPA-NONE 670# pairwise=NONE 671# group=TKIP 672# psk="secret passphrase" 673#} 674 675 676# Catch all example that allows more or less all configuration modes 677#network={ 678# ssid="example" 679# scan_ssid=1 680# key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE 681# pairwise=CCMP TKIP 682# group=CCMP TKIP WEP104 WEP40 683# psk="very secret passphrase" 684# eap=TTLS PEAP TLS 685# identity="user@example.com" 686# password="foobar" 687# ca_cert="/etc/cert/ca.pem" 688# client_cert="/etc/cert/user.pem" 689# private_key="/etc/cert/user.prv" 690# private_key_passwd="password" 691# phase1="peaplabel=0" 692#} 693 694# Example of EAP-TLS with smartcard (openssl engine) 695#network={ 696# ssid="example" 697# key_mgmt=WPA-EAP 698# eap=TLS 699# proto=RSN 700# pairwise=CCMP TKIP 701# group=CCMP TKIP 702# identity="user@example.com" 703# ca_cert="/etc/cert/ca.pem" 704# client_cert="/etc/cert/user.pem" 705# 706# engine=1 707# 708 # The engine configured here must be available. Look at 709 # OpenSSL engine support in the global section. 710 # The key available through the engine must be the private key 711 # matching the client certificate configured above. 712 713 # use the opensc engine 714 #engine_id="opensc" 715 #key_id="45" 716 717 # use the pkcs11 engine 718# engine_id="pkcs11" 719# key_id="id_45" 720 721 # Optional PIN configuration; this can be left out and PIN will be 722 # asked through the control interface 723# pin="1234" 724#} 725 726# Example configuration showing how to use an inlined blob as a CA certificate 727# data instead of using external file 728#network={ 729# ssid="example" 730# key_mgmt=WPA-EAP 731# eap=TTLS 732# identity="user@example.com" 733# anonymous_identity="anonymous@example.com" 734# password="foobar" 735# ca_cert="blob://exampleblob" 736# priority=20 737#} 738 739#blob-base64-exampleblob={ 740#SGVsbG8gV29ybGQhCg== 741#} 742 743# Wildcard match for SSID (plaintext APs only). This example selects any 744# open AP regardless of its SSID. 745#network={ 746# key_mgmt=NONE 747#} 748