|URAL(4)||Device Drivers Manual||URAL(4)|
ural — Ralink
Technology/MediaTek USB IEEE 802.11b/g wireless network device
ural* at uhub? port ?
ural driver supports USB 2.0 wireless
adapters based on the Ralink RT2500USB chipset.
The RT2500USB chipset is the first generation of 802.11b/g adapters from Ralink. It consists of two integrated chips, an RT2570 MAC/BBP and an RT2526 radio transceiver.
These are the modes the
ural driver can
ural driver can be configured to use
Wired Equivalent Privacy (WEP) or Wi-Fi Protected Access (WPA1 and WPA2).
WPA2 is the current encryption standard for wireless networks. It is
strongly recommended that neither WEP nor WPA1 are used as the sole
mechanism to secure wireless communication, due to serious weaknesses. WPA1
is disabled by default and may be enabled using the option
wpa1,wpa2". For standard WPA networks which use
pre-shared keys (PSK), keys are configured using the
wpakey" option. WPA-Enterprise networks
require use of the wpa_supplicant package. The
driver relies on the software 802.11 stack for both encryption and
decryption of data frames.
The transmit speed is user-selectable or can be adapted automatically by the driver depending on the number of hardware transmission retries.
The following adapters should work:
The following example scans for available networks:
# ifconfig ural0 scan
The following hostname.if(5) example configures ural0 to join network “mynwid”, using WPA key “mywpakey”, obtaining an IP address using DHCP:
nwid mynwid wpakey mywpakey inet autoconf
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
ural driver first appeared in
ural driver was written by
ural driver supports automatic control
of the transmit speed in BSS mode only. Therefore the use of an
ural 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).
|October 15, 2021||OpenBSD-current|