1.\" $OpenBSD: atw.4,v 1.30 2009/09/02 07:00:24 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: September 2 2009 $ 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 137.Xr hostname.if 5 138example configures atw0 to join whatever network is available on boot, 139using WEP key 140.Dq 0x1deadbeef1 , 141channel 11, obtaining an IP address using DHCP: 142.Bd -literal -offset indent 143dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11 144.Ed 145.Pp 146Configure atw0 for WEP, using hex key 147.Dq 0x1deadbeef1 : 148.Bd -literal -offset indent 149# ifconfig atw0 nwkey 0x1deadbeef1 150.Ed 151.Pp 152Return atw0 to its default settings: 153.Bd -literal -offset indent 154# ifconfig atw0 -bssid -chan media autoselect \e 155 nwid "" -nwkey 156.Ed 157.Pp 158Join an existing BSS network, 159.Dq my_net : 160.Bd -literal -offset indent 161# ifconfig atw0 192.168.1.1 netmask 0xffffff00 nwid my_net 162.Ed 163.Sh DIAGNOSTICS 164.Bl -diag 165.It "atw0: failed to tune channel %d" 166The driver failed to tune the radio to a new channel. 167The radio remains tuned to the old channel. 168.It "atw0: atw_si4136_write wrote %08x, SYNCTL still busy" 169The driver waited 100ms without seeing an indication that the 170ADM8211 had finished writing a register on the Si4126 RF/IF 171synthesizer. 172.It "atw0: device timeout" 173The ADM8211 failed to generate an interrupt to acknowledge a transmit 174command. 175.El 176.Sh SEE ALSO 177.Xr arp 4 , 178.Xr cardbus 4 , 179.Xr ifmedia 4 , 180.Xr intro 4 , 181.Xr netintro 4 , 182.Xr pci 4 , 183.Xr hostname.if 5 , 184.Xr ifconfig 8 185.Rs 186.%T ADMtek 187.%O http://www.admtek.com.tw 188.Re 189.Rs 190.%T Silicon Laboratories 191.%O http://www.silabs.com 192.Re 193.Rs 194.%T RF Micro Devices 195.%O http://www.rfmd.com 196.Re 197.Sh HISTORY 198The 199.Nm 200device driver first appeared in 201.Ox 3.6 . 202.Sh AUTHORS 203.An -nosplit 204The 205.Nm 206driver was written by 207.An David Young 208.Aq dyoung@NetBSD.org . 209For features which the ADM8211 has in common with the DECchip 21x4x, 210code was liberally borrowed from the 211.Nx 212tlp driver by 213.An Jason Thorpe 214.Aq thorpej@NetBSD.org . 215.Sh BUGS 216The author does not fully understand what processing the duration 217fields for the PLCP header and the 802.11 header undergo before 218they are applied to a transmitted frame. 219If the duration fields in transmitted frames are incorrect, 220network performance may suffer. 221.Pp 222The driver does not provide rate control when the media type is 223set to autoselect. 224.Pp 225The driver will sometimes complain that it cannot re-tune the radio 226because the transmit process has not gone idle. 227The author is investigating. 228.Pp 229Many features are still missing, especially WEP decryption and 230802.11 power-saving. 231.Pp 232The ad-hoc mode has not been rigorously tested. 233IBSSs with the same SSID may not coalesce, but this should not 234matter for most applications. 235.Pp 236The driver is untested in the ad-hoc demo mode of Lucent WaveLAN 237cards. 238.Pp 239The ADM8211 supports 802.11 power-saving; however, 240.Nm 241does not support it yet. 242For time-bounded service, the ADM8211 will interoperate with an 243access point which implements the 802.11 Point Coordination Function; 244however, this is also not supported. 245.Pp 246Combinations of an ADM8211 with either an Intersil or a Marvell RF 247front-end are not supported. 248.Pp 249.Nm 250contains incomplete support for the ADM8211's WEP encryption/decryption 251engine. 252.Nm 253does not yet support hardware WEP decryption; however, it will use 254the ADM8211's crypto engine to encrypt transmitted frames. 255Documentation from ADMtek claims that, in addition to the 4 104-bit 256shared WEP keys, the ADM8211 will store WEP key pairs for up to 20 257peers. 258The documentation provides no details, hence 259.Nm 260does not support the 20 key-pairs. 261