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