summaryrefslogtreecommitdiffstats
path: root/share/man/man4/wi.4
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man4/wi.4')
-rw-r--r--share/man/man4/wi.4178
1 files changed, 61 insertions, 117 deletions
diff --git a/share/man/man4/wi.4 b/share/man/man4/wi.4
index 2e35536..5a08527 100644
--- a/share/man/man4/wi.4
+++ b/share/man/man4/wi.4
@@ -31,12 +31,12 @@
.\" $FreeBSD$
.\" $OpenBSD: wi.4tbl,v 1.14 2002/04/29 19:53:50 jsyn Exp $
.\"
-.Dd July 16, 2005
+.Dd April 13, 2008
.Dt WI 4
.Os
.Sh NAME
.Nm wi
-.Nd "Lucent Hermes, Intersil PRISM and Spectrum24 IEEE 802.11 driver"
+.Nd "Lucent Hermes, and Intersil PRISM IEEE 802.11 driver"
.Sh SYNOPSIS
To compile this driver into the kernel,
place the following lines in your
@@ -55,74 +55,30 @@ if_wi_load="YES"
.Sh DESCRIPTION
The
.Nm
-driver provides support for wireless network adapters based around
-the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil
-Prism-3, and Symbol Spectrum24 chipsets.
-All five chipsets provide a similar interface to the driver.
-.Pp
-Supported features include 802.11 and 802.3 frames, power management, BSS,
-IBSS, WDS and old-style Lucent ad-hoc operation modes.
-Cards based on the Intersil PRISM chips also support a host-based
-access point mode which allows a card to act as a normal access point
-(with some assistance from the
-.Nm
-driver).
-The Lucent Hermes and Symbol Spectrum24 chipsets do not contain this
-functionality.
-The PRISM family of chips do not support the WDS functionality.
+driver provides support for 802.11b wireless network adapters based around
+the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, and Intersil
+Prism-3 chipsets.
+All chipsets provide a similar interface to the driver.
+Only the Intersil chipsets support access point operation.
+Functionality, such as WPA support, depends on the specific version
+of the firmware used.
All host/device interaction is via programmed I/O, even on those cards
that support a DMA interface.
.Pp
-The
-.Nm
-driver encapsulates all IP and ARP traffic as 802.11 frames, however
-it can receive either 802.11 or 802.3 frames.
-Transmit speed is selectable between 1Mbps, 2Mbps, 5.5 Mbps and 11Mbps
-depending on your hardware.
-Most hardware supports 11Mbps where the signal quality allows, but
-falls back to slower speeds when it does not.
-Except for the Lucent WaveLAN Bronze cards, all cards supported by the
-.Nm
-driver support WEP for encryption.
-To enable encryption, use
-.Xr ifconfig 8
-as shown below.
-.Pp
-By default, the
-.Nm
-driver configures the card for BSS operation (aka infrastructure
-mode).
-This mode requires the use of an access point (base station).
+For more information on configuring this device, see
+.Xr ifconfig 8 .
.Pp
-The
.Nm
-driver also supports a point-to-point mode
-where stations can communicate amongst themselves without the
-aid of an access point.
-Note that there are two possible point-to-point modes.
-One mode, referred to as
-.Dq "ad-hoc demo mode" ,
-or
-.Dq "legacy Lucent ad-hoc mode" ,
-predates the IEEE 802.11 specification and so may not interoperate
-with cards from different vendors.
-The standardized point-to-point mode is called IBSS (or confusingly
-just ad-hoc mode), but is not supported by cards with very old
-firmware revisions.
-If your cards supports IBSS mode, it is recommended that you use it in
-preference to the
-.Dq "ad-hoc demo mode"
-in new installations.
-.Pp
-Cards supported by the driver based on the Intersil PRISM family of chips also
-have a host-based access point mode which allows the card to
-act as an access point (base station).
-Access points are different than operating in IBSS mode.
-They operate in BSS mode.
-They allow for easier roaming and bridge all Ethernet traffic such
-that machines connected via an access point appear to be on the local
-Ethernet segment.
-.Pp
+supports
+.Cm station ,
+.Cm adhoc ,
+.Cm adhoc-demo ,
+.Cm hostap ,
+and
+.Cm monitor
+mode operation.
+Only one
+virtual interface may be configured at a time.
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
@@ -151,7 +107,6 @@ driver:
.Pp
.Bl -column -compact "Linksys Instant Wireless WPC11 2.5" "Spectrum24" "PCI or PCMCIA"
.Em "Card Chip Bus"
-3Com AirConnect 3CRWE737A Spectrum24 PCMCIA
3Com AirConnect 3CRWE777A Prism-II PCI
Accton airDirect WN3301 PCMCIA
ACTIONTEC HWC01170 Prism-2.5 PCMCIA
@@ -191,7 +146,6 @@ ELSA MC-11 PCMCIA
ELSA XI300 Prism-II PCMCIA
ELSA XI800 Prism-II CF
EMTAC A2424i Prism-II PCMCIA
-Ericsson Wireless LAN CARD C11 Spectrum24 PCMCIA
Farallon Skyline Prism-II PCMCIA
Gemtek WL-311 Prism-2.5 PCMCIA
Hawking Technology WE110P Prism-2.5 PCMCIA
@@ -199,7 +153,6 @@ Home Wireless Networks Prism-II PCMCIA
IBM High Rate Wireless Hermes PCMCIA
ICOM SL-1100 Prism-II PCMCIA
I-O DATA WN-B11/PCM Prism-II PCMCIA
-Intel PRO/Wireless 2011 Spectrum24 PCMCIA
Intersil Prism II Prism-II PCMCIA
Intersil Mini-PCI Prism-2.5 PCI
Intersil ISL37100P Prism-3 PCMCIA
@@ -240,8 +193,6 @@ SMC 2632 EZ Connect Prism-II PCMCIA
Socket Low Power WLAN-CF Prism-II CF
Sony PCWA-C100 Lucent PCMCIA
Sony PEGA-WL110 Prism-2.5 PCMCIA
-Symbol Spectrum24 Spectrum24 PCMCIA
-Symbol LA-4100 Spectrum24 CF
TDK LAK-CD011WL Prism-II PCMCIA
Toshiba Wireless LAN Card Prism-II PCMCIA
U.S.\& Robotics Wireless Card 2410 Prism-II PCMCIA
@@ -284,52 +235,53 @@ DLink DWL520
.Sh EXAMPLES
Join an existing BSS network (ie: connect to an access point):
.Pp
-.Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev wi0 inet 192.168.0.20 \e
+ netmask 0xffffff00
+.Ed
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev wi0 inet 192.168.0.20 \e
+ netmask 0xffffff00 ssid my_net
.Pp
Join a specific BSS network with WEP encryption:
.Bd -literal -offset indent
-ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x8736639624
+ifconfig wlan create wlandev wi0 inet 192.168.0.20 \e
+ netmask 0xffffff00 ssid my_net \e
+ wepmode on wepkey 0x8736639624 weptxkey 1
.Ed
.Pp
Join a Lucent legacy demo ad-hoc network with network name
.Dq Li my_net :
.Bd -literal -offset indent
-ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- media DS/11Mbps mediaopt adhoc,link0
+ifconfig wlan create wlandev wi0 wlanmode ahdemo \e
+ inet 192.168.0.20 netmask 0xffffff00 ssid my_net
.Ed
.Pp
Join/create an IBSS network with network name
.Dq Li my_net :
.Bd -literal -offset indent
-ifconfig wi0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e
- media DS/11Mbps mediaopt adhoc
+ifconfig wlan create wlandev wi0 wlanmode adhoc wi0 \e
+ inet 192.168.0.22 netmask 0xffffff00 ssid my_net
.Ed
.Pp
Create a host-based access point (Prism only):
.Bd -literal -offset indent
-ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
- media DS/11Mbps mediaopt hostap
+ifconfig wlan create wlandev wi0 wlanmode hostap \e
+ inet 192.168.0.10 netmask 0xffffff00 ssid my_ap
.Ed
.Pp
-Create a host-based access point with WEP enabled (Prism only):
+Create a host-based access point with WEP enabled (Prism only)
+and plumb it into bridge to fxp0:
.Bd -literal -offset indent
-ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
- wepmode on wepkey 0x1234567890 media DS/11Mbps \e
- mediaopt hostap
-.Ed
-.Pp
-Create a host-based wireless bridge to fxp0 (Prism only):
-.Bd -literal -offset indent
-ifconfig wi0 inet up ssid my_ap media DS/11Mbps mediaopt hostap
-sysctl net.inet.ip.check_interface=0
+ifconfig wlan0 create wlandev wi0 wlanmode hostap \e
+ inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
+ wepmode on wepkey 0x1234567890 weptxkey 1
ifconfig bridge0 create
-ifconfig bridge0 addm wi0 addm fxp0 up
+ifconfig bridge0 addm wlan0 addm fxp0 up
.Ed
.Pp
This will give you the same functionality as an access point.
@@ -347,16 +299,18 @@ The WaveLAN card failed to generate an interrupt to acknowledge a transmit
command.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr an 4 ,
-.Xr arp 4 ,
-.Xr ath 4 ,
-.Xr netintro 4 ,
+.Xr intro 4 ,
.Xr pccard 4 ,
.Xr pccbb 4 ,
.Xr pcic 4 ,
.Xr wlan 4 ,
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr wlan_xauth 4 ,
+.Xr hostapd 8 ,
.Xr ifconfig 8 ,
+.Xr wpa_supplicant 8 .
.Rs
.%T HCF Light programming specification
.%O http://www.wavelan.com
@@ -367,24 +321,21 @@ The
device driver first appeared in
.Fx 3.0 .
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Bill Paul Aq wpaul@ctr.columbia.edu .
This man page comes from
.Ox .
.Sh CAVEATS
-Different regulatory domains have different default channels for adhoc
-mode.
-See
-.Xr ifconfig 8
-for information on how to change the channel.
-The Intersil Prism family of chips' host-based access point mode has
-bugs for station firmware versions prior to 0.8.3.
-The driver currently precludes hostap functionality with older station
-firmware.
-The best version of the station firmware for the Prism family of chips
-seems to be 1.4.9.
+The driver will reject devices with old firmware to
+avoid dealing with numerous defects.
+Unfortunately the driver does not support downloading new firmware
+to the card so if new firmware is needed users will have to boot
+a different system to accomplish this.
+.Pp
+Intersil Prism cards must have firmware versions 0.8.0 or later and
+version 1.7.0 or later are required to support functionality such as WPA.
Some users of Prism-II and 2.5 based cards report that station firmware
version 1.3.4 works better for them in hostap than 1.4.9.
Older versions of the Prism station firmware have a number of issues
@@ -394,15 +345,8 @@ later.
The IBSS/adhoc mode appears to have problems for some people with
older versions of station firmware.
.Pp
-Lucent cards prior to firmware version 6.0.6 do not support IBSS
-mode.
-These cards support only the pre-802.11 mode known as
-.Dq "demo ad-hoc mode"
-which does not interoperate with stations in IBSS mode.
-.Pp
-Prism cards prior to version 0.8.0 do not support IBSS mode.
-.Pp
-Symbol cards prior to version 2.50.00 do not support IBSS mode.
+Lucent cards prior to firmware version 6.0.6 do not implement IBSS
+mode and are not supported.
.Sh BUGS
Not all the new messages are documented here, and many of them are
indications of transient errors that are not indications of serious
OpenPOWER on IntegriCloud