various tweaks;

ok reyk@

1 files changed, 34 insertions, 45 deletions

diff --git a/usr.sbin/hostapd/hostapd.8 b/usr.sbin/hostapd/hostapd.8
index 104276f59d2..ab614cd4ed5 100644
--- a/usr.sbin/hostapd/hostapd.8
+++ b/usr.sbin/hostapd/hostapd.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: hostapd.8,v 1.4 2005/04/13 19:06:11 deraadt Exp $
+.\" $OpenBSD: hostapd.8,v 1.5 2005/04/13 19:56:44 jmc Exp $
 .\"
 .\" Copyright (c) 2004, 2005 Reyk Floeter <reyk@vantronix.net>
 .\"
@@ -22,7 +22,7 @@
 .Nd Host Access Point daemon
 .Sh SYNOPSIS
 .Nm hostapd
-.Op Fl dvb
+.Op Fl bdv
 .Op Fl a Ar interface
 .Oo Xo
 .Fl D Ar macro Ns = Ns Ar value Oc
@@ -33,35 +33,32 @@
 .Nm
 is an daemon which allows communication between different 802.11
 wireless access points running in
-.Pa Host AP
+.Em Host AP
 mode.
 .Pp
 .Nm
 implements the Inter Access Points Protocol (IAPP).
-It's purpose is to exchange station association updates between access
+Its purpose is to exchange station association updates between access
 points in large wireless networks.
 IAPP has been designed to speed up roaming between different access
-points in the same
-.Pa BSS .
-IAPP is described in the
-.Pa IEEE 802.11f
-standard.
+points in the same Extended Service Set (ESS).
+IAPP is described in the IEEE 802.11f standard.
 .Pp
 .Nm
-additionally allows to monitor and to log stations associations on a
+additionally allows the monitoring and logging of station associations on a
 non-hostap host which is receiving IAPP messages.
 .Pp
 .Nm
 uses two network interfaces as options on startup.
-The first interface
-.Pa ( Fl a Ar interface )
-is used to access the
-.Pa Host AP ,
-which is a wireless interface running in Host AP mode. Please use
-.Xr ifconfig 8
-to enable Host AP mode. The second interface
-.Pa ( Fl i Ar interface )
-is used to communicate with other
+The first interface,
+specified using the
+.Fl a
+flag,
+is used to access the Host AP,
+which is a wireless interface running in Host AP mode.
+Host AP mode can be enabled using
+.Xr ifconfig 8 .
+The second interface is used to communicate with other
 .Nm
 in the same broadcast domain or multicast group.
 Usually a wired interface is used to communicate with other
@@ -70,24 +67,18 @@ Usually a wired interface is used to communicate with other
 The
 .Nm
 will send an
-.Pa ADD.notify
-IAPP message if a new station has been associated successfully to the
-.Pa Host AP .
+.Em ADD.notify
+IAPP message if a new station has been associated successfully to the Host AP.
 If the
 .Nm
-receives
-.Pa ADD.notify
-messages it will request the
-.Pa Host AP
-to remove a station which has been associated to another access point.
+receives ADD.notify messages it will request the Host AP
+remove a station which has been associated to another access point.
 .Pp
 The options are as follows:
 .Bl -tag -width Ds
 .It Fl a Ar interface
-Specify the 802.11 wireless network interface running in
-.Pa Host AP
-mode.
-This this option could be omitted to use the
+Specify the 802.11 wireless network interface running in Host AP mode.
+This option could be omitted to use the
 .Nm
 to log received
 .Pa IAPP
@@ -133,23 +124,10 @@ configuration file
 .Xr hostapd.conf 5 ,
 .Xr ifconfig 8
 .Rs
-.%R IEEE 802.11F
+.%R IEEE 802.11f
 .%T Inter Access Point Protocol
 .%D March 2001
 .Re
-.Sh CAVEATS
-.Nm
-depends on drivers using the
-.Pa net80211
-kernel wireless layer with support of
-.Pa Host AP mode.
-For traditional reasons,
-the
-.Xr wi 4
-driver still uses it's own Host AP code in
-.Pa if_wi_hostap
-which is not supported by
-.Nm .
 .Sh HISTORY
 The
 .Nm
@@ -161,3 +139,14 @@ The
 .Nm
 program was written by
 .An Reyk Floeter Aq reyk@openbsd.org .
+.Sh CAVEATS
+.Nm
+depends on drivers using the net80211
+kernel wireless layer with support of Host AP mode.
+For traditional reasons,
+the
+.Xr wi 4
+driver still uses its own Host AP code in
+.Fn if_wi_hostap ,
+which is not supported by
+.Nm .