ray - Raytheon Raylink / WebGear Aviator IEEE 802.11FH 2Mbps
ray* at pcmcia? function ?
The ray device driver supports the Raytheon Raylink and Aviator 2.4/PRO
802.11 Frequency Hopping 2Mbps wireless PCMCIA cards. The
cards can be
operated in either adhoc or infrastructure modes. The operating mode is
selectable with ifconfig(8) through a media option.
Cards supported by the ray driver include:
WebGear Aviator 2.4
WebGear Aviator PRO
Raytheon Raylink WLAN
To communicate with other 802.11 cards a common network ID
or NWID must
be specified on each station that wishes to participate in
wireless network. The NWID can be set with ifconfig(8).
The device uses IEEE 802.11 standard Frequency Hopping
signaling and operates in the ranges of 2.400 to 2.4835 Gigahertz. This
frequency range is further restricted by country according
to that country's
regulations. Currently the ray driver defaults to using the ranges
appropriate for the USA. To change this setting you must
define the kernel
option RAY_PID_COUNTRY_CODE_DEFAULT to one of the following values:
RAY_PID_COUNTRY_CODE_USA [Toc] [Back]
The output power of the transceiver is 100mW and the card's
is 365 mA @ 5 volts. The transmission range in
open air (line
of sight) is a maximum of 1000 feet (or ~304 meters), and
with obstructions) it is a maximum of 500 feet (152 meters).
Windows drivers may use one of two framing modes for wireless packets,
"translation" and "encapsulation." "Encapsulation" is the
mode available when using some older Windows drivers.
Setting link0 flag on the interface allows the Ethernet2 in
framing method used by older Windows drivers
for the card.
For all other purposes, link0 should not be used, and
should be selected if you are given the option in a newer
ray0: card failed self test: status x Indicates the card
has failed its
initial startup tests.
awi(4), ifmedia(4), intro(4), pcmcia(4), hostname.if(5), ifconfig(8)
The ray device driver first appeared in NetBSD 1.5. OpenBSD
added in OpenBSD 2.7.
The ray driver was written by Christian E. Hopps
ported to OpenBSD by
Michael Shalayeff <firstname.lastname@example.org>. Support for interoperating with
newer Windows driver was added by
Steve Weiss <email@example.com>.
Currently the infrastructure mode is untested, and authentication using
WEP is unimplemented.
Firmware version 4 does not interop with version 5 or higher.
OpenBSD 3.6 January 24, 2000
[ Back ]