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. 24#update_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 existence 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=/var/run/wpa_supplicant 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; if no APs matching to 93# the currently enabled networks are found, a new network (IBSS or AP mode 94# operation) may be initialized (if configured) (default) 95# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association 96# parameters (e.g., WPA IE generation); this mode can also be used with 97# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with 98# APs (i.e., external program needs to control association). This mode must 99# also be used when using wired Ethernet drivers. 100# 2: like 0, but associate with APs using security policy and SSID (but not 101# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to 102# enable operation with hidden SSIDs and optimized roaming; in this mode, 103# the network blocks in the configuration file are tried one by one until 104# the driver reports successful association; each network block should have 105# explicit security policy (i.e., only one option in the lists) for 106# key_mgmt, pairwise, group, proto variables 107# When using IBSS or AP mode, ap_scan=2 mode can force the new network to be 108# created immediately regardless of scan results. ap_scan=1 mode will first try 109# to scan for existing networks and only if no matches with the enabled 110# networks are found, a new IBSS or AP mode network is created. 111ap_scan=1 112 113# EAP fast re-authentication 114# By default, fast re-authentication is enabled for all EAP methods that 115# support it. This variable can be used to disable fast re-authentication. 116# Normally, there is no need to disable this. 117fast_reauth=1 118 119# OpenSSL Engine support 120# These options can be used to load OpenSSL engines. 121# The two engines that are supported currently are shown below: 122# They are both from the opensc project (http://www.opensc.org/) 123# By default no engines are loaded. 124# make the opensc engine available 125#opensc_engine_path=/usr/lib/opensc/engine_opensc.so 126# make the pkcs11 engine available 127#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so 128# configure the path to the pkcs11 module required by the pkcs11 engine 129#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so 130 131# Dynamic EAP methods 132# If EAP methods were built dynamically as shared object files, they need to be 133# loaded here before being used in the network blocks. By default, EAP methods 134# are included statically in the build, so these lines are not needed 135#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so 136#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so 137 138# Driver interface parameters 139# This field can be used to configure arbitrary driver interace parameters. The 140# format is specific to the selected driver interface. This field is not used 141# in most cases. 142#driver_param="field=value" 143 144# Country code 145# The ISO/IEC alpha2 country code for the country in which this device is 146# currently operating. 147#country=US 148 149# Maximum lifetime for PMKSA in seconds; default 43200 150#dot11RSNAConfigPMKLifetime=43200 151# Threshold for reauthentication (percentage of PMK lifetime); default 70 152#dot11RSNAConfigPMKReauthThreshold=70 153# Timeout for security association negotiation in seconds; default 60 154#dot11RSNAConfigSATimeout=60 155 156# Wi-Fi Protected Setup (WPS) parameters 157 158# Universally Unique IDentifier (UUID; see RFC 4122) of the device 159# If not configured, UUID will be generated based on the local MAC address. 160#uuid=12345678-9abc-def0-1234-56789abcdef0 161 162# Device Name 163# User-friendly description of device; up to 32 octets encoded in UTF-8 164#device_name=Wireless Client 165 166# Manufacturer 167# The manufacturer of the device (up to 64 ASCII characters) 168#manufacturer=Company 169 170# Model Name 171# Model of the device (up to 32 ASCII characters) 172#model_name=cmodel 173 174# Model Number 175# Additional device description (up to 32 ASCII characters) 176#model_number=123 177 178# Serial Number 179# Serial number of the device (up to 32 characters) 180#serial_number=12345 181 182# Primary Device Type 183# Used format: <categ>-<OUI>-<subcateg> 184# categ = Category as an integer value 185# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for 186# default WPS OUI 187# subcateg = OUI-specific Sub Category as an integer value 188# Examples: 189# 1-0050F204-1 (Computer / PC) 190# 1-0050F204-2 (Computer / Server) 191# 5-0050F204-1 (Storage / NAS) 192# 6-0050F204-1 (Network Infrastructure / AP) 193#device_type=1-0050F204-1 194 195# OS Version 196# 4-octet operating system version number (hex string) 197#os_version=01020300 198 199# Config Methods 200# List of the supported configuration methods 201# Available methods: usba ethernet label display ext_nfc_token int_nfc_token 202# nfc_interface push_button keypad virtual_display physical_display 203# virtual_push_button physical_push_button 204# For WSC 1.0: 205#config_methods=label display push_button keypad 206# For WSC 2.0: 207#config_methods=label virtual_display virtual_push_button keypad 208 209# Credential processing 210# 0 = process received credentials internally (default) 211# 1 = do not process received credentials; just pass them over ctrl_iface to 212# external program(s) 213# 2 = process received credentials internally and pass them over ctrl_iface 214# to external program(s) 215#wps_cred_processing=0 216 217# Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing 218# The vendor attribute contents to be added in M1 (hex string) 219#wps_vendor_ext_m1=000137100100020001 220 221# NFC password token for WPS 222# These parameters can be used to configure a fixed NFC password token for the 223# station. This can be generated, e.g., with nfc_pw_token. When these 224# parameters are used, the station is assumed to be deployed with a NFC tag 225# that includes the matching NFC password token (e.g., written based on the 226# NDEF record from nfc_pw_token). 227# 228#wps_nfc_dev_pw_id: Device Password ID (16..65535) 229#wps_nfc_dh_pubkey: Hexdump of DH Public Key 230#wps_nfc_dh_privkey: Hexdump of DH Private Key 231#wps_nfc_dev_pw: Hexdump of Device Password 232 233# Maximum number of BSS entries to keep in memory 234# Default: 200 235# This can be used to limit memory use on the BSS entries (cached scan 236# results). A larger value may be needed in environments that have huge number 237# of APs when using ap_scan=1 mode. 238#bss_max_count=200 239 240# Automatic scan 241# This is an optional set of parameters for automatic scanning 242# within an interface in following format: 243#autoscan=<autoscan module name>:<module parameters> 244#Â autoscan is like bgscan but on disconnected or inactive state. 245#Â For instance, on exponential module parameters would be <base>:<limit> 246#autoscan=exponential:3:300 247# Which means a delay between scans on a base exponential of 3, 248#Â up to the limit of 300 seconds (3, 9, 27 ... 300) 249#Â For periodic module, parameters would be <fixed interval> 250#autoscan=periodic:30 251#Â So a delay of 30 seconds will be applied between each scan 252 253# filter_ssids - SSID-based scan result filtering 254# 0 = do not filter scan results (default) 255# 1 = only include configured SSIDs in scan results/BSS table 256#filter_ssids=0 257 258# Password (and passphrase, etc.) backend for external storage 259# format: <backend name>[:<optional backend parameters>] 260#ext_password_backend=test:pw1=password|pw2=testing 261 262# Timeout in seconds to detect STA inactivity (default: 300 seconds) 263# 264# This timeout value is used in P2P GO mode to clean up 265# inactive stations. 266#p2p_go_max_inactivity=300 267 268# Opportunistic Key Caching (also known as Proactive Key Caching) default 269# This parameter can be used to set the default behavior for the 270# proactive_key_caching parameter. By default, OKC is disabled unless enabled 271# with the global okc=1 parameter or with the per-network 272# proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but 273# can be disabled with per-network proactive_key_caching=0 parameter. 274#okc=0 275 276# Protected Management Frames default 277# This parameter can be used to set the default behavior for the ieee80211w 278# parameter. By default, PMF is disabled unless enabled with the global pmf=1/2 279# parameter or with the per-network ieee80211w=1/2 parameter. With pmf=1/2, PMF 280# is enabled/required by default, but can be disabled with the per-network 281# ieee80211w parameter. 282#pmf=0 283 284# Enabled SAE finite cyclic groups in preference order 285# By default (if this parameter is not set), the mandatory group 19 (ECC group 286# defined over a 256-bit prime order field) is preferred, but other groups are 287# also enabled. If this parameter is set, the groups will be tried in the 288# indicated order. The group values are listed in the IANA registry: 289# http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9 290#sae_groups=21 20 19 26 25 291 292# Default value for DTIM period (if not overridden in network block) 293#dtim_period=2 294 295# Default value for Beacon interval (if not overridden in network block) 296#beacon_int=100 297 298# Additional vendor specific elements for Beacon and Probe Response frames 299# This parameter can be used to add additional vendor specific element(s) into 300# the end of the Beacon and Probe Response frames. The format for these 301# element(s) is a hexdump of the raw information elements (id+len+payload for 302# one or more elements). This is used in AP and P2P GO modes. 303#ap_vendor_elements=dd0411223301 304 305# Ignore scan results older than request 306# 307# The driver may have a cache of scan results that makes it return 308# information that is older than our scan trigger. This parameter can 309# be used to configure such old information to be ignored instead of 310# allowing it to update the internal BSS table. 311#ignore_old_scan_res=0 312 313 314# Interworking (IEEE 802.11u) 315 316# Enable Interworking 317# interworking=1 318 319# Homogenous ESS identifier 320# If this is set, scans will be used to request response only from BSSes 321# belonging to the specified Homogeneous ESS. This is used only if interworking 322# is enabled. 323# hessid=00:11:22:33:44:55 324 325# Automatic network selection behavior 326# 0 = do not automatically go through Interworking network selection 327# (i.e., require explicit interworking_select command for this; default) 328# 1 = perform Interworking network selection if one or more 329# credentials have been configured and scan did not find a 330# matching network block 331#auto_interworking=0 332 333# credential block 334# 335# Each credential used for automatic network selection is configured as a set 336# of parameters that are compared to the information advertised by the APs when 337# interworking_select and interworking_connect commands are used. 338# 339# credential fields: 340# 341# priority: Priority group 342# By default, all networks and credentials get the same priority group 343# (0). This field can be used to give higher priority for credentials 344# (and similarly in struct wpa_ssid for network blocks) to change the 345# Interworking automatic networking selection behavior. The matching 346# network (based on either an enabled network block or a credential) 347# with the highest priority value will be selected. 348# 349# pcsc: Use PC/SC and SIM/USIM card 350# 351# realm: Home Realm for Interworking 352# 353# username: Username for Interworking network selection 354# 355# password: Password for Interworking network selection 356# 357# ca_cert: CA certificate for Interworking network selection 358# 359# client_cert: File path to client certificate file (PEM/DER) 360# This field is used with Interworking networking selection for a case 361# where client certificate/private key is used for authentication 362# (EAP-TLS). Full path to the file should be used since working 363# directory may change when wpa_supplicant is run in the background. 364# 365# Alternatively, a named configuration blob can be used by setting 366# this to blob://blob_name. 367# 368# private_key: File path to client private key file (PEM/DER/PFX) 369# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 370# commented out. Both the private key and certificate will be read 371# from the PKCS#12 file in this case. Full path to the file should be 372# used since working directory may change when wpa_supplicant is run 373# in the background. 374# 375# Windows certificate store can be used by leaving client_cert out and 376# configuring private_key in one of the following formats: 377# 378# cert://substring_to_match 379# 380# hash://certificate_thumbprint_in_hex 381# 382# For example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 383# 384# Note that when running wpa_supplicant as an application, the user 385# certificate store (My user account) is used, whereas computer store 386# (Computer account) is used when running wpasvc as a service. 387# 388# Alternatively, a named configuration blob can be used by setting 389# this to blob://blob_name. 390# 391# private_key_passwd: Password for private key file 392# 393# imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format 394# 395# milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN> 396# format 397# 398# domain: Home service provider FQDN 399# This is used to compare against the Domain Name List to figure out 400# whether the AP is operated by the Home SP. 401# 402# roaming_consortium: Roaming Consortium OI 403# If roaming_consortium_len is non-zero, this field contains the 404# Roaming Consortium OI that can be used to determine which access 405# points support authentication with this credential. This is an 406# alternative to the use of the realm parameter. When using Roaming 407# Consortium to match the network, the EAP parameters need to be 408# pre-configured with the credential since the NAI Realm information 409# may not be available or fetched. 410# 411# eap: Pre-configured EAP method 412# This optional field can be used to specify which EAP method will be 413# used with this credential. If not set, the EAP method is selected 414# automatically based on ANQP information (e.g., NAI Realm). 415# 416# phase1: Pre-configure Phase 1 (outer authentication) parameters 417# This optional field is used with like the 'eap' parameter. 418# 419# phase2: Pre-configure Phase 2 (inner authentication) parameters 420# This optional field is used with like the 'eap' parameter. 421# 422# excluded_ssid: Excluded SSID 423# This optional field can be used to excluded specific SSID(s) from 424# matching with the network. Multiple entries can be used to specify more 425# than one SSID. 426# 427# for example: 428# 429#cred={ 430# realm="example.com" 431# username="user@example.com" 432# password="password" 433# ca_cert="/etc/wpa_supplicant/ca.pem" 434# domain="example.com" 435#} 436# 437#cred={ 438# imsi="310026-000000000" 439# milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82" 440#} 441# 442#cred={ 443# realm="example.com" 444# username="user" 445# password="password" 446# ca_cert="/etc/wpa_supplicant/ca.pem" 447# domain="example.com" 448# roaming_consortium=223344 449# eap=TTLS 450# phase2="auth=MSCHAPV2" 451#} 452 453# Hotspot 2.0 454# hs20=1 455 456# network block 457# 458# Each network (usually AP's sharing the same SSID) is configured as a separate 459# block in this configuration file. The network blocks are in preference order 460# (the first match is used). 461# 462# network block fields: 463# 464# disabled: 465# 0 = this network can be used (default) 466# 1 = this network block is disabled (can be enabled through ctrl_iface, 467# e.g., with wpa_cli or wpa_gui) 468# 469# id_str: Network identifier string for external scripts. This value is passed 470# to external action script through wpa_cli as WPA_ID_STR environment 471# variable to make it easier to do network specific configuration. 472# 473# ssid: SSID (mandatory); network name in one of the optional formats: 474# - an ASCII string with double quotation 475# - a hex string (two characters per octet of SSID) 476# - a printf-escaped ASCII string P"<escaped string>" 477# 478# scan_ssid: 479# 0 = do not scan this SSID with specific Probe Request frames (default) 480# 1 = scan with SSID-specific Probe Request frames (this can be used to 481# find APs that do not accept broadcast SSID or use multiple SSIDs; 482# this will add latency to scanning, so enable this only when needed) 483# 484# bssid: BSSID (optional); if set, this network block is used only when 485# associating with the AP using the configured BSSID 486# 487# priority: priority group (integer) 488# By default, all networks will get same priority group (0). If some of the 489# networks are more desirable, this field can be used to change the order in 490# which wpa_supplicant goes through the networks when selecting a BSS. The 491# priority groups will be iterated in decreasing priority (i.e., the larger the 492# priority value, the sooner the network is matched against the scan results). 493# Within each priority group, networks will be selected based on security 494# policy, signal strength, etc. 495# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not 496# using this priority to select the order for scanning. Instead, they try the 497# networks in the order that used in the configuration file. 498# 499# mode: IEEE 802.11 operation mode 500# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default) 501# 1 = IBSS (ad-hoc, peer-to-peer) 502# 2 = AP (access point) 503# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) 504# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). WPA-None requires 505# following network block options: 506# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not 507# both), and psk must also be set. 508# 509# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g., 510# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial 511# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode. 512# In addition, this value is only used by the station that creates the IBSS. If 513# an IBSS network with the configured SSID is already present, the frequency of 514# the network will be used instead of this configured value. 515# 516# scan_freq: List of frequencies to scan 517# Space-separated list of frequencies in MHz to scan when searching for this 518# BSS. If the subset of channels used by the network is known, this option can 519# be used to optimize scanning to not occur on channels that the network does 520# not use. Example: scan_freq=2412 2437 2462 521# 522# freq_list: Array of allowed frequencies 523# Space-separated list of frequencies in MHz to allow for selecting the BSS. If 524# set, scan results that do not match any of the specified frequencies are not 525# considered when selecting a BSS. 526# 527# bgscan: Background scanning 528# wpa_supplicant behavior for background scanning can be specified by 529# configuring a bgscan module. These modules are responsible for requesting 530# background scans for the purpose of roaming within an ESS (i.e., within a 531# single network block with all the APs using the same SSID). The bgscan 532# parameter uses following format: "<bgscan module name>:<module parameters>" 533# Following bgscan modules are available: 534# simple - Periodic background scans based on signal strength 535# bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>: 536# <long interval>" 537# bgscan="simple:30:-45:300" 538# learn - Learn channels used by the network and try to avoid bgscans on other 539# channels (experimental) 540# bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>: 541# <long interval>[:<database file name>]" 542# bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan" 543# 544# proto: list of accepted protocols 545# WPA = WPA/IEEE 802.11i/D3.0 546# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN) 547# If not set, this defaults to: WPA RSN 548# 549# key_mgmt: list of accepted authenticated key management protocols 550# WPA-PSK = WPA pre-shared key (this requires 'psk' field) 551# WPA-EAP = WPA using EAP authentication 552# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically 553# generated WEP keys 554# NONE = WPA is not used; plaintext or static WEP could be used 555# WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms 556# WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms 557# If not set, this defaults to: WPA-PSK WPA-EAP 558# 559# ieee80211w: whether management frame protection is enabled 560# 0 = disabled (default unless changed with the global pmf parameter) 561# 1 = optional 562# 2 = required 563# The most common configuration options for this based on the PMF (protected 564# management frames) certification program are: 565# PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256 566# PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256 567# (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used) 568# 569# auth_alg: list of allowed IEEE 802.11 authentication algorithms 570# OPEN = Open System authentication (required for WPA/WPA2) 571# SHARED = Shared Key authentication (requires static WEP keys) 572# LEAP = LEAP/Network EAP (only used with LEAP) 573# If not set, automatic selection is used (Open System with LEAP enabled if 574# LEAP is allowed as one of the EAP methods). 575# 576# pairwise: list of accepted pairwise (unicast) ciphers for WPA 577# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 578# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 579# NONE = Use only Group Keys (deprecated, should not be included if APs support 580# pairwise keys) 581# If not set, this defaults to: CCMP TKIP 582# 583# group: list of accepted group (broadcast/multicast) ciphers for WPA 584# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 585# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 586# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key 587# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11] 588# If not set, this defaults to: CCMP TKIP WEP104 WEP40 589# 590# psk: WPA preshared key; 256-bit pre-shared key 591# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., 592# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be 593# generated using the passphrase and SSID). ASCII passphrase must be between 594# 8 and 63 characters (inclusive). ext:<name of external PSK field> format can 595# be used to indicate that the PSK/passphrase is stored in external storage. 596# This field is not needed, if WPA-EAP is used. 597# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys 598# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant 599# startup and reconfiguration time can be optimized by generating the PSK only 600# only when the passphrase or SSID has actually changed. 601# 602# eapol_flags: IEEE 802.1X/EAPOL options (bit field) 603# Dynamic WEP key required for non-WPA mode 604# bit0 (1): require dynamically generated unicast WEP key 605# bit1 (2): require dynamically generated broadcast WEP key 606# (3 = require both keys; default) 607# Note: When using wired authentication, eapol_flags must be set to 0 for the 608# authentication to be completed successfully. 609# 610# mixed_cell: This option can be used to configure whether so called mixed 611# cells, i.e., networks that use both plaintext and encryption in the same 612# SSID, are allowed when selecting a BSS from scan results. 613# 0 = disabled (default) 614# 1 = enabled 615# 616# proactive_key_caching: 617# Enable/disable opportunistic PMKSA caching for WPA2. 618# 0 = disabled (default unless changed with the global okc parameter) 619# 1 = enabled 620# 621# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or 622# hex without quotation, e.g., 0102030405) 623# wep_tx_keyidx: Default WEP key index (TX) (0..3) 624# 625# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is 626# allowed. This is only used with RSN/WPA2. 627# 0 = disabled (default) 628# 1 = enabled 629#peerkey=1 630# 631# wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to 632# enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies. 633# 634# Following fields are only used with internal EAP implementation. 635# eap: space-separated list of accepted EAP methods 636# MD5 = EAP-MD5 (unsecure and does not generate keying material -> 637# cannot be used with WPA; to be used as a Phase 2 method 638# with EAP-PEAP or EAP-TTLS) 639# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used 640# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 641# OTP = EAP-OTP (cannot be used separately with WPA; to be used 642# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 643# GTC = EAP-GTC (cannot be used separately with WPA; to be used 644# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 645# TLS = EAP-TLS (client and server certificate) 646# PEAP = EAP-PEAP (with tunnelled EAP authentication) 647# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2 648# authentication) 649# If not set, all compiled in methods are allowed. 650# 651# identity: Identity string for EAP 652# This field is also used to configure user NAI for 653# EAP-PSK/PAX/SAKE/GPSK. 654# anonymous_identity: Anonymous identity string for EAP (to be used as the 655# unencrypted identity with EAP types that support different tunnelled 656# identity, e.g., EAP-TTLS). This field can also be used with 657# EAP-SIM/AKA/AKA' to store the pseudonym identity. 658# password: Password string for EAP. This field can include either the 659# plaintext password (using ASCII or hex string) or a NtPasswordHash 660# (16-byte MD4 hash of password) in hash:<32 hex digits> format. 661# NtPasswordHash can only be used when the password is for MSCHAPv2 or 662# MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP). 663# EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit 664# PSK) is also configured using this field. For EAP-GPSK, this is a 665# variable length PSK. ext:<name of external password field> format can 666# be used to indicate that the password is stored in external storage. 667# ca_cert: File path to CA certificate file (PEM/DER). This file can have one 668# or more trusted CA certificates. If ca_cert and ca_path are not 669# included, server certificate will not be verified. This is insecure and 670# a trusted CA certificate should always be configured when using 671# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may 672# change when wpa_supplicant is run in the background. 673# 674# Alternatively, this can be used to only perform matching of the server 675# certificate (SHA-256 hash of the DER encoded X.509 certificate). In 676# this case, the possible CA certificates in the server certificate chain 677# are ignored and only the server certificate is verified. This is 678# configured with the following format: 679# hash:://server/sha256/cert_hash_in_hex 680# For example: "hash://server/sha256/ 681# 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a" 682# 683# On Windows, trusted CA certificates can be loaded from the system 684# certificate store by setting this to cert_store://<name>, e.g., 685# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 686# Note that when running wpa_supplicant as an application, the user 687# certificate store (My user account) is used, whereas computer store 688# (Computer account) is used when running wpasvc as a service. 689# ca_path: Directory path for CA certificate files (PEM). This path may 690# contain multiple CA certificates in OpenSSL format. Common use for this 691# is to point to system trusted CA list which is often installed into 692# directory like /etc/ssl/certs. If configured, these certificates are 693# added to the list of trusted CAs. ca_cert may also be included in that 694# case, but it is not required. 695# client_cert: File path to client certificate file (PEM/DER) 696# Full path should be used since working directory may change when 697# wpa_supplicant is run in the background. 698# Alternatively, a named configuration blob can be used by setting this 699# to blob://<blob name>. 700# private_key: File path to client private key file (PEM/DER/PFX) 701# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 702# commented out. Both the private key and certificate will be read from 703# the PKCS#12 file in this case. Full path should be used since working 704# directory may change when wpa_supplicant is run in the background. 705# Windows certificate store can be used by leaving client_cert out and 706# configuring private_key in one of the following formats: 707# cert://substring_to_match 708# hash://certificate_thumbprint_in_hex 709# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 710# Note that when running wpa_supplicant as an application, the user 711# certificate store (My user account) is used, whereas computer store 712# (Computer account) is used when running wpasvc as a service. 713# Alternatively, a named configuration blob can be used by setting this 714# to blob://<blob name>. 715# private_key_passwd: Password for private key file (if left out, this will be 716# asked through control interface) 717# dh_file: File path to DH/DSA parameters file (in PEM format) 718# This is an optional configuration file for setting parameters for an 719# ephemeral DH key exchange. In most cases, the default RSA 720# authentication does not use this configuration. However, it is possible 721# setup RSA to use ephemeral DH key exchange. In addition, ciphers with 722# DSA keys always use ephemeral DH keys. This can be used to achieve 723# forward secrecy. If the file is in DSA parameters format, it will be 724# automatically converted into DH params. 725# subject_match: Substring to be matched against the subject of the 726# authentication server certificate. If this string is set, the server 727# sertificate is only accepted if it contains this string in the subject. 728# The subject string is in following format: 729# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com 730# altsubject_match: Semicolon separated string of entries to be matched against 731# the alternative subject name of the authentication server certificate. 732# If this string is set, the server sertificate is only accepted if it 733# contains one of the entries in an alternative subject name extension. 734# altSubjectName string is in following format: TYPE:VALUE 735# Example: EMAIL:server@example.com 736# Example: DNS:server.example.com;DNS:server2.example.com 737# Following types are supported: EMAIL, DNS, URI 738# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters 739# (string with field-value pairs, e.g., "peapver=0" or 740# "peapver=1 peaplabel=1") 741# 'peapver' can be used to force which PEAP version (0 or 1) is used. 742# 'peaplabel=1' can be used to force new label, "client PEAP encryption", 743# to be used during key derivation when PEAPv1 or newer. Most existing 744# PEAPv1 implementation seem to be using the old label, "client EAP 745# encryption", and wpa_supplicant is now using that as the default value. 746# Some servers, e.g., Radiator, may require peaplabel=1 configuration to 747# interoperate with PEAPv1; see eap_testing.txt for more details. 748# 'peap_outer_success=0' can be used to terminate PEAP authentication on 749# tunneled EAP-Success. This is required with some RADIUS servers that 750# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 751# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode) 752# include_tls_length=1 can be used to force wpa_supplicant to include 753# TLS Message Length field in all TLS messages even if they are not 754# fragmented. 755# sim_min_num_chal=3 can be used to configure EAP-SIM to require three 756# challenges (by default, it accepts 2 or 3) 757# result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use 758# protected result indication. 759# 'crypto_binding' option can be used to control PEAPv0 cryptobinding 760# behavior: 761# * 0 = do not use cryptobinding (default) 762# * 1 = use cryptobinding if server supports it 763# * 2 = require cryptobinding 764# EAP-WSC (WPS) uses following options: pin=<Device Password> or 765# pbc=1. 766# phase2: Phase2 (inner authentication with TLS tunnel) parameters 767# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 768# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS) 769# 770# TLS-based methods can use the following parameters to control TLS behavior 771# (these are normally in the phase1 parameter, but can be used also in the 772# phase2 parameter when EAP-TLS is used within the inner tunnel): 773# tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the 774# TLS library, these may be disabled by default to enforce stronger 775# security) 776# tls_disable_time_checks=1 - ignore certificate validity time (this requests 777# the TLS library to accept certificates even if they are not currently 778# valid, i.e., have expired or have not yet become valid; this should be 779# used only for testing purposes) 780# tls_disable_session_ticket=1 - disable TLS Session Ticket extension 781# tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used 782# Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS 783# as a workaround for broken authentication server implementations unless 784# EAP workarounds are disabled with eap_workarounds=0. 785# For EAP-FAST, this must be set to 0 (or left unconfigured for the 786# default value to be used automatically). 787# 788# Following certificate/private key fields are used in inner Phase2 789# authentication when using EAP-TTLS or EAP-PEAP. 790# ca_cert2: File path to CA certificate file. This file can have one or more 791# trusted CA certificates. If ca_cert2 and ca_path2 are not included, 792# server certificate will not be verified. This is insecure and a trusted 793# CA certificate should always be configured. 794# ca_path2: Directory path for CA certificate files (PEM) 795# client_cert2: File path to client certificate file 796# private_key2: File path to client private key file 797# private_key2_passwd: Password for private key file 798# dh_file2: File path to DH/DSA parameters file (in PEM format) 799# subject_match2: Substring to be matched against the subject of the 800# authentication server certificate. 801# altsubject_match2: Substring to be matched against the alternative subject 802# name of the authentication server certificate. 803# 804# fragment_size: Maximum EAP fragment size in bytes (default 1398). 805# This value limits the fragment size for EAP methods that support 806# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 807# small enough to make the EAP messages fit in MTU of the network 808# interface used for EAPOL. The default value is suitable for most 809# cases. 810# 811# EAP-FAST variables: 812# pac_file: File path for the PAC entries. wpa_supplicant will need to be able 813# to create this file and write updates to it when PAC is being 814# provisioned or refreshed. Full path to the file should be used since 815# working directory may change when wpa_supplicant is run in the 816# background. Alternatively, a named configuration blob can be used by 817# setting this to blob://<blob name> 818# phase1: fast_provisioning option can be used to enable in-line provisioning 819# of EAP-FAST credentials (PAC): 820# 0 = disabled, 821# 1 = allow unauthenticated provisioning, 822# 2 = allow authenticated provisioning, 823# 3 = allow both unauthenticated and authenticated provisioning 824# fast_max_pac_list_len=<num> option can be used to set the maximum 825# number of PAC entries to store in a PAC list (default: 10) 826# fast_pac_format=binary option can be used to select binary format for 827# storing PAC entries in order to save some space (the default 828# text format uses about 2.5 times the size of minimal binary 829# format) 830# 831# wpa_supplicant supports number of "EAP workarounds" to work around 832# interoperability issues with incorrectly behaving authentication servers. 833# These are enabled by default because some of the issues are present in large 834# number of authentication servers. Strict EAP conformance mode can be 835# configured by disabling workarounds with eap_workaround=0. 836 837# Station inactivity limit 838# 839# If a station does not send anything in ap_max_inactivity seconds, an 840# empty data frame is sent to it in order to verify whether it is 841# still in range. If this frame is not ACKed, the station will be 842# disassociated and then deauthenticated. This feature is used to 843# clear station table of old entries when the STAs move out of the 844# range. 845# 846# The station can associate again with the AP if it is still in range; 847# this inactivity poll is just used as a nicer way of verifying 848# inactivity; i.e., client will not report broken connection because 849# disassociation frame is not sent immediately without first polling 850# the STA with a data frame. 851# default: 300 (i.e., 5 minutes) 852#ap_max_inactivity=300 853 854# DTIM period in Beacon intervals for AP mode (default: 2) 855#dtim_period=2 856 857# Beacon interval (default: 100 TU) 858#beacon_int=100 859 860# disable_ht: Whether HT (802.11n) should be disabled. 861# 0 = HT enabled (if AP supports it) 862# 1 = HT disabled 863# 864# disable_ht40: Whether HT-40 (802.11n) should be disabled. 865# 0 = HT-40 enabled (if AP supports it) 866# 1 = HT-40 disabled 867# 868# disable_sgi: Whether SGI (short guard interval) should be disabled. 869# 0 = SGI enabled (if AP supports it) 870# 1 = SGI disabled 871# 872# ht_mcs: Configure allowed MCS rates. 873# Parsed as an array of bytes, in base-16 (ascii-hex) 874# ht_mcs="" // Use all available (default) 875# ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only 876# ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only 877# 878# disable_max_amsdu: Whether MAX_AMSDU should be disabled. 879# -1 = Do not make any changes. 880# 0 = Enable MAX-AMSDU if hardware supports it. 881# 1 = Disable AMSDU 882# 883# ampdu_density: Allow overriding AMPDU density configuration. 884# Treated as hint by the kernel. 885# -1 = Do not make any changes. 886# 0-3 = Set AMPDU density (aka factor) to specified value. 887 888# disable_vht: Whether VHT should be disabled. 889# 0 = VHT enabled (if AP supports it) 890# 1 = VHT disabled 891# 892# vht_capa: VHT capabilities to set in the override 893# vht_capa_mask: mask of VHT capabilities 894# 895# vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8 896# vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8 897# 0: MCS 0-7 898# 1: MCS 0-8 899# 2: MCS 0-9 900# 3: not supported 901 902# Example blocks: 903 904# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers 905network={ 906 ssid="simple" 907 psk="very secret passphrase" 908 priority=5 909} 910 911# Same as previous, but request SSID-specific scanning (for APs that reject 912# broadcast SSID) 913network={ 914 ssid="second ssid" 915 scan_ssid=1 916 psk="very secret passphrase" 917 priority=2 918} 919 920# Only WPA-PSK is used. Any valid cipher combination is accepted. 921network={ 922 ssid="example" 923 proto=WPA 924 key_mgmt=WPA-PSK 925 pairwise=CCMP TKIP 926 group=CCMP TKIP WEP104 WEP40 927 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 928 priority=2 929} 930 931# WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying 932network={ 933 ssid="example" 934 proto=WPA 935 key_mgmt=WPA-PSK 936 pairwise=TKIP 937 group=TKIP 938 psk="not so secure passphrase" 939 wpa_ptk_rekey=600 940} 941 942# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104 943# or WEP40 as the group cipher will not be accepted. 944network={ 945 ssid="example" 946 proto=RSN 947 key_mgmt=WPA-EAP 948 pairwise=CCMP TKIP 949 group=CCMP TKIP 950 eap=TLS 951 identity="user@example.com" 952 ca_cert="/etc/cert/ca.pem" 953 client_cert="/etc/cert/user.pem" 954 private_key="/etc/cert/user.prv" 955 private_key_passwd="password" 956 priority=1 957} 958 959# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel 960# (e.g., Radiator) 961network={ 962 ssid="example" 963 key_mgmt=WPA-EAP 964 eap=PEAP 965 identity="user@example.com" 966 password="foobar" 967 ca_cert="/etc/cert/ca.pem" 968 phase1="peaplabel=1" 969 phase2="auth=MSCHAPV2" 970 priority=10 971} 972 973# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the 974# unencrypted use. Real identity is sent only within an encrypted TLS tunnel. 975network={ 976 ssid="example" 977 key_mgmt=WPA-EAP 978 eap=TTLS 979 identity="user@example.com" 980 anonymous_identity="anonymous@example.com" 981 password="foobar" 982 ca_cert="/etc/cert/ca.pem" 983 priority=2 984} 985 986# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted 987# use. Real identity is sent only within an encrypted TLS tunnel. 988network={ 989 ssid="example" 990 key_mgmt=WPA-EAP 991 eap=TTLS 992 identity="user@example.com" 993 anonymous_identity="anonymous@example.com" 994 password="foobar" 995 ca_cert="/etc/cert/ca.pem" 996 phase2="auth=MSCHAPV2" 997} 998 999# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner 1000# authentication. 1001network={ 1002 ssid="example" 1003 key_mgmt=WPA-EAP 1004 eap=TTLS 1005 # Phase1 / outer authentication 1006 anonymous_identity="anonymous@example.com" 1007 ca_cert="/etc/cert/ca.pem" 1008 # Phase 2 / inner authentication 1009 phase2="autheap=TLS" 1010 ca_cert2="/etc/cert/ca2.pem" 1011 client_cert2="/etc/cer/user.pem" 1012 private_key2="/etc/cer/user.prv" 1013 private_key2_passwd="password" 1014 priority=2 1015} 1016 1017# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and 1018# group cipher. 1019network={ 1020 ssid="example" 1021 bssid=00:11:22:33:44:55 1022 proto=WPA RSN 1023 key_mgmt=WPA-PSK WPA-EAP 1024 pairwise=CCMP 1025 group=CCMP 1026 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 1027} 1028 1029# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP 1030# and all valid ciphers. 1031network={ 1032 ssid=00010203 1033 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 1034} 1035 1036 1037# EAP-SIM with a GSM SIM or USIM 1038network={ 1039 ssid="eap-sim-test" 1040 key_mgmt=WPA-EAP 1041 eap=SIM 1042 pin="1234" 1043 pcsc="" 1044} 1045 1046 1047# EAP-PSK 1048network={ 1049 ssid="eap-psk-test" 1050 key_mgmt=WPA-EAP 1051 eap=PSK 1052 anonymous_identity="eap_psk_user" 1053 password=06b4be19da289f475aa46a33cb793029 1054 identity="eap_psk_user@example.com" 1055} 1056 1057 1058# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using 1059# EAP-TLS for authentication and key generation; require both unicast and 1060# broadcast WEP keys. 1061network={ 1062 ssid="1x-test" 1063 key_mgmt=IEEE8021X 1064 eap=TLS 1065 identity="user@example.com" 1066 ca_cert="/etc/cert/ca.pem" 1067 client_cert="/etc/cert/user.pem" 1068 private_key="/etc/cert/user.prv" 1069 private_key_passwd="password" 1070 eapol_flags=3 1071} 1072 1073 1074# LEAP with dynamic WEP keys 1075network={ 1076 ssid="leap-example" 1077 key_mgmt=IEEE8021X 1078 eap=LEAP 1079 identity="user" 1080 password="foobar" 1081} 1082 1083# EAP-IKEv2 using shared secrets for both server and peer authentication 1084network={ 1085 ssid="ikev2-example" 1086 key_mgmt=WPA-EAP 1087 eap=IKEV2 1088 identity="user" 1089 password="foobar" 1090} 1091 1092# EAP-FAST with WPA (WPA or WPA2) 1093network={ 1094 ssid="eap-fast-test" 1095 key_mgmt=WPA-EAP 1096 eap=FAST 1097 anonymous_identity="FAST-000102030405" 1098 identity="username" 1099 password="password" 1100 phase1="fast_provisioning=1" 1101 pac_file="/etc/wpa_supplicant.eap-fast-pac" 1102} 1103 1104network={ 1105 ssid="eap-fast-test" 1106 key_mgmt=WPA-EAP 1107 eap=FAST 1108 anonymous_identity="FAST-000102030405" 1109 identity="username" 1110 password="password" 1111 phase1="fast_provisioning=1" 1112 pac_file="blob://eap-fast-pac" 1113} 1114 1115# Plaintext connection (no WPA, no IEEE 802.1X) 1116network={ 1117 ssid="plaintext-test" 1118 key_mgmt=NONE 1119} 1120 1121 1122# Shared WEP key connection (no WPA, no IEEE 802.1X) 1123network={ 1124 ssid="static-wep-test" 1125 key_mgmt=NONE 1126 wep_key0="abcde" 1127 wep_key1=0102030405 1128 wep_key2="1234567890123" 1129 wep_tx_keyidx=0 1130 priority=5 1131} 1132 1133 1134# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key 1135# IEEE 802.11 authentication 1136network={ 1137 ssid="static-wep-test2" 1138 key_mgmt=NONE 1139 wep_key0="abcde" 1140 wep_key1=0102030405 1141 wep_key2="1234567890123" 1142 wep_tx_keyidx=0 1143 priority=5 1144 auth_alg=SHARED 1145} 1146 1147 1148# IBSS/ad-hoc network with WPA-None/TKIP. 1149network={ 1150 ssid="test adhoc" 1151 mode=1 1152 frequency=2412 1153 proto=WPA 1154 key_mgmt=WPA-NONE 1155 pairwise=NONE 1156 group=TKIP 1157 psk="secret passphrase" 1158} 1159 1160 1161# Catch all example that allows more or less all configuration modes 1162network={ 1163 ssid="example" 1164 scan_ssid=1 1165 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE 1166 pairwise=CCMP TKIP 1167 group=CCMP TKIP WEP104 WEP40 1168 psk="very secret passphrase" 1169 eap=TTLS PEAP TLS 1170 identity="user@example.com" 1171 password="foobar" 1172 ca_cert="/etc/cert/ca.pem" 1173 client_cert="/etc/cert/user.pem" 1174 private_key="/etc/cert/user.prv" 1175 private_key_passwd="password" 1176 phase1="peaplabel=0" 1177} 1178 1179# Example of EAP-TLS with smartcard (openssl engine) 1180network={ 1181 ssid="example" 1182 key_mgmt=WPA-EAP 1183 eap=TLS 1184 proto=RSN 1185 pairwise=CCMP TKIP 1186 group=CCMP TKIP 1187 identity="user@example.com" 1188 ca_cert="/etc/cert/ca.pem" 1189 client_cert="/etc/cert/user.pem" 1190 1191 engine=1 1192 1193 # The engine configured here must be available. Look at 1194 # OpenSSL engine support in the global section. 1195 # The key available through the engine must be the private key 1196 # matching the client certificate configured above. 1197 1198 # use the opensc engine 1199 #engine_id="opensc" 1200 #key_id="45" 1201 1202 # use the pkcs11 engine 1203 engine_id="pkcs11" 1204 key_id="id_45" 1205 1206 # Optional PIN configuration; this can be left out and PIN will be 1207 # asked through the control interface 1208 pin="1234" 1209} 1210 1211# Example configuration showing how to use an inlined blob as a CA certificate 1212# data instead of using external file 1213network={ 1214 ssid="example" 1215 key_mgmt=WPA-EAP 1216 eap=TTLS 1217 identity="user@example.com" 1218 anonymous_identity="anonymous@example.com" 1219 password="foobar" 1220 ca_cert="blob://exampleblob" 1221 priority=20 1222} 1223 1224blob-base64-exampleblob={ 1225SGVsbG8gV29ybGQhCg== 1226} 1227 1228 1229# Wildcard match for SSID (plaintext APs only). This example select any 1230# open AP regardless of its SSID. 1231network={ 1232 key_mgmt=NONE 1233} 1234