Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OpenBSD-5.7)
Apropos / Subsearch:
optional field

RUN(4)                   BSD Kernel Interfaces Manual                   RUN(4)

     run -- Ralink Technology USB IEEE 802.11a/b/g/n wireless network device

     run* at uhub? port ?

     The run driver supports USB 2.0 wireless adapters based on the Ralink
     RT2700U, RT2800U, RT3000U and RT3900E chipsets.

     The RT2700U chipset consists of two integrated chips, an RT2770 MAC/BBP
     and an RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio transceiver.

     The RT2800U chipset consists of two integrated chips, an RT2870 MAC/BBP
     and an RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio transceiver.

     The RT3000U is a single-chip solution based on an RT3070 MAC/BBP and an
     RT3020 (1T1R), RT3021 (1T2R), RT3022 (2T2R) or RT3052 (dual-band 2T2R)
     radio transceiver.

     The RT3900E is a single-chip solution based on an RT3593, RT5390, RT5392
     or an RT5592 MAC/BBP and an RT3053 (dual-band 3T3R), RT5370 (1T1R),
     RT5372 (2T2R), or RT5572 (dual-band 2T2R) radio transceiver.

     These are the modes the run driver can operate in:

     BSS mode       Also known as infrastructure mode, this is used when asso-
                    ciating with an access point, through which all traffic
                    passes.  This mode is the default.

     monitor mode   In this mode the driver is able to receive packets without
                    associating with an access point.  This disables the
                    internal receive filter and enables the card to capture
                    packets from networks which it wouldn't normally have
                    access to, or to scan for access points.

     The run driver can be configured to use Wired Equivalent Privacy (WEP) or
     Wi-Fi Protected Access (WPA-PSK and WPA2-PSK).  WPA is the current
     encryption standard for wireless networks.  It is strongly recommended
     that WEP not be used as the sole mechanism to secure wireless communica-
     tion, due to serious weaknesses in it.  The run driver offloads both
     encryption and decryption of data frames to the hardware for the WEP40,
     WEP104, TKIP(+MIC) and CCMP ciphers.

     The run driver can be configured at runtime with ifconfig(8) or on boot
     with hostname.if(5).

     The driver needs the following firmware files, which are loaded when an
     interface is brought up:


     The following adapters should work:

           Airlink101 AWLL6090
           ASUS USB-N11
           ASUS USB-N13 ver. A1
           ASUS USB-N53
           ASUS USB-N66
           ASUS WL-160N
           Belkin F5D8051 ver 3000
           Belkin F5D8053
           Belkin F5D8055
           Belkin F6D4050 ver 1
           Belkin F6D4050 ver 2
           Belkin F7D1101 ver 2
           Belkin F9L1103
           Buffalo WLI-UC-AG300N
           Buffalo WLI-UC-G300N
           Buffalo WLI-UC-G301N
           Buffalo WLI-UC-GN
           Buffalo WLI-UC-GNHP
           Buffalo WLI-UC-GNM
           Buffalo WLI-UC-GNM2
           Cisco AM10
           Corega CG-WLUSB2GNL
           Corega CG-WLUSB2GNR
           Corega CG-WLUSB300AGN
           Corega CG-WLUSB300GNM
           D-Link DWA-127
           D-Link DWA-130 rev B1
           D-Link DWA-140 rev B1, B2, B3, D1
           D-Link DWA-160 rev B2
           D-Link DWA-162
           DrayTek Vigor N61
           Edimax EW-7711UAn
           Edimax EW-7711USn
           Edimax EW-7711UTn
           Edimax EW-7717Un
           Edimax EW-7718Un
           Edimax EW-7722UTn
           Edimax EW-7733UnD
           Gigabyte GN-WB30N
           Gigabyte GN-WB31N
           Gigabyte GN-WB32L
           Hawking HWDN1
           Hawking HWUN1
           Hawking HWUN2
           Hercules HWNU-300
           Keebox W150NU
           Linksys AE1000
           Linksys WUSB54GC v3
           Linksys WUSB600N
           LogiLink WL0084B
           Logitec gLAN-W150NU2BK
           Logitec LAN-W150N/U2
           Logitec LAN-W300N/U2
           Logitec LAN-W300N/U2S
           Mvix Nubbin MS-811N
           Planex GW-USMicroN
           Planex GW-US300MiniS
           Sitecom WL-182
           Sitecom WL-188
           Sitecom WL-301
           Sitecom WL-302
           Sitecom WL-315
           Sitecom WLA-4000
           Sitecom WLA-5000
           SMC SMCWUSBS-N2
           Sweex LW153
           Sweex LW303
           Sweex LW313
           TP-LINK TL-WDN3200
           TP-LINK TL-WN727N v3
           TRENDnet TEW-645UB
           Unex DNUR-81
           Unex DNUR-82
           ZyXEL NWD-211AN
           ZyXEL NWD-271N
           ZyXEL NWD2105
           ZyXEL NWD210N
           ZyXEL NWD2205
           ZyXEL NWD270N
           ZyXEL NWD2705

     The following example scans for available networks:

           # ifconfig run0 scan

     The following hostname.if(5) example configures run0 to join network
     ``mynwid'', using WPA key ``mywpakey'', obtaining an IP address using

           nwid mynwid
           wpakey mywpakey

     run0: error N, could not read firmware ...  For some reason, the driver
     was unable to read the microcode file from the filesystem.  The file
     might be missing or corrupted.

     run0: could not load 8051 microcode  An error occurred while attempting
     to upload the microcode to the onboard 8051 microcontroller unit.

     run0: device timeout  A frame dispatched to the hardware for transmission
     did not complete in time.  The driver will reset the hardware.  This
     should not happen.

     arp(4), ifmedia(4), intro(4), netintro(4), usb(4), hostname.if(5),

     Ralink Technology:

     The run driver first appeared in OpenBSD 4.5.

     The run driver was written by Damien Bergamini

     The run driver does not support any of the 802.11n capabilities offered
     by the RT2800 and RT3000 chipsets.  Additional work is required in
     ieee80211(9) before those features can be supported.

BSD                            February 6, 2015                            BSD