- NetBSD Manual Pages
RUN(4) NetBSD Kernel Interfaces Manual RUN(4)
Powered by man-cgi (2020-09-24).
Maintained for NetBSD
by Kimmo Suominen.
Based on man-cgi by Panagiotis Christias.
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 and RT3000U 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)
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 de facto
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
The driver needs the following firmware files, which are loaded when an
interface is brought up:
The following adapters should work:
Belkin F5D8051 ver 3000
Belkin F6D4050 ver 1
Belkin F6D4050 ver 2
Belkin F7D1101 ver 2
D-Link DWA-130 rev B1
DrayTek Vigor N61
Linksys WUSB54GC v3
Mvix Nubbin MS-811N
The following ifconfig.if(5) example configures run0 to join whatever
network is available on boot, using WEP key ``0x1deadbeef1'', channel 11,
obtaining an IP address using DHCP:
dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11
Join an existing BSS network, ``my_net'':
# ifconfig run0 192.168.1.1 netmask 0xffffff00 nwid my_net
run%d: error %d, could not read firmware %s For some reason, the driver
was unable to read the microcode file from the filesystem. The file
might be missing or corrupted.
run%d: could not load 8051 microcode An error occurred while attempting
to upload the microcode to the onboard 8051 microcontroller unit.
run%d: device timeout A frame dispatched to the hardware for transmis-
sion did not complete in time. The driver will reset the hardware. This
should not happen.
arp(4), ifmedia(4), netintro(4), usb(4), ifconfig.if(5),
wpa_supplicant.conf(5), ifconfig(8), wpa_supplicant(8)
Ralink Technology: http://www.ralinktech.com/
The run driver first appeared in OpenBSD 4.5 and in NetBSD 7.0.
The run driver was written by Damien Bergamini <firstname.lastname@example.org> for
OpenBSD and ported to NetBSD by FUKAUMI Naoki.
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.
NetBSD 9.0 July 31, 2013 NetBSD 9.0