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