xref: /openbsd/usr.sbin/hostapd/hostapd.8 (revision 898184e3)
1.\" $OpenBSD: hostapd.8,v 1.18 2012/08/15 19:25:41 jmc Exp $
2.\"
3.\" Copyright (c) 2004, 2005 Reyk Floeter <reyk@openbsd.org>
4.\"
5.\" Permission to use, copy, modify, and distribute this software for any
6.\" purpose with or without fee is hereby granted, provided that the above
7.\" copyright notice and this permission notice appear in all copies.
8.\"
9.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16.\"
17.Dd $Mdocdate: August 15 2012 $
18.Dt HOSTAPD 8
19.Os
20.Sh NAME
21.Nm hostapd
22.Nd Host Access Point daemon
23.Sh SYNOPSIS
24.Nm hostapd
25.Op Fl dv
26.Op Fl D Ar macro Ns = Ns Ar value
27.Op Fl f Ar file
28.Sh DESCRIPTION
29.Nm
30is a daemon which allows communication between different 802.11
31wireless access points running in
32.Em Host AP
33mode.
34.Pp
35.Nm
36implements the Inter Access Point Protocol (IAPP).
37Its purpose is to exchange station association updates between access
38points in large wireless networks.
39IAPP has been designed to speed up roaming between different access
40points in the same Extended Service Set (ESS).
41IAPP is described in the IEEE 802.11f standard.
42.Pp
43.Nm
44additionally allows the monitoring and logging of station associations on a
45non-hostap host which is receiving IAPP messages.
46.Pp
47.Nm
48uses two network interfaces on startup specified in the configuration file
49.Xr hostapd.conf 5 .
50The first interface is used to access the Host AP,
51which is a wireless interface running in Host AP mode.
52Host AP mode can be enabled using
53.Xr ifconfig 8 .
54The second interface is used to communicate with other
55.Nm
56in the same broadcast domain or multicast group.
57Usually a wired interface is used to communicate with other
58.Nm .
59.Pp
60.Nm
61broadcasts an
62.Em ADD.notify
63IAPP message when a new station is associated to the Host AP.
64When
65.Nm
66receives an ADD.notify message it tells the Host AP
67to remove the specified station.
68.Pp
69.Nm
70may also handle dynamic roaming of IP addresses and routes in
71addition to the standard IAPP ADD.notify behaviour.
72See the section called
73.Sx IP Roaming
74in
75.Xr hostapd.conf 5
76for details.
77.Pp
78The options are as follows:
79.Bl -tag -width Ds
80.It Fl D Ar macro Ns = Ns Ar value
81Define
82.Ar macro
83to be set to
84.Ar value
85on the command line.
86Overrides the definition of
87.Ar macro
88in the configuration file.
89.It Fl d
90Do not daemonize and log to
91.Em stderr .
92.It Fl f Ar file
93Use
94.Ar file
95as the configuration file, instead of the default
96.Pa /etc/hostapd.conf .
97.It Fl v
98Produce more verbose output.
99.El
100.Sh FILES
101.Bl -tag -width "/etc/hostapd.confXXX" -compact
102.It Pa /etc/hostapd.conf
103default
104.Nm
105configuration file
106.El
107.Sh SEE ALSO
108.Xr hostapd.conf 5 ,
109.Xr ifconfig 8
110.Rs
111.%R IEEE 802.11f
112.%T Inter Access Point Protocol
113.%D March 2001
114.Re
115.Sh HISTORY
116The
117.Nm
118program first appeared at the 21st Chaos Communication Congress
119.Pq Lk http://www.ccc.de/congress/2004/
120and later in
121.Ox 3.8 .
122.Sh AUTHORS
123The
124.Nm
125program was written by
126.An Reyk Floeter Aq reyk@openbsd.org .
127.Sh CAVEATS
128.Nm
129depends on drivers using the net80211
130kernel wireless layer with support of Host AP mode.
131For traditional reasons,
132the
133.Xr wi 4
134driver still uses its own Host AP code in
135.Fn if_wi_hostap ,
136which is not supported by
137.Nm .
138.Pp
139The IEEE 802.11 WLAN protocol lacks authentication of management
140frames and is vulnerable to various Denial-of-Service and
141Man-in-the-Middle attacks.
142That should be considered when implementing wireless networks
143with
144.Nm .
145