RUN(4) BSD Kernel Interfaces Manual RUN(4)NAMErun — Ralink Technology USB IEEE 802.11a/g/n wireless network device
To compile this driver into the kernel, place the following lines in your
kernel configuration file:
Firmware is also needed, and provided by:
Alternatively, to load the driver as a module at boot time, place the
following lines in loader.conf(5):
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) or RT3022 (2T2R) single-band radio trans‐
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.
Host AP mode In this mode the driver acts as an access point (base sta‐
tion) for other cards.
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).
The run driver supports the following wireless adapters:
Belkin F5D8051 ver 3000
Belkin F6D4050 ver 1
D-Link DWA-130 rev B1
DrayTek Vigor N61
Linksys WUSB54GC v3
Mvix Nubbin MS-811N
Join an existing BSS network (i.e., connect to an access point):
ifconfig wlan create wlandev run0 inet 192.168.0.20 \
Join a specific BSS network with network name “my_net”:
ifconfig wlan create wlandev run0 ssid my_net up
Join a specific BSS network with 64-bit WEP encryption:
ifconfig wlan create wlandev run0 ssid my_net \
wepmode on wepkey 0x1234567890 weptxkey 1 up
Join a specific BSS network with 128-bit WEP encryption:
ifconfig wlan create wlandev run0 wlanmode adhoc ssid my_net \
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
run%d: faild load firmware of file runfw 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.
SEE ALSOrunfw(4), intro(4), netintro(4), usb(4), wlan(4), wlan_amrr(4),
wlan_ccmp(4), wlan_tkip(4), wlan_wep(4), wlan_xauth(4), ifconfig(8),
Ralink Technology: http://www.ralinktech.com/
The run driver first appeared in OpenBSD 4.5.
The run driver was written by Damien Bergamini ⟨email@example.com⟩.
The run driver does not support any of the 802.11n capabilities offered
by the RT2800 and RT3000 chipsets.
BSD January 12, 2011 BSD