RUM(4)
π RUM(4) β the Kernel Interfaces Manual, but make it cute β¨
Okay bestie, gather 'round because we're about to talk about the rum driver β and no, it's not about your Friday night margaritas (though honestly, same energy). This is the Ralink Technology USB IEEE 802.11a/b/g wireless network driver and it's about to be your new hyperfixation. π
β¨ SYNOPSIS β¨
So like, if you wanna compile this driver into your kernel (main character move, honestly), you gotta put these lines in your kernel config file. No cap, copy them exactly:
device ehci
device uhci
device ohci
device usb
device rum
device wlan
device wlan_amrr
OR β and this is the lowkey easier way β you can load the driver as a module at boot time by putting this line in loader.conf(5):
if_rum_load="YES"
It's giving "I don't have time to rebuild my kernel" and honestly? Valid. π«Ά
πΈ DESCRIPTION πΈ
Okay so first things first: the rum driver supports USB 2.0 and PCI Express Mini Card wireless adapters based on the Ralink RT2501USB and RT2601USB chipsets. Obsessed.
Here's the tea on those Ralink PCI Express Mini Card adapters: they literally show up as normal USB 2.0 devices, so the rum driver handles them like it's NBD. πββοΈ
The RT2501USB chipset is the second generation of 802.11a/b/g adapters from Ralink. It's got two integrated chips β an RT2571W MAC/BBP and either an RT2528 or RT5226 radio transceiver. It's giving "iconic duo" energy. π
The RT2601USB chipset also has two integrated chips β an RT2671 MAC/BBP and either an RT2527 or RT5225 radio transceiver. But this one's special because it uses MIMO (multiple-input multiple-output) technology with multiple antennas to extend the operating range and achieve higher throughput. Literally slay. π₯
All chips have hardware support for WEP, AES-CCM, TKIP, and Michael cryptographic operations. Security? We love to see it. π
The rum driver supports station, adhoc, adhoc-demo, hostap, and monitor mode operation. But here's the catch bestie β only one virtual interface may be configured at any time. That's a hard limit, no cap. For more deets on configuring this device, check out ifconfig(8).
π¦ HARDWARE π¦
The rum driver supports USB 2.0 wireless adapters based on the Ralink RT2501USB and RT2601USB chipsets, including β and bestie, I'm about to list ALL of them so buckle up:
3Com Aolynk WUB320gβ USBAbocom WUG2700 Taβ USBAirlink101 AWLL5025β USBASUS WL-167g ver 2β USBBelkin F5D7050 ver 3β USBBelkin F5D9050 ver 3β USBBuffalo WLI-U2-SG54HPβ USBBuffalo WLI-U2-SG54HGβ USBBuffalo WLI-U2-G54HPβ USBBuffalo WLI-UC-Gβ USBCNet CWD-854 ver Fβ USBConceptronic C54RU ver 2β USBCorega CG-WLUSB2GOβ USBD-Link DWA-110β USBD-Link DWA-111β USBD-Link DWL-G122 rev C1β USBD-Link WUA-1340β USBDigitus DN-7003GRβ USBEdimax EW-7318USGβ USBGigabyte GN-WB01GSβ USBGigabyte GN-WI05GSβ USBHawking HWUG1β USBHawking HWU54DMβ USBHercules HWGUSB2-54-LBβ USBHercules HWGUSB2-54V2-APβ USBLevelOne WNC-0301USB v3β USBLinksys WUSB54G rev Cβ USBLinksys WUSB54GRβ USBPlanex GW-US54HPβ USBPlanex GW-US54Mini2β USBPlanex GW-USMMβ USBSenao NUB-3701β USBSitecom WL-113 ver 2β USBSitecom WL-172β USBSweex LW053β USBTP-LINK TL-WN321G v1/v2/v3β USB
If your adapter's on this list, you're literally golden. If not... well, bestie, iykyk. π
π EXAMPLES π
Okay so here's where it gets fun. These are the literal commands to get you connected. Exact vibes only β don't change a single character. β¨
Join an existing BSS network (i.e., connect to an access point):
ifconfig wlan create wlandev rum0 inet 192.0.2.20/24
Join a specific BSS network with network name my_net:
ifconfig wlan create wlandev rum0 ssid my_net up
Join a specific BSS network with 64-bit WEP encryption (the vintage vibes):
ifconfig wlan create wlandev rum0 ssid my_net \
wepmode on wepkey 0x1234567890 weptxkey 1 up
Join a specific BSS network with 128-bit WEP encryption (extra secure, extra iconic):
ifconfig wlan create wlandev rum0 wlanmode adhoc ssid my_net \
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
Not me copying these exactly because I refuse to be the reason your wifi doesn't work. π
π₯ DIAGNOSTICS π₯
If you see this message:
rum%d: could not load 8051 microcode
...that means an error occurred while attempting to upload the microcode to the onboard 8051 microcontroller unit. The driver will reset the hardware. But bestie β this should not happen. If it does, it's giving "something went horribly wrong" energy and you should probably pay attention. π
π SEE ALSO π
Like, literally go read these if you want the full picture:
intro(4)netintro(4)usb(4)wlan(4)wlan_amrr(4)wlan_ccmp(4)wlan_tkip(4)wlan_wep(4)wlan_xauth(4)networking(7)hostapd(8)ifconfig(8)wpa_supplicant(8)
No skips, bestie. This is your syllabus. π
β HISTORY β
The rum driver first appeared in OpenBSD 4.0 and FreeBSD 7.0. It's been around longer than some of us have been alive (no shade, just facts). π§
π AUTHORS π
The original rum driver was written by two absolute legends:
- Niall O'Higgins
<niallo@openbsd.org> - Damien Bergamini
<damien@openbsd.org>
We stan. π«Ά
Debian β November 10, 2024
Okay that's the whole page bestie, you're literally a rum expert now. Go forth and connect to all the networks. Slay. π
β¨πΈπ¦π
π¦ where this page comes from
- freebsd 14.5: base 14.5
- freebsd 15.1: base 15.1
- π the page's license: ISC
- Copyright (c) 2005-2007 Damien Bergamini <damien.bergamini@free.fr>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms