d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3b06401650
freebsd-skq/share/man/man4/wi.4
imp c999bc6458 Try to de-confuse ad-hoc, demo ad-hoc and ibss: 
o Don't ever refer to ad-hoc mode in the raw.  Instead, refer to it as
  demo ad-hoc mode or lucent legacy demo ad-hoc or some variation on this
  theme.
o Talk about point-to-point modes rather than ad-hoc modes.  Use ibss where
  appropriate.
o Fix type IBBS -> IBSS
2002-05-04 04:59:20 +00:00

326 lines
11 KiB
Groff
Raw Blame History

.\" Copyright (c) 1997, 1998, 1999
.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by Bill Paul.
.\" 4. Neither the name of the author nor the names of any co-contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
.\" THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $FreeBSD$
.\" $OpenBSD: wi.4tbl,v 1.14 2002/04/29 19:53:50 jsyn Exp $
.\"
.Dd May 2, 2002
.Dt WI 4
.Os
.Sh NAME
.Nm wi
.Nd WaveLAN/IEEE, PRISM-II and Spectrum24 802.11DS wireless network driver
.Sh SYNOPSIS
.Cd "device wi"
.Sh DESCRIPTION
The
.Nm
driver provides support for wireless network adapters based around
the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, and Symbol
Spectrum24 chipsets.
All four chipsets provide a similar interface to the driver.
.Pp
All host/device interaction is via programmed I/O.
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-II and PRISM-2.5 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.
PRISM-II and PRISM-2.5 chips do not support the WDS functionality.
.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 fixed, 2Mbps fixed, 2Mbps
with auto fallback, 5.5Mbps, 8Mbps, or 11Mbps depending on your hardware.
The Lucent WaveLAN/IEEE Silver and Gold cards as well as the Intersil
and Symbol cards have support for WEP encryption.
The WaveLAN Gold as well as newer Intersil and Symbol cards support
104bit keys, the others only accept 40bit keys.
The Lucent WaveLAN/IEEE Bronze cards do not support WEP at all.
To enable encryption, use the
.Xr wicontrol 8
utility to set your keys, or 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).
.Pp
The
.Nm
driver also supports an point-to-point mode where the ssid is
ignored and 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 based on the Intersil PRISM-II and PRISM-2.5 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
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
Cards supported by the
.Nm
driver come in a variety of packages, though the most common
are of the PCMCIA type.
In many cases, the PCI version of a wireless card is simply
a PCMCIA card bundled with a PCI adapter.
The PCI adapters come in two flavors: true PCMCIA bridges and
dumb PCMCIA bridges.
A true PCMCIA bridge (such as those sold by Lucent) will attach
as a real PCMCIA controller.
The wireless card will then attach to the PCMCIA bus.
Wireless cards in PCMCIA slots may be inserted and ejected on the fly.
.br
A dumb bridge, on the other hand, does not show up as a true PCMCIA bus.
The wireless card will simply appear to the host as a normal PCI
device and will not require any PCMCIA support.
Cards in this type of adapter should only be removed when the
machine is powered down.
.Pp
The following cards are among those supported by the
.Nm
driver:
.Pp
.in +\n(dIu
.TS
tab (:) ;
l l l
_ _ _
l l l .
Card:Chip:Bus
3Com AirConnect 3CRWE737A:Spectrum24:PCMCIA
3Com AirConnect 3CRWE777A:Prism-II:PCI
ACTIONTEC HWC01170:Prism-2.5:PCMCIA
Addtron AWP-100:Prism-II:PCMCIA
Agere Orinoco:Hermes:PCMCIA
Buffalo AirStation:Prism-II:PCMCIA
Buffalo AirStation:Prism-II:CF
Cabletron RoamAbout:Hermes:PCMCIA
Compaq Agency NC5004:Prism-II:PCMCIA
Contec FLEXLAN/FX-DS110-PCC:Prism-II:PCMCIA
Corega PCC-11:Prism-II:PCMCIA
Corega PCCA-11:Prism-II:PCMCIA
Corega PCCB-11:Prism-II:PCMCIA
Corega CGWLPCIA11:Prism-II:PCI
Dlink DWL520:Prism-2.5:PCI
Dlink DWL650:Prism-2.5:PCMCIA
ELSA XI300:Prism-II:PCMCIA
ELSA XI800:Prism-II:CF
EMTAC A2424i:Prism-II:PCMCIA
Ericsson Wireless LAN CARD C11:Spectrum24:PCMCIA
Gemtek WL-311:Prism-2.5:PCMCIA
Hawking Technology WE110P:Prism-2.5: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
Linksys Instant Wireless WPC11:Prism-II:PCMCIA
Linksys Instant Wireless WPC11 2.5:Prism-2.5:PCMCIA
Lucent WaveLAN:Hermes:PCMCIA
NANOSPEED ROOT-RZ2000:Prism-II:PCMCIA
NDC/Sohoware NCP130:Prism-II:PCI
NEC CMZ-RT-WP:Prism-II:PCMCIA
Netgear MA401:Prism-II:PCMCIA
NTT-ME 11Mbps Wireless LAN:Prism-II:PCMCIA
Proxim RangeLAN-DS:Prism-II:PCMCIA
Samsung MagicLAN SWL-2000N:Prism-II:PCMCIA
Socket Low Power WLAN-CF:Prism-II:CF
SMC 2602 EZ Connect (3.3V):Prism-II:PCI or PCMCIA
SMC 2632 EZ Connect:Prism-II:PCMCIA
Symbol Spectrum24:Spectrum24:PCMCIA
TDK LAK-CD011WL:Prism-II:PCMCIA
.TE
.in -\n(dIu
.Pp
Several vendors sell PCI adapters built around the PLX Technology 9050
or 9052 chip.
The following such adapters are supported or expected to work:
.Pp
.Bl -tag -width -compact
.It 3Com AirConnect 3CRWE777A (3.3V)
.It Belkin F5D6000 (a rebadged WL11000P)
.It Eumitcom WL11000P
.It Global Sun Technology GL24110P (untested)
.It Global Sun Technology GL24110P02
.It LinkSys WDT11 (a rebadged GL24110P02)
.It Netgear MA301
.It US Robotics 2415 (rebadged WL11000P)
.El
.Pp
.Sh EXAMPLES
The following examples utilize
.Xr ifconfig 8
for simplicity, however,
.Xr wicontrol 8
can also be used to set wireless parameters.
.Pp
Join an existing BSS network (ie: connect to an access point):
.Dl # ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00
.Pp
Join a specific BSS network with network name
.Dq my_net .
.Dl # ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net
.br
.Pp
Join a specific BSS network with WEP encryption:
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
wepkey 0x8736639624
.Ed
.Pp
Join a Lucent legacy demo ad-hoc network with network name
.Dq my_net .
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
mediaopt adhoc
.Ed
.Pp
Create an IBSS network with network name
.Dq my_net .
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
mediaopt ibss-master
.Ed
Note: The infrastructure for mediaopt ibss-master has not been
committed yet.
.Pp
Join an IBSS network with network name
.Dq my_net .
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e
mediaopt ibss
.Ed
Note: The infrastructure for mediaopt ibss has not been
committed yet.
.Pp
Create a host-based access point (Prism only):
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
mediaopt hostap
.Ed
.Pp
Create a host-based access point with WEP enabled (Prism only):
.Bd -literal -compact -offset indent
# ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
wepkey 0x1234567890 mediaopt hostap
.Ed
.Pp
Create a host-based wireless bridge to fxp0 (Prism only):
.Bd -literal -compact -offset indent
Add BRIDGE to the kernel config.
# ifconfig wi0 inet up ssid my_ap mediaopt hostap
# sysctl net.link.ether.bridge=1
# sysctl net.link.ether.bridge_cfg="wi0 fxp0"
# sysctl net.inet.ip.forwarding=1
.Ed
This will give you approximately the same functionality as an access
point.
.Sh DIAGNOSTICS
.Bl -diag
.It "wi%d: init failed"
The WaveLAN card failed to come ready after an initialization command
was issued.
.It "wi%d: failed to allocate %d bytes on NIC"
The driver was unable to allocate memory for transmit frames in the
NIC's on-board RAM.
.It "wi%d: device timeout"
The WaveLAN failed to generate an interrupt to acknowledge a transmit
command.
.El
.Sh SEE ALSO
.Xr an 4 ,
.Xr arp 4 ,
.Xr netintro 4 ,
.Xr ifmedia 4 ,
.Xr hostname.if 5 ,
.Xr ifconfig 8 ,
.Xr wicontrol 8
.Rs
.%T HCF Light programming specification
.%O http://www.wavelan.com
.Re
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 3.0 .
.Sh AUTHORS
The
.Nm
driver was written by Bill Paul <wpaul@ctr.columbia.edu>.
This man page comes from
.Ox .
.Sh CAVEATS
The original Lucent WaveLAN cards usually default to channel 3;
newer cards use channel 10 by default.
Non-Lucent cards vary, for instance the Addtron cards use channel
11 by default.
Different regulatory domains have different default channels.
See
.Xr wicontrol 8
for information on how to change the channel.
.Pp
IBSS creation does not currently work with Symbol cards.
.Pp
Prism2 host-based access point mode has bugs for firmware versions
prior to 0.8.3.
.Pp
Lucent cards prior to firmware version 6.0.4 do not support ibss
mode.
Reference in New Issue View Git Blame Copy Permalink