Lines Matching full:configuration
1 ##### Example wpa_supplicant configuration file ###############################
3 # This file describes configuration file format and lists all available option.
4 # Please also take a look at simpler configuration examples in 'examples'
12 # Note: All file paths in this configuration file should use full (absolute,
16 # Whether to allow wpa_supplicant to update (overwrite) configuration
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
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
26 # global configuration (shared by all network blocks)
32 # in configuration is used to determine whether the control interface is
37 # external programs (CLI/GUI, etc.) for status information and configuration.
47 # configuration and open raw sockets) and still allow GUI/CLI components to be
49 # change the network configuration, this access needs to be protected in many
54 # not included in the configuration file, group will not be changed from the
82 # to 1 by default. This configuration value can be used to set it to the new
101 # the network blocks in the configuration file are tried one by one until
204 # block in this configuration file. The network blocks are in preference order
216 # variable to make it easier to do network specific configuration.
240 # networks in the order that used in the configuration file.
389 # Alternatively, a named configuration blob can be used by setting this
404 # Alternatively, a named configuration blob can be used by setting this
409 # This is an optional configuration file for setting parameters for an
411 # authentication does not use this configuration. However, it is possible
437 # Some servers, e.g., Radiator, may require peaplabel=1 configuration to
488 # background. Alternatively, a named configuration blob can be used by
566 # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
580 # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
593 # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
768 # Catch all example that allows more or less all configuration modes
813 # Optional PIN configuration; this can be left out and PIN will be
818 # Example configuration showing how to use an inlined blob as a CA certificate
