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.Dt RUN 4 21.Os 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 102.Nm 103driver supports the following wireless adapters: 104.Pp 105.Bl -tag -width Ds -offset indent -compact 106.It Airlink101 AWLL6090 107.It ASUS USB-N11 108.It ASUS USB-N13 109.It ASUS WL-160N 110.It Belkin F5D8051 ver 3000 111.It Belkin F5D8053 112.It Belkin F5D8055 113.It Belkin F6D4050 ver 1 114.It Buffalo WLI-UC-AG300N 115.It Buffalo WLI-UC-G300N 116.It Buffalo WLI-UC-GN 117.It Corega CG-WLUSB2GNL 118.It Corega CG-WLUSB2GNR 119.It Corega CG-WLUSB300AGN 120.It Corega CG-WLUSB300GNM 121.It D-Link DWA-130 rev B1 122.It D-Link DWA-140 123.It DrayTek Vigor N61 124.It Edimax EW-7711UAn 125.It Edimax EW-7711UTn 126.It Edimax EW-7717Un 127.It Edimax EW-7718Un 128.It Gigabyte GN-WB30N 129.It Gigabyte GN-WB31N 130.It Gigabyte GN-WB32L 131.It Hawking HWDN1 132.It Hawking HWUN1 133.It Hawking HWUN2 134.It Hercules HWNU-300 135.It Linksys WUSB54GC v3 136.It Linksys WUSB600N 137.It Mvix Nubbin MS-811N 138.It Planex GW-USMicroN 139.It Planex GW-US300MiniS 140.It Sitecom WL-182 141.It Sitecom WL-188 142.It Sitecom WL-301 143.It Sitecom WL-302 144.It Sitecom WL-315 145.It SMC SMCWUSBS-N2 146.It Sweex LW303 147.It Sweex LW313 148.It Unex DNUR-81 149.It Unex DNUR-82 150.It ZyXEL NWD210N 151.It ZyXEL NWD270N 152.El 153.Sh EXAMPLES 154Join an existing BSS network (i.e., connect to an access point): 155.Pp 156.Bd -literal -offset indent 157ifconfig wlan create wlandev run0 inet 192.168.0.20 \e 158 netmask 0xffffff00 159.Ed 160.Pp 161Join a specific BSS network with network name 162.Dq Li my_net : 163.Pp 164.Dl "ifconfig wlan create wlandev run0 ssid my_net up" 165.Pp 166Join a specific BSS network with 64-bit WEP encryption: 167.Bd -literal -offset indent 168ifconfig wlan create wlandev run0 ssid my_net \e 169 wepmode on wepkey 0x1234567890 weptxkey 1 up 170.Ed 171.Pp 172Join a specific BSS network with 128-bit WEP encryption: 173.Bd -literal -offset indent 174ifconfig wlan create wlandev run0 wlanmode adhoc ssid my_net \e 175 wepmode on wepkey 0x01020304050607080910111213 weptxkey 1 176.Ed 177.Sh DIAGNOSTICS 178.Bl -diag 179.It "run%d: error %d, could not read firmware %s" 180For some reason, the driver was unable to read the microcode file from the 181filesystem. 182The file might be missing or corrupted. 183.It "run%d: could not load 8051 microcode" 184An error occurred while attempting to upload the microcode to the onboard 8051 185microcontroller unit. 186.It "run%d: device timeout" 187A frame dispatched to the hardware for transmission did not complete in time. 188The driver will reset the hardware. 189This should not happen. 190.El 191.Sh SEE ALSO 192.Xr intro 4 , 193.Xr netintro 4 , 194.Xr usb 4 , 195.Xr wlan 4 , 196.Xr wlan_amrr 4 , 197.Xr wlan_ccmp 4 , 198.Xr wlan_tkip 4 , 199.Xr wlan_wep 4 , 200.Xr wlan_xauth 4 , 201.Xr ifconfig 8 , 202.Xr hostapd 8 , 203.Xr wpa_supplicant 8 . 204.Pp 205Ralink Technology: 206.Pa http://www.ralinktech.com/ 207.Sh HISTORY 208The 209.Nm 210driver first appeared in 211.Ox 4.5 . 212.Sh AUTHORS 213The 214.Nm 215driver was written by 216.An Damien Bergamini Aq damien@openbsd.org . 217.Sh CAVEATS 218The 219.Nm 220driver does not support any of the 802.11n capabilities offered by the 221RT2800 and RT3000 chipsets. 222