ray man page on MirBSD

Man page or keyword search:  
man Server   6113 pages
apropos Keyword Search (all sections)
Output format
MirBSD logo
[printable version]

RAY(4)			   BSD Programmer's Manual			RAY(4)

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

SYNOPSIS
     ray* at pcmcia? function ?
     option RAY_PID_COUNTRY_CODE_DEFAULT=RAY_PID_COUNTRY_CODE_USA

DESCRIPTION
     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
	   RAY_PID_COUNTRY_CODE_EUROPE
	   RAY_PID_COUNTRY_CODE_JAPAN
	   RAY_PID_COUNTRY_CODE_KOREA
	   RAY_PID_COUNTRY_CODE_SPAIN
	   RAY_PID_COUNTRY_CODE_FRANCE
	   RAY_PID_COUNTRY_CODE_ISRAEL
	   RAY_PID_COUNTRY_CODE_AUSTRALIA

     The output power of the transceiver is 100mW and the card's power con-
     sumption 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 "en-
     capsulation" framing method used by older Windows drivers for the card.
     For all other purposes, link0 should not be used, and "translation"
     should be selected if you are given the option in a newer Windows driver.

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

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

HISTORY
     The ray device driver first appeared in NetBSD 1.5. OpenBSD support was
     added in OpenBSD 2.7.
AUTHORS
     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
     Currently the infrastructure mode is untested, and authentication using
     WEP is unimplemented.

     Firmware version 4 does not interop with version 5 or higher.

MirOS BSD #10-current	       January 24, 2000				     1
[top]

List of man pages available for MirBSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net