1.\" $OpenBSD: run.4,v 1.48 2016/06/16 17:25:32 martijn 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: June 16 2016 $ 18.Dt RUN 4 19.Os 20.Sh NAME 21.Nm run 22.Nd Ralink Technology/MediaTek USB IEEE 802.11a/b/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, RT3000U and RT3900E 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 41The RT3900E is a single-chip solution based on an RT3593, RT5390, 42RT5392 or an RT5592 MAC/BBP and an RT3053 (dual-band 3T3R), 43RT5370 (1T1R), RT5372 (2T2R), or RT5572 (dual-band 2T2R) 44radio transceiver. 45.Pp 46These are the modes the 47.Nm 48driver can operate in: 49.Bl -tag -width "IBSS-masterXX" 50.It BSS mode 51Also known as 52.Em infrastructure 53mode, this is used when associating with an access point, through 54which all traffic passes. 55This mode is the default. 56.It monitor mode 57In this mode the driver is able to receive packets without 58associating with an access point. 59This disables the internal receive filter and enables the card to 60capture packets from networks which it wouldn't normally have access to, 61or to scan for access points. 62.El 63.Pp 64The 65.Nm 66driver can be configured to use 67Wired Equivalent Privacy (WEP) or 68Wi-Fi Protected Access (WPA-PSK and WPA2-PSK). 69WPA is the current encryption standard for wireless networks. 70It is strongly recommended that WEP 71not be used as the sole mechanism 72to secure wireless communication, 73due to serious weaknesses in it. 74The 75.Nm 76driver offloads both encryption and decryption of data frames to the 77hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers. 78.Pp 79The 80.Nm 81driver can be configured at runtime with 82.Xr ifconfig 8 83or on boot with 84.Xr hostname.if 5 . 85.Sh FILES 86The driver needs the following firmware files, 87which are loaded when an interface is brought up: 88.Pp 89.Bl -tag -width Ds -offset indent -compact 90.It /etc/firmware/run-rt2870 91.It /etc/firmware/run-rt3071 92.El 93.Sh HARDWARE 94The following adapters should work: 95.Pp 96.Bl -tag -width Ds -offset indent -compact 97.It Airlink101 AWLL6090 98.It ASUS USB-N11 99.It ASUS USB-N13 ver. A1 100.It ASUS USB-N53 101.It ASUS USB-N66 102.It ASUS WL-160N 103.It Belkin F5D8051 ver 3000 104.It Belkin F5D8053 105.It Belkin F5D8055 106.It Belkin F6D4050 ver 1 107.It Belkin F6D4050 ver 2 108.It Belkin F7D1101 ver 2 109.It Belkin F9L1103 110.It Buffalo WLI-UC-AG300N 111.It Buffalo WLI-UC-G300N 112.It Buffalo WLI-UC-G301N 113.It Buffalo WLI-UC-GN 114.It Buffalo WLI-UC-GNHP 115.It Buffalo WLI-UC-GNM 116.It Buffalo WLI-UC-GNM2 117.It Cisco AM10 118.It Corega CG-WLUSB2GNL 119.It Corega CG-WLUSB2GNR 120.It Corega CG-WLUSB300AGN 121.It Corega CG-WLUSB300GNM 122.It D-Link DWA-127 123.It D-Link DWA-130 rev B1 124.It D-Link DWA-140 rev B1, B2, B3, \&D1 125.It D-Link DWA-160 rev B2 126.It D-Link DWA-162 127.It DrayTek Vigor N61 128.It Edimax EW-7711UAn 129.It Edimax EW-7711USn 130.It Edimax EW-7711UTn 131.It Edimax EW-7717Un 132.It Edimax EW-7718Un 133.It Edimax EW-7722UTn 134.It Edimax EW-7733UnD 135.It Gigabyte GN-WB30N 136.It Gigabyte GN-WB31N 137.It Gigabyte GN-WB32L 138.It Hawking HWDN1 139.It Hawking HWUN1 140.It Hawking HWUN2 141.It Hercules HWNU-300 142.It Keebox W150NU 143.It Linksys AE1000 144.It Linksys WUSB54GC v3 145.It Linksys WUSB600N 146.It LogiLink WL0084B 147.It Logitec gLAN-W150NU2BK 148.It Logitec LAN-W150N/U2 149.It Logitec LAN-W300N/U2 150.It Logitec LAN-W300N/U2S 151.It Mvix Nubbin MS-811N 152.It Planex GW-USMicroN 153.It Planex GW-US300MiniS 154.It Sitecom WL-182 155.It Sitecom WL-188 156.It Sitecom WL-301 157.It Sitecom WL-302 158.It Sitecom WL-315 159.It Sitecom WLA-4000 160.It Sitecom WLA-5000 161.It SMC SMCWUSBS-N2 162.It Sweex LW153 163.It Sweex LW303 164.It Sweex LW313 165.It TP-LINK TL-WDN3200 166.It TP-LINK TL-WN727N v3 167.It TRENDnet TEW-645UB 168.It Unex DNUR-81 169.It Unex DNUR-82 170.It ZyXEL NWD-211AN 171.It ZyXEL NWD-271N 172.It ZyXEL NWD2105 173.It ZyXEL NWD210N 174.It ZyXEL NWD2205 175.It ZyXEL NWD270N 176.It ZyXEL NWD2705 177.El 178.Sh EXAMPLES 179The following example scans for available networks: 180.Pp 181.Dl # ifconfig run0 scan 182.Pp 183The following 184.Xr hostname.if 5 185example configures run0 to join network 186.Dq mynwid , 187using WPA key 188.Dq mywpakey , 189obtaining an IP address using DHCP: 190.Bd -literal -offset indent 191nwid mynwid 192wpakey mywpakey 193dhcp 194.Ed 195.Sh DIAGNOSTICS 196.Bl -diag 197.It "run0: error N, could not read firmware ..." 198For some reason, the driver was unable to read the microcode file from the 199filesystem. 200The file might be missing or corrupted. 201.It "run0: could not load 8051 microcode" 202An error occurred while attempting to upload the microcode to the onboard 8051 203microcontroller unit. 204.It "run0: device timeout" 205A frame dispatched to the hardware for transmission did not complete in time. 206The driver will reset the hardware. 207This should not happen. 208.El 209.Sh SEE ALSO 210.Xr arp 4 , 211.Xr ifmedia 4 , 212.Xr intro 4 , 213.Xr netintro 4 , 214.Xr usb 4 , 215.Xr hostname.if 5 , 216.Xr ifconfig 8 217.Sh HISTORY 218The 219.Nm 220driver first appeared in 221.Ox 4.5 . 222.Sh AUTHORS 223The 224.Nm 225driver was written by 226.An Damien Bergamini Aq Mt damien.bergamini@free.fr . 227.Sh CAVEATS 228The 229.Nm 230driver does not support any of the 802.11n capabilities offered by the 231RT2800 and RT3000 chipsets. 232Additional work is required in 233.Xr ieee80211 9 234before those features can be supported. 235