1.\" $OpenBSD: run.4,v 1.22 2009/11/23 06:16:32 jmc 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.\" $FreeBSD$ 18.\" 19.Dd January 29, 2010 20.Os 21.Dt RUN 4 22.Sh NAME 23.Nm run 24.Nd Ralink Technology USB IEEE 802.11a/g/n wireless network device 25.Sh SYNOPSIS 26To compile this driver into the kernel, 27place the following lines in your 28kernel configuration file: 29.Bd -ragged -offset indent 30.Cd "device ehci" 31.Cd "device uhci" 32.Cd "device ohci" 33.Cd "device usb" 34.Cd "device run" 35.Cd "device wlan" 36.Cd "device wlan_amrr" 37.Ed 38.Pp 39Alternatively, to load the driver as a 40module at boot time, place the following line in 41.Xr loader.conf 5 : 42.Bd -literal -offset indent 43if_run_load="YES" 44.Ed 45.Sh DESCRIPTION 46The 47.Nm 48driver supports USB 2.0 wireless adapters based on the Ralink RT2700U, 49RT2800U and RT3000U chipsets. 50.Pp 51The RT2700U chipset consists of two integrated chips, an RT2770 MAC/BBP and 52an RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio transceiver. 53.Pp 54The RT2800U chipset consists of two integrated chips, an RT2870 MAC/BBP and 55an RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio transceiver. 56.Pp 57The RT3000U is a single-chip solution based on an RT3070 MAC/BBP and 58an RT3020 (1T1R), RT3021 (1T2R) or RT3022 (2T2R) single-band radio 59transceiver. 60.Pp 61These are the modes the 62.Nm 63driver can operate in: 64.Bl -tag -width "IBSS-masterXX" 65.It BSS mode 66Also known as 67.Em infrastructure 68mode, this is used when associating with an access point, through 69which all traffic passes. 70This mode is the default. 71.It monitor mode 72In this mode the driver is able to receive packets without 73associating with an access point. 74This disables the internal receive filter and enables the card to 75capture packets from networks which it wouldn't normally have access to, 76or to scan for access points. 77.El 78.Pp 79The 80.Nm 81driver can be configured to use 82Wired Equivalent Privacy (WEP) or 83Wi-Fi Protected Access (WPA-PSK and WPA2-PSK). 84WPA is the de facto encryption standard for wireless networks. 85It is strongly recommended that WEP 86not be used as the sole mechanism 87to secure wireless communication, 88due to serious weaknesses in it. 89The 90.Nm 91driver offloads both encryption and decryption of data frames to the 92hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers. 93.Pp 94The 95.Nm 96driver can be configured at runtime with 97.Xr ifconfig 8 98or on boot with 99.Xr hostname.if 5 . 100.Sh HARDWARE 101The following adapters should work: 102.Pp 103.Bl -tag -width Ds -offset indent -compact 104.It Airlink101 AWLL6090 105.It ASUS USB-N11 106.It ASUS USB-N13 107.It ASUS WL-160N 108.It Belkin F5D8051 ver 3000 109.It Belkin F5D8053 110.It Belkin F5D8055 111.It Belkin F6D4050 ver 1 112.It Buffalo WLI-UC-AG300N 113.It Buffalo WLI-UC-G300N 114.It Buffalo WLI-UC-GN 115.It Corega CG-WLUSB2GNL 116.It Corega CG-WLUSB2GNR 117.It Corega CG-WLUSB300AGN 118.It Corega CG-WLUSB300GNM 119.It D-Link DWA-130 rev B1 120.It D-Link DWA-140 121.It DrayTek Vigor N61 122.It Edimax EW-7711UAn 123.It Edimax EW-7711UTn 124.It Edimax EW-7717Un 125.It Edimax EW-7718Un 126.It Gigabyte GN-WB30N 127.It Gigabyte GN-WB31N 128.It Gigabyte GN-WB32L 129.It Hawking HWDN1 130.It Hawking HWUN1 131.It Hawking HWUN2 132.It Hercules HWNU-300 133.It Linksys WUSB54GC v3 134.It Linksys WUSB600N 135.It Mvix Nubbin MS-811N 136.It Planex GW-USMicroN 137.It Planex GW-US300MiniS 138.It Sitecom WL-182 139.It Sitecom WL-188 140.It Sitecom WL-301 141.It Sitecom WL-302 142.It Sitecom WL-315 143.It SMC SMCWUSBS-N2 144.It Sweex LW303 145.It Sweex LW313 146.It Unex DNUR-81 147.It Unex DNUR-82 148.It ZyXEL NWD210N 149.It ZyXEL NWD270N 150.El 151.Sh EXAMPLES 152Join an existing BSS network (i.e., connect to an access point): 153.Pp 154.Bd -literal -offset indent 155ifconfig wlan create wlandev run0 inet 192.168.0.20 \e 156 netmask 0xffffff00 157.Ed 158.Pp 159Join a specific BSS network with network name 160.Dq Li my_net : 161.Pp 162.Dl "ifconfig wlan create wlandev run0 ssid my_net up" 163.Pp 164Join a specific BSS network with 64-bit WEP encryption: 165.Bd -literal -offset indent 166ifconfig wlan create wlandev run0 ssid my_net \e 167 wepmode on wepkey 0x1234567890 weptxkey 1 up 168.Ed 169.Pp 170Join a specific BSS network with 128-bit WEP encryption: 171.Bd -literal -offset indent 172ifconfig wlan create wlandev run0 wlanmode adhoc ssid my_net \e 173 wepmode on wepkey 0x01020304050607080910111213 weptxkey 1 174.Ed 175.Sh DIAGNOSTICS 176.Bl -diag 177.It "run%d: error %d, could not read firmware %s" 178For some reason, the driver was unable to read the microcode file from the 179filesystem. 180The file might be missing or corrupted. 181.It "run%d: could not load 8051 microcode" 182An error occurred while attempting to upload the microcode to the onboard 8051 183microcontroller unit. 184.It "run%d: device timeout" 185A frame dispatched to the hardware for transmission did not complete in time. 186The driver will reset the hardware. 187This should not happen. 188.El 189.Sh SEE ALSO 190.Xr intro 4 , 191.Xr netintro 4 , 192.Xr usb 4 , 193.Xr wlan 4 , 194.Xr wlan_amrr 4 , 195.Xr wlan_ccmp 4 , 196.Xr wlan_tkip 4 , 197.Xr wlan_wep 4 , 198.Xr wlan_xauth 4 , 199.Xr ifconfig 8 , 200.Xr hostapd 8 , 201.Xr wpa_supplicant 8 . 202.Pp 203Ralink Technology: 204.Pa http://www.ralinktech.com/ 205.Sh HISTORY 206The 207.Nm 208driver first appeared in 209.Ox 4.5 . 210.Sh AUTHORS 211The 212.Nm 213driver was written by 214.An Damien Bergamini Aq damien@openbsd.org . 215.Sh CAVEATS 216The 217.Nm 218driver does not support any of the 802.11n capabilities offered by the 219RT2800 and RT3000 chipsets. 220