xref: /netbsd/share/man/man4/an.4 (revision bf9ec67e)
1.\"     $NetBSD: an.4,v 1.8 2001/09/11 17:39:01 wiz Exp $
2.\"
3.\" Copyright (c) 1997, 1998, 1999
4.\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by Bill Paul.
17.\" 4. Neither the name of the author nor the names of any co-contributors
18.\"    may be used to endorse or promote products derived from this software
19.\"   without specific prior written permission.
20.\"
21.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
25.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
26.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
29.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
31.\" THE POSSIBILITY OF SUCH DAMAGE.
32.\"
33.\" $FreeBSD: src/share/man/man4/an.4,v 1.6 2000/11/17 11:43:59 ru Exp $
34.\"
35.Dd December 13, 2000
36.Dt AN 4
37.Os
38.Sh NAME
39.Nm an
40.Nd
41Aironet 4500/4800 and Cisco 340/350 series wireless network driver
42.Sh SYNOPSIS
43.Cd "an* at pcmcia? function ?"
44.Cd "an* at pci? dev ? function ?"
45.Cd "an* at isapnp?"
46.Sh DESCRIPTION
47The
48.Nm
49driver provides support for Aironet Communications 4500/4800
50and Cisco Aironet 340/350 series
51wireless network adapters.
52This includes the ISA, PCI and PCMCIA
53varieties.
54The 4500 series adapters operate at 1 and 2Mbps while
55the 4800 series and 340/350 series can operate at 1, 2, 5.5 and 11Mbps.
56The ISA, PCI
57and PCMCIA devices are all based on the same core PCMCIA modules
58and all have the same programming interface, however unlike the
59Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the
60host as normal ISA and PCI devices and do not require any PCMCIA
61support.
62.Pp
63The PCMCIA Aironet cards require PCMCIA support.
64ISA cards can either be configured to use ISA Plug and Play
65or to use a particular I/O address and IRQ
66by properly setting the DIP switches on the board.
67(The default
68switch setting is for plug and play.)
69The
70.Nm
71driver has Plug and Play support and will work in either configuration,
72however when using a hard-wired I/O address and IRQ, the driver
73configuration and the NIC's switch settings must agree.
74PCI cards
75require no switch settings of any kind and will be automatically
76probed and attached.
77.Pp
78All host/device interaction with the Aironet cards is via programmed I/O.
79The Aironet devices support 802.11 and 802.3 frames, power management,
80BSS (infrastructure) and IBSS (ad-hoc) operation modes.
81The
82.Nm
83driver encapsulates all IP and ARP traffic as 802.11 frames, however
84it can receive either 802.11 or 802.3 frames.
85Transmit speed is
86selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or
87"auto" (the NIC automatically chooses the best speed).
88.Pp
89By default, the
90.Nm
91driver configures the Aironet card to join an access point with an SSID
92of null string.
93For adhoc mode, in which
94stations can communicate among each other without the aid of an access
95point, the driver must be set using
96.Xr ifconfig 8 .
97.Pp
98For more information on configuring this device, see
99.Xr ifconfig 8
100and
101.Xr ifmedia 4 .
102.Sh HARDWARE
103Cards supported by the
104.Nm
105driver include:
106.Pp
107.Bl -item -offset indent
108.It
109Aironet 4500 Series
110.It
111Aironet 4800 Series
112.It
113Cisco Aironet 340 Series
114.It
115Cisco Aironet 350 Series
116.Sh DIAGNOSTICS
117.Bl -diag
118.It "an%d: init failed"
119The Aironet card failed to come ready after an initialization command was
120issued.
121.It "an%d: failed to allocate %d bytes on NIC"
122The driver was unable to allocate memory for transmit frames in the
123NIC's on-board RAM.
124.It "an%d: device timeout"
125The Aironet card failed to generate an interrupt to acknowledge a transmit
126command.
127.El
128.Sh SEE ALSO
129.Xr arp 4 ,
130.Xr ifmedia 4 ,
131.Xr netintro 4 ,
132.Xr ifconfig 8
133.Sh HISTORY
134The
135.Nm
136device driver first appeared in
137.Fx 4.0 ,
138and then in
139.Nx 1.6 .
140.Sh AUTHORS
141The
142.Nm
143driver was written by
144.An Bill Paul Aq wpaul@ee.columbia.edu .
145