Realtek RTL8188SU/RTL8192SU USB IEEE
802.11b/g/n wireless network device
rsu* at uhub? port ?
rsu driver supports USB 2.0 wireless
network devices based on Realtek RTL8188SU, RTL8191SU and RTL8192SU
The RTL8188SU is a highly integrated 802.11n adapter that combines a MAC, a 1T1R capable baseband and an RF in a single chip. It operates in the 2GHz spectrum only.
The RTL8191SU is a highly integrated multiple-in, single-out (MISO) 802.11n adapter that combines a MAC, a 1T2R capable baseband and an RF in a single chip. It operates in the 2GHz spectrum only.
The RTL8192SU is a highly integrated multiple-in, multiple-out (MIMO) 802.11n adapter that combines a MAC, a 2T2R capable baseband and an RF in a single chip. It operates in the 2GHz spectrum only.
These are the modes the
rsu driver can
- BSS mode
- Also known as infrastructure mode, this is used when associating with an access point, through which all traffic passes. This mode is the default.
rsu 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.
rsu driver can be configured at
ifconfig(8) or on boot with
The driver needs at least version 1.1 of the following firmware file, which is loaded when an interface is attached:
A prepackaged version of the firmware can be installed using fw_update(1).
The following adapters should work:
- ASUS USB-N10
- ASUS WL-167G V3
- Belkin F7D1101 v1
- D-Link DWA-131 A1
- Hercules HWGUn-54
- Hercules HWNUm-300
- Planex GW-USNano
- Sitecom WL-349 v1
- Sitecom WL-353
- Sweex LW154
- TRENDnet TEW-648UB
- TRENDnet TEW-649UB
The following example scans for available networks:
# ifconfig rsu0 scan
The following hostname.if(5) example configures rsu0 to join network “mynwid”, using WPA key “mywpakey”, obtaining an IP address using DHCP:
nwid mynwid wpakey mywpakey dhcp
- rsu0: error N, could not read firmware ...
- For some reason, the driver was unable to read the microcode file from the filesystem. The file might be missing or corrupted.
- rsu0: device timeout
- A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware. This should not happen.
arp(4), ifmedia(4), intro(4), netintro(4), usb(4), hostname.if(5), ifconfig(8)
rsu driver first appeared in
rsu driver was written by
rsu driver does not support any of the
802.11n capabilities offered by the adapters. Additional work is required in
ieee80211(9) before those features can be supported.