xref: /openbsd/share/man/man4/atw.4 (revision 898184e3)
1.\"     $OpenBSD: atw.4,v 1.32 2013/02/14 07:40:42 jmc Exp $
2.\"	$NetBSD: atw.4,v 1.8 2004/06/06 04:05:49 wiz Exp $
3.\"
4.\" Copyright (c) 2003
5.\"	David Young <dyoung@NetBSD.org>. All rights reserved.
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\"    notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\"    notice, this list of conditions and the following disclaimer in the
14.\"    documentation and/or other materials provided with the distribution.
15.\" 3. 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 David Young 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 David Young
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.Dd $Mdocdate: February 14 2013 $
32.Dt ATW 4
33.Os
34.Sh NAME
35.Nm atw
36.Nd ADMtek ADM8211 IEEE 802.11b wireless network device
37.Sh SYNOPSIS
38.Cd "atw* at cardbus?"
39.Cd "atw* at pci?"
40.Sh DESCRIPTION
41The
42.Nm
43driver supports PCI/CardBus 802.11b wireless adapters based on the
44ADMtek ADM8211.
45.Pp
46The ADM8211 is a bus-mastering 802.11 Media Access Controller (MAC)
47which is derived from ADMtek's DEC/Intel 21143 clones (see
48.Xr dc 4
49for more information).
50It supports contention-free traffic (with an 802.11 Point Coordinator).
51The ADM8211 integrates an RF3000 baseband processor (BBP) by RF
52Microdevices.
53.Pp
54In a typical application, the ADM8211 is coupled with an RF front-end
55by RFMD and a Silicon Laboratories Si4126 RF/IF synthesizer.
56.Pp
57With the ADM8211, the division of labor between the host and NIC
58is different than with firmware-based NICs such as
59.Xr an 4
60and
61.Xr wi 4 .
62The ADM8211 is still responsible for real-time 802.11 functions
63such as sending ACK/RTS/CTS/ATIM frames, sending beacons, and
64answering CF polls from the access point, but the host takes
65responsibility for providing 802.11 functions such as scanning,
66association, and authentication.
67The host is also responsible for programming both the BBP and the
68RF/IF synthesizer.
69.Pp
70These are the modes the
71.Nm
72driver can operate in:
73.Bl -tag -width "IBSS-masterXX"
74.It BSS mode
75Also known as
76.Em infrastructure
77mode, this is used when associating with an access point, through
78which all traffic passes.
79This mode is the default.
80.It IBSS mode
81Also known as
82.Em IEEE ad-hoc
83mode or
84.Em peer-to-peer
85mode.
86This is the standardized method of operating without an access point.
87Stations associate with a service set.
88However, actual connections between stations are peer-to-peer.
89.El
90.Pp
91The
92.Nm
93driver can be configured to use hardware
94Wired Equivalent Privacy (WEP)
95(though see
96.Sx BUGS ,
97below).
98It is strongly recommended that WEP
99not be used as the sole mechanism
100to secure wireless communication,
101due to serious weaknesses in it.
102.Pp
103The
104.Nm
105driver can be configured at runtime with
106.Xr ifconfig 8
107or on boot with
108.Xr hostname.if 5 .
109.Sh HARDWARE
110The
111.Nm
112driver supports PCI and CardBus cards using revisions 0x11 and 0x15
113of the ADM8211 (aka ADM8211A) and revision 0x20 (aka ADM8211B).
114This includes:
115.Pp
116.Bl -tag -width Ds -offset indent -compact
117.It 3Com OfficeConnect 3CRSHPW796 CardBus
118.It Belkin F5D6001 PCI (version 2 only)
119.It Blitz NetWave Point CardBus
120.It D-Link DWL-650 Rev. \&L1 CardBus
121.It D-Link DWL-520 Rev. \&C1 PCI
122.It LanReady WP2000 PCI
123.It SMC 2635W CardBus (version 1 only)
124.It TRENDnet TEW-221PC CardBus
125.It Xterasys XN2511B PCI
126.El
127.Pp
128The
129.Nm
130driver does not yet support cards using revision 0x30 (ADM8211C).
131.\"This includes:
132.\".Pp
133.\".Bl -tag -width Ds -offset indent -compact
134.\".El
135.Sh EXAMPLES
136The following example scans for available networks:
137.Pp
138.Dl # ifconfig atw0 scan
139.Pp
140The following
141.Xr hostname.if 5
142example configures atw0 to join network
143.Dq mynwid ,
144using WEP key
145.Dq mywepkey ,
146obtaining an IP address using DHCP:
147.Bd -literal -offset indent
148nwid mynwid
149nwkey mywepkey
150dhcp
151.Ed
152.Sh DIAGNOSTICS
153.Bl -diag
154.It "atw0: failed to tune channel %d"
155The driver failed to tune the radio to a new channel.
156The radio remains tuned to the old channel.
157.It "atw0: atw_si4136_write wrote %08x, SYNCTL still busy"
158The driver waited 100ms without seeing an indication that the
159ADM8211 had finished writing a register on the Si4126 RF/IF
160synthesizer.
161.It "atw0: device timeout"
162The ADM8211 failed to generate an interrupt to acknowledge a transmit
163command.
164.El
165.Sh SEE ALSO
166.Xr arp 4 ,
167.Xr cardbus 4 ,
168.Xr ifmedia 4 ,
169.Xr intro 4 ,
170.Xr netintro 4 ,
171.Xr pci 4 ,
172.Xr hostname.if 5 ,
173.Xr ifconfig 8
174.Rs
175.%T ADMtek
176.%U http://www.admtek.com.tw
177.Re
178.Rs
179.%T Silicon Laboratories
180.%U http://www.silabs.com
181.Re
182.Rs
183.%T RF Micro Devices
184.%U http://www.rfmd.com
185.Re
186.Sh HISTORY
187The
188.Nm
189device driver first appeared in
190.Ox 3.6 .
191.Sh AUTHORS
192.An -nosplit
193The
194.Nm
195driver was written by
196.An David Young
197.Aq dyoung@NetBSD.org .
198For features which the ADM8211 has in common with the DECchip 21x4x,
199code was liberally borrowed from the
200.Nx
201tlp driver by
202.An Jason Thorpe
203.Aq thorpej@NetBSD.org .
204.Sh BUGS
205The author does not fully understand what processing the duration
206fields for the PLCP header and the 802.11 header undergo before
207they are applied to a transmitted frame.
208If the duration fields in transmitted frames are incorrect,
209network performance may suffer.
210.Pp
211The driver does not provide rate control when the media type is
212set to autoselect.
213.Pp
214The driver will sometimes complain that it cannot re-tune the radio
215because the transmit process has not gone idle.
216The author is investigating.
217.Pp
218Many features are still missing, especially WEP decryption and
219802.11 power-saving.
220.Pp
221The ad-hoc mode has not been rigorously tested.
222IBSSs with the same SSID may not coalesce, but this should not
223matter for most applications.
224.Pp
225The driver is untested in the ad-hoc demo mode of Lucent WaveLAN
226cards.
227.Pp
228The ADM8211 supports 802.11 power-saving; however,
229.Nm
230does not support it yet.
231For time-bounded service, the ADM8211 will interoperate with an
232access point which implements the 802.11 Point Coordination Function;
233however, this is also not supported.
234.Pp
235Combinations of an ADM8211 with either an Intersil or a Marvell RF
236front-end are not supported.
237.Pp
238.Nm
239contains incomplete support for the ADM8211's WEP encryption/decryption
240engine.
241.Nm
242does not yet support hardware WEP decryption; however, it will use
243the ADM8211's crypto engine to encrypt transmitted frames.
244Documentation from ADMtek claims that, in addition to the 4 104-bit
245shared WEP keys, the ADM8211 will store WEP key pairs for up to 20
246peers.
247The documentation provides no details, hence
248.Nm
249does not support the 20 key-pairs.
250