*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->OpenBSD man pages -> ray (4)              



NAME    [Toc]    [Back]

     ray - Raytheon Raylink / WebGear Aviator IEEE 802.11FH 2Mbps

SYNOPSIS    [Toc]    [Back]

     ray* at pcmcia? function ?

DESCRIPTION    [Toc]    [Back]

     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
the shared
     wireless network.  The NWID can be set with ifconfig(8).

     The  device  uses  IEEE  802.11  standard  Frequency Hopping
Spread Spectrum
     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
power consumption
 is 365 mA @ 5 volts.   The  transmission  range  in
open air (line
     of  sight)  is  a maximum of 1000 feet (or ~304 meters), and
indoors (i.e.,
     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
only framing
     mode available when using some older Windows drivers.

     Setting  link0 flag on the interface allows the Ethernet2 in
802.11 "encapsulation"
 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
Windows driver.

DIAGNOSTICS    [Toc]    [Back]

     ray0:  card  failed  self test: status x  Indicates the card
has failed its
     initial startup tests.

SEE ALSO    [Toc]    [Back]

     awi(4), ifmedia(4), intro(4), pcmcia(4), hostname.if(5), ifconfig(8)

HISTORY    [Toc]    [Back]

     The ray device driver first appeared in NetBSD 1.5.  OpenBSD
support was
     added in OpenBSD 2.7.

AUTHORS    [Toc]    [Back]

     The  ray  driver  was  written   by   Christian   E.   Hopps
<chopps@netbsd.org> and
     ported to OpenBSD by
     Michael  Shalayeff <mickey@openbsd.org>.  Support for interoperating with
     newer Windows driver was added by
     Steve Weiss <srw@alum.mit.edu>.

BUGS    [Toc]    [Back]

     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 ]
 Similar pages
Name OS Title
ray FreeBSD Raytheon Raylink/Webgear Aviator PCCard driver
raycontrol FreeBSD configure Raytheon Raylink/Webgear Aviator devices
awi OpenBSD BayStack 650 IEEE 802.11FH PCMCIA wireless network driver
if_awi FreeBSD AMD PCnetMobile IEEE 802.11 PCMCIA wireless network driver
awi FreeBSD AMD PCnetMobile IEEE 802.11 PCMCIA wireless network driver
wi OpenBSD WaveLAN/IEEE, PRISM 2-3 and Spectrum24 802.11DS wireless network driver
an OpenBSD Aironet Communications 4500/4800 IEEE 802.11DS wireless network adapter
imp IRIX driver for IMP wireless presentation mouse
atw OpenBSD ADMtek ADM8211 802.11 wireless network driver
wicontrol FreeBSD configure Lucent, Intersil, & Atheros wireless devices
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service