xref: /dragonfly/share/man/man4/wi.4 (revision 8e1c6f81)
1.\" Copyright (c) 1997, 1998, 1999
2.\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by Bill Paul.
15.\" 4. Neither the name of the author nor the names of any co-contributors
16.\"    may be used to endorse or promote products derived from this software
17.\"   without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
29.\" THE POSSIBILITY OF SUCH DAMAGE.
30.\"
31.\" $FreeBSD: src/share/man/man4/wi.4,v 1.9.4.12 2003/03/03 18:59:15 trhodes Exp $
32.\" $DragonFly: src/share/man/man4/wi.4,v 1.12 2008/07/26 15:52:39 swildner Exp $
33.\"	$OpenBSD: wi.4tbl,v 1.14 2002/04/29 19:53:50 jsyn Exp $
34.\"
35.Dd May 2, 2002
36.Dt WI 4
37.Os
38.Sh NAME
39.Nm wi
40.Nd "WaveLAN/IEEE, PRISM-II and Spectrum24 802.11DS wireless network driver"
41.Sh SYNOPSIS
42.Cd "device wi"
43.Cd "device wlan"
44.Sh DESCRIPTION
45The
46.Nm
47driver provides support for wireless network adapters based around
48the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, and Symbol
49Spectrum24 chipsets.
50All four chipsets provide a similar interface to the driver.
51.Pp
52All host/device interaction is via programmed I/O.
53Supported features include 802.11 and 802.3 frames, power management, BSS,
54IBSS, WDS and old-style Lucent ad-hoc operation modes.
55Cards based on the Intersil PRISM-II and PRISM-2.5 chips also support a
56host-based access point mode which allows a card to act as a normal access
57point (with some assistance from the
58.Nm
59driver).
60The Lucent Hermes and Symbol Spectrum24 chipsets do not contain this
61functionality.
62PRISM-II and PRISM-2.5 chips do not support the WDS functionality.
63.Pp
64The
65.Nm
66driver encapsulates all IP and ARP traffic as 802.11 frames, however
67it can receive either 802.11 or 802.3 frames.
68Transmit speed is selectable between 1Mbps fixed, 2Mbps fixed, 2Mbps
69with auto fallback, 5.5Mbps, 8Mbps, or 11Mbps depending on your hardware.
70The Lucent WaveLAN/IEEE Silver and Gold cards as well as the Intersil
71and Symbol cards have support for WEP encryption.
72The WaveLAN Gold as well as newer Intersil and Symbol cards support
73104bit keys, the others only accept 40bit keys.
74The Lucent WaveLAN/IEEE Bronze cards do not support WEP at all.
75To enable encryption, use
76.Xr ifconfig 8
77as shown below.
78.Pp
79By default, the
80.Nm
81driver configures the card for BSS operation (aka infrastructure
82mode).
83This mode requires the use of an access point (base station).
84.Pp
85The
86.Nm
87driver also supports a point-to-point mode where the ssid is
88ignored and stations can communicate amongst themselves without the
89aid of an access point.
90Note that there are two possible point-to-point modes.
91One mode, referred to as
92.Dq "ad-hoc demo mode" ,
93or
94.Dq "legacy Lucent ad-hoc mode" ,
95predates the IEEE 802.11 specification and so may not interoperate
96with cards from different vendors.
97The standardized point-to-point mode, is called IBSS (or confusingly
98just ad-hoc mode), but is not supported by cards with very old
99firmware revisions.
100If your cards supports IBSS mode, it is recommended that you use it in
101preference to the
102.Dq "ad-hoc demo mode"
103in new installations.
104.Pp
105Cards based on the Intersil PRISM-II and PRISM-2.5 chips also
106have a host-based access point mode which allows the card to
107act as an access point (base station).
108Access points are different than operating in IBSS mode.
109They operate in BSS mode.
110They allow for easier roaming and bridge all ethernet traffic such
111that machines connected via an access point appear to be on the local
112ethernet segment.
113.Pp
114For more information on configuring this device, see
115.Xr ifconfig 8 .
116The
117.Nm
118driver supports
119.Xr polling 4 .
120.Pp
121Cards supported by the
122.Nm
123driver come in a variety of packages, though the most common
124are of the PCMCIA type.
125In many cases, the PCI version of a wireless card is simply
126a PCMCIA card bundled with a PCI adapter.
127The PCI adapters come in two flavors: true PCMCIA bridges and
128dumb PCMCIA bridges.
129A true PCMCIA bridge (such as those sold by Lucent) will attach
130as a real PCMCIA controller.
131The wireless card will then attach to the PCMCIA bus.
132Wireless cards in PCMCIA slots may be inserted and ejected on the fly.
133.Pp
134A dumb bridge, on the other hand, does not show up as a true PCMCIA bus.
135The wireless card will simply appear to the host as a normal PCI
136device and will not require any PCMCIA support.
137Cards in this type of adapter should only be removed when the
138machine is powered down.
139.Pp
140The following cards are among those supported by the
141.Nm
142driver:
143.Pp
144.Bl -column -compact "Linksys Instant Wireless WPC11 2.5" "Spectrum24" "PCI or PCMCIA"
145.Em "Card	Chip	Bus"
1463Com AirConnect 3CRWE737A	Spectrum24	PCMCIA
1473Com AirConnect 3CRWE777A	Prism-II	PCI
148ACTIONTEC HWC01170	Prism-2.5	PCMCIA
149Addtron AWP-100	Prism-II	PCMCIA
150Adtec Adlink/340C	Prism-II	PCMCIA
151Agere Orinoco	Hermes	PCMCIA
152Avaya Wireless	Prism-II	PCMCIA
153Blue Concentric Circle WL-379F	PRISM-II	CF
154BreezeNet Wireless	Prism-II	PCMCIA
155Buffalo WLI-PCM-S11	Prism-II	PCMCIA
156Buffalo WLI-PCM-L11G	Hermes	PCMCIA
157Buffalo WLI-CF-S11G	Prism-II	CF
158Cabletron RoamAbout	Hermes	PCMCIA
159Compaq Agency NC5004	Prism-II	PCMCIA
160Compaq WL100	Prism-II	PCMCIA
161Compaq WL110	Prism-II	PCMCIA
162Compaq WL200	Prism-II	PCMCIA
163Contec FLEXLAN/FX-DS110-PCC	Prism-II	PCMCIA
164Corega PCC-11	Prism-II	PCMCIA
165Corega PCCA-11	Prism-II	PCMCIA
166Corega PCCB-11	Prism-II	PCMCIA
167Corega CGWLPCIA11	Prism-II	PCI
168Dell TrueMobile 1150	Hermes	PCMCIA
169Dlink DWL520	Prism-2.5	PCI
170Dlink DWL650	Prism-2.5	PCMCIA
171ELSA XI300	Prism-II	PCMCIA
172ELSA XI800	Prism-II	CF
173EMTAC A2424i	Prism-II	PCMCIA
174Ericsson Wireless LAN CARD C11	Spectrum24	PCMCIA
175Farallon Skyline	Prism-II	PCMCIA
176Gemtek WL-311	Prism-2.5	PCMCIA
177Hawking Technology WE110P	Prism-2.5	PCMCIA
178Home Wireless Networks	Prism-II	PCMCIA
179IBM High Rate Wireless	Hermes	PCMCIA
180ICOM SL-1100	Prism-II	PCMCIA
181I-O DATA WN-B11/PCM	Prism-II	PCMCIA
182Intel PRO/Wireless 2011	Spectrum24	PCMCIA
183Intersil Prism II	Prism-II	PCMCIA
184Intersil Mini-PCI	Prism-2.5	PCI
185Linksys Instant Wireless WPC11	Prism-II	PCMCIA
186Linksys Instant Wireless WPC11 2.5	Prism-2.5	PCMCIA
187Linksys Instant Wireless WPC11 3.0	Prism-3	PCMCIA
188Lucent WaveLAN	Hermes	PCMCIA
189Melco Airconnect	Prism-II	PCMCIA
190NANOSPEED ROOT-RZ2000	Prism-II	PCMCIA
191NDC/Sohoware NCP130	Prism-II	PCI
192NEC CMZ-RT-WP	Prism-II	PCMCIA
193NEC PK-WL001	Prism-II	PCMCIA
194NEC PC-WL/11C	PRISM-II	PCMCIA
195Netgear MA401	Prism-II	PCMCIA
196NTT-ME 11Mbps Wireless LAN	Prism-II	PCMCIA
197Planex GeoWave/GW-NS110	Prism-II	PCMCIA
198Planex GW-NS11H	Prism-II	PCMCIA
199Proxim Harmony	Prism-II	PCMCIA
200Proxim RangeLAN-DS	Prism-II	PCMCIA
201Samsung MagicLAN SWL-2000N	Prism-II	PCMCIA
202SMC 2602 EZ Connect (3.3V)	Prism-II	PCI or PCMCIA
203SMC 2632 EZ Connect	Prism-II	PCMCIA
204Socket Low Power WLAN-CF	Prism-II	CF
205Sony PCWA-C100	Lucent	PCMCIA
206Symbol Spectrum24	Spectrum24	PCMCIA
207Symbol LA-4100	Spectrum24	CF
208TDK LAK-CD011WL	Prism-II	PCMCIA
209Toshiba Wireless LAN Card	Prism-II	PCMCIA
210U.S. Robotics Wireless Card 2410	Prism-II	PCMCIA
211.El
212.Pp
213Several vendors sell PCI adapters built around the PLX Technology 9050
214or 9052 chip.
215The following such adapters are supported or expected to work:
216.Pp
217.Bl -tag -compact
218.It 3Com AirConnect 3CRWE777A (3.3V)
219.It Belkin F5D6000 (a rebadged WL11000P)
220.It Eumitcom WL11000P
221.It Global Sun Technology GL24110P (untested)
222.It Global Sun Technology GL24110P02
223.It LinkSys WDT11 (a rebadged GL24110P02)
224.It Netgear MA301
225.It US Robotics 2415 (rebadged WL11000P)
226.El
227.Sh EXAMPLES
228Join an existing BSS network (ie: connect to an access point):
229.Pp
230.Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00"
231.Pp
232Join a specific BSS network with network name
233.Dq Li my_net :
234.Pp
235.Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
236.Pp
237Join a specific BSS network with WEP encryption:
238.Bd -literal -offset indent
239ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
240	wepmode on wepkey 0x8736639624
241.Ed
242.Pp
243Join a Lucent legacy demo ad-hoc network with network name
244.Dq Li my_net :
245.Bd -literal -offset indent
246ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
247	mediaopt adhoc
248.Ed
249.Pp
250Create an IBSS network with network name
251.Dq Li my_net :
252.Bd -literal -offset indent
253ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
254	mediaopt ibss-master
255.Ed
256.Pp
257.Em Note :
258The infrastructure for
259.Cm mediaopt ibss-master
260has not been committed yet.
261.Pp
262Join an IBSS network with network name
263.Dq Li my_net :
264.Bd -literal -offset indent
265ifconfig wi0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e
266	mediaopt ibss
267.Ed
268.Pp
269.Em Note :
270The infrastructure for
271.Cm mediaopt ibss
272has not been committed yet.
273.Pp
274Create a host-based access point (Prism only):
275.Bd -literal -offset indent
276ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
277	mediaopt hostap
278.Ed
279.Pp
280Create a host-based access point with WEP enabled (Prism only):
281.Bd -literal -offset indent
282ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
283	wepmode on wepkey 0x1234567890 mediaopt hostap
284.Ed
285.Pp
286Create a host-based wireless bridge to fxp0 (Prism only):
287.Bd -literal -offset indent
288Add BRIDGE to the kernel config.
289ifconfig wi0 inet up ssid my_ap mediaopt hostap
290sysctl net.link.ether.bridge=1
291sysctl net.link.ether.bridge_cfg="wi0 fxp0"
292sysctl net.inet.ip.forwarding=1
293.Ed
294.Pp
295This will give you approximately the same functionality as an access
296point.
297.Sh DIAGNOSTICS
298.Bl -diag
299.It "wi%d: init failed"
300The WaveLAN card failed to come ready after an initialization command
301was issued.
302.It "wi%d: failed to allocate %d bytes on NIC"
303The driver was unable to allocate memory for transmit frames in the
304NIC's on-board RAM.
305.It "wi%d: device timeout"
306The WaveLAN failed to generate an interrupt to acknowledge a transmit
307command.
308.El
309.Sh SEE ALSO
310.Xr an 4 ,
311.Xr arp 4 ,
312.Xr ifmedia 4 ,
313.Xr netintro 4 ,
314.Xr polling 4 ,
315.Xr hostapd 8 ,
316.Xr ifconfig 8 ,
317.Xr wpa_supplicant 8
318.Rs
319.%T HCF Light programming specification
320.%O http://web.archive.org/web/*/http://www.wavelan.com
321.Re
322.Sh HISTORY
323The
324.Nm
325device driver first appeared in
326.Fx 3.0 .
327.Sh AUTHORS
328The
329.Nm
330driver was written by
331.An Bill Paul Aq wpaul@ctr.columbia.edu .
332This man page comes from
333.Ox .
334.Sh CAVEATS
335Different regulatory domains have different default channels for adhoc
336mode.
337See
338.Xr ifconfig 8
339for information on how to change the channel.
340.Pp
341The Intersil Prism family of chips' host-based access point mode has
342bugs for station firmware versions prior to 0.8.3.
343The driver currently precludes hostap functionality older station
344firmware.
345The best version of the station firmware for the Prism family of chips
346seems to be 1.4.9.
347Some users of Prism-II and 2.5 based cards report that station firmware
348version 1.3.4 works better for them in hostap than 1.4.9.
349Older versions of the Prism station firmware have a number of issues
350with hostap mode.
351The IBSS/adhoc mode appears to work well on station firmware 1.3.1 and
352later.
353The IBSS/adhoc mode appears to have problems for some people with
354older versions of station firmware.
355.Pp
356Lucent cards prior to firmware version 6.0.4 do not support IBSS
357mode.
358These cards support only the pre 802.11 mode known as
359.Dq "demo ad-hoc mode"
360which does not interoperate with stations in IBSS mode.
361.Sh BUGS
362Not all the new messages are documented here, and many of them are
363indications of transient errors that are not indications of serious
364problems.
365.Pp
366WL200 PCI wireless cards are based on a Cirrus Logic CL-PD6729 bridge
367chips glued to an intersil prism-II pcmcia chipset w/o the PC Card
368form factor being present.
369These chips are special and require special care to use properly.
370One must set
371.Va hw.pcic.pd6729_intr_path Ns = Ns Qq Li 2
372in
373.Pa /boot/loader.conf .
374This tells the pccard system to use PCI interrupts for this odd beast.
375It is not possible to know automatically which kind of interrupts to use.
376OLDCARD devices (pcic and card) support this device.
377