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