Difference between revisions of "WPA supplicant"

From ArchWiki
Jump to: navigation, search
(Connecting with wpa_cli: ctrl_interface)
(Problems with eduroam and other MSCHAPv2 connections: rm "as of", reword)
 
(200 intermediate revisions by 31 users not shown)
Line 1: Line 1:
[[Category:Wireless Networking]]  
+
[[Category:Wireless networking]]
 +
[[Category:Network configuration]]
 
[[es:WPA supplicant]]
 
[[es:WPA supplicant]]
 
[[it:WPA supplicant]]
 
[[it:WPA supplicant]]
[[ru:WPA Supplicant]]
+
[[ja:WPA supplicant]]
[[zh-CN:WPA Supplicant]]
+
[[ru:WPA supplicant]]
{{Article summary start}}
+
[[zh-hans:WPA supplicant]]
{{Article summary text|Setup and usage of wpa_supplicant}}
+
{{Related articles start}}
{{Article summary heading|Related}}
+
{{Related|Network configuration}}
{{Article summary wiki|Network Configuration}}
+
{{Related|Wireless network configuration}}
{{Article summary wiki|Wireless Setup}}
+
{{Related|WPA2 Enterprise}}
{{Article summary end}}
+
{{Related articles end}}
  
[http://hostap.epitest.fi/wpa_supplicant/ wpa_supplicant] is a cross-platform [[Wikipedia:Supplicant (computer)|WPA Supplicant]] with support for WPA and WPA2 ([https://en.wikipedia.org/wiki/IEEE_802.11i IEEE 802.11i] / RSN (Robust Secure Network)). It is suitable for both desktop/laptop computers and embedded systems. {{ic|wpa_supplicant}} is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wlan driver.
+
[http://hostap.epitest.fi/wpa_supplicant/ wpa_supplicant] is a cross-platform [[Wikipedia:Supplicant (computer)|supplicant]] with support for WEP, WPA and WPA2 ([[wikipedia:IEEE_802.11i|IEEE 802.11i]] / RSN (Robust Secure Network)). It is suitable for desktops, laptops and embedded systems.
 +
 
 +
''wpa_supplicant'' is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wireless driver.
  
 
== Installation ==
 
== Installation ==
  
Install {{Pkg|wpa_supplicant}} from the [[official repositories]].
+
[[Install]] the {{Pkg|wpa_supplicant}} package.
 +
 
 +
Optionally also install {{Pkg|wpa_supplicant_gui}}, which provides ''wpa_gui'', a graphical front-end for ''wpa_supplicant''.
 +
 
 +
== Overview ==
 +
 
 +
The first step to connect to an encrypted wireless network is having ''wpa_supplicant'' obtain authentication from a WPA authenticator. In order to do this, ''wpa_supplicant'' must be configured so that it will be able to submit the correct credentials to the authenticator.
  
Optionally {{Pkg|wpa_supplicant_gui}} can be installed which provides {{ic|wpa_gui}}; a graphical frontend for {{ic|wpa_supplicant}} using the {{pkg|qt4}} toolkit.
+
Once the authentication is successful, it will be possible to connect to the network by obtaining an IP address in the usual way. For example, the [[Core utilities#ip|iproute2]] suite of utilities can be used for temporary configuration during initial testing of the network interface. [[dhcpcd]] and [[systemd-networkd]] can obtain an IP address automatically via DHCP. See [[Network configuration#Configure the IP address]] for more details. The [[Wireless_network_configuration#Wireless management]] section may help as well.
  
 
== Connecting with wpa_cli ==
 
== Connecting with wpa_cli ==
  
To associate with a wireless access point (WAP) using {{ic|wpa_supplicant}}, use the including command line tool {{ic|wpa_cli}}. In order to use {{ic|wpa_cli}}, a ''control interface'' must be specified for {{ic|wpa_supplicant}}. Do this by creating a config file containing {{ic|ctrl_interface=/var/run/wpa_supplicant}}.
+
This connection method allows scanning for the available networks, making use of ''wpa_cli'', a command line tool which can be used to interactively configure ''wpa_supplicant'' at runtime. See [http://linux.die.net/man/8/wpa_cli wpa_cli(8)] for details.
 +
 
 +
In order to use ''wpa_cli'', a control interface must be specified for ''wpa_supplicant'', and it must be given the rights to update the configuration. Do this by creating a minimal configuration file:
 +
 
 +
{{hc|/etc/wpa_supplicant/example.conf|2=
 +
ctrl_interface=/run/wpa_supplicant
 +
update_config=1
 +
}}
 +
 
 +
Now start ''wpa_supplicant'' with:
 +
 
 +
# wpa_supplicant -B -i ''interface'' -c /etc/wpa_supplicant/example.conf
 +
 
 +
{{Tip|To discover your wireless network interface name, issue the {{ic|ip link}} command.}}
 +
 
 +
At this point run:
 +
 
 +
# wpa_cli
 +
 
 +
This will present an interactive prompt ({{ic|>}}), which has tab completion and descriptions of completed commands.
  
{{Tip|Refer to the provided {{ic|/etc/wpa_supplicant/wpa_supplicant.conf}} for details.}}
+
{{Tip|The default location of the control socket is {{ic|/var/run/wpa_supplicant/}}, custom path can be set manually with the {{ic|-p}} option to match the ''wpa_supplicant'' configuration. It is also possible to specify the interface to be configured with the {{ic|-i}} option, otherwise the first found wireless interface managed by ''wpa_supplicant'' will be used.}}
  
To enable saving changes made using wpa_cli, append the line {{ic|update_config=1}} to the configuration file. Start wpa_supplicant with
+
Use the {{ic|scan}} and {{ic|scan_results}} commands to see the available networks:
  
  # wpa_supplicant -B -i ''interface'' -c ''/path/to/config''
+
> scan
 +
OK
 +
<3>CTRL-EVENT-SCAN-RESULTS
 +
> scan_results
 +
bssid / frequency / signal level / flags / ssid
 +
00:00:00:00:00:00 2462 -49 [WPA2-PSK-CCMP][ESS] MYSSID
 +
11:11:11:11:11:11 2437 -64 [WPA2-PSK-CCMP][ESS] ANOTHERSSID
  
Invoke {{ic|wpa_cli}} with no arguments to get an interactive prompt ({{ic|>}}). The prompt has tab completion and descriptions of completed commands. The command {{ic|scan}} initiates a scan; a notification is issued when the scan is complete. Then:
+
To associate with {{ic|MYSSID}}, add the network, set the credentials and enable it:
  
  > scan_results
+
> add_network
  bssid / frequency / signal level / flags / ssid
+
0
  00:00:00:00:00:00 2462 -49 [WPA2-PSK-CCMP][ESS] MYSSID
+
> set_network 0 ssid "MYSSID"
  11:11:11:11:11:11 2437 -64 [WPA2-PSK-CCMP][ESS] ANOTHERSSID
+
> set_network 0 psk "passphrase"
 +
> enable_network 0
 +
<2>CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=0 id_str=]
  
To associate with ''MYSSID'', tell {{ic|wpa_supplicant}} about it. Each network is indexed numerically, so the first network will have index zero. The [http://en.wikipedia.org/wiki/Pre-shared_key PSK] can be provided without quotes as an alternative to providing the passphrase in this example:
+
If the SSID does not have password authentication, you must explicitly configure the network as keyless by replacing the command {{ic|set_network 0 psk "passphrase"}} with {{ic|set_network 0 key_mgmt NONE}}.
  
  > add_network
+
{{Note|
  0
+
* Each network is indexed numerically, so the first network will have index 0.
  > set_network 0 ssid "''MYSSID''"
+
* The [[wikipedia:Pre-shared_key|PSK]] is computed from the ''quoted'' "passphrase" string, as also shown by the [[#Connecting with wpa_passphrase|wpa_passphrase]] command. Nonetheless, you can enter the PSK directly by passing it to {{ic|psk}} ''without'' quotes.}}
  > set_network 0 psk "''passphrase''"
 
  > enable_network 0
 
  <2>CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=0 id_str=]
 
  
To save this network in the configuration file,
+
Finally save this network in the configuration file:
  
  > save_config
+
> save_config
  OK
+
OK
  
Now that association with the WAP is complete, obtain an IP address via {{Pkg|dhcpcd}} or using the {{Pkg|iproute2}} tools.
+
Once association is complete, all that is left to do is obtain an IP address as indicated in the [[#Overview]], for example:
  
== Configuration ==
+
# dhcpcd ''interface''
  
{{Pkg|wpa_supplicant}} provides a reference configuration file located at {{ic|/etc/wpa_supplicant/wpa_supplicant.conf}} which contains detailed documentation for the all available options and their utilisation.
+
== Connecting with wpa_passphrase ==
  
In its simplest form, a configuration file requires only a network block. For example:
+
This connection method allows quickly connecting to a network whose SSID is already known, making use of ''wpa_passphrase'', a command line tool which generates the minimal configuration needed by ''wpa_supplicant''. For example:
  
{{hc|/etc/wpa_supplicant/foobar.conf|2=
+
{{hc|$ wpa_passphrase MYSSID passphrase|2=
 
network={
 
network={
     ssid="..."
+
     ssid="MYSSID"
 +
    #psk="passphrase"
 +
    psk=59e0d07fa4c7741797a4e394f38a5c321e3bed51d54ad5fcbd3f84bc7415d73d
 
}
 
}
 
}}
 
}}
  
This can easily be generated using the {{ic|wpa_passphrase}} tool. For example:
+
This means that ''wpa_supplicant'' can be associated with ''wpa_passphrase'' and simply started with:
 +
 
 +
# wpa_supplicant -B -i ''interface'' -c <(wpa_passphrase MYSSID passphrase)
 +
 
 +
{{Note|Because of the process substitution, you '''cannot''' run this command with [[sudo]] - you will need a root shell. Just pre-pending ''sudo'' will lead to the following error:
 +
Successfully initialized wpa_supplicant
 +
Failed to open config file '/dev/fd/63', error: No such file or directory
 +
Failed to read or parse configuration '/dev/fd/63'
 +
See also [[Help:Reading#Regular user or root]].}}
 +
 
 +
{{Tip|
 +
* Use quotes, if the input contains spaces. For example: {{ic|"secret passphrase"}}
 +
* To discover your wireless network interface name, issue the {{ic|ip link}} command.
 +
* Some unusually complex passphrases may require input from a file, e.g. {{ic|wpa_passphrase MYSSID < passphrase.txt}}, or here strings, e.g. {{ic|wpa_passphrase MYSSID <<< "passphrase"}}.
 +
}}
 +
 
 +
Finally, you should obtain an IP address as indicated in the [[#Overview]], for example:
 +
 
 +
# dhcpcd ''interface''
 +
 
 +
== Advanced usage ==
 +
 
 +
For networks of varying complexity, possibly employing extensive use of [[wikipedia:Extensible_Authentication_Protocol|EAP]], it will be useful to maintain a customised configuration file. For an overview of the configuration with examples, refer to {{man|5|wpa_supplicant.conf|url=http://linux.die.net/man/5/wpa_supplicant.conf}}; for details on all the supported configuration parameters, refer to the example file {{ic|/usr/share/doc/wpa_supplicant/wpa_supplicant.conf}}.[https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf]
 +
 
 +
=== Configuration ===
 +
 
 +
As is clear after reading [[#Connecting with wpa_passphrase]], a basic configuration file can be generated with:
 +
 
 +
# wpa_passphrase MYSSID passphrase > /etc/wpa_supplicant/example.conf
 +
 
 +
This will only create a {{ic|network}} section. A configuration file with some more common options may look like:
 +
 
 +
{{hc|/etc/wpa_supplicant/example.conf|2=<nowiki>
 +
ctrl_interface=/var/run/wpa_supplicant
 +
ctrl_interface_group=wheel
 +
update_config=1
 +
fast_reauth=1
 +
ap_scan=1
  
{{hc|$ wpa_passphrase ''essid'' ''passphrase''|2=
 
 
network={
 
network={
     ssid="''essid''"
+
     ssid="MYSSID"
     #psk="''passphrase''"
+
    psk=59e0d07fa4c7741797a4e394f38a5c321e3bed51d54ad5fcbd3f84bc7415d73d
     psk=f5d1c49e15e679bebe385c37648d4141bc5c9297796a8a185d7bc5ac62f954e3
+
}</nowiki>
 +
}}
 +
 
 +
The passphrase can alternatively be defined in clear text by enclosing it in quotes, if the resulting security problems are not of concern:
 +
 
 +
{{bc|1=
 +
network={
 +
    ssid="MYSSID"
 +
     psk="passphrase"
 +
}
 +
}}
 +
 
 +
If the network does not have a passphrase, e.g. a public Wi-Fi:
 +
 
 +
{{bc|1=
 +
network={
 +
    ssid="MYSSID"
 +
     key_mgmt=NONE
 
}
 
}
 
}}
 
}}
  
Now both {{ic|wpa_supplicant}} and {{ic|wpa_passphrase}} can be combined to associate with almost all WPA2 (Personal) networks:
+
Further {{ic|network}} blocks may be added manually, or using ''wpa_cli'' as illustrated in [[#Connecting with wpa_cli]]. In order to use ''wpa_cli'', a control interface must be set with the {{ic|ctrl_interface}} option. Setting {{ic|1=ctrl_interface_group=wheel}} allows users belonging to such group to execute ''wpa_cli''. This setting can be used to enable users without root access (or equivalent via sudo etc) to connect to wireless networks. Also add {{ic|1=update_config=1}} so that changes made with ''wpa_cli'' to {{ic|example.conf}} can be saved. Note that any user that is a member of the {{ic|ctrl_interface_group}} group will be able to make changes to the file if this is turned on.
 +
 
 +
{{ic|<nowiki>fast_reauth=1</nowiki>}} and {{ic|<nowiki>ap_scan=1</nowiki>}} are the ''wpa_supplicant'' options active globally at the time of writing. Whether you need them, or other global options too for that matter, depends on the type of network to connect to. If you need other global options, simply copy them over to the file from {{ic|/usr/share/doc/wpa_supplicant/wpa_supplicant.conf}}.
 +
 
 +
Alternatively, {{ic|wpa_cli set}} can be used to see options' status or set new ones. Multiple network blocks may be appended to this configuration: the supplicant will handle association to and roaming between all of them. The strongest signal defined with a network block usually is connected to by default, one may define {{ic|priority<nowiki>=</nowiki>}} to influence behaviour.
 +
 
 +
Once you have finished the configuration file, you can optionally use it as a system-wide or per-interface default configuration by naming it according to the paths listed in [[#At boot (systemd)]]. This also applies if you use additional network manager tools, which may rely on the paths (for example [[Dhcpcd#10-wpa_supplicant]]).
 +
 
 +
{{Tip|To configure a network block to a hidden wireless ''SSID'', which by definition will not turn up in a regular scan, the option {{ic|scan_ssid<nowiki>=</nowiki>1}} has to be defined in the network block.}}
 +
 
 +
=== Connection ===
 +
 
 +
==== Manual ====
 +
 
 +
First start ''wpa_supplicant'' command, whose most commonly used arguments are:
 +
 
 +
* {{ic|-B}} - Fork into background.
 +
* {{ic|-c ''filename''}} - Path to configuration file.
 +
* {{ic|-i ''interface''}} - Interface to listen on.
 +
* {{ic|-D ''driver''}} - Optionally specify the driver to be used. For a list of supported drivers see the output of {{ic|wpa_supplicant -h}}.
 +
** {{ic|nl80211}} is the current standard, but not all wireless chip's modules support it.
 +
** {{ic|wext}} is currently deprecated, but still widely supported.
 +
 
 +
See [http://linux.die.net/man/8/wpa_supplicant wpa_supplicant(8)] for the full argument list. For example:
 +
 
 +
# wpa_supplicant -B -i ''interface'' -c /etc/wpa_supplicant/example.conf
 +
 
 +
followed by a method to obtain an ip address manually as indicated in the [[#Overview]], for example:
  
  # wpa_supplicant -B -i ''interface'' -c <(wpa_passphrase ''essid'' ''passphrase'')
+
  # dhcpcd ''interface''
  
All that remains is to simply connect using a [[Network Configuration#Static IP Address|static IP]] or [[Network Configuration#Dynamic IP Address|DHCP]]. For example:
+
{{Tip|
 +
* ''dhcpcd'' has a hook that can lauch ''wpa_supplicant'' implicitly, see [[dhcpcd#10-wpa_supplicant]].
 +
* While testing arguments/configuration it may be helpful to launch ''wpa_supplicant'' in the foreground (i.e. ''without'' the {{ic|-B}} option) for better debugging messages.
 +
}}
  
# dhcpcd -A ''interface''
+
==== At boot (systemd) ====
  
== Maintaining a custom configuration ==
+
The ''wpa_supplicant'' package provides multiple [[systemd]] service files:
  
{{Poor writing|This section is planned to be rewritten with a clearer structure and direction and more attention will be given to maintaining networks and controlling them effectively.}}
+
* {{ic|wpa_supplicant.service}} - uses [[D-Bus]], recommended for [[NetworkManager]] users.
 +
* {{ic|wpa_supplicant@.service}} - accepts the interface name as an argument and starts the ''wpa_supplicant'' daemon for this interface. It reads a {{ic|/etc/wpa_supplicant/wpa_supplicant-''interface''.conf}} configuration file.
 +
* {{ic|wpa_supplicant-nl80211@.service}} - also interface specific, but explicitly forces the {{ic|nl80211}} driver (see below). The configuration file path is {{ic|/etc/wpa_supplicant/wpa_supplicant-nl80211-''interface''.conf}}.
 +
* {{ic|wpa_supplicant-wired@.service}} - also interface specific, uses the {{ic|wired}} driver. The configuration file path is {{ic|/etc/wpa_supplicant/wpa_supplicant-wired-''interface''.conf}}.
  
{{Note|To discover your network interface name, issue the {{ic|ip link}} command.}}
+
To enable wireless at boot, enable an instance of one of the above services on a particular wireless interface. For example, [[enable]] the {{ic|wpa_supplicant@''interface''}} systemd unit.
  
As discussed above we can make use of {{ic|wpa_passphrase}} to generate a basic configuration which we can augment with additional networks and options of our choosing. This may be necessary for more advanced networks employing extensive use of [https://en.wikipedia.org/wiki/Extensible_Authentication_Protocol EAP].
+
Now choose and [[enable]] an instance of a service to obtain an ip address for the particular ''interface'' as indicated in the [[#Overview]]. For example, [[enable]] the {{ic|dhcpcd@''interface''}} systemd unit.
  
Firstly we will use {{ic|wpa_passphrase}} to create our basic configuration file.
+
{{Tip|''dhcpcd'' has a hook that can lauch ''wpa_supplicant'' implicitly, see [[dhcpcd#10-wpa_supplicant]].}}
  
# wpa_passphrase ''essid'' ''passphrase'' > /etc/wpa_supplicant/foobar.conf
+
=== wpa_cli action script ===
  
{{Tip|Some unusually complex passphrases may require input from a file: {{bc|# wpa_passphrase ''essid'' < ''passphrase.txt'' > /etc/wpa_supplicant/foobar.conf}} }}
+
''wpa_cli'' can run in daemon mode and execute a specified script based on events from ''wpa_supplicant''. Two events are supported: {{ic|CONNECTED}} and {{ic|DISCONNECTED}}. Some [[environment variables]] are available to the script, see [http://linux.die.net/man/8/wpa_cli wpa_cli(8)] for details.
  
Next add a {{ic|ctrl_interface}} so that we may control the {{ic|wpa_supplicant}} daemon. We can allow {{ic|wpa_cli}} to edit this configuration by setting {{ic|1=update_config=1}}.
+
The following example will use [[desktop notifications]] to notify the user about the events:
  
{{hc|/etc/wpa_supplicant/foobar.conf|2=
+
{{bc|
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel # allow control for members in the 'wheel' group
+
#!/bin/bash
update_config=1
 
  
network={
+
case "$2" in
     ssid="foobarssid"
+
     CONNECTED)
     psk=f5d1c49e15e679bebe385c37648d4141bc5c9297796a8a185d7bc5ac62f954e3
+
        notify-send "WPA supplicant: connection established";
}
+
        ;;
 +
     DISCONNECTED)
 +
        notify-send "WPA supplicant: connection lost";
 +
        ;;
 +
esac
 
}}
 
}}
  
Multiple network blocks may be appended to this configuration.
+
Remember to make the script executable, then use the {{ic|-a}} flag to pass the script path to ''wpa_cli'':
  
To start your network simply run the following:
+
$ wpa_cli -a ''/path/to/script''
  
# ip link set ''interface'' up
+
== Troubleshooting ==
# wpa_supplicant -B -D nl80211 -i ''interface'' -c /etc/wpa_supplicant/foobar.conf
 
# dhcpcd -A ''interface''
 
  
{{Note|{{ic|nl80211}} is preferred over the deprecated {{ic|wext}} driver. For a list of supported drivers see the output of {{ic|wpa_supplicant -h}}.}}
+
{{Note|Make sure that you do not have remnant configuration files based on the full documentation example {{ic|/usr/share/doc/wpa_supplicant/wpa_supplicant.conf}}. It is filled with uncommented network examples that may lead random errors in practice ({{Bug|40661}}).}}
  
For networks of varying complexity please study the examples provided in the default {{ic|/etc/wpa_supplicant/wpa_supplicant.conf}} file.
+
=== nl80211 driver not supported on some hardware ===
  
=== Enabling with systemd ===
+
On some (especially old) hardware, ''wpa_supplicant'' may fail with the following error:
  
In order to enable wireless at boot, enable {{ic|wpa_supplicant}} on your particular wireless interface. To get connectivity with DHCP, enable {{ic|dhcpcd.service}} as well. Finally, to handle possible ethernet connections, install {{ic|ifplugd}} and enable it on your ethernet interface. For instance, the invocations might look like
+
Successfully initialized wpa_supplicant
 +
nl80211: Driver does not support authentication/association or connect commands
 +
wlan0: Failed to initialize driver interface
  
# systemctl enable wpa_supplicant@wlp3s1
+
This indicates that the standard {{ic|nl80211}} driver does not support the given hardware. The deprecated {{ic|wext}} driver might still support the device:
# systemctl enable dhcpcd
 
# systemctl enable ifplugd@enp5s2
 
  
WPA Supplicant handles roaming for all the SSIDs in its configuration file, and {{ic|ifplugd}} will configure ethernet and bring down wireless when an ethernet cable is plugged into the machine. {{ic|dhcpcd}} takes care of leasing an IP on all interfaces.
+
# wpa_supplicant -B -i wlan0 '''-D wext''' -c /etc/wpa_supplicant/example.conf
  
It is likely that {{ic|wpa_supplicant@.service}} will have to be modified so that it will read the proper configuration file. To override the {{ic|ExecStart&#61;}} line, create the following:
+
If the command works to connect, and the user wishes to use [[systemd]] to manage the wireless connection, it is necessary to [[systemd#Drop-in_files|edit]] the {{ic|wpa_supplicant@.service}} unit provided by the package and modify the {{ic|ExecStart}} line accordingly:
  
{{hc|/etc/systemd/system/wpa_supplicant@.service.d/foo.conf|<nowiki>
+
{{hc|/etc/systemd/system/wpa_supplicant@.service.d/wext.conf|2=
 
[Service]
 
[Service]
 
ExecStart=
 
ExecStart=
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/bar.conf -i%i
+
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I '''-Dnl80211,wext'''
</nowiki>}}
+
}}
 +
 
 +
{{Note|Multiple comma separated driver wrappers in option {{ic|-Dnl80211,wext}} makes ''wpa_supplicant'' use the first driver wrapper that is able to initialize the interface (see {{Man|8|wpa_supplicant|url=http://linux.die.net/man/8/wpa_supplicant}}). This is useful when using mutiple or removable (e.g. USB) wireless devices which use different drivers.}}
 +
 
 +
=== Problem with mounted network shares (cifs) and shutdown ===
 +
When you use wireless to connect to network shares you might have the problem that the shutdown takes a very long time. That is because systemd runs against a 3 minute timeout. The reason is that WPA supplicant is shut down too early, i.e. before systemd tries to unmount the share(s). A [https://github.com/systemd/systemd/issues/1435 bug report] suggests a work-around by [[systemd#Drop-in_files|editing]] the {{ic|wpa_supplicant@.service}} as follows:
 +
 
 +
{{hc|/etc/systemd/system/wpa_supplicant.service.d/override.conf|2=
 +
[Unit]
 +
After=dbus.service
 +
}}
 +
 
 +
=== Password-related problems ===
 +
 
 +
{{Pkg|wpa_supplicant}} may not work properly if directly passed via stdin particularly long or complex passphrases which include special characters. This may lead to errors such as {{ic|failed 4-way WPA handshake, PSK may be wrong}} when launching {{Pkg|wpa_supplicant}}.
 +
 
 +
In order to solve this try using here strings {{ic|wpa_passphrase <MYSSID> <<< "<passphrase>"}} or passing a file to the {{ic|-c}} flag instead:
 +
 
 +
# wpa_supplicant -i <interface> -c /etc/wpa_supplicant/example.conf
  
The {{ic|1=WantedBy=}} section in the current version is incorrect. If the line in {{ic|wpa_supplicant@.service}} does not match your interface name (wlan0), it will be necessary to copy the service file to {{ic|/etc/systemd/system}} and edit it to reflect
+
In some instances it was found that storing the passphrase cleartext in the {{ic|psk}} key of the {{ic|wpa_supplicant.conf}} {{ic|network}} block gave positive results (see [http://www.linuxquestions.org/questions/linux-wireless-networking-41/wpa-4-way-handshake-failed-843394/]). However, this approach is rather insecure. Using {{ic|wpa_cli}} to create this file instead of manually writing it gives the best results most of the time and therefore is the recommended way to proceed.
  
[Install]
+
=== Problems with eduroam and other MSCHAPv2 connections ===
WantedBy=multi-user.target
 
  
The issue is fixed in this [http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=commitdiff;h=893a0a558cd8fd9a7dc5827f379e0f8a273a4fe5 commit]
+
Ensure that your config uses
 +
phase2="auth=MSCHAPV2"
 +
with a capital "v" (see {{Bug|51358}}). You could even omit this setting entirely, since MSCHAPV2 is the default.
  
== Related Links ==
+
== See also ==
  
 +
* [http://hostap.epitest.fi/wpa_supplicant/ WPA Supplicant home]
 +
* [https://gist.github.com/buhman/7162560 wpa_cli usage examples]
 +
* [http://linux.die.net/man/8/wpa_supplicant wpa_supplicant(8)]
 +
* [http://linux.die.net/man/5/wpa_supplicant.conf wpa_supplicant.conf(5)]
 +
* [http://linux.die.net/man/8/wpa_cli wpa_cli(8)]
 
* [http://wireless.kernel.org/en/users/Documentation/wpa_supplicant Kernel.org wpa_supplicant documentation]
 
* [http://wireless.kernel.org/en/users/Documentation/wpa_supplicant Kernel.org wpa_supplicant documentation]

Latest revision as of 18:30, 1 March 2017

wpa_supplicant is a cross-platform supplicant with support for WEP, WPA and WPA2 (IEEE 802.11i / RSN (Robust Secure Network)). It is suitable for desktops, laptops and embedded systems.

wpa_supplicant is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wireless driver.

Installation

Install the wpa_supplicant package.

Optionally also install wpa_supplicant_gui, which provides wpa_gui, a graphical front-end for wpa_supplicant.

Overview

The first step to connect to an encrypted wireless network is having wpa_supplicant obtain authentication from a WPA authenticator. In order to do this, wpa_supplicant must be configured so that it will be able to submit the correct credentials to the authenticator.

Once the authentication is successful, it will be possible to connect to the network by obtaining an IP address in the usual way. For example, the iproute2 suite of utilities can be used for temporary configuration during initial testing of the network interface. dhcpcd and systemd-networkd can obtain an IP address automatically via DHCP. See Network configuration#Configure the IP address for more details. The Wireless_network_configuration#Wireless management section may help as well.

Connecting with wpa_cli

This connection method allows scanning for the available networks, making use of wpa_cli, a command line tool which can be used to interactively configure wpa_supplicant at runtime. See wpa_cli(8) for details.

In order to use wpa_cli, a control interface must be specified for wpa_supplicant, and it must be given the rights to update the configuration. Do this by creating a minimal configuration file:

/etc/wpa_supplicant/example.conf
ctrl_interface=/run/wpa_supplicant
update_config=1

Now start wpa_supplicant with:

# wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf
Tip: To discover your wireless network interface name, issue the ip link command.

At this point run:

# wpa_cli

This will present an interactive prompt (>), which has tab completion and descriptions of completed commands.

Tip: The default location of the control socket is /var/run/wpa_supplicant/, custom path can be set manually with the -p option to match the wpa_supplicant configuration. It is also possible to specify the interface to be configured with the -i option, otherwise the first found wireless interface managed by wpa_supplicant will be used.

Use the scan and scan_results commands to see the available networks:

> scan
OK
<3>CTRL-EVENT-SCAN-RESULTS
> scan_results
bssid / frequency / signal level / flags / ssid
00:00:00:00:00:00 2462 -49 [WPA2-PSK-CCMP][ESS] MYSSID
11:11:11:11:11:11 2437 -64 [WPA2-PSK-CCMP][ESS] ANOTHERSSID

To associate with MYSSID, add the network, set the credentials and enable it:

> add_network
0
> set_network 0 ssid "MYSSID"
> set_network 0 psk "passphrase"
> enable_network 0
<2>CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=0 id_str=]

If the SSID does not have password authentication, you must explicitly configure the network as keyless by replacing the command set_network 0 psk "passphrase" with set_network 0 key_mgmt NONE.

Note:
  • Each network is indexed numerically, so the first network will have index 0.
  • The PSK is computed from the quoted "passphrase" string, as also shown by the wpa_passphrase command. Nonetheless, you can enter the PSK directly by passing it to psk without quotes.

Finally save this network in the configuration file:

> save_config
OK

Once association is complete, all that is left to do is obtain an IP address as indicated in the #Overview, for example:

# dhcpcd interface

Connecting with wpa_passphrase

This connection method allows quickly connecting to a network whose SSID is already known, making use of wpa_passphrase, a command line tool which generates the minimal configuration needed by wpa_supplicant. For example:

$ wpa_passphrase MYSSID passphrase
network={
    ssid="MYSSID"
    #psk="passphrase"
    psk=59e0d07fa4c7741797a4e394f38a5c321e3bed51d54ad5fcbd3f84bc7415d73d
}

This means that wpa_supplicant can be associated with wpa_passphrase and simply started with:

# wpa_supplicant -B -i interface -c <(wpa_passphrase MYSSID passphrase)
Note: Because of the process substitution, you cannot run this command with sudo - you will need a root shell. Just pre-pending sudo will lead to the following error:
Successfully initialized wpa_supplicant
Failed to open config file '/dev/fd/63', error: No such file or directory
Failed to read or parse configuration '/dev/fd/63'
See also Help:Reading#Regular user or root.
Tip:
  • Use quotes, if the input contains spaces. For example: "secret passphrase"
  • To discover your wireless network interface name, issue the ip link command.
  • Some unusually complex passphrases may require input from a file, e.g. wpa_passphrase MYSSID < passphrase.txt, or here strings, e.g. wpa_passphrase MYSSID <<< "passphrase".

Finally, you should obtain an IP address as indicated in the #Overview, for example:

# dhcpcd interface

Advanced usage

For networks of varying complexity, possibly employing extensive use of EAP, it will be useful to maintain a customised configuration file. For an overview of the configuration with examples, refer to wpa_supplicant.conf(5); for details on all the supported configuration parameters, refer to the example file /usr/share/doc/wpa_supplicant/wpa_supplicant.conf.[1]

Configuration

As is clear after reading #Connecting with wpa_passphrase, a basic configuration file can be generated with:

# wpa_passphrase MYSSID passphrase > /etc/wpa_supplicant/example.conf

This will only create a network section. A configuration file with some more common options may look like:

/etc/wpa_supplicant/example.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
fast_reauth=1
ap_scan=1

network={
    ssid="MYSSID"
    psk=59e0d07fa4c7741797a4e394f38a5c321e3bed51d54ad5fcbd3f84bc7415d73d
}

The passphrase can alternatively be defined in clear text by enclosing it in quotes, if the resulting security problems are not of concern:

network={
    ssid="MYSSID"
    psk="passphrase"
}

If the network does not have a passphrase, e.g. a public Wi-Fi:

network={
    ssid="MYSSID"
    key_mgmt=NONE
}

Further network blocks may be added manually, or using wpa_cli as illustrated in #Connecting with wpa_cli. In order to use wpa_cli, a control interface must be set with the ctrl_interface option. Setting ctrl_interface_group=wheel allows users belonging to such group to execute wpa_cli. This setting can be used to enable users without root access (or equivalent via sudo etc) to connect to wireless networks. Also add update_config=1 so that changes made with wpa_cli to example.conf can be saved. Note that any user that is a member of the ctrl_interface_group group will be able to make changes to the file if this is turned on.

fast_reauth=1 and ap_scan=1 are the wpa_supplicant options active globally at the time of writing. Whether you need them, or other global options too for that matter, depends on the type of network to connect to. If you need other global options, simply copy them over to the file from /usr/share/doc/wpa_supplicant/wpa_supplicant.conf.

Alternatively, wpa_cli set can be used to see options' status or set new ones. Multiple network blocks may be appended to this configuration: the supplicant will handle association to and roaming between all of them. The strongest signal defined with a network block usually is connected to by default, one may define priority= to influence behaviour.

Once you have finished the configuration file, you can optionally use it as a system-wide or per-interface default configuration by naming it according to the paths listed in #At boot (systemd). This also applies if you use additional network manager tools, which may rely on the paths (for example Dhcpcd#10-wpa_supplicant).

Tip: To configure a network block to a hidden wireless SSID, which by definition will not turn up in a regular scan, the option scan_ssid=1 has to be defined in the network block.

Connection

Manual

First start wpa_supplicant command, whose most commonly used arguments are:

  • -B - Fork into background.
  • -c filename - Path to configuration file.
  • -i interface - Interface to listen on.
  • -D driver - Optionally specify the driver to be used. For a list of supported drivers see the output of wpa_supplicant -h.
    • nl80211 is the current standard, but not all wireless chip's modules support it.
    • wext is currently deprecated, but still widely supported.

See wpa_supplicant(8) for the full argument list. For example:

# wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf

followed by a method to obtain an ip address manually as indicated in the #Overview, for example:

# dhcpcd interface
Tip:
  • dhcpcd has a hook that can lauch wpa_supplicant implicitly, see dhcpcd#10-wpa_supplicant.
  • While testing arguments/configuration it may be helpful to launch wpa_supplicant in the foreground (i.e. without the -B option) for better debugging messages.

At boot (systemd)

The wpa_supplicant package provides multiple systemd service files:

  • wpa_supplicant.service - uses D-Bus, recommended for NetworkManager users.
  • wpa_supplicant@.service - accepts the interface name as an argument and starts the wpa_supplicant daemon for this interface. It reads a /etc/wpa_supplicant/wpa_supplicant-interface.conf configuration file.
  • wpa_supplicant-nl80211@.service - also interface specific, but explicitly forces the nl80211 driver (see below). The configuration file path is /etc/wpa_supplicant/wpa_supplicant-nl80211-interface.conf.
  • wpa_supplicant-wired@.service - also interface specific, uses the wired driver. The configuration file path is /etc/wpa_supplicant/wpa_supplicant-wired-interface.conf.

To enable wireless at boot, enable an instance of one of the above services on a particular wireless interface. For example, enable the wpa_supplicant@interface systemd unit.

Now choose and enable an instance of a service to obtain an ip address for the particular interface as indicated in the #Overview. For example, enable the dhcpcd@interface systemd unit.

Tip: dhcpcd has a hook that can lauch wpa_supplicant implicitly, see dhcpcd#10-wpa_supplicant.

wpa_cli action script

wpa_cli can run in daemon mode and execute a specified script based on events from wpa_supplicant. Two events are supported: CONNECTED and DISCONNECTED. Some environment variables are available to the script, see wpa_cli(8) for details.

The following example will use desktop notifications to notify the user about the events:

#!/bin/bash

case "$2" in
    CONNECTED)
        notify-send "WPA supplicant: connection established";
        ;;
    DISCONNECTED)
        notify-send "WPA supplicant: connection lost";
        ;;
esac

Remember to make the script executable, then use the -a flag to pass the script path to wpa_cli:

$ wpa_cli -a /path/to/script

Troubleshooting

Note: Make sure that you do not have remnant configuration files based on the full documentation example /usr/share/doc/wpa_supplicant/wpa_supplicant.conf. It is filled with uncommented network examples that may lead random errors in practice (FS#40661).

nl80211 driver not supported on some hardware

On some (especially old) hardware, wpa_supplicant may fail with the following error:

Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
wlan0: Failed to initialize driver interface

This indicates that the standard nl80211 driver does not support the given hardware. The deprecated wext driver might still support the device:

# wpa_supplicant -B -i wlan0 -D wext -c /etc/wpa_supplicant/example.conf

If the command works to connect, and the user wishes to use systemd to manage the wireless connection, it is necessary to edit the wpa_supplicant@.service unit provided by the package and modify the ExecStart line accordingly:

/etc/systemd/system/wpa_supplicant@.service.d/wext.conf
[Service]
ExecStart=
ExecStart=/usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I -Dnl80211,wext
Note: Multiple comma separated driver wrappers in option -Dnl80211,wext makes wpa_supplicant use the first driver wrapper that is able to initialize the interface (see wpa_supplicant(8)). This is useful when using mutiple or removable (e.g. USB) wireless devices which use different drivers.

Problem with mounted network shares (cifs) and shutdown

When you use wireless to connect to network shares you might have the problem that the shutdown takes a very long time. That is because systemd runs against a 3 minute timeout. The reason is that WPA supplicant is shut down too early, i.e. before systemd tries to unmount the share(s). A bug report suggests a work-around by editing the wpa_supplicant@.service as follows:

/etc/systemd/system/wpa_supplicant.service.d/override.conf
[Unit]
After=dbus.service

Password-related problems

wpa_supplicant may not work properly if directly passed via stdin particularly long or complex passphrases which include special characters. This may lead to errors such as failed 4-way WPA handshake, PSK may be wrong when launching wpa_supplicant.

In order to solve this try using here strings wpa_passphrase <MYSSID> <<< "<passphrase>" or passing a file to the -c flag instead:

# wpa_supplicant -i <interface> -c /etc/wpa_supplicant/example.conf

In some instances it was found that storing the passphrase cleartext in the psk key of the wpa_supplicant.conf network block gave positive results (see [2]). However, this approach is rather insecure. Using wpa_cli to create this file instead of manually writing it gives the best results most of the time and therefore is the recommended way to proceed.

Problems with eduroam and other MSCHAPv2 connections

Ensure that your config uses

phase2="auth=MSCHAPV2"

with a capital "v" (see FS#51358). You could even omit this setting entirely, since MSCHAPV2 is the default.

See also