|RUM(4)||Device Drivers Manual||RUM(4)|
rum — Ralink
Technology/MediaTek USB IEEE 802.11a/b/g wireless network device
rum* at uhub? port ?
rum driver supports USB 2.0 and PCI
Express Mini Card wireless adapters based on the Ralink RT2501USB and
Ralink PCI Express Mini Card adapters show up as normal USB 2.0
devices and are thus handled by the
The RT2501USB chipset is the second generation of 802.11a/b/g adapters from Ralink. It consists of two integrated chips, an RT2571W MAC/BBP and an RT2528 or RT5226 radio transceiver.
The RT2601USB chipset consists of two integrated chips, an RT2671 MAC/BBP and an RT2527 or RT5225 radio transceiver. This chipset uses the MIMO (multiple-input multiple-output) technology with multiple antennas to extend the operating range of the adapter and to achieve higher throughput.
These are the modes the
rum driver can
rum 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 communication, due to serious weaknesses in it. The
rum driver relies on the software 802.11 stack for
both encryption and decryption of data frames.
The following firmware file is loaded when an interface is brought up:
The following adapters should work:
The following example scans for available networks:
# ifconfig rum0 scan
The following hostname.if(5) example configures rum0 to join network “mynwid”, using WPA key “mywpakey”, obtaining an IP address using DHCP:
nwid mynwid wpakey mywpakey dhcp
The following hostname.if(5) example creates a host-based access point on boot:
mediaopt hostap nwid mynwid wpakey mywpakey inet 192.168.1.1 255.255.255.0
rum driver first appeared in
rum driver supports automatic control
of the transmit speed in BSS mode only. Therefore the use of a
rum adapter in Host AP mode is discouraged.
Host AP mode doesn't support power saving. Clients attempting to use power saving mode may experience significant packet loss (disabling power saving on the client will fix this).
|June 16, 2016||OpenBSD-6.1|