[OpenBSD]

Manual Page Search Parameters

RAY(4) Device Drivers Manual RAY(4)

ray
Raytheon Raylink/WebGear Aviator IEEE 802.11FH wireless network device

ray* at pcmcia?
option RAY_PID_COUNTRY_CODE_DEFAULT=RAY_PID_COUNTRY_CODE_USA

The ray device driver supports the Raytheon Raylink and Aviator 2.4/PRO 802.11 Frequency Hopping 2Mbps wireless PCMCIA cards.
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, 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
These are the modes the ray driver can operate in:
 
 
BSS mode
Also known as infrastructure mode, this is used when associating with an access point, through which all traffic passes. This mode is the default.
 
 
IBSS mode
Also known as IEEE ad-hoc mode or peer-to-peer mode. This is the standardized method of operating without an access point. Stations associate with a service set. However, actual connections between stations are peer-to-peer.
The ray driver can be configured at runtime with ifconfig(8) or on boot with hostname.if(5).

Cards supported by the ray driver include:
Raytheon Raylink WLAN
 
WebGear Aviator 2.4
 
WebGear Aviator PRO
 

The following example scans for available networks:
# ifconfig ray0 scan
The following hostname.if(5) example configures ray0 to join network “mynwid”, obtaining an IP address using DHCP:
nwid mynwid 
dhcp

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

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

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

The ray driver was written by Christian E. Hopps <chopps@netbsd.org> and ported to OpenBSD by Michael Shalayeff <mickey@openbsd.org>.

Currently the infrastructure mode is untested, and authentication using WEP is unimplemented.
Firmware version 4 does not interop with version 5 or higher.
July 16, 2013 OpenBSD-5.4