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