wpa_supplicant.conf revision d5e4923d04122f81300fa68fb07d64ede28fd44d
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# Interworking (IEEE 802.11u) 285 286# Enable Interworking 287# interworking=1 288 289# Homogenous ESS identifier 290# If this is set, scans will be used to request response only from BSSes 291# belonging to the specified Homogeneous ESS. This is used only if interworking 292# is enabled. 293# hessid=00:11:22:33:44:55 294 295# Automatic network selection behavior 296# 0 = do not automatically go through Interworking network selection 297# (i.e., require explicit interworking_select command for this; default) 298# 1 = perform Interworking network selection if one or more 299# credentials have been configured and scan did not find a 300# matching network block 301#auto_interworking=0 302 303# credential block 304# 305# Each credential used for automatic network selection is configured as a set 306# of parameters that are compared to the information advertised by the APs when 307# interworking_select and interworking_connect commands are used. 308# 309# credential fields: 310# 311# priority: Priority group 312# By default, all networks and credentials get the same priority group 313# (0). This field can be used to give higher priority for credentials 314# (and similarly in struct wpa_ssid for network blocks) to change the 315# Interworking automatic networking selection behavior. The matching 316# network (based on either an enabled network block or a credential) 317# with the highest priority value will be selected. 318# 319# pcsc: Use PC/SC and SIM/USIM card 320# 321# realm: Home Realm for Interworking 322# 323# username: Username for Interworking network selection 324# 325# password: Password for Interworking network selection 326# 327# ca_cert: CA certificate for Interworking network selection 328# 329# client_cert: File path to client certificate file (PEM/DER) 330# This field is used with Interworking networking selection for a case 331# where client certificate/private key is used for authentication 332# (EAP-TLS). Full path to the file should be used since working 333# directory may change when wpa_supplicant is run in the background. 334# 335# Alternatively, a named configuration blob can be used by setting 336# this to blob://blob_name. 337# 338# private_key: File path to client private key file (PEM/DER/PFX) 339# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 340# commented out. Both the private key and certificate will be read 341# from the PKCS#12 file in this case. Full path to the file should be 342# used since working directory may change when wpa_supplicant is run 343# in the background. 344# 345# Windows certificate store can be used by leaving client_cert out and 346# configuring private_key in one of the following formats: 347# 348# cert://substring_to_match 349# 350# hash://certificate_thumbprint_in_hex 351# 352# For example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 353# 354# Note that when running wpa_supplicant as an application, the user 355# certificate store (My user account) is used, whereas computer store 356# (Computer account) is used when running wpasvc as a service. 357# 358# Alternatively, a named configuration blob can be used by setting 359# this to blob://blob_name. 360# 361# private_key_passwd: Password for private key file 362# 363# imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format 364# 365# milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN> 366# format 367# 368# domain: Home service provider FQDN 369# This is used to compare against the Domain Name List to figure out 370# whether the AP is operated by the Home SP. 371# 372# roaming_consortium: Roaming Consortium OI 373# If roaming_consortium_len is non-zero, this field contains the 374# Roaming Consortium OI that can be used to determine which access 375# points support authentication with this credential. This is an 376# alternative to the use of the realm parameter. When using Roaming 377# Consortium to match the network, the EAP parameters need to be 378# pre-configured with the credential since the NAI Realm information 379# may not be available or fetched. 380# 381# eap: Pre-configured EAP method 382# This optional field can be used to specify which EAP method will be 383# used with this credential. If not set, the EAP method is selected 384# automatically based on ANQP information (e.g., NAI Realm). 385# 386# phase1: Pre-configure Phase 1 (outer authentication) parameters 387# This optional field is used with like the 'eap' parameter. 388# 389# phase2: Pre-configure Phase 2 (inner authentication) parameters 390# This optional field is used with like the 'eap' parameter. 391# 392# for example: 393# 394#cred={ 395# realm="example.com" 396# username="user@example.com" 397# password="password" 398# ca_cert="/etc/wpa_supplicant/ca.pem" 399# domain="example.com" 400#} 401# 402#cred={ 403# imsi="310026-000000000" 404# milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82" 405#} 406# 407#cred={ 408# realm="example.com" 409# username="user" 410# password="password" 411# ca_cert="/etc/wpa_supplicant/ca.pem" 412# domain="example.com" 413# roaming_consortium=223344 414# eap=TTLS 415# phase2="auth=MSCHAPV2" 416#} 417 418# Hotspot 2.0 419# hs20=1 420 421# network block 422# 423# Each network (usually AP's sharing the same SSID) is configured as a separate 424# block in this configuration file. The network blocks are in preference order 425# (the first match is used). 426# 427# network block fields: 428# 429# disabled: 430# 0 = this network can be used (default) 431# 1 = this network block is disabled (can be enabled through ctrl_iface, 432# e.g., with wpa_cli or wpa_gui) 433# 434# id_str: Network identifier string for external scripts. This value is passed 435# to external action script through wpa_cli as WPA_ID_STR environment 436# variable to make it easier to do network specific configuration. 437# 438# ssid: SSID (mandatory); network name in one of the optional formats: 439# - an ASCII string with double quotation 440# - a hex string (two characters per octet of SSID) 441# - a printf-escaped ASCII string P"<escaped string>" 442# 443# scan_ssid: 444# 0 = do not scan this SSID with specific Probe Request frames (default) 445# 1 = scan with SSID-specific Probe Request frames (this can be used to 446# find APs that do not accept broadcast SSID or use multiple SSIDs; 447# this will add latency to scanning, so enable this only when needed) 448# 449# bssid: BSSID (optional); if set, this network block is used only when 450# associating with the AP using the configured BSSID 451# 452# priority: priority group (integer) 453# By default, all networks will get same priority group (0). If some of the 454# networks are more desirable, this field can be used to change the order in 455# which wpa_supplicant goes through the networks when selecting a BSS. The 456# priority groups will be iterated in decreasing priority (i.e., the larger the 457# priority value, the sooner the network is matched against the scan results). 458# Within each priority group, networks will be selected based on security 459# policy, signal strength, etc. 460# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not 461# using this priority to select the order for scanning. Instead, they try the 462# networks in the order that used in the configuration file. 463# 464# mode: IEEE 802.11 operation mode 465# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default) 466# 1 = IBSS (ad-hoc, peer-to-peer) 467# 2 = AP (access point) 468# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) 469# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). WPA-None requires 470# following network block options: 471# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not 472# both), and psk must also be set. 473# 474# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g., 475# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial 476# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode. 477# In addition, this value is only used by the station that creates the IBSS. If 478# an IBSS network with the configured SSID is already present, the frequency of 479# the network will be used instead of this configured value. 480# 481# scan_freq: List of frequencies to scan 482# Space-separated list of frequencies in MHz to scan when searching for this 483# BSS. If the subset of channels used by the network is known, this option can 484# be used to optimize scanning to not occur on channels that the network does 485# not use. Example: scan_freq=2412 2437 2462 486# 487# freq_list: Array of allowed frequencies 488# Space-separated list of frequencies in MHz to allow for selecting the BSS. If 489# set, scan results that do not match any of the specified frequencies are not 490# considered when selecting a BSS. 491# 492# proto: list of accepted protocols 493# WPA = WPA/IEEE 802.11i/D3.0 494# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN) 495# If not set, this defaults to: WPA RSN 496# 497# key_mgmt: list of accepted authenticated key management protocols 498# WPA-PSK = WPA pre-shared key (this requires 'psk' field) 499# WPA-EAP = WPA using EAP authentication 500# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically 501# generated WEP keys 502# NONE = WPA is not used; plaintext or static WEP could be used 503# WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms 504# WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms 505# If not set, this defaults to: WPA-PSK WPA-EAP 506# 507# ieee80211w: whether management frame protection is enabled 508# 0 = disabled (default unless changed with the global pmf parameter) 509# 1 = optional 510# 2 = required 511# The most common configuration options for this based on the PMF (protected 512# management frames) certification program are: 513# PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256 514# PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256 515# (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used) 516# 517# auth_alg: list of allowed IEEE 802.11 authentication algorithms 518# OPEN = Open System authentication (required for WPA/WPA2) 519# SHARED = Shared Key authentication (requires static WEP keys) 520# LEAP = LEAP/Network EAP (only used with LEAP) 521# If not set, automatic selection is used (Open System with LEAP enabled if 522# LEAP is allowed as one of the EAP methods). 523# 524# pairwise: list of accepted pairwise (unicast) ciphers for WPA 525# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 526# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 527# NONE = Use only Group Keys (deprecated, should not be included if APs support 528# pairwise keys) 529# If not set, this defaults to: CCMP TKIP 530# 531# group: list of accepted group (broadcast/multicast) ciphers for WPA 532# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 533# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 534# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key 535# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11] 536# If not set, this defaults to: CCMP TKIP WEP104 WEP40 537# 538# psk: WPA preshared key; 256-bit pre-shared key 539# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., 540# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be 541# generated using the passphrase and SSID). ASCII passphrase must be between 542# 8 and 63 characters (inclusive). ext:<name of external PSK field> format can 543# be used to indicate that the PSK/passphrase is stored in external storage. 544# This field is not needed, if WPA-EAP is used. 545# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys 546# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant 547# startup and reconfiguration time can be optimized by generating the PSK only 548# only when the passphrase or SSID has actually changed. 549# 550# eapol_flags: IEEE 802.1X/EAPOL options (bit field) 551# Dynamic WEP key required for non-WPA mode 552# bit0 (1): require dynamically generated unicast WEP key 553# bit1 (2): require dynamically generated broadcast WEP key 554# (3 = require both keys; default) 555# Note: When using wired authentication, eapol_flags must be set to 0 for the 556# authentication to be completed successfully. 557# 558# mixed_cell: This option can be used to configure whether so called mixed 559# cells, i.e., networks that use both plaintext and encryption in the same 560# SSID, are allowed when selecting a BSS from scan results. 561# 0 = disabled (default) 562# 1 = enabled 563# 564# proactive_key_caching: 565# Enable/disable opportunistic PMKSA caching for WPA2. 566# 0 = disabled (default unless changed with the global okc parameter) 567# 1 = enabled 568# 569# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or 570# hex without quotation, e.g., 0102030405) 571# wep_tx_keyidx: Default WEP key index (TX) (0..3) 572# 573# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is 574# allowed. This is only used with RSN/WPA2. 575# 0 = disabled (default) 576# 1 = enabled 577#peerkey=1 578# 579# wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to 580# enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies. 581# 582# Following fields are only used with internal EAP implementation. 583# eap: space-separated list of accepted EAP methods 584# MD5 = EAP-MD5 (unsecure and does not generate keying material -> 585# cannot be used with WPA; to be used as a Phase 2 method 586# with EAP-PEAP or EAP-TTLS) 587# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used 588# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 589# OTP = EAP-OTP (cannot be used separately with WPA; to be used 590# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 591# GTC = EAP-GTC (cannot be used separately with WPA; to be used 592# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 593# TLS = EAP-TLS (client and server certificate) 594# PEAP = EAP-PEAP (with tunnelled EAP authentication) 595# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2 596# authentication) 597# If not set, all compiled in methods are allowed. 598# 599# identity: Identity string for EAP 600# This field is also used to configure user NAI for 601# EAP-PSK/PAX/SAKE/GPSK. 602# anonymous_identity: Anonymous identity string for EAP (to be used as the 603# unencrypted identity with EAP types that support different tunnelled 604# identity, e.g., EAP-TTLS). This field can also be used with 605# EAP-SIM/AKA/AKA' to store the pseudonym identity. 606# password: Password string for EAP. This field can include either the 607# plaintext password (using ASCII or hex string) or a NtPasswordHash 608# (16-byte MD4 hash of password) in hash:<32 hex digits> format. 609# NtPasswordHash can only be used when the password is for MSCHAPv2 or 610# MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP). 611# EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit 612# PSK) is also configured using this field. For EAP-GPSK, this is a 613# variable length PSK. ext:<name of external password field> format can 614# be used to indicate that the password is stored in external storage. 615# ca_cert: File path to CA certificate file (PEM/DER). This file can have one 616# or more trusted CA certificates. If ca_cert and ca_path are not 617# included, server certificate will not be verified. This is insecure and 618# a trusted CA certificate should always be configured when using 619# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may 620# change when wpa_supplicant is run in the background. 621# 622# Alternatively, this can be used to only perform matching of the server 623# certificate (SHA-256 hash of the DER encoded X.509 certificate). In 624# this case, the possible CA certificates in the server certificate chain 625# are ignored and only the server certificate is verified. This is 626# configured with the following format: 627# hash:://server/sha256/cert_hash_in_hex 628# For example: "hash://server/sha256/ 629# 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a" 630# 631# On Windows, trusted CA certificates can be loaded from the system 632# certificate store by setting this to cert_store://<name>, e.g., 633# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 634# Note that when running wpa_supplicant as an application, the user 635# certificate store (My user account) is used, whereas computer store 636# (Computer account) is used when running wpasvc as a service. 637# ca_path: Directory path for CA certificate files (PEM). This path may 638# contain multiple CA certificates in OpenSSL format. Common use for this 639# is to point to system trusted CA list which is often installed into 640# directory like /etc/ssl/certs. If configured, these certificates are 641# added to the list of trusted CAs. ca_cert may also be included in that 642# case, but it is not required. 643# client_cert: File path to client certificate file (PEM/DER) 644# Full path should be used since working directory may change when 645# wpa_supplicant is run in the background. 646# Alternatively, a named configuration blob can be used by setting this 647# to blob://<blob name>. 648# private_key: File path to client private key file (PEM/DER/PFX) 649# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 650# commented out. Both the private key and certificate will be read from 651# the PKCS#12 file in this case. Full path should be used since working 652# directory may change when wpa_supplicant is run in the background. 653# Windows certificate store can be used by leaving client_cert out and 654# configuring private_key in one of the following formats: 655# cert://substring_to_match 656# hash://certificate_thumbprint_in_hex 657# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 658# Note that when running wpa_supplicant as an application, the user 659# certificate store (My user account) is used, whereas computer store 660# (Computer account) is used when running wpasvc as a service. 661# Alternatively, a named configuration blob can be used by setting this 662# to blob://<blob name>. 663# private_key_passwd: Password for private key file (if left out, this will be 664# asked through control interface) 665# dh_file: File path to DH/DSA parameters file (in PEM format) 666# This is an optional configuration file for setting parameters for an 667# ephemeral DH key exchange. In most cases, the default RSA 668# authentication does not use this configuration. However, it is possible 669# setup RSA to use ephemeral DH key exchange. In addition, ciphers with 670# DSA keys always use ephemeral DH keys. This can be used to achieve 671# forward secrecy. If the file is in DSA parameters format, it will be 672# automatically converted into DH params. 673# subject_match: Substring to be matched against the subject of the 674# authentication server certificate. If this string is set, the server 675# sertificate is only accepted if it contains this string in the subject. 676# The subject string is in following format: 677# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com 678# altsubject_match: Semicolon separated string of entries to be matched against 679# the alternative subject name of the authentication server certificate. 680# If this string is set, the server sertificate is only accepted if it 681# contains one of the entries in an alternative subject name extension. 682# altSubjectName string is in following format: TYPE:VALUE 683# Example: EMAIL:server@example.com 684# Example: DNS:server.example.com;DNS:server2.example.com 685# Following types are supported: EMAIL, DNS, URI 686# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters 687# (string with field-value pairs, e.g., "peapver=0" or 688# "peapver=1 peaplabel=1") 689# 'peapver' can be used to force which PEAP version (0 or 1) is used. 690# 'peaplabel=1' can be used to force new label, "client PEAP encryption", 691# to be used during key derivation when PEAPv1 or newer. Most existing 692# PEAPv1 implementation seem to be using the old label, "client EAP 693# encryption", and wpa_supplicant is now using that as the default value. 694# Some servers, e.g., Radiator, may require peaplabel=1 configuration to 695# interoperate with PEAPv1; see eap_testing.txt for more details. 696# 'peap_outer_success=0' can be used to terminate PEAP authentication on 697# tunneled EAP-Success. This is required with some RADIUS servers that 698# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 699# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode) 700# include_tls_length=1 can be used to force wpa_supplicant to include 701# TLS Message Length field in all TLS messages even if they are not 702# fragmented. 703# sim_min_num_chal=3 can be used to configure EAP-SIM to require three 704# challenges (by default, it accepts 2 or 3) 705# result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use 706# protected result indication. 707# 'crypto_binding' option can be used to control PEAPv0 cryptobinding 708# behavior: 709# * 0 = do not use cryptobinding (default) 710# * 1 = use cryptobinding if server supports it 711# * 2 = require cryptobinding 712# EAP-WSC (WPS) uses following options: pin=<Device Password> or 713# pbc=1. 714# phase2: Phase2 (inner authentication with TLS tunnel) parameters 715# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 716# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS) 717# 718# TLS-based methods can use the following parameters to control TLS behavior 719# (these are normally in the phase1 parameter, but can be used also in the 720# phase2 parameter when EAP-TLS is used within the inner tunnel): 721# tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the 722# TLS library, these may be disabled by default to enforce stronger 723# security) 724# tls_disable_time_checks=1 - ignore certificate validity time (this requests 725# the TLS library to accept certificates even if they are not currently 726# valid, i.e., have expired or have not yet become valid; this should be 727# used only for testing purposes) 728# tls_disable_session_ticket=1 - disable TLS Session Ticket extension 729# tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used 730# Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS 731# as a workaround for broken authentication server implementations unless 732# EAP workarounds are disabled with eap_workarounds=0. 733# For EAP-FAST, this must be set to 0 (or left unconfigured for the 734# default value to be used automatically). 735# 736# Following certificate/private key fields are used in inner Phase2 737# authentication when using EAP-TTLS or EAP-PEAP. 738# ca_cert2: File path to CA certificate file. This file can have one or more 739# trusted CA certificates. If ca_cert2 and ca_path2 are not included, 740# server certificate will not be verified. This is insecure and a trusted 741# CA certificate should always be configured. 742# ca_path2: Directory path for CA certificate files (PEM) 743# client_cert2: File path to client certificate file 744# private_key2: File path to client private key file 745# private_key2_passwd: Password for private key file 746# dh_file2: File path to DH/DSA parameters file (in PEM format) 747# subject_match2: Substring to be matched against the subject of the 748# authentication server certificate. 749# altsubject_match2: Substring to be matched against the alternative subject 750# name of the authentication server certificate. 751# 752# fragment_size: Maximum EAP fragment size in bytes (default 1398). 753# This value limits the fragment size for EAP methods that support 754# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 755# small enough to make the EAP messages fit in MTU of the network 756# interface used for EAPOL. The default value is suitable for most 757# cases. 758# 759# EAP-FAST variables: 760# pac_file: File path for the PAC entries. wpa_supplicant will need to be able 761# to create this file and write updates to it when PAC is being 762# provisioned or refreshed. Full path to the file should be used since 763# working directory may change when wpa_supplicant is run in the 764# background. Alternatively, a named configuration blob can be used by 765# setting this to blob://<blob name> 766# phase1: fast_provisioning option can be used to enable in-line provisioning 767# of EAP-FAST credentials (PAC): 768# 0 = disabled, 769# 1 = allow unauthenticated provisioning, 770# 2 = allow authenticated provisioning, 771# 3 = allow both unauthenticated and authenticated provisioning 772# fast_max_pac_list_len=<num> option can be used to set the maximum 773# number of PAC entries to store in a PAC list (default: 10) 774# fast_pac_format=binary option can be used to select binary format for 775# storing PAC entries in order to save some space (the default 776# text format uses about 2.5 times the size of minimal binary 777# format) 778# 779# wpa_supplicant supports number of "EAP workarounds" to work around 780# interoperability issues with incorrectly behaving authentication servers. 781# These are enabled by default because some of the issues are present in large 782# number of authentication servers. Strict EAP conformance mode can be 783# configured by disabling workarounds with eap_workaround=0. 784 785# Station inactivity limit 786# 787# If a station does not send anything in ap_max_inactivity seconds, an 788# empty data frame is sent to it in order to verify whether it is 789# still in range. If this frame is not ACKed, the station will be 790# disassociated and then deauthenticated. This feature is used to 791# clear station table of old entries when the STAs move out of the 792# range. 793# 794# The station can associate again with the AP if it is still in range; 795# this inactivity poll is just used as a nicer way of verifying 796# inactivity; i.e., client will not report broken connection because 797# disassociation frame is not sent immediately without first polling 798# the STA with a data frame. 799# default: 300 (i.e., 5 minutes) 800#ap_max_inactivity=300 801 802# DTIM period in Beacon intervals for AP mode (default: 2) 803#dtim_period=2 804 805# Example blocks: 806 807# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers 808network={ 809 ssid="simple" 810 psk="very secret passphrase" 811 priority=5 812} 813 814# Same as previous, but request SSID-specific scanning (for APs that reject 815# broadcast SSID) 816network={ 817 ssid="second ssid" 818 scan_ssid=1 819 psk="very secret passphrase" 820 priority=2 821} 822 823# Only WPA-PSK is used. Any valid cipher combination is accepted. 824network={ 825 ssid="example" 826 proto=WPA 827 key_mgmt=WPA-PSK 828 pairwise=CCMP TKIP 829 group=CCMP TKIP WEP104 WEP40 830 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 831 priority=2 832} 833 834# WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying 835network={ 836 ssid="example" 837 proto=WPA 838 key_mgmt=WPA-PSK 839 pairwise=TKIP 840 group=TKIP 841 psk="not so secure passphrase" 842 wpa_ptk_rekey=600 843} 844 845# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104 846# or WEP40 as the group cipher will not be accepted. 847network={ 848 ssid="example" 849 proto=RSN 850 key_mgmt=WPA-EAP 851 pairwise=CCMP TKIP 852 group=CCMP TKIP 853 eap=TLS 854 identity="user@example.com" 855 ca_cert="/etc/cert/ca.pem" 856 client_cert="/etc/cert/user.pem" 857 private_key="/etc/cert/user.prv" 858 private_key_passwd="password" 859 priority=1 860} 861 862# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel 863# (e.g., Radiator) 864network={ 865 ssid="example" 866 key_mgmt=WPA-EAP 867 eap=PEAP 868 identity="user@example.com" 869 password="foobar" 870 ca_cert="/etc/cert/ca.pem" 871 phase1="peaplabel=1" 872 phase2="auth=MSCHAPV2" 873 priority=10 874} 875 876# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the 877# unencrypted use. Real identity is sent only within an encrypted TLS tunnel. 878network={ 879 ssid="example" 880 key_mgmt=WPA-EAP 881 eap=TTLS 882 identity="user@example.com" 883 anonymous_identity="anonymous@example.com" 884 password="foobar" 885 ca_cert="/etc/cert/ca.pem" 886 priority=2 887} 888 889# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted 890# use. Real identity is sent only within an encrypted TLS tunnel. 891network={ 892 ssid="example" 893 key_mgmt=WPA-EAP 894 eap=TTLS 895 identity="user@example.com" 896 anonymous_identity="anonymous@example.com" 897 password="foobar" 898 ca_cert="/etc/cert/ca.pem" 899 phase2="auth=MSCHAPV2" 900} 901 902# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner 903# authentication. 904network={ 905 ssid="example" 906 key_mgmt=WPA-EAP 907 eap=TTLS 908 # Phase1 / outer authentication 909 anonymous_identity="anonymous@example.com" 910 ca_cert="/etc/cert/ca.pem" 911 # Phase 2 / inner authentication 912 phase2="autheap=TLS" 913 ca_cert2="/etc/cert/ca2.pem" 914 client_cert2="/etc/cer/user.pem" 915 private_key2="/etc/cer/user.prv" 916 private_key2_passwd="password" 917 priority=2 918} 919 920# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and 921# group cipher. 922network={ 923 ssid="example" 924 bssid=00:11:22:33:44:55 925 proto=WPA RSN 926 key_mgmt=WPA-PSK WPA-EAP 927 pairwise=CCMP 928 group=CCMP 929 psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 930} 931 932# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP 933# and all valid ciphers. 934network={ 935 ssid=00010203 936 psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 937} 938 939 940# EAP-SIM with a GSM SIM or USIM 941network={ 942 ssid="eap-sim-test" 943 key_mgmt=WPA-EAP 944 eap=SIM 945 pin="1234" 946 pcsc="" 947} 948 949 950# EAP-PSK 951network={ 952 ssid="eap-psk-test" 953 key_mgmt=WPA-EAP 954 eap=PSK 955 anonymous_identity="eap_psk_user" 956 password=06b4be19da289f475aa46a33cb793029 957 identity="eap_psk_user@example.com" 958} 959 960 961# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using 962# EAP-TLS for authentication and key generation; require both unicast and 963# broadcast WEP keys. 964network={ 965 ssid="1x-test" 966 key_mgmt=IEEE8021X 967 eap=TLS 968 identity="user@example.com" 969 ca_cert="/etc/cert/ca.pem" 970 client_cert="/etc/cert/user.pem" 971 private_key="/etc/cert/user.prv" 972 private_key_passwd="password" 973 eapol_flags=3 974} 975 976 977# LEAP with dynamic WEP keys 978network={ 979 ssid="leap-example" 980 key_mgmt=IEEE8021X 981 eap=LEAP 982 identity="user" 983 password="foobar" 984} 985 986# EAP-IKEv2 using shared secrets for both server and peer authentication 987network={ 988 ssid="ikev2-example" 989 key_mgmt=WPA-EAP 990 eap=IKEV2 991 identity="user" 992 password="foobar" 993} 994 995# EAP-FAST with WPA (WPA or WPA2) 996network={ 997 ssid="eap-fast-test" 998 key_mgmt=WPA-EAP 999 eap=FAST 1000 anonymous_identity="FAST-000102030405" 1001 identity="username" 1002 password="password" 1003 phase1="fast_provisioning=1" 1004 pac_file="/etc/wpa_supplicant.eap-fast-pac" 1005} 1006 1007network={ 1008 ssid="eap-fast-test" 1009 key_mgmt=WPA-EAP 1010 eap=FAST 1011 anonymous_identity="FAST-000102030405" 1012 identity="username" 1013 password="password" 1014 phase1="fast_provisioning=1" 1015 pac_file="blob://eap-fast-pac" 1016} 1017 1018# Plaintext connection (no WPA, no IEEE 802.1X) 1019network={ 1020 ssid="plaintext-test" 1021 key_mgmt=NONE 1022} 1023 1024 1025# Shared WEP key connection (no WPA, no IEEE 802.1X) 1026network={ 1027 ssid="static-wep-test" 1028 key_mgmt=NONE 1029 wep_key0="abcde" 1030 wep_key1=0102030405 1031 wep_key2="1234567890123" 1032 wep_tx_keyidx=0 1033 priority=5 1034} 1035 1036 1037# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key 1038# IEEE 802.11 authentication 1039network={ 1040 ssid="static-wep-test2" 1041 key_mgmt=NONE 1042 wep_key0="abcde" 1043 wep_key1=0102030405 1044 wep_key2="1234567890123" 1045 wep_tx_keyidx=0 1046 priority=5 1047 auth_alg=SHARED 1048} 1049 1050 1051# IBSS/ad-hoc network with WPA-None/TKIP. 1052network={ 1053 ssid="test adhoc" 1054 mode=1 1055 frequency=2412 1056 proto=WPA 1057 key_mgmt=WPA-NONE 1058 pairwise=NONE 1059 group=TKIP 1060 psk="secret passphrase" 1061} 1062 1063 1064# Catch all example that allows more or less all configuration modes 1065network={ 1066 ssid="example" 1067 scan_ssid=1 1068 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE 1069 pairwise=CCMP TKIP 1070 group=CCMP TKIP WEP104 WEP40 1071 psk="very secret passphrase" 1072 eap=TTLS PEAP TLS 1073 identity="user@example.com" 1074 password="foobar" 1075 ca_cert="/etc/cert/ca.pem" 1076 client_cert="/etc/cert/user.pem" 1077 private_key="/etc/cert/user.prv" 1078 private_key_passwd="password" 1079 phase1="peaplabel=0" 1080} 1081 1082# Example of EAP-TLS with smartcard (openssl engine) 1083network={ 1084 ssid="example" 1085 key_mgmt=WPA-EAP 1086 eap=TLS 1087 proto=RSN 1088 pairwise=CCMP TKIP 1089 group=CCMP TKIP 1090 identity="user@example.com" 1091 ca_cert="/etc/cert/ca.pem" 1092 client_cert="/etc/cert/user.pem" 1093 1094 engine=1 1095 1096 # The engine configured here must be available. Look at 1097 # OpenSSL engine support in the global section. 1098 # The key available through the engine must be the private key 1099 # matching the client certificate configured above. 1100 1101 # use the opensc engine 1102 #engine_id="opensc" 1103 #key_id="45" 1104 1105 # use the pkcs11 engine 1106 engine_id="pkcs11" 1107 key_id="id_45" 1108 1109 # Optional PIN configuration; this can be left out and PIN will be 1110 # asked through the control interface 1111 pin="1234" 1112} 1113 1114# Example configuration showing how to use an inlined blob as a CA certificate 1115# data instead of using external file 1116network={ 1117 ssid="example" 1118 key_mgmt=WPA-EAP 1119 eap=TTLS 1120 identity="user@example.com" 1121 anonymous_identity="anonymous@example.com" 1122 password="foobar" 1123 ca_cert="blob://exampleblob" 1124 priority=20 1125} 1126 1127blob-base64-exampleblob={ 1128SGVsbG8gV29ybGQhCg== 1129} 1130 1131 1132# Wildcard match for SSID (plaintext APs only). This example select any 1133# open AP regardless of its SSID. 1134network={ 1135 key_mgmt=NONE 1136} 1137