Authenticator for IEEE 802.11 networks


hostapd-version [-BdhKtv] [-e entropy_file] [-f output_file] [-g global_ctrl_interface]
                [-G group] [-P PID_file] [-Z num] config-file ...

Runs on:

QNX Neutrino


Detach from the controlling terminal and run as a daemon process in the background.
Enable debugging messages. If this option is supplied twice, more verbose messages are displayed.
-e entropy_file
Specify the (readable and writable) entropy file for the hostapd utility to use.
-f output_file
Send the output to the specified file, instead of to standard output.
-g global_ctrl_interface
The path to the global_ctrl_interface socket.
-G group
The name of the global_ctrl_interface group.
Show help text.
Include key information in debugging output.
-P PID_file
Specify the location of the PID file.
Include timestamps in some debugging output.
Display version information on the terminal, and then exit.
-Z num
(QNX Neutrino extension; QNX Neutrino 7.0 or later) Specify the number of 4 KB pages for the slog2 buffer. The minimum is 5, the default is 10, and the maximum is 500.

The daemon has its own configuration file that can be used to define AP options. The distribution package contains an example of a configuration file. This is installed as /usr/share/examples/hostapd/hostapd.conf for you to use as a basis for configuration. It includes examples of all supported configuration options and a short description of each option. Start the hostapd utility with a full path to the configuration file as the command line argument; for example,./hostapd /etc/hostapd.conf. This file contains the name of the wireless interface.


The hostapd utility is an authenticator for IEEE 802.11 networks. It provides full support for WPA/IEEE 802.11i and can also act as an IEEE 802.1X Authenticator with a suitable backend Authentication Server (typically FreeRADIUS). The hostapd utility implements the authentication protocols that piggyback on top of the normal IEEE 802.11 protocol mechanisms.

The number in the hostapd utility name indicates the WPA version it supports. For example, hostapd-2.5 supports version 2.5.

To use hostapd as an authenticator, the underlying device must support some basic functionality, such as the ability to set security information in the 802.11 management frames. Note that not all devices have this support.

The hostapd utility is designed to be a daemon program that runs in the background and acts as the backend component controlling the wireless connection. It supports separate front-end programs such as the text-based front-end, hostapd_cli.

To reload changes to the configuration file, send a SIGHUP signal to the hostapd processor, or use the hostapd_cli reconfigure command.