summaryrefslogtreecommitdiff
path: root/share/man/man4/ray.4
blob: 0c8a029e28e15ec48496ed60302e1be2d004bb0c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
.\"	$OpenBSD: ray.4,v 1.14 2004/11/09 22:01:59 jmc Exp $
.\"	$NetBSD: ray.4,v 1.5 2000/02/28 13:54:55 enami Exp $
.\"
.\" Copyright (c) 2000 Christian E. Hopps
.\" 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. The name of the author may not be used to endorse or promote products
.\"    derived from this software without specific prior written permission
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 THE AUTHOR 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.
.\"
.Dd January 24, 2000
.Dt RAY 4
.Os
.Sh NAME
.Nm ray
.Nd Raytheon Raylink/WebGear Aviator IEEE 802.11FH 2Mbps wireless
network adapter
.Sh SYNOPSIS
.Cd "ray* at pcmcia?"
.Cd "option RAY_PID_COUNTRY_CODE_DEFAULT=RAY_PID_COUNTRY_CODE_USA"
.Sh DESCRIPTION
The
.Nm
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
.Xr ifconfig 8
through a media option.
.Pp
Cards supported by the
.Nm
driver include:
.Pp
.Bl -item -offset indent -compact
.It
WebGear Aviator 2.4
.It
WebGear Aviator PRO
.It
Raytheon Raylink WLAN
.El
.Pp
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
.Xr ifconfig 8 .
.Pp
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
.Nm
driver defaults to using the ranges appropriate for the USA.
To change this setting you must define the kernel option
.Dv RAY_PID_COUNTRY_CODE_DEFAULT
to one of the following values:
.Pp
.Bl -item -offset indent -compact
.It
.Cd RAY_PID_COUNTRY_CODE_USA
.It
.Cd RAY_PID_COUNTRY_CODE_EUROPE
.It
.Cd RAY_PID_COUNTRY_CODE_JAPAN
.It
.Cd RAY_PID_COUNTRY_CODE_KOREA
.It
.Cd RAY_PID_COUNTRY_CODE_SPAIN
.It
.Cd RAY_PID_COUNTRY_CODE_FRANCE
.It
.Cd RAY_PID_COUNTRY_CODE_ISRAEL
.It
.Cd RAY_PID_COUNTRY_CODE_AUSTRALIA
.El
.Pp
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).
.Pp
.Tn 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
.Tn Windows
drivers.
.Pp
Setting
.Em link0
flag on the interface allows the
Ethernet2 in 802.11 "encapsulation" framing method used by
older
.Tn 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
.Tn Windows
driver.
.Sh DIAGNOSTICS
.Bl -diag
.It "ray0: card failed self test: status x"
Indicates the card has failed its initial startup tests.
.El
.Sh SEE ALSO
.Xr ifmedia 4 ,
.Xr intro 4 ,
.Xr pcmcia 4 ,
.Xr hostname.if 5 ,
.Xr ifconfig 8
.Sh HISTORY
The
.Nm
device driver first appeared in
.Nx 1.5 .
.Ox
support was added in
.Ox 2.7 .
.Sh AUTHORS
The
.Nm
driver was written by
.An Christian E. Hopps Aq chopps@netbsd.org
and ported to
.Ox
by
.An Michael Shalayeff Aq mickey@openbsd.org .
Support for interoperating with newer
.Tn Windows
driver was added by
.An Steve Weiss Aq srw@alum.mit.edu .
.Sh BUGS
Currently the infrastructure mode is untested, and authentication
using WEP is unimplemented.
.Pp
Firmware version 4 does not interop with version 5 or higher.