SliTaz Repositories

     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/wpa_supplicant/stuff/etc/wpa/wpa_supplicant.conf	Sun Mar 23 22:37:08 2014 +0100
     1.3 @@ -0,0 +1,1273 @@
     1.4 +##### Example wpa_supplicant configuration file ###############################
     1.5 +#
     1.6 +# This file describes configuration file format and lists all available option.
     1.7 +# Please also take a look at simpler configuration examples in 'examples'
     1.8 +# subdirectory.
     1.9 +#
    1.10 +# Empty lines and lines starting with # are ignored
    1.11 +
    1.12 +# NOTE! This file may contain password information and should probably be made
    1.13 +# readable only by root user on multiuser systems.
    1.14 +
    1.15 +# Note: All file paths in this configuration file should use full (absolute,
    1.16 +# not relative to working directory) path in order to allow working directory
    1.17 +# to be changed. This can happen if wpa_supplicant is run in the background.
    1.18 +
    1.19 +# Whether to allow wpa_supplicant to update (overwrite) configuration
    1.20 +#
    1.21 +# This option can be used to allow wpa_supplicant to overwrite configuration
    1.22 +# file whenever configuration is changed (e.g., new network block is added with
    1.23 +# wpa_cli or wpa_gui, or a password is changed). This is required for
    1.24 +# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
    1.25 +# Please note that overwriting configuration file will remove the comments from
    1.26 +# it.
    1.27 +#update_config=1
    1.28 +
    1.29 +# global configuration (shared by all network blocks)
    1.30 +#
    1.31 +# Parameters for the control interface. If this is specified, wpa_supplicant
    1.32 +# will open a control interface that is available for external programs to
    1.33 +# manage wpa_supplicant. The meaning of this string depends on which control
    1.34 +# interface mechanism is used. For all cases, the existence of this parameter
    1.35 +# in configuration is used to determine whether the control interface is
    1.36 +# enabled.
    1.37 +#
    1.38 +# For UNIX domain sockets (default on Linux and BSD): This is a directory that
    1.39 +# will be created for UNIX domain sockets for listening to requests from
    1.40 +# external programs (CLI/GUI, etc.) for status information and configuration.
    1.41 +# The socket file will be named based on the interface name, so multiple
    1.42 +# wpa_supplicant processes can be run at the same time if more than one
    1.43 +# interface is used.
    1.44 +# /var/run/wpa_supplicant is the recommended directory for sockets and by
    1.45 +# default, wpa_cli will use it when trying to connect with wpa_supplicant.
    1.46 +#
    1.47 +# Access control for the control interface can be configured by setting the
    1.48 +# directory to allow only members of a group to use sockets. This way, it is
    1.49 +# possible to run wpa_supplicant as root (since it needs to change network
    1.50 +# configuration and open raw sockets) and still allow GUI/CLI components to be
    1.51 +# run as non-root users. However, since the control interface can be used to
    1.52 +# change the network configuration, this access needs to be protected in many
    1.53 +# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
    1.54 +# want to allow non-root users to use the control interface, add a new group
    1.55 +# and change this value to match with that group. Add users that should have
    1.56 +# control interface access to this group. If this variable is commented out or
    1.57 +# not included in the configuration file, group will not be changed from the
    1.58 +# value it got by default when the directory or socket was created.
    1.59 +#
    1.60 +# When configuring both the directory and group, use following format:
    1.61 +# DIR=/var/run/wpa_supplicant GROUP=wheel
    1.62 +# DIR=/var/run/wpa_supplicant GROUP=0
    1.63 +# (group can be either group name or gid)
    1.64 +#
    1.65 +# For UDP connections (default on Windows): The value will be ignored. This
    1.66 +# variable is just used to select that the control interface is to be created.
    1.67 +# The value can be set to, e.g., udp (ctrl_interface=udp)
    1.68 +#
    1.69 +# For Windows Named Pipe: This value can be used to set the security descriptor
    1.70 +# for controlling access to the control interface. Security descriptor can be
    1.71 +# set using Security Descriptor String Format (see http://msdn.microsoft.com/
    1.72 +# library/default.asp?url=/library/en-us/secauthz/security/
    1.73 +# security_descriptor_string_format.asp). The descriptor string needs to be
    1.74 +# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
    1.75 +# DACL (which will reject all connections). See README-Windows.txt for more
    1.76 +# information about SDDL string format.
    1.77 +#
    1.78 +ctrl_interface=/var/run/wpa_supplicant
    1.79 +
    1.80 +# IEEE 802.1X/EAPOL version
    1.81 +# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
    1.82 +# EAPOL version 2. However, there are many APs that do not handle the new
    1.83 +# version number correctly (they seem to drop the frames completely). In order
    1.84 +# to make wpa_supplicant interoperate with these APs, the version number is set
    1.85 +# to 1 by default. This configuration value can be used to set it to the new
    1.86 +# version (2).
    1.87 +eapol_version=1
    1.88 +
    1.89 +# AP scanning/selection
    1.90 +# By default, wpa_supplicant requests driver to perform AP scanning and then
    1.91 +# uses the scan results to select a suitable AP. Another alternative is to
    1.92 +# allow the driver to take care of AP scanning and selection and use
    1.93 +# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
    1.94 +# information from the driver.
    1.95 +# 1: wpa_supplicant initiates scanning and AP selection; if no APs matching to
    1.96 +#    the currently enabled networks are found, a new network (IBSS or AP mode
    1.97 +#    operation) may be initialized (if configured) (default)
    1.98 +# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
    1.99 +#    parameters (e.g., WPA IE generation); this mode can also be used with
   1.100 +#    non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
   1.101 +#    APs (i.e., external program needs to control association). This mode must
   1.102 +#    also be used when using wired Ethernet drivers.
   1.103 +# 2: like 0, but associate with APs using security policy and SSID (but not
   1.104 +#    BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
   1.105 +#    enable operation with hidden SSIDs and optimized roaming; in this mode,
   1.106 +#    the network blocks in the configuration file are tried one by one until
   1.107 +#    the driver reports successful association; each network block should have
   1.108 +#    explicit security policy (i.e., only one option in the lists) for
   1.109 +#    key_mgmt, pairwise, group, proto variables
   1.110 +# When using IBSS or AP mode, ap_scan=2 mode can force the new network to be
   1.111 +# created immediately regardless of scan results. ap_scan=1 mode will first try
   1.112 +# to scan for existing networks and only if no matches with the enabled
   1.113 +# networks are found, a new IBSS or AP mode network is created.
   1.114 +ap_scan=1
   1.115 +
   1.116 +# EAP fast re-authentication
   1.117 +# By default, fast re-authentication is enabled for all EAP methods that
   1.118 +# support it. This variable can be used to disable fast re-authentication.
   1.119 +# Normally, there is no need to disable this.
   1.120 +fast_reauth=1
   1.121 +
   1.122 +# OpenSSL Engine support
   1.123 +# These options can be used to load OpenSSL engines.
   1.124 +# The two engines that are supported currently are shown below:
   1.125 +# They are both from the opensc project (http://www.opensc.org/)
   1.126 +# By default no engines are loaded.
   1.127 +# make the opensc engine available
   1.128 +#opensc_engine_path=/usr/lib/opensc/engine_opensc.so
   1.129 +# make the pkcs11 engine available
   1.130 +#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
   1.131 +# configure the path to the pkcs11 module required by the pkcs11 engine
   1.132 +#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
   1.133 +
   1.134 +# Dynamic EAP methods
   1.135 +# If EAP methods were built dynamically as shared object files, they need to be
   1.136 +# loaded here before being used in the network blocks. By default, EAP methods
   1.137 +# are included statically in the build, so these lines are not needed
   1.138 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
   1.139 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
   1.140 +
   1.141 +# Driver interface parameters
   1.142 +# This field can be used to configure arbitrary driver interace parameters. The
   1.143 +# format is specific to the selected driver interface. This field is not used
   1.144 +# in most cases.
   1.145 +#driver_param="field=value"
   1.146 +
   1.147 +# Country code
   1.148 +# The ISO/IEC alpha2 country code for the country in which this device is
   1.149 +# currently operating.
   1.150 +#country=US
   1.151 +
   1.152 +# Maximum lifetime for PMKSA in seconds; default 43200
   1.153 +#dot11RSNAConfigPMKLifetime=43200
   1.154 +# Threshold for reauthentication (percentage of PMK lifetime); default 70
   1.155 +#dot11RSNAConfigPMKReauthThreshold=70
   1.156 +# Timeout for security association negotiation in seconds; default 60
   1.157 +#dot11RSNAConfigSATimeout=60
   1.158 +
   1.159 +# Wi-Fi Protected Setup (WPS) parameters
   1.160 +
   1.161 +# Universally Unique IDentifier (UUID; see RFC 4122) of the device
   1.162 +# If not configured, UUID will be generated based on the local MAC address.
   1.163 +#uuid=12345678-9abc-def0-1234-56789abcdef0
   1.164 +
   1.165 +# Device Name
   1.166 +# User-friendly description of device; up to 32 octets encoded in UTF-8
   1.167 +#device_name=Wireless Client
   1.168 +
   1.169 +# Manufacturer
   1.170 +# The manufacturer of the device (up to 64 ASCII characters)
   1.171 +#manufacturer=Company
   1.172 +
   1.173 +# Model Name
   1.174 +# Model of the device (up to 32 ASCII characters)
   1.175 +#model_name=cmodel
   1.176 +
   1.177 +# Model Number
   1.178 +# Additional device description (up to 32 ASCII characters)
   1.179 +#model_number=123
   1.180 +
   1.181 +# Serial Number
   1.182 +# Serial number of the device (up to 32 characters)
   1.183 +#serial_number=12345
   1.184 +
   1.185 +# Primary Device Type
   1.186 +# Used format: <categ>-<OUI>-<subcateg>
   1.187 +# categ = Category as an integer value
   1.188 +# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
   1.189 +#       default WPS OUI
   1.190 +# subcateg = OUI-specific Sub Category as an integer value
   1.191 +# Examples:
   1.192 +#   1-0050F204-1 (Computer / PC)
   1.193 +#   1-0050F204-2 (Computer / Server)
   1.194 +#   5-0050F204-1 (Storage / NAS)
   1.195 +#   6-0050F204-1 (Network Infrastructure / AP)
   1.196 +#device_type=1-0050F204-1
   1.197 +
   1.198 +# OS Version
   1.199 +# 4-octet operating system version number (hex string)
   1.200 +#os_version=01020300
   1.201 +
   1.202 +# Config Methods
   1.203 +# List of the supported configuration methods
   1.204 +# Available methods: usba ethernet label display ext_nfc_token int_nfc_token
   1.205 +#	nfc_interface push_button keypad virtual_display physical_display
   1.206 +#	virtual_push_button physical_push_button
   1.207 +# For WSC 1.0:
   1.208 +#config_methods=label display push_button keypad
   1.209 +# For WSC 2.0:
   1.210 +#config_methods=label virtual_display virtual_push_button keypad
   1.211 +
   1.212 +# Credential processing
   1.213 +#   0 = process received credentials internally (default)
   1.214 +#   1 = do not process received credentials; just pass them over ctrl_iface to
   1.215 +#	external program(s)
   1.216 +#   2 = process received credentials internally and pass them over ctrl_iface
   1.217 +#	to external program(s)
   1.218 +#wps_cred_processing=0
   1.219 +
   1.220 +# Vendor attribute in WPS M1, e.g., Windows 7 Vertical Pairing
   1.221 +# The vendor attribute contents to be added in M1 (hex string)
   1.222 +#wps_vendor_ext_m1=000137100100020001
   1.223 +
   1.224 +# NFC password token for WPS
   1.225 +# These parameters can be used to configure a fixed NFC password token for the
   1.226 +# station. This can be generated, e.g., with nfc_pw_token. When these
   1.227 +# parameters are used, the station is assumed to be deployed with a NFC tag
   1.228 +# that includes the matching NFC password token (e.g., written based on the
   1.229 +# NDEF record from nfc_pw_token).
   1.230 +#
   1.231 +#wps_nfc_dev_pw_id: Device Password ID (16..65535)
   1.232 +#wps_nfc_dh_pubkey: Hexdump of DH Public Key
   1.233 +#wps_nfc_dh_privkey: Hexdump of DH Private Key
   1.234 +#wps_nfc_dev_pw: Hexdump of Device Password
   1.235 +
   1.236 +# Maximum number of BSS entries to keep in memory
   1.237 +# Default: 200
   1.238 +# This can be used to limit memory use on the BSS entries (cached scan
   1.239 +# results). A larger value may be needed in environments that have huge number
   1.240 +# of APs when using ap_scan=1 mode.
   1.241 +#bss_max_count=200
   1.242 +
   1.243 +# Automatic scan
   1.244 +# This is an optional set of parameters for automatic scanning
   1.245 +# within an interface in following format:
   1.246 +#autoscan=<autoscan module name>:<module parameters>
   1.247 +# autoscan is like bgscan but on disconnected or inactive state.
   1.248 +# For instance, on exponential module parameters would be <base>:<limit>
   1.249 +#autoscan=exponential:3:300
   1.250 +# Which means a delay between scans on a base exponential of 3,
   1.251 +# up to the limit of 300 seconds (3, 9, 27 ... 300)
   1.252 +# For periodic module, parameters would be <fixed interval>
   1.253 +#autoscan=periodic:30
   1.254 +# So a delay of 30 seconds will be applied between each scan
   1.255 +
   1.256 +# filter_ssids - SSID-based scan result filtering
   1.257 +# 0 = do not filter scan results (default)
   1.258 +# 1 = only include configured SSIDs in scan results/BSS table
   1.259 +#filter_ssids=0
   1.260 +
   1.261 +# Password (and passphrase, etc.) backend for external storage
   1.262 +# format: <backend name>[:<optional backend parameters>]
   1.263 +#ext_password_backend=test:pw1=password|pw2=testing
   1.264 +
   1.265 +# Timeout in seconds to detect STA inactivity (default: 300 seconds)
   1.266 +#
   1.267 +# This timeout value is used in P2P GO mode to clean up
   1.268 +# inactive stations.
   1.269 +#p2p_go_max_inactivity=300
   1.270 +
   1.271 +# Opportunistic Key Caching (also known as Proactive Key Caching) default
   1.272 +# This parameter can be used to set the default behavior for the
   1.273 +# proactive_key_caching parameter. By default, OKC is disabled unless enabled
   1.274 +# with the global okc=1 parameter or with the per-network
   1.275 +# proactive_key_caching=1 parameter. With okc=1, OKC is enabled by default, but
   1.276 +# can be disabled with per-network proactive_key_caching=0 parameter.
   1.277 +#okc=0
   1.278 +
   1.279 +# Protected Management Frames default
   1.280 +# This parameter can be used to set the default behavior for the ieee80211w
   1.281 +# parameter. By default, PMF is disabled unless enabled with the global pmf=1/2
   1.282 +# parameter or with the per-network ieee80211w=1/2 parameter. With pmf=1/2, PMF
   1.283 +# is enabled/required by default, but can be disabled with the per-network
   1.284 +# ieee80211w parameter.
   1.285 +#pmf=0
   1.286 +
   1.287 +# Enabled SAE finite cyclic groups in preference order
   1.288 +# By default (if this parameter is not set), the mandatory group 19 (ECC group
   1.289 +# defined over a 256-bit prime order field) is preferred, but other groups are
   1.290 +# also enabled. If this parameter is set, the groups will be tried in the
   1.291 +# indicated order. The group values are listed in the IANA registry:
   1.292 +# http://www.iana.org/assignments/ipsec-registry/ipsec-registry.xml#ipsec-registry-9
   1.293 +#sae_groups=21 20 19 26 25
   1.294 +
   1.295 +# Default value for DTIM period (if not overridden in network block)
   1.296 +#dtim_period=2
   1.297 +
   1.298 +# Default value for Beacon interval (if not overridden in network block)
   1.299 +#beacon_int=100
   1.300 +
   1.301 +# Additional vendor specific elements for Beacon and Probe Response frames
   1.302 +# This parameter can be used to add additional vendor specific element(s) into
   1.303 +# the end of the Beacon and Probe Response frames. The format for these
   1.304 +# element(s) is a hexdump of the raw information elements (id+len+payload for
   1.305 +# one or more elements). This is used in AP and P2P GO modes.
   1.306 +#ap_vendor_elements=dd0411223301
   1.307 +
   1.308 +# Ignore scan results older than request
   1.309 +#
   1.310 +# The driver may have a cache of scan results that makes it return
   1.311 +# information that is older than our scan trigger. This parameter can
   1.312 +# be used to configure such old information to be ignored instead of
   1.313 +# allowing it to update the internal BSS table.
   1.314 +#ignore_old_scan_res=0
   1.315 +
   1.316 +# scan_cur_freq: Whether to scan only the current frequency
   1.317 +# 0:  Scan all available frequencies. (Default)
   1.318 +# 1:  Scan current operating frequency if another VIF on the same radio
   1.319 +#     is already associated.
   1.320 +
   1.321 +# Interworking (IEEE 802.11u)
   1.322 +
   1.323 +# Enable Interworking
   1.324 +# interworking=1
   1.325 +
   1.326 +# Homogenous ESS identifier
   1.327 +# If this is set, scans will be used to request response only from BSSes
   1.328 +# belonging to the specified Homogeneous ESS. This is used only if interworking
   1.329 +# is enabled.
   1.330 +# hessid=00:11:22:33:44:55
   1.331 +
   1.332 +# Automatic network selection behavior
   1.333 +# 0 = do not automatically go through Interworking network selection
   1.334 +#     (i.e., require explicit interworking_select command for this; default)
   1.335 +# 1 = perform Interworking network selection if one or more
   1.336 +#     credentials have been configured and scan did not find a
   1.337 +#     matching network block
   1.338 +#auto_interworking=0
   1.339 +
   1.340 +# credential block
   1.341 +#
   1.342 +# Each credential used for automatic network selection is configured as a set
   1.343 +# of parameters that are compared to the information advertised by the APs when
   1.344 +# interworking_select and interworking_connect commands are used.
   1.345 +#
   1.346 +# credential fields:
   1.347 +#
   1.348 +# temporary: Whether this credential is temporary and not to be saved
   1.349 +#
   1.350 +# priority: Priority group
   1.351 +#	By default, all networks and credentials get the same priority group
   1.352 +#	(0). This field can be used to give higher priority for credentials
   1.353 +#	(and similarly in struct wpa_ssid for network blocks) to change the
   1.354 +#	Interworking automatic networking selection behavior. The matching
   1.355 +#	network (based on either an enabled network block or a credential)
   1.356 +#	with the highest priority value will be selected.
   1.357 +#
   1.358 +# pcsc: Use PC/SC and SIM/USIM card
   1.359 +#
   1.360 +# realm: Home Realm for Interworking
   1.361 +#
   1.362 +# username: Username for Interworking network selection
   1.363 +#
   1.364 +# password: Password for Interworking network selection
   1.365 +#
   1.366 +# ca_cert: CA certificate for Interworking network selection
   1.367 +#
   1.368 +# client_cert: File path to client certificate file (PEM/DER)
   1.369 +#	This field is used with Interworking networking selection for a case
   1.370 +#	where client certificate/private key is used for authentication
   1.371 +#	(EAP-TLS). Full path to the file should be used since working
   1.372 +#	directory may change when wpa_supplicant is run in the background.
   1.373 +#
   1.374 +#	Alternatively, a named configuration blob can be used by setting
   1.375 +#	this to blob://blob_name.
   1.376 +#
   1.377 +# private_key: File path to client private key file (PEM/DER/PFX)
   1.378 +#	When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
   1.379 +#	commented out. Both the private key and certificate will be read
   1.380 +#	from the PKCS#12 file in this case. Full path to the file should be
   1.381 +#	used since working directory may change when wpa_supplicant is run
   1.382 +#	in the background.
   1.383 +#
   1.384 +#	Windows certificate store can be used by leaving client_cert out and
   1.385 +#	configuring private_key in one of the following formats:
   1.386 +#
   1.387 +#	cert://substring_to_match
   1.388 +#
   1.389 +#	hash://certificate_thumbprint_in_hex
   1.390 +#
   1.391 +#	For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
   1.392 +#
   1.393 +#	Note that when running wpa_supplicant as an application, the user
   1.394 +#	certificate store (My user account) is used, whereas computer store
   1.395 +#	(Computer account) is used when running wpasvc as a service.
   1.396 +#
   1.397 +#	Alternatively, a named configuration blob can be used by setting
   1.398 +#	this to blob://blob_name.
   1.399 +#
   1.400 +# private_key_passwd: Password for private key file
   1.401 +#
   1.402 +# imsi: IMSI in <MCC> | <MNC> | '-' | <MSIN> format
   1.403 +#
   1.404 +# milenage: Milenage parameters for SIM/USIM simulator in <Ki>:<OPc>:<SQN>
   1.405 +#	format
   1.406 +#
   1.407 +# domain: Home service provider FQDN(s)
   1.408 +#	This is used to compare against the Domain Name List to figure out
   1.409 +#	whether the AP is operated by the Home SP. Multiple domain entries can
   1.410 +#	be used to configure alternative FQDNs that will be considered home
   1.411 +#	networks.
   1.412 +#
   1.413 +# roaming_consortium: Roaming Consortium OI
   1.414 +#	If roaming_consortium_len is non-zero, this field contains the
   1.415 +#	Roaming Consortium OI that can be used to determine which access
   1.416 +#	points support authentication with this credential. This is an
   1.417 +#	alternative to the use of the realm parameter. When using Roaming
   1.418 +#	Consortium to match the network, the EAP parameters need to be
   1.419 +#	pre-configured with the credential since the NAI Realm information
   1.420 +#	may not be available or fetched.
   1.421 +#
   1.422 +# eap: Pre-configured EAP method
   1.423 +#	This optional field can be used to specify which EAP method will be
   1.424 +#	used with this credential. If not set, the EAP method is selected
   1.425 +#	automatically based on ANQP information (e.g., NAI Realm).
   1.426 +#
   1.427 +# phase1: Pre-configure Phase 1 (outer authentication) parameters
   1.428 +#	This optional field is used with like the 'eap' parameter.
   1.429 +#
   1.430 +# phase2: Pre-configure Phase 2 (inner authentication) parameters
   1.431 +#	This optional field is used with like the 'eap' parameter.
   1.432 +#
   1.433 +# excluded_ssid: Excluded SSID
   1.434 +#	This optional field can be used to excluded specific SSID(s) from
   1.435 +#	matching with the network. Multiple entries can be used to specify more
   1.436 +#	than one SSID.
   1.437 +#
   1.438 +# for example:
   1.439 +#
   1.440 +#cred={
   1.441 +#	realm="example.com"
   1.442 +#	username="user@example.com"
   1.443 +#	password="password"
   1.444 +#	ca_cert="/etc/wpa_supplicant/ca.pem"
   1.445 +#	domain="example.com"
   1.446 +#}
   1.447 +#
   1.448 +#cred={
   1.449 +#	imsi="310026-000000000"
   1.450 +#	milenage="90dca4eda45b53cf0f12d7c9c3bc6a89:cb9cccc4b9258e6dca4760379fb82"
   1.451 +#}
   1.452 +#
   1.453 +#cred={
   1.454 +#	realm="example.com"
   1.455 +#	username="user"
   1.456 +#	password="password"
   1.457 +#	ca_cert="/etc/wpa_supplicant/ca.pem"
   1.458 +#	domain="example.com"
   1.459 +#	roaming_consortium=223344
   1.460 +#	eap=TTLS
   1.461 +#	phase2="auth=MSCHAPV2"
   1.462 +#}
   1.463 +
   1.464 +# Hotspot 2.0
   1.465 +# hs20=1
   1.466 +
   1.467 +# network block
   1.468 +#
   1.469 +# Each network (usually AP's sharing the same SSID) is configured as a separate
   1.470 +# block in this configuration file. The network blocks are in preference order
   1.471 +# (the first match is used).
   1.472 +#
   1.473 +# network block fields:
   1.474 +#
   1.475 +# disabled:
   1.476 +#	0 = this network can be used (default)
   1.477 +#	1 = this network block is disabled (can be enabled through ctrl_iface,
   1.478 +#	    e.g., with wpa_cli or wpa_gui)
   1.479 +#
   1.480 +# id_str: Network identifier string for external scripts. This value is passed
   1.481 +#	to external action script through wpa_cli as WPA_ID_STR environment
   1.482 +#	variable to make it easier to do network specific configuration.
   1.483 +#
   1.484 +# ssid: SSID (mandatory); network name in one of the optional formats:
   1.485 +#	- an ASCII string with double quotation
   1.486 +#	- a hex string (two characters per octet of SSID)
   1.487 +#	- a printf-escaped ASCII string P"<escaped string>"
   1.488 +#
   1.489 +# scan_ssid:
   1.490 +#	0 = do not scan this SSID with specific Probe Request frames (default)
   1.491 +#	1 = scan with SSID-specific Probe Request frames (this can be used to
   1.492 +#	    find APs that do not accept broadcast SSID or use multiple SSIDs;
   1.493 +#	    this will add latency to scanning, so enable this only when needed)
   1.494 +#
   1.495 +# bssid: BSSID (optional); if set, this network block is used only when
   1.496 +#	associating with the AP using the configured BSSID
   1.497 +#
   1.498 +# priority: priority group (integer)
   1.499 +# By default, all networks will get same priority group (0). If some of the
   1.500 +# networks are more desirable, this field can be used to change the order in
   1.501 +# which wpa_supplicant goes through the networks when selecting a BSS. The
   1.502 +# priority groups will be iterated in decreasing priority (i.e., the larger the
   1.503 +# priority value, the sooner the network is matched against the scan results).
   1.504 +# Within each priority group, networks will be selected based on security
   1.505 +# policy, signal strength, etc.
   1.506 +# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
   1.507 +# using this priority to select the order for scanning. Instead, they try the
   1.508 +# networks in the order that used in the configuration file.
   1.509 +#
   1.510 +# mode: IEEE 802.11 operation mode
   1.511 +# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
   1.512 +# 1 = IBSS (ad-hoc, peer-to-peer)
   1.513 +# 2 = AP (access point)
   1.514 +# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) and
   1.515 +# WPA-PSK (with proto=RSN). In addition, key_mgmt=WPA-NONE (fixed group key
   1.516 +# TKIP/CCMP) is available for backwards compatibility, but its use is
   1.517 +# deprecated. WPA-None requires following network block options:
   1.518 +# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
   1.519 +# both), and psk must also be set.
   1.520 +#
   1.521 +# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
   1.522 +# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
   1.523 +# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
   1.524 +# In addition, this value is only used by the station that creates the IBSS. If
   1.525 +# an IBSS network with the configured SSID is already present, the frequency of
   1.526 +# the network will be used instead of this configured value.
   1.527 +#
   1.528 +# scan_freq: List of frequencies to scan
   1.529 +# Space-separated list of frequencies in MHz to scan when searching for this
   1.530 +# BSS. If the subset of channels used by the network is known, this option can
   1.531 +# be used to optimize scanning to not occur on channels that the network does
   1.532 +# not use. Example: scan_freq=2412 2437 2462
   1.533 +#
   1.534 +# freq_list: Array of allowed frequencies
   1.535 +# Space-separated list of frequencies in MHz to allow for selecting the BSS. If
   1.536 +# set, scan results that do not match any of the specified frequencies are not
   1.537 +# considered when selecting a BSS.
   1.538 +#
   1.539 +# This can also be set on the outside of the network block. In this case,
   1.540 +# it limits the frequencies that will be scanned.
   1.541 +#
   1.542 +# bgscan: Background scanning
   1.543 +# wpa_supplicant behavior for background scanning can be specified by
   1.544 +# configuring a bgscan module. These modules are responsible for requesting
   1.545 +# background scans for the purpose of roaming within an ESS (i.e., within a
   1.546 +# single network block with all the APs using the same SSID). The bgscan
   1.547 +# parameter uses following format: "<bgscan module name>:<module parameters>"
   1.548 +# Following bgscan modules are available:
   1.549 +# simple - Periodic background scans based on signal strength
   1.550 +# bgscan="simple:<short bgscan interval in seconds>:<signal strength threshold>:
   1.551 +# <long interval>"
   1.552 +# bgscan="simple:30:-45:300"
   1.553 +# learn - Learn channels used by the network and try to avoid bgscans on other
   1.554 +# channels (experimental)
   1.555 +# bgscan="learn:<short bgscan interval in seconds>:<signal strength threshold>:
   1.556 +# <long interval>[:<database file name>]"
   1.557 +# bgscan="learn:30:-45:300:/etc/wpa_supplicant/network1.bgscan"
   1.558 +#
   1.559 +# This option can also be set outside of all network blocks for the bgscan
   1.560 +# parameter to apply for all the networks that have no specific bgscan
   1.561 +# parameter.
   1.562 +#
   1.563 +# proto: list of accepted protocols
   1.564 +# WPA = WPA/IEEE 802.11i/D3.0
   1.565 +# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
   1.566 +# If not set, this defaults to: WPA RSN
   1.567 +#
   1.568 +# key_mgmt: list of accepted authenticated key management protocols
   1.569 +# WPA-PSK = WPA pre-shared key (this requires 'psk' field)
   1.570 +# WPA-EAP = WPA using EAP authentication
   1.571 +# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
   1.572 +#	generated WEP keys
   1.573 +# NONE = WPA is not used; plaintext or static WEP could be used
   1.574 +# WPA-PSK-SHA256 = Like WPA-PSK but using stronger SHA256-based algorithms
   1.575 +# WPA-EAP-SHA256 = Like WPA-EAP but using stronger SHA256-based algorithms
   1.576 +# If not set, this defaults to: WPA-PSK WPA-EAP
   1.577 +#
   1.578 +# ieee80211w: whether management frame protection is enabled
   1.579 +# 0 = disabled (default unless changed with the global pmf parameter)
   1.580 +# 1 = optional
   1.581 +# 2 = required
   1.582 +# The most common configuration options for this based on the PMF (protected
   1.583 +# management frames) certification program are:
   1.584 +# PMF enabled: ieee80211w=1 and key_mgmt=WPA-EAP WPA-EAP-SHA256
   1.585 +# PMF required: ieee80211w=2 and key_mgmt=WPA-EAP-SHA256
   1.586 +# (and similarly for WPA-PSK and WPA-WPSK-SHA256 if WPA2-Personal is used)
   1.587 +#
   1.588 +# auth_alg: list of allowed IEEE 802.11 authentication algorithms
   1.589 +# OPEN = Open System authentication (required for WPA/WPA2)
   1.590 +# SHARED = Shared Key authentication (requires static WEP keys)
   1.591 +# LEAP = LEAP/Network EAP (only used with LEAP)
   1.592 +# If not set, automatic selection is used (Open System with LEAP enabled if
   1.593 +# LEAP is allowed as one of the EAP methods).
   1.594 +#
   1.595 +# pairwise: list of accepted pairwise (unicast) ciphers for WPA
   1.596 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
   1.597 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
   1.598 +# NONE = Use only Group Keys (deprecated, should not be included if APs support
   1.599 +#	pairwise keys)
   1.600 +# If not set, this defaults to: CCMP TKIP
   1.601 +#
   1.602 +# group: list of accepted group (broadcast/multicast) ciphers for WPA
   1.603 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
   1.604 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
   1.605 +# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
   1.606 +# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
   1.607 +# If not set, this defaults to: CCMP TKIP WEP104 WEP40
   1.608 +#
   1.609 +# psk: WPA preshared key; 256-bit pre-shared key
   1.610 +# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
   1.611 +# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
   1.612 +# generated using the passphrase and SSID). ASCII passphrase must be between
   1.613 +# 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
   1.614 +# be used to indicate that the PSK/passphrase is stored in external storage.
   1.615 +# This field is not needed, if WPA-EAP is used.
   1.616 +# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
   1.617 +# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
   1.618 +# startup and reconfiguration time can be optimized by generating the PSK only
   1.619 +# only when the passphrase or SSID has actually changed.
   1.620 +#
   1.621 +# eapol_flags: IEEE 802.1X/EAPOL options (bit field)
   1.622 +# Dynamic WEP key required for non-WPA mode
   1.623 +# bit0 (1): require dynamically generated unicast WEP key
   1.624 +# bit1 (2): require dynamically generated broadcast WEP key
   1.625 +# 	(3 = require both keys; default)
   1.626 +# Note: When using wired authentication, eapol_flags must be set to 0 for the
   1.627 +# authentication to be completed successfully.
   1.628 +#
   1.629 +# mixed_cell: This option can be used to configure whether so called mixed
   1.630 +# cells, i.e., networks that use both plaintext and encryption in the same
   1.631 +# SSID, are allowed when selecting a BSS from scan results.
   1.632 +# 0 = disabled (default)
   1.633 +# 1 = enabled
   1.634 +#
   1.635 +# proactive_key_caching:
   1.636 +# Enable/disable opportunistic PMKSA caching for WPA2.
   1.637 +# 0 = disabled (default unless changed with the global okc parameter)
   1.638 +# 1 = enabled
   1.639 +#
   1.640 +# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
   1.641 +# hex without quotation, e.g., 0102030405)
   1.642 +# wep_tx_keyidx: Default WEP key index (TX) (0..3)
   1.643 +#
   1.644 +# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
   1.645 +# allowed. This is only used with RSN/WPA2.
   1.646 +# 0 = disabled (default)
   1.647 +# 1 = enabled
   1.648 +#peerkey=1
   1.649 +#
   1.650 +# wpa_ptk_rekey: Maximum lifetime for PTK in seconds. This can be used to
   1.651 +# enforce rekeying of PTK to mitigate some attacks against TKIP deficiencies.
   1.652 +#
   1.653 +# Following fields are only used with internal EAP implementation.
   1.654 +# eap: space-separated list of accepted EAP methods
   1.655 +#	MD5 = EAP-MD5 (unsecure and does not generate keying material ->
   1.656 +#			cannot be used with WPA; to be used as a Phase 2 method
   1.657 +#			with EAP-PEAP or EAP-TTLS)
   1.658 +#       MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
   1.659 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   1.660 +#       OTP = EAP-OTP (cannot be used separately with WPA; to be used
   1.661 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   1.662 +#       GTC = EAP-GTC (cannot be used separately with WPA; to be used
   1.663 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   1.664 +#	TLS = EAP-TLS (client and server certificate)
   1.665 +#	PEAP = EAP-PEAP (with tunnelled EAP authentication)
   1.666 +#	TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
   1.667 +#			 authentication)
   1.668 +#	If not set, all compiled in methods are allowed.
   1.669 +#
   1.670 +# identity: Identity string for EAP
   1.671 +#	This field is also used to configure user NAI for
   1.672 +#	EAP-PSK/PAX/SAKE/GPSK.
   1.673 +# anonymous_identity: Anonymous identity string for EAP (to be used as the
   1.674 +#	unencrypted identity with EAP types that support different tunnelled
   1.675 +#	identity, e.g., EAP-TTLS). This field can also be used with
   1.676 +#	EAP-SIM/AKA/AKA' to store the pseudonym identity.
   1.677 +# password: Password string for EAP. This field can include either the
   1.678 +#	plaintext password (using ASCII or hex string) or a NtPasswordHash
   1.679 +#	(16-byte MD4 hash of password) in hash:<32 hex digits> format.
   1.680 +#	NtPasswordHash can only be used when the password is for MSCHAPv2 or
   1.681 +#	MSCHAP (EAP-MSCHAPv2, EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
   1.682 +#	EAP-PSK (128-bit PSK), EAP-PAX (128-bit PSK), and EAP-SAKE (256-bit
   1.683 +#	PSK) is also configured using this field. For EAP-GPSK, this is a
   1.684 +#	variable length PSK. ext:<name of external password field> format can
   1.685 +#	be used to indicate that the password is stored in external storage.
   1.686 +# ca_cert: File path to CA certificate file (PEM/DER). This file can have one
   1.687 +#	or more trusted CA certificates. If ca_cert and ca_path are not
   1.688 +#	included, server certificate will not be verified. This is insecure and
   1.689 +#	a trusted CA certificate should always be configured when using
   1.690 +#	EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
   1.691 +#	change when wpa_supplicant is run in the background.
   1.692 +#
   1.693 +#	Alternatively, this can be used to only perform matching of the server
   1.694 +#	certificate (SHA-256 hash of the DER encoded X.509 certificate). In
   1.695 +#	this case, the possible CA certificates in the server certificate chain
   1.696 +#	are ignored and only the server certificate is verified. This is
   1.697 +#	configured with the following format:
   1.698 +#	hash:://server/sha256/cert_hash_in_hex
   1.699 +#	For example: "hash://server/sha256/
   1.700 +#	5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
   1.701 +#
   1.702 +#	On Windows, trusted CA certificates can be loaded from the system
   1.703 +#	certificate store by setting this to cert_store://<name>, e.g.,
   1.704 +#	ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
   1.705 +#	Note that when running wpa_supplicant as an application, the user
   1.706 +#	certificate store (My user account) is used, whereas computer store
   1.707 +#	(Computer account) is used when running wpasvc as a service.
   1.708 +# ca_path: Directory path for CA certificate files (PEM). This path may
   1.709 +#	contain multiple CA certificates in OpenSSL format. Common use for this
   1.710 +#	is to point to system trusted CA list which is often installed into
   1.711 +#	directory like /etc/ssl/certs. If configured, these certificates are
   1.712 +#	added to the list of trusted CAs. ca_cert may also be included in that
   1.713 +#	case, but it is not required.
   1.714 +# client_cert: File path to client certificate file (PEM/DER)
   1.715 +#	Full path should be used since working directory may change when
   1.716 +#	wpa_supplicant is run in the background.
   1.717 +#	Alternatively, a named configuration blob can be used by setting this
   1.718 +#	to blob://<blob name>.
   1.719 +# private_key: File path to client private key file (PEM/DER/PFX)
   1.720 +#	When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
   1.721 +#	commented out. Both the private key and certificate will be read from
   1.722 +#	the PKCS#12 file in this case. Full path should be used since working
   1.723 +#	directory may change when wpa_supplicant is run in the background.
   1.724 +#	Windows certificate store can be used by leaving client_cert out and
   1.725 +#	configuring private_key in one of the following formats:
   1.726 +#	cert://substring_to_match
   1.727 +#	hash://certificate_thumbprint_in_hex
   1.728 +#	for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
   1.729 +#	Note that when running wpa_supplicant as an application, the user
   1.730 +#	certificate store (My user account) is used, whereas computer store
   1.731 +#	(Computer account) is used when running wpasvc as a service.
   1.732 +#	Alternatively, a named configuration blob can be used by setting this
   1.733 +#	to blob://<blob name>.
   1.734 +# private_key_passwd: Password for private key file (if left out, this will be
   1.735 +#	asked through control interface)
   1.736 +# dh_file: File path to DH/DSA parameters file (in PEM format)
   1.737 +#	This is an optional configuration file for setting parameters for an
   1.738 +#	ephemeral DH key exchange. In most cases, the default RSA
   1.739 +#	authentication does not use this configuration. However, it is possible
   1.740 +#	setup RSA to use ephemeral DH key exchange. In addition, ciphers with
   1.741 +#	DSA keys always use ephemeral DH keys. This can be used to achieve
   1.742 +#	forward secrecy. If the file is in DSA parameters format, it will be
   1.743 +#	automatically converted into DH params.
   1.744 +# subject_match: Substring to be matched against the subject of the
   1.745 +#	authentication server certificate. If this string is set, the server
   1.746 +#	sertificate is only accepted if it contains this string in the subject.
   1.747 +#	The subject string is in following format:
   1.748 +#	/C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
   1.749 +# altsubject_match: Semicolon separated string of entries to be matched against
   1.750 +#	the alternative subject name of the authentication server certificate.
   1.751 +#	If this string is set, the server sertificate is only accepted if it
   1.752 +#	contains one of the entries in an alternative subject name extension.
   1.753 +#	altSubjectName string is in following format: TYPE:VALUE
   1.754 +#	Example: EMAIL:server@example.com
   1.755 +#	Example: DNS:server.example.com;DNS:server2.example.com
   1.756 +#	Following types are supported: EMAIL, DNS, URI
   1.757 +# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
   1.758 +#	(string with field-value pairs, e.g., "peapver=0" or
   1.759 +#	"peapver=1 peaplabel=1")
   1.760 +#	'peapver' can be used to force which PEAP version (0 or 1) is used.
   1.761 +#	'peaplabel=1' can be used to force new label, "client PEAP encryption",
   1.762 +#	to be used during key derivation when PEAPv1 or newer. Most existing
   1.763 +#	PEAPv1 implementation seem to be using the old label, "client EAP
   1.764 +#	encryption", and wpa_supplicant is now using that as the default value.
   1.765 +#	Some servers, e.g., Radiator, may require peaplabel=1 configuration to
   1.766 +#	interoperate with PEAPv1; see eap_testing.txt for more details.
   1.767 +#	'peap_outer_success=0' can be used to terminate PEAP authentication on
   1.768 +#	tunneled EAP-Success. This is required with some RADIUS servers that
   1.769 +#	implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
   1.770 +#	Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
   1.771 +#	include_tls_length=1 can be used to force wpa_supplicant to include
   1.772 +#	TLS Message Length field in all TLS messages even if they are not
   1.773 +#	fragmented.
   1.774 +#	sim_min_num_chal=3 can be used to configure EAP-SIM to require three
   1.775 +#	challenges (by default, it accepts 2 or 3)
   1.776 +#	result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
   1.777 +#	protected result indication.
   1.778 +#	'crypto_binding' option can be used to control PEAPv0 cryptobinding
   1.779 +#	behavior:
   1.780 +#	 * 0 = do not use cryptobinding (default)
   1.781 +#	 * 1 = use cryptobinding if server supports it
   1.782 +#	 * 2 = require cryptobinding
   1.783 +#	EAP-WSC (WPS) uses following options: pin=<Device Password> or
   1.784 +#	pbc=1.
   1.785 +# phase2: Phase2 (inner authentication with TLS tunnel) parameters
   1.786 +#	(string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
   1.787 +#	"autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
   1.788 +#
   1.789 +# TLS-based methods can use the following parameters to control TLS behavior
   1.790 +# (these are normally in the phase1 parameter, but can be used also in the
   1.791 +# phase2 parameter when EAP-TLS is used within the inner tunnel):
   1.792 +# tls_allow_md5=1 - allow MD5-based certificate signatures (depending on the
   1.793 +#	TLS library, these may be disabled by default to enforce stronger
   1.794 +#	security)
   1.795 +# tls_disable_time_checks=1 - ignore certificate validity time (this requests
   1.796 +#	the TLS library to accept certificates even if they are not currently
   1.797 +#	valid, i.e., have expired or have not yet become valid; this should be
   1.798 +#	used only for testing purposes)
   1.799 +# tls_disable_session_ticket=1 - disable TLS Session Ticket extension
   1.800 +# tls_disable_session_ticket=0 - allow TLS Session Ticket extension to be used
   1.801 +#	Note: If not set, this is automatically set to 1 for EAP-TLS/PEAP/TTLS
   1.802 +#	as a workaround for broken authentication server implementations unless
   1.803 +#	EAP workarounds are disabled with eap_workarounds=0.
   1.804 +#	For EAP-FAST, this must be set to 0 (or left unconfigured for the
   1.805 +#	default value to be used automatically).
   1.806 +#
   1.807 +# Following certificate/private key fields are used in inner Phase2
   1.808 +# authentication when using EAP-TTLS or EAP-PEAP.
   1.809 +# ca_cert2: File path to CA certificate file. This file can have one or more
   1.810 +#	trusted CA certificates. If ca_cert2 and ca_path2 are not included,
   1.811 +#	server certificate will not be verified. This is insecure and a trusted
   1.812 +#	CA certificate should always be configured.
   1.813 +# ca_path2: Directory path for CA certificate files (PEM)
   1.814 +# client_cert2: File path to client certificate file
   1.815 +# private_key2: File path to client private key file
   1.816 +# private_key2_passwd: Password for private key file
   1.817 +# dh_file2: File path to DH/DSA parameters file (in PEM format)
   1.818 +# subject_match2: Substring to be matched against the subject of the
   1.819 +#	authentication server certificate.
   1.820 +# altsubject_match2: Substring to be matched against the alternative subject
   1.821 +#	name of the authentication server certificate.
   1.822 +#
   1.823 +# fragment_size: Maximum EAP fragment size in bytes (default 1398).
   1.824 +#	This value limits the fragment size for EAP methods that support
   1.825 +#	fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
   1.826 +#	small enough to make the EAP messages fit in MTU of the network
   1.827 +#	interface used for EAPOL. The default value is suitable for most
   1.828 +#	cases.
   1.829 +#
   1.830 +# ocsp: Whether to use/require OCSP to check server certificate
   1.831 +#	0 = do not use OCSP stapling (TLS certificate status extension)
   1.832 +#	1 = try to use OCSP stapling, but not require response
   1.833 +#	2 = require valid OCSP stapling response
   1.834 +#
   1.835 +# EAP-FAST variables:
   1.836 +# pac_file: File path for the PAC entries. wpa_supplicant will need to be able
   1.837 +#	to create this file and write updates to it when PAC is being
   1.838 +#	provisioned or refreshed. Full path to the file should be used since
   1.839 +#	working directory may change when wpa_supplicant is run in the
   1.840 +#	background. Alternatively, a named configuration blob can be used by
   1.841 +#	setting this to blob://<blob name>
   1.842 +# phase1: fast_provisioning option can be used to enable in-line provisioning
   1.843 +#         of EAP-FAST credentials (PAC):
   1.844 +#         0 = disabled,
   1.845 +#         1 = allow unauthenticated provisioning,
   1.846 +#         2 = allow authenticated provisioning,
   1.847 +#         3 = allow both unauthenticated and authenticated provisioning
   1.848 +#	fast_max_pac_list_len=<num> option can be used to set the maximum
   1.849 +#		number of PAC entries to store in a PAC list (default: 10)
   1.850 +#	fast_pac_format=binary option can be used to select binary format for
   1.851 +#		storing PAC entries in order to save some space (the default
   1.852 +#		text format uses about 2.5 times the size of minimal binary
   1.853 +#		format)
   1.854 +#
   1.855 +# wpa_supplicant supports number of "EAP workarounds" to work around
   1.856 +# interoperability issues with incorrectly behaving authentication servers.
   1.857 +# These are enabled by default because some of the issues are present in large
   1.858 +# number of authentication servers. Strict EAP conformance mode can be
   1.859 +# configured by disabling workarounds with eap_workaround=0.
   1.860 +
   1.861 +# Station inactivity limit
   1.862 +#
   1.863 +# If a station does not send anything in ap_max_inactivity seconds, an
   1.864 +# empty data frame is sent to it in order to verify whether it is
   1.865 +# still in range. If this frame is not ACKed, the station will be
   1.866 +# disassociated and then deauthenticated. This feature is used to
   1.867 +# clear station table of old entries when the STAs move out of the
   1.868 +# range.
   1.869 +#
   1.870 +# The station can associate again with the AP if it is still in range;
   1.871 +# this inactivity poll is just used as a nicer way of verifying
   1.872 +# inactivity; i.e., client will not report broken connection because
   1.873 +# disassociation frame is not sent immediately without first polling
   1.874 +# the STA with a data frame.
   1.875 +# default: 300 (i.e., 5 minutes)
   1.876 +#ap_max_inactivity=300
   1.877 +
   1.878 +# DTIM period in Beacon intervals for AP mode (default: 2)
   1.879 +#dtim_period=2
   1.880 +
   1.881 +# Beacon interval (default: 100 TU)
   1.882 +#beacon_int=100
   1.883 +
   1.884 +# disable_ht: Whether HT (802.11n) should be disabled.
   1.885 +# 0 = HT enabled (if AP supports it)
   1.886 +# 1 = HT disabled
   1.887 +#
   1.888 +# disable_ht40: Whether HT-40 (802.11n) should be disabled.
   1.889 +# 0 = HT-40 enabled (if AP supports it)
   1.890 +# 1 = HT-40 disabled
   1.891 +#
   1.892 +# disable_sgi: Whether SGI (short guard interval) should be disabled.
   1.893 +# 0 = SGI enabled (if AP supports it)
   1.894 +# 1 = SGI disabled
   1.895 +#
   1.896 +# ht_mcs:  Configure allowed MCS rates.
   1.897 +#  Parsed as an array of bytes, in base-16 (ascii-hex)
   1.898 +# ht_mcs=""                                   // Use all available (default)
   1.899 +# ht_mcs="0xff 00 00 00 00 00 00 00 00 00 "   // Use MCS 0-7 only
   1.900 +# ht_mcs="0xff ff 00 00 00 00 00 00 00 00 "   // Use MCS 0-15 only
   1.901 +#
   1.902 +# disable_max_amsdu:  Whether MAX_AMSDU should be disabled.
   1.903 +# -1 = Do not make any changes.
   1.904 +# 0  = Enable MAX-AMSDU if hardware supports it.
   1.905 +# 1  = Disable AMSDU
   1.906 +#
   1.907 +# ampdu_density:  Allow overriding AMPDU density configuration.
   1.908 +#  Treated as hint by the kernel.
   1.909 +# -1 = Do not make any changes.
   1.910 +# 0-3 = Set AMPDU density (aka factor) to specified value.
   1.911 +
   1.912 +# disable_vht: Whether VHT should be disabled.
   1.913 +# 0 = VHT enabled (if AP supports it)
   1.914 +# 1 = VHT disabled
   1.915 +#
   1.916 +# vht_capa: VHT capabilities to set in the override
   1.917 +# vht_capa_mask: mask of VHT capabilities
   1.918 +#
   1.919 +# vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8
   1.920 +# vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8
   1.921 +#  0: MCS 0-7
   1.922 +#  1: MCS 0-8
   1.923 +#  2: MCS 0-9
   1.924 +#  3: not supported
   1.925 +
   1.926 +# Example blocks:
   1.927 +
   1.928 +# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
   1.929 +network={
   1.930 +	ssid="simple"
   1.931 +	psk="very secret passphrase"
   1.932 +	priority=5
   1.933 +}
   1.934 +
   1.935 +# Same as previous, but request SSID-specific scanning (for APs that reject
   1.936 +# broadcast SSID)
   1.937 +network={
   1.938 +	ssid="second ssid"
   1.939 +	scan_ssid=1
   1.940 +	psk="very secret passphrase"
   1.941 +	priority=2
   1.942 +}
   1.943 +
   1.944 +# Only WPA-PSK is used. Any valid cipher combination is accepted.
   1.945 +network={
   1.946 +	ssid="example"
   1.947 +	proto=WPA
   1.948 +	key_mgmt=WPA-PSK
   1.949 +	pairwise=CCMP TKIP
   1.950 +	group=CCMP TKIP WEP104 WEP40
   1.951 +	psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
   1.952 +	priority=2
   1.953 +}
   1.954 +
   1.955 +# WPA-Personal(PSK) with TKIP and enforcement for frequent PTK rekeying
   1.956 +network={
   1.957 +	ssid="example"
   1.958 +	proto=WPA
   1.959 +	key_mgmt=WPA-PSK
   1.960 +	pairwise=TKIP
   1.961 +	group=TKIP
   1.962 +	psk="not so secure passphrase"
   1.963 +	wpa_ptk_rekey=600
   1.964 +}
   1.965 +
   1.966 +# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
   1.967 +# or WEP40 as the group cipher will not be accepted.
   1.968 +network={
   1.969 +	ssid="example"
   1.970 +	proto=RSN
   1.971 +	key_mgmt=WPA-EAP
   1.972 +	pairwise=CCMP TKIP
   1.973 +	group=CCMP TKIP
   1.974 +	eap=TLS
   1.975 +	identity="user@example.com"
   1.976 +	ca_cert="/etc/cert/ca.pem"
   1.977 +	client_cert="/etc/cert/user.pem"
   1.978 +	private_key="/etc/cert/user.prv"
   1.979 +	private_key_passwd="password"
   1.980 +	priority=1
   1.981 +}
   1.982 +
   1.983 +# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
   1.984 +# (e.g., Radiator)
   1.985 +network={
   1.986 +	ssid="example"
   1.987 +	key_mgmt=WPA-EAP
   1.988 +	eap=PEAP
   1.989 +	identity="user@example.com"
   1.990 +	password="foobar"
   1.991 +	ca_cert="/etc/cert/ca.pem"
   1.992 +	phase1="peaplabel=1"
   1.993 +	phase2="auth=MSCHAPV2"
   1.994 +	priority=10
   1.995 +}
   1.996 +
   1.997 +# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
   1.998 +# unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
   1.999 +network={
  1.1000 +	ssid="example"
  1.1001 +	key_mgmt=WPA-EAP
  1.1002 +	eap=TTLS
  1.1003 +	identity="user@example.com"
  1.1004 +	anonymous_identity="anonymous@example.com"
  1.1005 +	password="foobar"
  1.1006 +	ca_cert="/etc/cert/ca.pem"
  1.1007 +	priority=2
  1.1008 +}
  1.1009 +
  1.1010 +# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
  1.1011 +# use. Real identity is sent only within an encrypted TLS tunnel.
  1.1012 +network={
  1.1013 +	ssid="example"
  1.1014 +	key_mgmt=WPA-EAP
  1.1015 +	eap=TTLS
  1.1016 +	identity="user@example.com"
  1.1017 +	anonymous_identity="anonymous@example.com"
  1.1018 +	password="foobar"
  1.1019 +	ca_cert="/etc/cert/ca.pem"
  1.1020 +	phase2="auth=MSCHAPV2"
  1.1021 +}
  1.1022 +
  1.1023 +# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
  1.1024 +# authentication.
  1.1025 +network={
  1.1026 +	ssid="example"
  1.1027 +	key_mgmt=WPA-EAP
  1.1028 +	eap=TTLS
  1.1029 +	# Phase1 / outer authentication
  1.1030 +	anonymous_identity="anonymous@example.com"
  1.1031 +	ca_cert="/etc/cert/ca.pem"
  1.1032 +	# Phase 2 / inner authentication
  1.1033 +	phase2="autheap=TLS"
  1.1034 +	ca_cert2="/etc/cert/ca2.pem"
  1.1035 +	client_cert2="/etc/cer/user.pem"
  1.1036 +	private_key2="/etc/cer/user.prv"
  1.1037 +	private_key2_passwd="password"
  1.1038 +	priority=2
  1.1039 +}
  1.1040 +
  1.1041 +# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
  1.1042 +# group cipher.
  1.1043 +network={
  1.1044 +	ssid="example"
  1.1045 +	bssid=00:11:22:33:44:55
  1.1046 +	proto=WPA RSN
  1.1047 +	key_mgmt=WPA-PSK WPA-EAP
  1.1048 +	pairwise=CCMP
  1.1049 +	group=CCMP
  1.1050 +	psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
  1.1051 +}
  1.1052 +
  1.1053 +# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
  1.1054 +# and all valid ciphers.
  1.1055 +network={
  1.1056 +	ssid=00010203
  1.1057 +	psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
  1.1058 +}
  1.1059 +
  1.1060 +
  1.1061 +# EAP-SIM with a GSM SIM or USIM
  1.1062 +network={
  1.1063 +	ssid="eap-sim-test"
  1.1064 +	key_mgmt=WPA-EAP
  1.1065 +	eap=SIM
  1.1066 +	pin="1234"
  1.1067 +	pcsc=""
  1.1068 +}
  1.1069 +
  1.1070 +
  1.1071 +# EAP-PSK
  1.1072 +network={
  1.1073 +	ssid="eap-psk-test"
  1.1074 +	key_mgmt=WPA-EAP
  1.1075 +	eap=PSK
  1.1076 +	anonymous_identity="eap_psk_user"
  1.1077 +	password=06b4be19da289f475aa46a33cb793029
  1.1078 +	identity="eap_psk_user@example.com"
  1.1079 +}
  1.1080 +
  1.1081 +
  1.1082 +# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
  1.1083 +# EAP-TLS for authentication and key generation; require both unicast and
  1.1084 +# broadcast WEP keys.
  1.1085 +network={
  1.1086 +	ssid="1x-test"
  1.1087 +	key_mgmt=IEEE8021X
  1.1088 +	eap=TLS
  1.1089 +	identity="user@example.com"
  1.1090 +	ca_cert="/etc/cert/ca.pem"
  1.1091 +	client_cert="/etc/cert/user.pem"
  1.1092 +	private_key="/etc/cert/user.prv"
  1.1093 +	private_key_passwd="password"
  1.1094 +	eapol_flags=3
  1.1095 +}
  1.1096 +
  1.1097 +
  1.1098 +# LEAP with dynamic WEP keys
  1.1099 +network={
  1.1100 +	ssid="leap-example"
  1.1101 +	key_mgmt=IEEE8021X
  1.1102 +	eap=LEAP
  1.1103 +	identity="user"
  1.1104 +	password="foobar"
  1.1105 +}
  1.1106 +
  1.1107 +# EAP-IKEv2 using shared secrets for both server and peer authentication
  1.1108 +network={
  1.1109 +	ssid="ikev2-example"
  1.1110 +	key_mgmt=WPA-EAP
  1.1111 +	eap=IKEV2
  1.1112 +	identity="user"
  1.1113 +	password="foobar"
  1.1114 +}
  1.1115 +
  1.1116 +# EAP-FAST with WPA (WPA or WPA2)
  1.1117 +network={
  1.1118 +	ssid="eap-fast-test"
  1.1119 +	key_mgmt=WPA-EAP
  1.1120 +	eap=FAST
  1.1121 +	anonymous_identity="FAST-000102030405"
  1.1122 +	identity="username"
  1.1123 +	password="password"
  1.1124 +	phase1="fast_provisioning=1"
  1.1125 +	pac_file="/etc/wpa_supplicant.eap-fast-pac"
  1.1126 +}
  1.1127 +
  1.1128 +network={
  1.1129 +	ssid="eap-fast-test"
  1.1130 +	key_mgmt=WPA-EAP
  1.1131 +	eap=FAST
  1.1132 +	anonymous_identity="FAST-000102030405"
  1.1133 +	identity="username"
  1.1134 +	password="password"
  1.1135 +	phase1="fast_provisioning=1"
  1.1136 +	pac_file="blob://eap-fast-pac"
  1.1137 +}
  1.1138 +
  1.1139 +# Plaintext connection (no WPA, no IEEE 802.1X)
  1.1140 +network={
  1.1141 +	ssid="plaintext-test"
  1.1142 +	key_mgmt=NONE
  1.1143 +}
  1.1144 +
  1.1145 +
  1.1146 +# Shared WEP key connection (no WPA, no IEEE 802.1X)
  1.1147 +network={
  1.1148 +	ssid="static-wep-test"
  1.1149 +	key_mgmt=NONE
  1.1150 +	wep_key0="abcde"
  1.1151 +	wep_key1=0102030405
  1.1152 +	wep_key2="1234567890123"
  1.1153 +	wep_tx_keyidx=0
  1.1154 +	priority=5
  1.1155 +}
  1.1156 +
  1.1157 +
  1.1158 +# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
  1.1159 +# IEEE 802.11 authentication
  1.1160 +network={
  1.1161 +	ssid="static-wep-test2"
  1.1162 +	key_mgmt=NONE
  1.1163 +	wep_key0="abcde"
  1.1164 +	wep_key1=0102030405
  1.1165 +	wep_key2="1234567890123"
  1.1166 +	wep_tx_keyidx=0
  1.1167 +	priority=5
  1.1168 +	auth_alg=SHARED
  1.1169 +}
  1.1170 +
  1.1171 +
  1.1172 +# IBSS/ad-hoc network with RSN
  1.1173 +network={
  1.1174 +	ssid="ibss-rsn"
  1.1175 +	key_mgmt=WPA-PSK
  1.1176 +	proto=RSN
  1.1177 +	psk="12345678"
  1.1178 +	mode=1
  1.1179 +	frequency=2412
  1.1180 +	pairwise=CCMP
  1.1181 +	group=CCMP
  1.1182 +}
  1.1183 +
  1.1184 +# IBSS/ad-hoc network with WPA-None/TKIP (deprecated)
  1.1185 +network={
  1.1186 +	ssid="test adhoc"
  1.1187 +	mode=1
  1.1188 +	frequency=2412
  1.1189 +	proto=WPA
  1.1190 +	key_mgmt=WPA-NONE
  1.1191 +	pairwise=NONE
  1.1192 +	group=TKIP
  1.1193 +	psk="secret passphrase"
  1.1194 +}
  1.1195 +
  1.1196 +
  1.1197 +# Catch all example that allows more or less all configuration modes
  1.1198 +network={
  1.1199 +	ssid="example"
  1.1200 +	scan_ssid=1
  1.1201 +	key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
  1.1202 +	pairwise=CCMP TKIP
  1.1203 +	group=CCMP TKIP WEP104 WEP40
  1.1204 +	psk="very secret passphrase"
  1.1205 +	eap=TTLS PEAP TLS
  1.1206 +	identity="user@example.com"
  1.1207 +	password="foobar"
  1.1208 +	ca_cert="/etc/cert/ca.pem"
  1.1209 +	client_cert="/etc/cert/user.pem"
  1.1210 +	private_key="/etc/cert/user.prv"
  1.1211 +	private_key_passwd="password"
  1.1212 +	phase1="peaplabel=0"
  1.1213 +}
  1.1214 +
  1.1215 +# Example of EAP-TLS with smartcard (openssl engine)
  1.1216 +network={
  1.1217 +	ssid="example"
  1.1218 +	key_mgmt=WPA-EAP
  1.1219 +	eap=TLS
  1.1220 +	proto=RSN
  1.1221 +	pairwise=CCMP TKIP
  1.1222 +	group=CCMP TKIP
  1.1223 +	identity="user@example.com"
  1.1224 +	ca_cert="/etc/cert/ca.pem"
  1.1225 +	client_cert="/etc/cert/user.pem"
  1.1226 +
  1.1227 +	engine=1
  1.1228 +
  1.1229 +	# The engine configured here must be available. Look at
  1.1230 +	# OpenSSL engine support in the global section.
  1.1231 +	# The key available through the engine must be the private key
  1.1232 +	# matching the client certificate configured above.
  1.1233 +
  1.1234 +	# use the opensc engine
  1.1235 +	#engine_id="opensc"
  1.1236 +	#key_id="45"
  1.1237 +
  1.1238 +	# use the pkcs11 engine
  1.1239 +	engine_id="pkcs11"
  1.1240 +	key_id="id_45"
  1.1241 +
  1.1242 +	# Optional PIN configuration; this can be left out and PIN will be
  1.1243 +	# asked through the control interface
  1.1244 +	pin="1234"
  1.1245 +}
  1.1246 +
  1.1247 +# Example configuration showing how to use an inlined blob as a CA certificate
  1.1248 +# data instead of using external file
  1.1249 +network={
  1.1250 +	ssid="example"
  1.1251 +	key_mgmt=WPA-EAP
  1.1252 +	eap=TTLS
  1.1253 +	identity="user@example.com"
  1.1254 +	anonymous_identity="anonymous@example.com"
  1.1255 +	password="foobar"
  1.1256 +	ca_cert="blob://exampleblob"
  1.1257 +	priority=20
  1.1258 +}
  1.1259 +
  1.1260 +blob-base64-exampleblob={
  1.1261 +SGVsbG8gV29ybGQhCg==
  1.1262 +}
  1.1263 +
  1.1264 +
  1.1265 +# Wildcard match for SSID (plaintext APs only). This example select any
  1.1266 +# open AP regardless of its SSID.
  1.1267 +network={
  1.1268 +	key_mgmt=NONE
  1.1269 +}
  1.1270 +
  1.1271 +
  1.1272 +# Example config file that will only scan on channel 36.
  1.1273 +freq_list=5180
  1.1274 +network={
  1.1275 +	key_mgmt=NONE
  1.1276 +}