xref: /openbsd-src/share/man/man4/run.4 (revision d13be5d47e4149db2549a9828e244d59dbc43f15)
1.\" $OpenBSD: run.4,v 1.33 2011/01/10 16:59:05 damien Exp $
2.\"
3.\" Copyright (c) 2008 Damien Bergamini <damien.bergamini@free.fr>
4.\"
5.\" Permission to use, copy, modify, and distribute this software for any
6.\" purpose with or without fee is hereby granted, provided that the above
7.\" copyright notice and this permission notice appear in all copies.
8.\"
9.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16.\"
17.Dd $Mdocdate: January 10 2011 $
18.Dt RUN 4
19.Os
20.Sh NAME
21.Nm run
22.Nd Ralink Technology USB IEEE 802.11a/g/n wireless network device
23.Sh SYNOPSIS
24.Cd "run* at uhub? port ?"
25.Sh DESCRIPTION
26The
27.Nm
28driver supports USB 2.0 wireless adapters based on the Ralink RT2700U,
29RT2800U and RT3000U chipsets.
30.Pp
31The RT2700U chipset consists of two integrated chips, an RT2770 MAC/BBP and
32an RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio transceiver.
33.Pp
34The RT2800U chipset consists of two integrated chips, an RT2870 MAC/BBP and
35an RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio transceiver.
36.Pp
37The RT3000U is a single-chip solution based on an RT3070 MAC/BBP and
38an RT3020 (1T1R), RT3021 (1T2R), RT3022 (2T2R) or RT3052 (dual-band 2T2R)
39radio transceiver.
40.Pp
41These are the modes the
42.Nm
43driver can operate in:
44.Bl -tag -width "IBSS-masterXX"
45.It BSS mode
46Also known as
47.Em infrastructure
48mode, this is used when associating with an access point, through
49which all traffic passes.
50This mode is the default.
51.It monitor mode
52In this mode the driver is able to receive packets without
53associating with an access point.
54This disables the internal receive filter and enables the card to
55capture packets from networks which it wouldn't normally have access to,
56or to scan for access points.
57.El
58.Pp
59The
60.Nm
61driver can be configured to use
62Wired Equivalent Privacy (WEP) or
63Wi-Fi Protected Access (WPA-PSK and WPA2-PSK).
64WPA is the de facto encryption standard for wireless networks.
65It is strongly recommended that WEP
66not be used as the sole mechanism
67to secure wireless communication,
68due to serious weaknesses in it.
69The
70.Nm
71driver offloads both encryption and decryption of data frames to the
72hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers.
73.Pp
74The
75.Nm
76driver can be configured at runtime with
77.Xr ifconfig 8
78or on boot with
79.Xr hostname.if 5 .
80.Sh FILES
81The driver needs the following firmware files,
82which are loaded when an interface is brought up:
83.Pp
84.Bl -tag -width Ds -offset indent -compact
85.It /etc/firmware/run-rt2870
86.It /etc/firmware/run-rt3071
87.El
88.Sh HARDWARE
89The following adapters should work:
90.Pp
91.Bl -tag -width Ds -offset indent -compact
92.It Airlink101 AWLL6090
93.It ASUS USB-N11
94.It ASUS USB-N13
95.It ASUS WL-160N
96.It Belkin F5D8051 ver 3000
97.It Belkin F5D8053
98.It Belkin F5D8055
99.It Belkin F6D4050 ver 1
100.It Belkin F6D4050 ver 2
101.It Buffalo WLI-UC-AG300N
102.It Buffalo WLI-UC-G300N
103.It Buffalo WLI-UC-GN
104.It Buffalo WLI-UC-GNHP
105.It Buffalo WLI-UC-GNM
106.It Corega CG-WLUSB2GNL
107.It Corega CG-WLUSB2GNR
108.It Corega CG-WLUSB300AGN
109.It Corega CG-WLUSB300GNM
110.It D-Link DWA-130 rev B1
111.It D-Link DWA-140
112.It DrayTek Vigor N61
113.It Edimax EW-7711UAn
114.It Edimax EW-7711UTn
115.It Edimax EW-7717Un
116.It Edimax EW-7718Un
117.It Gigabyte GN-WB30N
118.It Gigabyte GN-WB31N
119.It Gigabyte GN-WB32L
120.It Hawking HWDN1
121.It Hawking HWUN1
122.It Hawking HWUN2
123.It Hercules HWNU-300
124.It Linksys WUSB54GC v3
125.It Linksys WUSB600N
126.It Logitec gLAN-W150NU2BK
127.It Mvix Nubbin MS-811N
128.It Planex GW-USMicroN
129.It Planex GW-US300MiniS
130.It Sitecom WL-182
131.It Sitecom WL-188
132.It Sitecom WL-301
133.It Sitecom WL-302
134.It Sitecom WL-315
135.It SMC SMCWUSBS-N2
136.It Sweex LW153
137.It Sweex LW303
138.It Sweex LW313
139.It Unex DNUR-81
140.It Unex DNUR-82
141.It ZyXEL NWD210N
142.It ZyXEL NWD2205
143.It ZyXEL NWD270N
144.El
145.Sh EXAMPLES
146The following
147.Xr hostname.if 5
148example configures run0 to join whatever network is available on boot,
149using WEP key
150.Dq 0x1deadbeef1 ,
151channel 11, obtaining an IP address using DHCP:
152.Bd -literal -offset indent
153dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11
154.Ed
155.Pp
156Configure run0 to join network
157.Dq my_net
158using WPA with passphrase
159.Dq my_passphrase :
160.Bd -literal -offset indent
161# ifconfig run0 nwid my_net wpakey my_passphrase
162.Ed
163.Pp
164Join an existing BSS network,
165.Dq my_net :
166.Bd -literal -offset indent
167# ifconfig run0 192.168.1.1 netmask 0xffffff00 nwid my_net
168.Ed
169.Sh DIAGNOSTICS
170.Bl -diag
171.It "run%d: error %d, could not read firmware %s"
172For some reason, the driver was unable to read the microcode file from the
173filesystem.
174The file might be missing or corrupted.
175.It "run%d: could not load 8051 microcode"
176An error occurred while attempting to upload the microcode to the onboard 8051
177microcontroller unit.
178.It "run%d: device timeout"
179A frame dispatched to the hardware for transmission did not complete in time.
180The driver will reset the hardware.
181This should not happen.
182.El
183.Sh SEE ALSO
184.Xr arp 4 ,
185.Xr ifmedia 4 ,
186.Xr intro 4 ,
187.Xr netintro 4 ,
188.Xr usb 4 ,
189.Xr hostname.if 5 ,
190.Xr ifconfig 8
191.Pp
192Ralink Technology:
193.Pa http://www.ralinktech.com/
194.Sh HISTORY
195The
196.Nm
197driver first appeared in
198.Ox 4.5 .
199.Sh AUTHORS
200The
201.Nm
202driver was written by
203.An Damien Bergamini Aq damien@openbsd.org .
204.Sh CAVEATS
205The
206.Nm
207driver does not support any of the 802.11n capabilities offered by the
208RT2800 and RT3000 chipsets.
209Additional work is required in
210.Xr ieee80211 9
211before those features can be supported.
212